About the company
Mercury's services ecosystem is transitioning as more of Mercury moves beyond its core Haskell monolith, with product teams increasingly building and operating independent services.
About the role
We're looking for a Staff Infrastructure Engineer to become a technical owner for Mercury's services platform. You'll help define the paved road for building and running services at Mercury. This is a deeply technical role, but the hardest problems won't be solved by writing code. You'll need excellent judgment about what is worth standardizing, what should stay flexible, how quickly we can move, and how to bring a large engineering organization along with you.
Responsibilities
- Define and build the platform Mercury engineers use to deploy, operate, and evolve services
- Own the strategy for service ecosystem at Mercury including identity, authentication, discovery and communication
- Work with product stakeholders and Release Engineering to create a paved deployment path with strong defaults for rollouts, rollbacks, configuration, secrets, and operational safety
- Help evolve Mercury's service runtime architecture, including our use of Kubernetes, while keeping existing services healthy through the transition
- Make observability self-service so product engineers can understand and debug their systems without routing every question through Infrastructure
- Partner closely with Release Engineering, Security, and product engineering teams to create infrastructure that is compliant with financial regulations
- Find the highest-leverage gaps in our services ecosystem and ship pragmatic improvements
- Establish patterns that let Mercury support many more services without multiplying operational complexity
- Mentor engineers and shape infrastructure thinking beyond the systems you directly own
Requirements
- Deep experience operating Kubernetes in production and strong instincts around deployment architecture, failure modes, and migrations
- Have designed or materially owned service-to-service authentication, workload identity, service discovery, service mesh, or related distributed-systems infrastructure
- Experience building self-service observability or operational tooling for application engineers
- Strong opinions about platform design, paired with the judgment to know when not to build something
- Think of internal platforms as products
- Ability to gain alignment across teams with different goals and perspectives
- Communicate technical tradeoffs clearly
- Experience building an internal developer platform or service infrastructure at a scaled engineering organization would be particularly useful
Conditions
- Location: San Francisco, CA, New York, NY, Portland, OR, or Remote within Canada or United States
- Total rewards package includes base salary, equity (stock options/RSUs), and benefits