Startups

Staff Software Engineer - Services Platform

Mercury · San Francisco, CA, New York, NY, Portland, OR, or Remote within Canada or United States · Remote

← All jobs
About Mercury

Everything you do with money. All in one place. Apply in 10 minutes for business banking that transforms how you operate. Backed by Sequoia, a16z and 500 Global.

About the role

We’re looking for a Staff Software Engineer - Services Platform to become a technical owner for Mercury’s services platform. Found on 1752vc Careers, the job board for startup and VC roles.

What they're looking for

  • 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
More about this 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 Staff Software Engineer - Services Platform 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...

Read the full posting on Mercury's site ↗

Engineering

Build your edge while you search

Free tools for founders and investors, plus VC Unfiltered, our take on startups, venture and the people who build them.