I’m Chris, VP Engineering at Fazeshift. We’re nine engineers plus our Founder/CTO and me, and I’m hiring someone who can help us do more, better: increase both what we can build and the quality and sophistication of the software we build.
Accounts receivable sounds boring until you look under the hood. It sits at the intersection of money, business relationships, software systems of various vintages, and a huge amount of repetitive human work. Instead of giving finance teams another dashboard to stare at, we’re building AI agents that actually do the work across billing, collections, payments, cash application, and the systems connecting them. We’ve grown revenue 12x since 2024, and eight unicorns now run AR on Fazeshift.
A big part of what makes the engineering interesting is that we’re intentionally not the system of record. Our customers already run on ERPs, CRMs, banks, billing systems, payment processors, spreadsheets, and internal software, so we have to understand state across systems we don’t control, act safely in them, and recover when reality disagrees with what an API says should have happened. A timeout doesn’t necessarily mean a write failed. Webhooks can arrive late or twice. A payment may not contain enough information to identify an invoice. In those cases, blindly retrying can be exactly the wrong thing to do.
We use coding agents heavily ourselves. Engineers use Conductor, stacked PRs, Linear, and multiple frontier models every day, with internal skills and tooling that let agents drive and validate our local development environment. We’re especially interested in engineers whose development workflow has already materially changed because of coding agents: people who are comfortable delegating meaningful work, keeping independent threads moving in parallel, debugging where agents get stuck, and improving the surrounding system when the workflow breaks down. But generated code is still your code. Judgment, debugging, systems thinking, taste, and understanding what actually shipped matter more here, not less.
Our development style is roughly: design enough to find the shape of the problem, then build to learn. There’s a short distance here between noticing a problem, deciding what should happen, building it, and seeing the result in production with our customers. You’ll own meaningful problems from ambiguity through design, implementation, rollout, and production, and you’ll work directly with the people affected by what you build.
We’re looking for 5+ years of professional experience, strong TypeScript/full-stack skills, solid systems judgment, and real production ownership. No fintech background needed. Stack: TypeScript/Next.js, tRPC, Prisma/MySQL/PlanetScale, Inngest, AWS.

Senior Software Engineer at Fazeshift