(Senior) DevOps Engineer

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 are DevOps Engineer #3. You join a Lead DevOps who has laid the groundwork - now you help scale it. You'll shape the infrastructure, automation, and reliability standards that let the entire engineering team ship faster and more safely. You own big projects and drive them autonomously. You'll build and operate the platform that everything runs on - AWS infrastructure, Kubernetes, CI/CD pipelines, observability, incident response, end to end. You work across engineering, security, and product to turn infrastructure into a competitive advantage. You design for failure, automate everything you can, and raise the bar for what production-grade means at a bank run by agents. Your First Six Months Months 1-2: You ramp up on the current infrastructure - how deployments work, where the rough edges are, what is automated and what is not. You pick up your first big project as an IC and start shipping. You pair with the Lead DevOps but operate independently from week one. Months 3-4: You ship your first big project - for example, PR environment deployments or multi-region infrastructure. You scope the next project on…