remote
Staff Software Engineer - Services Platform
Software Engineer
Staff-level platform/infrastructure engineer who owns Mercury's internal services platform: defining how product teams deploy, authenticate, discover, and observe independent services (largely around Kubernetes) as the company evolves beyond its core Haskell monolith. The work blends deep technical design with cross-team alignment, pragmatic delivery, and mentoring.
About the role
At its height, the Venetian Arsenal could produce ships at a speed that were mostly unmatched in its era. Its advantage was not simply that its craftspeople worked faster. Venice standardized the pieces around them. Parts, processes, and responsibilities became reusable enough that shipbuilding became stamp and repeat, not creating from scratch every time.
Mercury's services ecosystem is reaching a similar transition.
As more of Mercury moves beyond our core Haskell monolith, product teams are increasingly building and operating independent services. That gives teams more flexibility, but it also creates a new class of infrastructure problems. How should services authenticate to each other? How should they be discovered? What does a safe deployment look like? How does an engineer understand whether their service is healthy? And how do we answer those questions once, rather than asking every product team to build its own version?
We’re looking for a
Skills
authenticationcaddistributed systemsfintechhaskellkubernetesobservabilitysaas