Forward Deployed Engineer

Few people get to build a bank from scratch. Even fewer get to build one at a moment when banking itself is being reinvented. The dollar is the best product in the history of the world, with practically infinite global demand, but distribution is broken. Global clearing runs on legacy banks that are closed 115 days a year, built for humans and take two days to settle. Augustus is the update to the internet era. We received conditional approval from the OCC to charter America’s first stablecoin-native clearing bank that is always open, made for machines, at the speed of compute. We are a group of operators, unicorn early employees, ex-founders and people who walked away from degrees because they believe this is an industry and career defining opportunity. We're backed with $40M from Peter Thiel’s Valar Ventures, Creandum and founders of Ramp, Deel and Circle. We are regulated in Europe and live with Euro and Stablecoin clearing today. Now, we are building the US team from the ground up, while continuing to grow rapidly in Europe.

The Role You are the first Forward Deployed Engineer at Augustus and own the technical execution behind every Tier 1 account: building the integrations, scripts, and automations that get key merchants from signature to steady state. You make the technology work. When an Account Manager needs a merchant's webhook debugged, a custom integration scoped, or a one-off script to unblock a go-live, you ship it. You sit on the technical calls, read the logs, and turn each high-stakes integration into a building block of the system. The script you write to onboard one Tier 1 account becomes the flow that runs hands-off for the next ten. You work alongside Operations, Engineering, Product, and Revenue. The merchants are yours to drive technically; the system is yours to extend with every account you ship. Your First Six Months Month 1-2: You learn our API, our infrastructure, and our merchant base. You shadow live Tier 1 engagements, take ownership of your first accounts, and start writing the scripts that make repeated integration work disappear. Month 3-4: You're the technical engine on a full Tier 1 book. You debug API issues, walk merchant engineers through webhooks, own the integration side of the per-merchant go-live checklist, and drive accounts to full expansion. Every failure mode you hit becomes a ticket, a script, or an automation you push back into the system. Month 5-6: You're the model for how the FDE motion runs at Augustus. The flows you've automated for Tier 1 are now running hands-off for Tier 2. You've raised the bar on time-to-expansion, built the integration playbook the next FDE hires ramp on, and made the AM team faster on every account they touch. Who Will Thrive At Augustus We believe that throwing smart people with high agency at big problems produces the best outcomes. The people who succeed here share the following traits: Relentless: You can't leave something broken. You don't stop because it got hard or because no one is watching. Set The Bar: You're harder on yourself than anyone else would be. You don't need external accountability to care about quality. Shape The Game: You don't wait for a playbook and you don't need one. You walk into genuinely new territory and figure it out. You move before anyone asked you to. Systems First: You don't solve problems by adding people or effort. You build systems that make the problem smaller. Your first instinct is to automate, not to handle it manually. This role is for you if: You'd rather read a merchant's API logs than ask them what's wrong. The fastest path to a fix usually starts in the code. You can hold a customer call and a stack trace in the same hour without losing either. You see every one-off integration as an automation waiting to be written, and you write it. You see Customer Ops, Engineering, and Account Management as one team and know exactly where you sit in it: the technical engine that makes the integrations work and the system stronger with every account. You want to be the technical IC at a bank designed to run mostly without one - building the system from inside the highest-stakes accounts. This is not for you if: You want to own the customer relationship outright. The AM is the face of the merchant; you make their integration work. You need a mature onboarding playbook before you can move. Your first month, the playbook is what you're writing. You'd rather file a ticket at Engineering than open the codebase and propose the fix yourself. You think of customer-facing technical work as a step toward eventually managing a team. The path here is deeper ownership of harder integrations and more of the system, not bigger headcount. Hard