[Hiring] Staff Software Engineer - Services Platform @Mercury

Role Description

We’re looking for a Staff Infrastructure Engineer to become a technical owner for Mercury’s services platform.

• 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 and useful enough that teams actively want to adopt it.
• Find the highest-leverage gaps in our services ecosystem and ship pragmatic improvements instead of waiting for a perfect future architecture.
• Establish patterns that let Mercury support many more services without multiplying operational complexity at the same rate.
• Mentor engineers and shape infrastructure thinking beyond the systems you directly own.

Qualifications

• Have 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.
• Have experience building self-service observability or operational tooling for application engineers.
• Have strong opinions about platform design, paired with the judgment to know when not to build something.
• Think of internal platforms as products. Adoption, ergonomics, defaults, documentation, and escape hatches matter alongside technical architecture.
• Be able to gain alignment across teams with different goals and perspectives without requiring unanimity or creating unnecessary friction.
• Communicate technical tradeoffs clearly enough that engineers understand both the decision and the reasoning behind it.
• Enjoy 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 would be particularly useful.

Requirements

• Mercury’s infrastructure is evolving rapidly every day.
• The service ecosystem is large enough that these problems are real, but young enough that a great engineer can still shape the fundamentals.
• If you want to build the standards that make the next fifty services feel far less exciting to operate than the first ten, we’d love to talk.

Benefits

• The total rewards package at Mercury includes base salary, equity (stock options/RSUs), and benefits.
• Our salary and equity ranges are highly competitive within the SaaS and fintech industry and are updated regularly using the most reliable compensation survey data for our industry.
• New hire offers are made based on a candidate’s experience, expertise, geographic location, and internal pay equity relative to peers.
• Our target new hire base salary ranges for this role are the following:
• US employees (any location): $239,000 — $298,800 USD
• Canadian employees (any location): $225,900 — $282,400 USD