- Workplace
- Remote
- Type
- Full-time
- Level
- Not stated
- Salary
- Not listed
Who we are
About Stripe
Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world's largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities. Our mission is to increase the GDP of the internet, and we have a staggering amount of work ahead. That means you have an unprecedented opportunity to put the global economy within everyone's reach while doing the most important work of your career.
About the team
The Revenue and Financial Automation (RFA) organization at Stripe is building a modern, revenue-focused, financial management platform for fast-growing, digital-native companies. Hundreds of thousands of businesses of all sizes and types use Stripe Billing to collect revenue for recurring and one-time payments across a variety of different pricing models—from selling SaaS subscriptions, to orchestrating multi-stage contracts, delivering Usage-Based Billing, and providing recovery and retention tools to prevent customer churn.
The Metronome Infrastructure team builds and operates the infrastructure that Metronome product teams use to help users model and run their businesses. We own cloud infrastructure, container orchestration, databases, observability, deployments, and developer productivity. Working closely with Stripe Infrastructure, we scale our systems to support Stripe Revenue Suite’s rapid growth and help engineers build and ship faster through integrations with Stripe’s infrastructure.
What you'll do
As a Software Engineer on the Metronome Infrastructure team, you’ll build and scale the core systems our product teams rely on. Your work could include expanding database, network, or container orchestration capacity, or integrating AI tooling into our production stack across cloud infrastructure, observability, and deployments. You’ll take on startup-level ownership while collaborating across teams and drawing on Stripe’s deep technical expertise in operating at global scale.
Responsibilities
- Design, build, and maintain distributed cloud infrastructure and platform services
- Work on scaling, automation, reliability, and observability of infrastructure services
- Operate your services, debug issues, and support customers
- Participate in roadmap planning and prioritization.
Who you are
We're looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply. The preferred qualifications are a bonus, not a requirement.
Minimum requirements
- 2+ years of experience in backend software development
- Ability to write high-quality code (in programming languages like Go, Java, C/C++, etc.)
- Hands-on experience contributing to or building large-scale distributed systems
- Strong collaboration skills, with the ability to work across work streams within your team and contribute to your peers' success
- Ability to thrive with a high level of autonomy and responsibility, with an entrepreneurial mindset
Preferred qualifications
- Familiarity with event-driven architectures
- Experience with subscription management, usage-based billing, or financial reporting systems
- Interest in financial infrastructure and how businesses manage their revenue operations
- Direct leadership and mentorship experience
JobsPing insights
Our own analysis of this role, based on every open job we track. Updated daily.
Salary benchmark
DevOps & Infrastructure roles · 69 posted USD salaries
This listing doesn’t publish a USD salary. Use this range as a starting point when you discuss pay. How to negotiate
How in-demand these skills are
Share of all open roles on JobsPing that ask for each skill
Stripe right now
- Open roles
- 775
- Remote
- 15%
- New this week
- 59
Skills they ask for most: SQL, Python, Ruby, Java.
How to stand out for this role
- Describe infrastructure by scale: services, traffic, regions, uptime targets you were responsible for.
- Name the IaC, CI/CD and observability tools you used in production, not just in tutorials.
- Bring an incident story: what broke, how you found it, and what you changed so it couldn’t recur.
- Mention cost savings you delivered; infrastructure teams are often measured on them.