Member of Technical Staff: Backend

Member of Technical Staff: Backend

Monk is an AI-native accounts receivable (AR) platform for B2B companies helping businesses get paid fast.

The AR stack is broken. Finance teams still chase payments with spreadsheets, reconcile AR in spreadsheets and use software that was built a decade ago. We think this is one of the largest, most ignored problems in B2B software. Trillions of dollars sit in outstanding invoices and the tools to unlock cashflow are stuck in the past. We are rebuilding Monk with AI, speed, and real craftsmanship.

We are already doing this for over $1B of accounts receivables. We are backed by leading investors and our founders bring significant experience to our company (more here).

We are early, the upside is enormous, and the hardest, but also the most rewarding work is ahead of us.

The role:

We're looking for a backend engineer to join us in person in Flatiron, NYC. You'll own the foundational systems everything else runs on: the data layer, the integrations, the AI runtime environment, and the infrastructure that has to be right every time money moves between businesses. We care about one thing: whether you can build systems that scale, stay up, and get faster as we grow.

In this role you will:

• Build core agent infrastructure at the applied layer: Design and ship the system that powers Monk’s agentic products

• Own systems end to end: Build and maintain enduring financial architecture designed for agents

• Build for the future: Manage, evolve, and extend your architecture and design to thousands of use cases that slow down payment in B2B

• Own reliability at scale: Build and own monitoring, alerting, and incident response to get our customers paid fast

• Ship fast: Land changes that help customers daily and default to action

Who you are:

• 4+ years building and operating production backend systems. You've built them, broken them, and scaled them yourself

• A T-shaped engineer: deep in at least one area, broad enough to push the rest forward, and you do it in TypeScript/Node

• Strong with our stack and able to go deep where it counts: Postgres, AWS, data pipelines, observability

• You understand the tradeoffs you're making and you know when something has to be rebuilt instead of patched

• AI-native, not AI-dependent. You move fast with it and you know exactly when not to use it

• An owner. You don't file tickets about infrastructure problems. You fix them, and then make sure they can't happen again