Operations Lead

The Role
As Operations Lead at Augustus, you own one of the core operational domains of the bank end-to-end. Our operations are organized around customer workflows – customer operations, payment operations, fincrime operations – and each domain runs like a product team. The processes, the SOPs, the KPIs, the tooling, the automations, and the agents that run all of that – all yours.

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.

You design the system. You set the metrics that prove it works. You build the agents that run it. You work across Operations, Product, Engineering, and Compliance. You report to Joshua, our COO, and you’re trusted with every call from day one.

Your First Six Months
Months 1-2: Do the manual work yourself. Sit in the queue, run the cases, feel exactly where the process breaks. Take ownership of the domain as it exists today and define the KPIs that will tell you whether the system is working.

Months 3-4: Ship the first wave of automations. Prove the operating model on a live cohort. Drive a measurable lift with the flows you’ve rebuilt.

Months 5-6: Agents live across the domain. The long tail runs hands-off, humans handle only the highest-risk or knife-edge decisions. Scale the system – not the team.

This role is for you if:

You want to own an operating model, not inherit one. The SOPs, KPIs, escalation paths, tooling: you draft them, defend them, rewrite them when they break.

You’ve done the work you’d be automating. The best automations come from people who’ve felt where the process breaks – you go deep into the weeds precisely so you can engineer your way out of them.

You want to build alongside Engineering and Product, not file tickets at them. You’ll spec agents and shape tooling directly. If you’ve watched your best ideas die in someone else’s backlog, here you build them.

You want decisions that are actually yours. You own your domain end-to-end and answer for it to the COO directly. This suits someone who’s hit the ceiling of executing other people’s plans.

This is not for you if:

You measure your impact by the size of your team. Success here looks like volume multiplying while headcount stays flat. A growing org under you is the failure mode, not the goal.

You prefer a mature playbook to a blank page. Nothing tuned over five years, no vendor stack to administer, no team standing by. You’ll be designing the system, not optimizing within one.

You’ve outgrown the queue. Before anything gets automated here, someone has to run the cases by hand and understand them completely – including you.

“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.

Hard Requirements
3+ years building products or processes at a bank, fintech, payments, or crypto company – or a tier-1 consulting background with regulated financial services exposure.

You’ve shipped automations or agents that run in production today, not proofs of concept.

Based in New York or willing to relocate.