Software Engineer, Resource Automation

Stripe · South San Francisco, CA · Global Operations · listed October 22, 2026

The shape of it

Seniority
Mid level
Experience asked
2+ years
Where
Not stated
Stated pay
$156,800 – $235,200
Requirements listed
5
Length
361 words

In the posting’s own words

Additional benefits for this role may include: equity, company bonus or sales commissions/bonuses; 401(k) plan; medical, dental, and vision benefits; and wellness stipends. CA73

What it asks for · 5

  • Backend development in Go, including building production services and writing automated tests;
  • Distributed systems and microservices, and designing and implementing service APIs, including HTTP/REST or gRPC;
  • Deploying and operating services using common cloud primitives computing, networking, and storage in cloud environments including AWS, Azure, GCP, or OCI;
  • Containers and orchestration, including Docker and Kubernetes and operating containerized services in production; and
  • Observability and production troubleshooting, including using logs, metrics, and tracing to diagnose issues in Linux-based environments.

What the job covers

  • Design, implement, test, deploy, and maintain backend services that support internal infrastructure and microservice operations.
  • Develop automation and tooling that streamlines resource provisioning, deployments, and operational workflows for internal engineering teams.
  • Produce and review technical designs; evaluate tradeoffs across reliability, latency, throughput, resiliency, cost, and engineering velocity.
  • Improve service operability by implementing monitoring/alerting, participating in on-call support as applicable, performing root-cause analysis, and addressing recurring failure modes.
  • Uphold engineering standards through code reviews, documentation, testing practices, and iterative improvements to existing services and systems.

Tools and skills named

Cloud & infra
  • AWS
  • Azure
  • Distributed systems
  • Docker
  • GCP
  • Kubernetes
  • Linux
  • Microservices
  • Observability
Ways of working
  • Code review
  • On-call
  • Technical writing
  • Testing
Frameworks
  • gRPC
  • REST
Languages
  • Go

Words the posting leans on

  • services7×
  • engineering6×
  • production3×
  • backend2×
  • cloud2×
  • computer2×
  • design2×
  • experience2×
  • implementing2×
  • internal2×
  • microservice2×
  • operating2×
  • related2×
  • review2×
  • support2×
  • systems2×

Counted from the posting after the mission statement and the legal notices are set aside. The ones near the top are the ones a screener is looking for.

The posting, your resume, and the gaps between them. One click loads all three.

More open at Stripe

every open role at Stripe →

How this page was made

An automated read of a public job posting, fetched November 2, 2026 and last changed by Stripe on October 29, 2026. Every list above is pulled from the posting’s own sentences — nothing rewritten, nothing added, no judgment about the role or the company. Counts and seniority are read off the text by rule, so they can be wrong where the posting is unusual. The original is the only thing that binds. Openings close without warning; check the source before spending an evening on it.