Software Engineer - Infrastructure

Mercury•San Francisco, NY

13h

About The Position

The Infrastructure team at Mercury is an enablement lever for the rest of the business, building scalable, secure and maintainable foundations for the rest of the org to build on top of. Infrastructure is currently building out more platform features to make it easier for agents and humans to deploy code. This means security by default, observable by default and easy to use and operate. We do all this while not compromising on speed, and ship to prod all day, every day, which is a testament to the strong foundations this team has built. We are looking for an engineer to join our team to help build out the “platform” even further! We maintain everything from networking to container orchestration, and work with product teams to enable any AWS needs they have. We want someone who is passionate about building maintainable systems, is obsessed with quality and making sure the sharp edges are filed off, and is extremely helpful when diving into problems with our product counterparts. This is a role for someone who likes going deep, shipping often, and leaving systems better than they found them. Someone who cares about quality without turning quality into bureaucracy. Someone who is just as happy debugging a strange Linux problem as they are helping a product engineer understand why their service behaves differently in production. Our infrastructure is built primarily on AWS, including systems like EC2, RDS, OpenSearch, ECS, and EKS. We like to use the right tool for the job and bias towards cloud native open source tooling. We use Terraform extensively to manage infrastructure as code, GitHub and GitHub Actions for version control and delivery, and Prometheus, Grafana, OpenSearch, and OpenTelemetry to understand what is happening in production. We’re also increasingly building agentic infrastructure: systems that let AI agents safely interact with our infrastructure, and frameworks that give both agents and the humans operating them the right guardrails. You do not need to arrive knowing every tool we use. We care more about strong fundamentals, curiosity, and the ability to go deep. As we gear up for the next stages of Mercury's growth, you will: Build our “Infrastructure Platform” to support the growing needs of the Engineering Organization Focus on building a platform that is AI friendly while still usable for engineers. We want our users to be humans and Agents Deliver key infrastructure projects, break-down complex initiatives, and define our infrastructure strategy through detailed RFCs and technical specifications. The Infrastructure team sits in an interesting place at Mercury: close enough to production that the details matter, and broad enough that a good abstraction can make hundreds of engineers faster. There is a lot left to build. If you like infrastructure that is secure by default, observable by default, pleasant to use, and designed for people who want to ship, we’d love to hear from you.

Requirements

2+ years of experience with AWS
A keen interest in cloud native open source technologies, and feel comfortable contributing code upstream to these technologies
Strong knowledge of low-level operating system foundations (linux, file systems, containers, etc)
Demonstrated ability in technical writing, with at least 2 years of experience creating detailed technical documentation, RFCs, and tech specs that clearly communicate complex ideas

Nice To Haves

Used to operating in regulated environments such as HITRUST or SOC2, ensuring compliance and security
2+ years of experience working in massive terraform environments, with many engineers contributing code in a scalable way
2+ years of experience writing code. We are building an Infrastructure Platform from scratch and there is plenty of code to write to support that
Extremely willing to learn and dive into hard problems!

Responsibilities

Build our “Infrastructure Platform” to support the growing needs of the Engineering Organization
Focus on building a platform that is AI friendly while still usable for engineers. We want our users to be humans and Agents
Deliver key infrastructure projects, break-down complex initiatives, and define our infrastructure strategy through detailed RFCs and technical specifications