Business Systems & Automation Lead

What You'll Do

Build the systems
Design, build, and maintain integrations and automations so data moves cleanly between systems instead of through people
Own automation quality end to end: logging, error handling, monitoring, retries, secrets management, and clear ownership when something breaks
Build human approval steps into anything that touches money, access, or the ledger - automation should remove the tedious parts of a control, never the control itself
Partner with Data and Engineering on pipelines, source-of-truth definitions, and reporting people actually trust
Transform the processes
Sit with the people doing the work today, map what actually happens (not what the SOP says), and find the steps that shouldn't need a human
Redesign workflows in partnership with the people who own them - they own the process and the controls; you own the redesign and the build
Support the Campfire implementation and the FP&A platform selection and rollout, including integration design and data migration quality
Document what you build in Notion so it survives you, and train the teams who will live in it every day
Prove it worked
Baseline the before state, instrument the after, and report the delta honestly - including when a project didn't pay off
Own a small set of capacity metrics with the Head of Operations and keep them current

What You'll Bring

2+ years (typically 2 to 5) in business systems, finance systems, business or product operations, analytics, or a similar role where you owned building things, not just running them. Consulting, high-growth startup, and finance backgrounds all work. We care considerably more about what you've built than how long you've been doing it.
Something you built that runs without you. This is the one requirement we won't flex on, so we'd rather be upfront about it: we're going to ask you to walk us through a system you built - what it replaced, what broke, how you found out it broke, and whether it still runs now that you've moved on. A process you designed or a project you scoped for someone else to build won't get there. Rough and homemade is completely fine. It has to be a thing that runs.
Real technical skill. Strong spreadsheet fundamentals, plus hands-on ability with at least one of SQL, Python, or a modern BI tool. You'll be reading and reconciling data across systems constantly, and you need to do that without waiting for someone else.
Integration fundamentals. Working knowledge of REST APIs, webhooks, JSON, and authentication concepts, and the ability to troubleshoot an integration by reading logs and API responses rather than filing a ticket.
Genuine AI fluency. You reach for coding agents and AI tooling by default to increase your own output, and you have a point of view on where they're reliable and where they aren't.
Comfort with business and finance workflows. You don't need to be an accountant. You do need to understand how things like AR, AP, close, and forecasting actually work well enough to redesign them credibly - and to know when to defer to the people who own the controls.
The ability to change other people's processes without alienating them. This is the part most people underestimate. You'll be asking experienced teams to work differently. Doing that well is a communication skill before it's a technical one.
A tolerance for unglamorous work. Some of this job is reconciling messy data and sitting in on a close. That's how you learn where the leverage actually is.

Nice to have

Experience with an ERP implementation or migration, at any level of involvement

Familiarity with parts of our stack: HubSpot, Stripe, Hex, Notion, Campfire, or comparable systems

Exposure to workflow automation platforms, ETL tooling, or version control

You've been an early hire into a function that didn't exist yet

What This Role Is Not

We'd rather be direct than have you find out in month three:

This is not an accounting role. You won't own the close, and you won't be judged on ledger accuracy.

This is not a role where the requirements arrive fully scoped. Much of the job is figuring out what's worth building.

This is not a role for someone who wants to build in isolation. The best version of this person spends a lot of time sitting next to the people whose work they're changing.

This is not a fast-credibility role. You're asking experienced teams to change how they work. That's earned, not assigned.