Software Engineer, Backend


About Bridge

We believe that much like data moved to the cloud, dollars (and many other financial assets) will move on-chain. As this transition occurs, stablecoins will become core financial infrastructure. However, the current tools supporting stablecoin development have meaningfully limited adoption and utility. At Bridge (), we want to change this by building infrastructure and tooling that is both easy to use, and regulated and compliant.
While we’re a seed stage startup, we are well funded and have plenty of runway. We have a very small team of people who have previously built financial infrastructure at some of the world’s leading companies (Coinbase, Stripe, Square, Brex, Upstart, DoorDash, Airbnb).

About the Role

As one of the earliest engineers at Bridge, you will ship software to build out our suite of API products. We’re an engineering and API-first company, and you will learn first-hand and contribute towards building highly reliable, performant, and mission critical infrastructure serving thousands of developers across the globe.
For this role, we’re seeking engineers who either already have expertise in building high quality backend systems, or have a strong desire to learn and master these domains.

Qualifications and Skills

While various backgrounds may fit this role, an ideal candidate has:
Experience building backend systems with SQL databases. Experience with frameworks such as Rails, Django, Express or equivalent is a bonus
An enlarged sense of ownership and the ability to lead and influence the design and direction of our products.
An ability to thrive in a fast paced environment
A growth mindset and a constant curiosity and fearlessness to dive into the unknown
An ability to write maintainable, well-tested, modular code, but also be pragmatic about moving fast
Excellent written and verbal communication skills, including the ability to write clear technical documentation
Experience with building API products a plus, but not required
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
) instead.