Senior Full Stack Engineer

Who you are

• 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 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 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 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 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 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

What the job involves

• Most corporate innovation labs are where ideas go to be studied. Decks get made. Pilots get piloted. Nothing ever meets a customer
• We built Labs to be the opposite of that. We push out real, live, revenue-generating products, and every one has to clear the same two-part bar:
• A value proposition or economics only possible because of crypto. If a normal company could build it on normal rails, it fails the test. We only build things where owning the infrastructure is the unfair advantage
• Only buildable this fast because of AI. Three months from blank page to live product. Not a prototype, not a beta behind a waitlist. Live
• The first product is already out in the world, built and launched inside ninety days. More are coming. Some will become businesses. Some will be shut down on schedule, without ceremony, because the numbers said so. Both outcomes are the system working
• You'll be the engineering backbone of a product from its first commit to its first customer, working in a tiny team alongside a senior PM, the Head of Labs, and BitGo's CEO
• There is no separate frontend team, backend team, or infra team waiting to take tickets from you. You are the team. That's not a staffing gap. It's the design: one engineer who owns the whole stack moves faster than five who own slices of it, especially with AI doing the heavy lifting
• A cycle looks like this:
• Take a spec that's still warm and make the architecture calls that let it ship in ninety days. Choose boring technology on purpose. The innovation budget is spent on the product, not the stack
• Build the whole thing. Frontend, backend, data, deployment. Integrate BitGo's custody, wallet, stablecoin, and settlement rails where the product needs them, and third-party vendors where buying beats building
• Use AI as a force multiplier, not a party trick. The three-month clock only works if you're the kind of engineer who gets 5x output from these tools and knows exactly when not to trust them
• Ship to real users, instrument everything, and keep shipping. Launch day is the midpoint, not the finish line
• Then hand off, wind down, or double down. When a product graduates or dies, you start the next one with everything you learned
• You will not be handed a ticket queue. You'll be handed rails, a product thesis, and a deadline

Benefits

• Company-paid medical, dental, and vision plans
• Catered lunches, fresh snacks, and gourmet coffee
• Commuting made easy with company-paid Caltrain passes
• Competitive compensation, stock options, and 401k plan
• Top-end computer equipment to power your work
• Flexible vacation time
• Remote/hybrid friendly with physical location workspaces