Senior Full Stack Engineer (BitGo Labs)

Join BitGo Labs, a corporate innovation lab focused on creating real, revenue-generating products in the crypto space. As a Senior Full Stack Engineer, you will be the engineering backbone of a product from its inception to its first customer. You will work in a small team alongside a senior PM, the Head of Labs, and BitGo's CEO. Your role will involve making architecture calls, building the entire product stack, using AI as a force multiplier, and shipping to real users. You will not have a ticket queue but will be given rails, a product thesis, and a deadline.

• Architect and build the entire product, from frontend to backend, ensuring it meets the specifications and is delivered within the tight timeline.
• Integrate BitGo's custody, wallet, stablecoin, and settlement rails where necessary, and utilize AI as a force multiplier in the development process.
• Ship the product to real users, instrument everything, and continue to iterate and improve based on user feedback.
• Someone genuinely full-stack, 5+ years deep. Modern web frontend, API and service design, data modeling, cloud deployment. You don't need to be world-class at every layer. You need to be dangerous at all of them
• Someone who ships over polishes. You know the difference between the corners you can cut and the ones that cut back. Security and money-handling are the ones that cut back
• Someone comfortable with crypto, or unafraid of getting there fast. You don't need protocol-level expertise. Wallets, stablecoins, and settlement will be APIs you consume. Curiosity is required, maximalism is not
• Someone who has made AI part of how they work. Not "I've tried Copilot." Your daily throughput would be visibly impossible without these tools, and you have strong opinions about where they fail
• Someone who has built a product from nothing. Startup, side project, or the first engineer on a true zero-to-one team. You've made the tradeoffs that only matter when there's no one else to make them
• Someone who can throw away their own code. When a product gets killed, the code goes with it. Take the learning, keep the reusable parts, start the next one without a mourning period