GTMA Trust - Principal Full-Stack Software Engineer – PMTS

Salesforce•San Francisco, CA

2d•$197,300 - $344,700•Hybrid

About The Position

Join our dynamic team at Salesforce and make a real impact! GTMA Trust engineers keep Digital Wallet — the product that lets customers manage, budget, and track usage entitlements across their Salesforce investment — reliable at scale. This is a follow-the-sun team that doesn't just monitor and fix; it owns the operational, technical, and data-integrity backbone underneath a live billing/usage platform where mistakes have direct revenue and customer-trust consequences. As a PMTS, you set the technical direction for how the team protects that trust — architecture, tooling, governance, and the practices that let a small trust org support a much larger surface area.

Requirements

A related technical degree, or equivalent experience
8+ years of professional software development experience, with a track record of technical leadership beyond your own individual contributions
Deep knowledge of object oriented programming and expert-level experience with at least one object oriented programming language (Java, JavaScript, C++, C#, Ruby, Python)
Proven experience designing observability and monitoring strategy (e.g., New Relic, Splunk, Grafana) at a system or team level, beyond just consuming dashboards others built
High proficiency in at least one high-level programming language and web framework (NodeJS, Express, Hapi, etc.)
Proven understanding of web technologies, such as JavaScript, CSS, HTML5, XML, JSON, and/or Ajax
Validated understanding of database technologies such as SQL, PL/SQL, and relational database schema design, including at scale (data pipelines, large-scale reconciliation, schema correction)
Experience designing automated testing strategy and frameworks (Java, JUnit, JSUnit, Selenium) that other engineers build against
Demonstrated, hands-on proficiency with agentic coding tools (e.g., Claude Code, agent orchestration/agent teams) applied across the SDLC, including planning, validation, and review workflows, with the judgment to know when to trust automation and when human validation is non-negotiable
A strong communicator, experienced explaining complex technical concepts and driving alignment across designers, support, other engineers, and leadership
Passion for ensuring the customer has an exceptional experience using our products, and the judgment to prioritize systemic fixes over recurring firefighting
Curiosity about systems, and a demonstrated ability to root-cause deep, ambiguous, cross-system puzzles
You are motivated by helping other engineers succeed and grow. You proactively look for ways to remove toil, mentor others, and multiply the team's impact beyond your own hands-on work

Nice To Haves

Experience building and operating highly scalable, self-healing web applications and services
Experience designing and leading gated, phased production rollouts of automated systems (canary/pilot/full rollout)
Experience with Agile software development and test-driven development
Bachelor's degree in Computer Science or equivalent field, or equivalent depth of experience
Comfortable operating with significant autonomy and ambiguity, and driving cross-team consensus without formal authority
Track record of contributing reusable tools, skills, or plugins that raised the whole team's (or org's) baseline capability
Desire to drive problems to closure, including problems that require convincing other teams to act

Responsibilities

Own and drive resolution of the most complex, ambiguous, highest-impact production issues — spanning provisioning, billing/usage pipelines, and cross-org data reconciliation (data lake objects, usage/entitlement records tied to tenant billing, mismatches, tenant provisioning, sandbox-vs-prod attributions) — going beyond triage into systemic root cause and org-wide fixes.
Act as a technical gatekeeper and escalation authority for high-risk production changes: knowing when a "point fix" needs a real rollback path instead of repeat manual sign-off.
Set the technical direction for service health: define what "critical signal" means, design instrumentation/alerting/dashboard strategy, and drive Ops Review reporting that leadership and partner teams rely on.
Identify and lead multi-quarter structural fixes — including auto-detect-and-fix tooling that eliminates recurring manual interventions — rather than accumulating one-off patches.
Act as the technical anchor during major incidents and cross-team escalations (including revenue- or deal-critical customer situations), representing GTMA Trust on incident bridges and negotiating shared-issue closure with partner teams like Data360.
Build and maintain the team's institutional knowledge: root-cause catalogues, runbooks, and enablement docs that let any engineer — not just tenured ones — resolve recurring classes of issues correctly.
Partner at a peer level with product engineering's senior technical leadership, shaping roadmap and design decisions before they're finalized.
Be the primary technical voice and SME representing GTMA Trust to Product and partner engineering teams.
Define and evolve the team's development process, culture, and codebase standards.
Set the bar for the hybrid engineering model — quality and completeness of work, not just velocity.
Mentor and grow engineers in technologies, tools, processes, and career development.
Present designs and strategy to senior internal/external audiences, setting the standard for design review quality.
Define test strategy and automation frameworks that reflect real production risk, not checkbox coverage.
Participate in on-call rotation as an escalation point for the hardest real-time problems.
Lead adoption of AI-native and agentic engineering practices team-wide — owning concrete patterns like AI-assisted root-cause analysis on support requests/alerts before a human engages, building reusable skills/plugins, and reshaping workflows across the SDLC.
Coach the team progress along the AI proficiency journey, coaching orchestration-level use of agentic tools and identifying where automation can safely replace manual toil (e.g. approval triage, root-cause drafting, reconciliation queries).