TL;DR

Lead Member of Technical Staff (Cloud Platform): Responsible for the technical vision of the next-generation internal cloud platform, designing foundational blueprints, network topologies, and security standards. Focus on architecting enterprise multi-account cloud landing zones, ensuring high availability and automated failover, and advising internal application teams on secure and efficient cloud-native deployment.

Location: New York, NY; San Francisco, CA

Company

Salesforce is a company that builds and operates the highly available, active-active mission-critical infrastructure that powers Salesforce at scale.

What you will do

  • Architect the enterprise multi-account cloud landing zone, designing highly available, active-active multi-region architectures capable of automated, deterministic failover.
  • Architect global transit networks that enforce strict "Private-by-Default" segmentation and centralized egress inspection.
  • Establish the technical standards and security baselines that will be codified into reusable "Golden Modules" by the SRE team.
  • Act as the principal consultant for internal application teams, advising them on cloud-native application design, state replication, and platform onboarding.

Requirements

  • Bachelor's degree in Computer Science, Computer Engineering, Software Engineering or relevant work experience.
  • 8+ years of cloud infrastructure experience, with at least 3 years operating as a Lead Architect for enterprise-scale environments.
  • Expert-level knowledge of enterprise cloud architecture, including massive-scale multi-account strategies and centralized network transit.
  • Deep expertise in designing highly resilient, active-active distributed systems and stateless microservices architectures.
  • Strong programming/scripting skills and a deep appreciation for modern Infrastructure-as-Code (IaC) paradigms.

Culture & Benefits

  • Customer Focus: Treating internal developers as our primary customers and prioritizing their velocity and user experience.
  • Automation: Eradicating manual toil and "ticket-ops" via GitOps and AI-augmented workflows.
  • Security: Believing that security should be "shifted left" and built into the code, not bolted on as an afterthought.
  • SRE Mindset: Engineering for failure, prioritizing self-healing systems, and maintaining a 99.999% availability standard.
  • Observability: Relying on telemetry, centralized logging, and ChatOps to proactively identify and resolve issues.