Software Engineering SMTS

Salesforce•San Francisco, CA

1d•$148,500 - $246,000

About The Position

The Software Engineer, Member of Technical Staff (SMTS) role is part of the Advanced Cross-Region Continuity (ACRC) team within Salesforce's Core Infrastructure Engineering organization. ACRC is the engineering team responsible for building, automating, validating, and continuously hardening the workflows that ensure Salesforce can recover critical services across regions with defined RTO/RPO behavior. We are looking for a Software Engineer who is passionate about distributed systems, automation-first thinking, and making complex operational outcomes reliable and repeatable. You will join a team whose goal is workflow-as-code and continuous readiness validation — not manual run books.

Requirements

5+ years of software engineering experience in distributed systems, infrastructure automation, or platform reliability engineering.
Proven experience building workflow orchestration, automation pipelines, or control-plane systems at scale (e.g., site-switch automation, DR tooling, deployment orchestration).
Strong proficiency in at least one systems or backend language (Java, Go, Python, or equivalent) with experience building production-quality services.
Experience with observability tooling, telemetry design, and building operational dashboards that drive engineering decisions.

Nice To Haves

Familiarity with SDB, HBase, ZooKeeper, BookKeeper, or comparable distributed storage systems.
Experience with chaos engineering, fault injection, or large-scale resilience testing programs.
Prior work contributing to RTO/RPO programs, disaster recovery automation, or business continuity engineering for Tier-1 production services.
Understanding of multi-region cell architectures and cross-region dependency management.

Responsibilities

Design, build, and maintain cross-region continuity workflows and orchestration systems that automate site-switch and disaster recovery (DR) activation sequences for large-scale, mission-critical infrastructure.
Build validation frameworks and observability tooling (dashboards, telemetry, readiness signals) that answer "Are we ready right now?" — not just "Were we ready during the last review?"
Partner with service-owning teams (SDB Engine, LCM, Archival, SCRT2, HBase, VegaCache) to define cross-system continuity contracts, integration boundaries, and readiness standards.
Identify and retire manual steps through principled automation — documenting why each step exists, what can go wrong, and the signal that proves success.
Build software with operational excellence in mind — including clear runbooks, alerting, observability hooks, and deployment patterns that Site Reliability Engineering (SRE) and DevOps teams can own and operate with confidence.