Mercury
More roles at MercurySoftware Engineer - Infrastructure
Remote work allowed only within certain countries or regions.
Employer listed it 3 weeks ago · Added 2 months ago
Been open since 2 months ago. Long-running listings are sometimes left up after the role is filled.
Salary
$122,400 to $158,400
Location
Timezone
US East
Contract
Full-time
Experience
Mid
Category
Software
Stated by the employer in the job description
What the advert says
Quoted word for word from the employer's advert. Where it says nothing, we say so.
- Working hours
- Not mentioned in the advert
- Where you can work from
- Location eligibility not confirmed
- Contract
- Not mentioned in the advert
- Experience asked for
You have 2+ years of experience with AWS
- Pay
Total Rewards The total rewards package at Mercury includes base salary, equity (stock options/RSUs), and benefits.
Remote flexibility
Region Restricted
Remote work is allowed, but only for candidates based in United States, Canada.
What the employer says
- Source listing states candidate location: "San Francisco, CA, New York, NY, Portland, OR, or Remote within Canada or United States, Any Office or Remote"
What Nomaders makes of it
- Applications outside the listed area are usually rejected
- Timezone overlap with the listed area is often expected
The quotes above are the employer's own words; the reading is ours. Always check the original listing and employment terms before working from another country.
Before you apply
Experience: employer states
Written as a requirement
- “You have 2+ years of experience with AWS”
- “You have 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”
Questions worth asking: Nomaders interpretation
- The advert does not say where you can be based. Ask which countries they can legally employ or contract you from.
- The advert does not say whether this is employment or a contractor arrangement. Ask, as it affects tax and benefits.
Produced automatically from this advert's text; not reviewed by a person. The employer's own page is the final word.
About the role
The backbone of any technology org is its infrastructure, come join the team giving that skeleton superhuman abilities. The Infrastructure team at Mercury is an enablement lever for the rest of the business, building scaleable, 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.
Some of the technology you’ll work with
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
Must haves:
You have 2+ years of experience with AWS
You have 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)
You have 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
The ideal candidate should:
Be used to operating in regulated environments such as HITRUST or SOC2, ensuring compliance and security
Have 2+ years of experience working in massive terraform environments, with many engineers contributing code in a scalable way
Have 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
Be extremely willing to learn and dive into hard problems! We have many to solve!
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.
Requirements
- ·You have 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)
- ·You have 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
- ·The ideal candidate should:
- ·Be used to operating in regulated environments such as HITRUST or SOC2, ensuring compliance and security
Benefits
No benefits package published with this listing. Ask about it at first interview.
How to apply
- 1Check the flexibility label above, region restricted, matches where you plan to live and work.
- 2Tailor your CV to the role at Mercury, mentioning your remote working experience and working hours (US East).
- 3Apply directly on the employer's careers page using the button below. Nomaders never handles your application.
Found 2mo ago. Last checked 17 Nov. Always confirm the details on the original posting, salary and location can change after publication.
Listing sourced from Company boards.
Similar roles
Other open software roles with comparable remote rules.
$122,400 to $158,400 · You'll be taken to the employer's careers page.