SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Salary: USD 239,000 - 298,800 / annual
Mercury is a fintech platform providing banking, treasury, and financial workflow solutions for startups and technology companies. As the company scales beyond its core Haskell monolith, product teams are increasingly building and operating independent services. This creates new infrastructure challenges around service authentication, discovery, deployment safety, and observability.
You will serve as a technical owner for Mercury's services platform, defining the "paved road" for building and running services across the organization. This is a deeply technical role that requires excellent judgment about what to standardize, what to keep flexible, and how to bring a large engineering organization along with architectural decisions.
Key responsibilities include:
- Define and build the platform Mercury engineers use to deploy, operate, and evolve services
- Own the strategy for the service ecosystem, including identity, authentication, discovery, and communication patterns
- Work with product stakeholders and Release Engineering to create a paved deployment path with strong defaults for rollouts, rollbacks, configuration, secrets, and operational safety
- Evolve Mercury's service runtime architecture, including Kubernetes usage, while maintaining existing services through the transition
- Make observability self-service so product engineers can debug systems independently
- Partner with Release Engineering, Security, and product teams to ensure infrastructure is compliant with financial regulations and drives adoption
- Identify high-leverage gaps in the services ecosystem and ship pragmatic improvements
- Establish patterns that allow Mercury to support many more services without proportional increases in operational complexity
- Mentor engineers and shape infrastructure thinking across the organization
Requirements:
- Deep experience operating Kubernetes in production with strong instincts around deployment architecture, failure modes, and migrations
- 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 judgment about what not to build
- Think of internal platforms as products—adoption, ergonomics, defaults, documentation, and escape hatches matter alongside technical architecture
- Ability to gain alignment across teams with different goals without requiring unanimity
- Clear communication of technical tradeoffs so engineers understand both decisions and reasoning
- Comfort operating at the boundary between deep technical work and broad organizational leverage
- Experience building an internal developer platform or service infrastructure at a scaled engineering organization is particularly valuable, though the focus is on systems built, decisions made, and team adoption rather than company prestige
About Mercury
Fintech — banking, treasury, and financial workflow platform for startups and technology companies.
