Engineering Fellowship

Job description

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 - there is infinite global demand. But International Fintechs and non-US banks are left with two unsatisfying options to access it: Either they build on legacy clearing banks that are slow and unreliable, or they interface with middleware providers that don’t move and hold the dollars directly, but themselves rely on underlying legacy banks. Augustus collapses this stack by combining two things: A real, national bank charter (in organization), and Marble, our proprietary core banking system, built around intelligence, made of code. 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 are backed with more than $200M from Peter Thiel's Valar Ventures, Tiger Global, Hummingbird, QED, Creandum, and the founders of Nubank, Ramp, Deel, Circle, Fluidstack, Fuse, and n8n. 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’re a Fellow at Augustus, deployed to special projects across engineering, product, and the wider company. You own a project end to end: understand the problem, decide how to approach it, build the solution, and get it into use. The work depends on where you can have the most impact. You could build background coding agents, create a frontend component library, or solve an operational problem with agents. The common thread is a meaningful problem, a clear outcome, and ownership of getting it done. You’ll work closely with the team your project sits in. They provide context, technical guidance, and direct feedback. You bring the drive to turn an open-ended problem into something that works. As you deliver, the scope and difficulty of your projects grow. Your First Months Get context quickly, ship early, and take on harder problems as you prove yourself. Month 1: Join a team, understand the problem, and take ownership of your first project. Talk to the people who will use what you build, agree on what success looks like, and ship an initial version. Months 2–3: Drive the project through to adoption. Work thr…