Principal Software Engineer, PMTS
Job Description
Job Category
Software Engineering
Job Details
About Salesforce
Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets action. Tech meets trust. And innovation isn’t a buzzword — it’s a way of life. The world of work as we know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all.
Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce.
Salesforce is seeking a Principal Software Engineer (PMTS) to join the Agentforce Process Intelligence team, building process mining and optimization capabilities within the Agentforce platform. 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 Java and python application services.
Your Impact
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.
Set the long-term technical vision ( 2RR scope) for the Backend / Full-Stack pillar, including the evolution of Java-based application services (Spring Boot, Hibernate 6+, JPA) and companion microservices toward a pooled multi-tenant model with end-to-end tenant isolation.
Own the architecture for Python-based data processing services and ETL pipelines that feed large-scale data ingestion and transformation, ensuring contracts with the data platform layer are clean and forward-compatible.
Architect database consolidation and migration efforts using PostgreSQL, Liquibase, and connection pooling strategies, and validate the technical plans your teams produce against scalability, availability, and tenant-isolation requirements.
Drive integration with big data query and processing layers (distributed query engines, columnar storage formats) so analytical workloads route correctly and meet SLOs.
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.
