Software Engineering PMTS

Salesforce•Bellevue, WA

About The Position

Salesforce is seeking a Principal Software Engineer (PMTS) to join the Tableau Agent Analytics Agentforce Process Intelligence team. You will act as a technical leader across one or more teams, owning the end-to-end architecture of backend services and full-stack applications that enable enterprise customers to discover, simulate, and optimize their business processes at scale. This role sits at the intersection of large-scale distributed systems, data-intensive analytics, and cloud platform engineering. You will be a leading technical representative across the application stack — negotiating interfaces with peer teams, driving architectural alignment across the product, and setting the bar for non-functional quality (availability, multi-tenancy, security, performance) across GRPC and python application services.

Requirements

15+ years of professional software development experience, with a proven track record of shipping enterprise SaaS at scale and operating in a Principal-level technical leadership capacity.
Strong proficiency in Java and/or Python, with production-level fluency across multiple languages in real systems.
Hands-on experience designing, operating, and evolving highly available distributed systems on AWS or comparable cloud platforms, with 99.99%+ availability targets.
Demonstrated ability to drive proactive threat modeling and partner with security/compliance on AppSec, vulnerability management, and AI safety considerations for new features.
Hands-on experience with automated testing including unit, integration, and functional testing (JUnit, pytest, Selenium, Playwright), and a track record of defining test strategy for complex, cross-team systems.
Proven ability to lead technical initiatives across multiple teams, mentor LMTS/SMTS engineers, and drive architectural alignment across organizational boundaries.
Exceptional communication skills — including the ability to present technical strategy and trade-offs to VP-level engineering leadership, Product, and external customers.
A related technical degree required.

Nice To Haves

Familiarity with multi-tenant SaaS ecosystems and cloud platform engineering, including tenant-isolation patterns across database, cache, and storage layers.
Expertise in shaping experiences with LLMs and agents.
Proficient with evaluation of ML model performance.
Experience with Agile development methodologies, test-driven development (TDD), and zero-downtime deployment patterns (blue/green, rolling releases).
Prior experience as a Principal Engineer or similar leadership role, driving significant technical initiatives across multiple teams.
Familiarity with the business process management, process mining, or workflow automation domains.

Responsibilities

Drive the architecture, design, implementation, and delivery of secure, highly scalable backend services deployed on Kubernetes in a cellular, multi-AZ cloud architecture, and act as the technical leader for one or more teams.
Architect authentication and authorization integrations with identity providers (session-based auth, mTLS for service-to-service communication) and partner with Security on threat modeling, AppSec, and AI safety guardrails for new features.
Define SLIs and SLOs for the team's features and services in partnership with Product, design rollout strategy and telemetry that spans pre-release / canary / stagger periods, and lead service ownership: on-call rotations, ops and readiness reviews, runbooks, and automation.
Set test strategy across the pillar — unit, integration, functional, regression, and performance — and approve test plans for cross-team initiatives.
Write architectural documents, design specifications, and test plans for projects that span multiple teams; lead and participate in design reviews; and provide constructive feedback on peer teams' designs.
Provide technical coaching and mentorship to LMTS and SMTS engineers on the team and on peer teams, primarily through reviews; recognize which large designs to delegate and which to implement yourself.
Manage the technical backlog so that team goals and long-term technical debt are both addressed, and propose standards and best practices where they don't yet exist across the organization.
Represent the team to VP-level engineering leadership, Product, and external stakeholders — clearly and concisely explaining initiatives, high-level architectures, and trade-offs; act as a technical liaison for Customer Trust when needed.
Champion Customer Trust within the team: reinforce non-functional requirements, occasionally engage directly with customers to validate that features solve real problems, and lead critical problem management to limit customer impact.