Business Operations (Graduate)

Augustus•New York City, NY

5d•Hybrid

About The Position

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. As Business Operations at Augustus, you run one of the core operational domains of the bank day-to-day. Our operations are organized around customer workflows - customer operations, payment operations, fincrime operations - and each domain runs like a product team. You're in the queue: the cases, the reviews, the escalations. Your job is to make that queue disappear. We're building a dark bank, a bank that runs mostly autonomously, where operations are designed so the work doesn't emerge in the first place. Legacy banks scale operations with people. We build systems that make the work disappear. Every flow you automate correctly disappears for good. Every flow you patch with headcount compounds the wrong way. In most companies, operations means executing someone else's process. Here, the manual work is the raw material. Every case you run by hand teaches you - and the system - where the process breaks. You run the work, you document the failure modes, and you turn what you learn into the rules, flows, and agents that replace it. You report to your domain's Operations Lead. Scope grows as fast as you do.

Requirements

2-3 previous internships in high-growth startups, venture capital, or consulting and/or you have demonstrated initiative through side projects, student organizations, research, or entrepreneurial experiences.
Automated real work with AI tools - workflows you actually use, not experiments.
Based in New York or willing to relocate.
You close your own gaps.
You think the manual work is beneath you. Before anything gets automated here, someone smart has to do it by hand and understand it completely. That someone is you.
You need a training program. Nobody hands you a curriculum.

Nice To Haves

You'd rather have a steep slope than a safe title. Your scope here is set by what you prove, not by the org chart.
You measure progress by title and headcount. Success here looks like the queue you started in running without you. That's promotion material, not redundancy.
"Mostly autonomous operations" sounds like a marketing line to you. The dark bank thesis shapes every decision. Skepticism about it means rowing against the current daily.

Responsibilities

Run the cases yourself, log every place the process fights you, and become the person who knows your domain's day-to-day better than anyone in the building.
Automate your own work. Ship the rules and sub-flows that catch what you've been catching by hand.
Drive a measurable lift on the flows you've rebuilt.
Handle the knife-edge cases, and you're building the next wave.
Do the manual work first - and then make yourself obsolete.
Go deep into the weeds precisely so you can engineer your way out of them.
Reach for an agent before an escalation.
When the same case shows up twice, your first instinct is "what should have caught this?" - not "add it to the tracker."
Learn how a bank actually works from the inside. Payments, onboarding, monitoring - you'll touch the real workflows, not a sanitized version of them.
Turn your queue findings into specs for Engineering and Product, and help ship them.