Kinter builds AI agents that execute the expense-side of the accounting close for mid-market finance teams. Prepaid, accruals, payroll, reconciliation, and more: the repetitive, judgment-heavy work that keeps finance teams stuck in spreadsheets every close.
We're a lean, product-centric team (~30 people) moving fast with an exciting product we launched a few months ago. Here you'll do the best work of your life and have a massive impact: what you ship this month is used by finance teams the next.
How you'll make an impact here
Work with the team to build the Kinter platform from the ground up. We’re a few months into launching the full platform which means there’s a ton of product discovery, exploration, validation and complex problems to solve here.
Start by building the ERP integration layer connecting our agents to NetSuite and other ERPs: authentication, data mapping (chart of accounts, journal entries, vendor and customer records), OCR, and edge cases that only become obvious in production and at scale.
Work directly with customers and their finance teams to understand how their ERP is configured, and translate that into data that our agents can rely on.
Move fluidly across the stack: backend services that talk to ERPs, the data layer that feeds our agents, and the product that surfaces actionable intelligence to finance teams.
Own problems end to end, from investigating API quirks to shipping, monitoring, and iterating our flagship product.
Help define how Kinter approaches new data sources for our agents as we expand support for enterprise systems; the patterns you build now become the template for what comes next.
Work closely with product, engineering, leadership, and customers directly. Given the size of the team, decisions move fast and your work is visible.
What you'll bring to the team
Solid experience building web applications and services with Node.js, TypeScript, and React, and comfort working across frontend and backend as needed.
Experience integrating with third-party APIs, ideally ERPs (NetSuite, QuickBooks, Sage, Oracle Fusion, SAP) or other financial and accounting systems. Strong experience with complex, quirky third-party APIs more broadly (payments, banking, CRM) is also relevant if it involves careful data mapping and edge case handling.
Excellent problem-solving skills: comfortable diagnosing issues with incomplete information, breaking down ambiguous problems into actionable steps, creativity in finding solutions, and building resilient systems, often around unreliable third-party endpoints.
A generalist and self-starter mindset. You're energized by learning a new domain (accounting) and by owning a feature from idea to production, rather than staying in one layer of the stack. And you’re curious and show initiative, taking ownership beyond only what task is assigned to you.
Extreme collaboration. You’ll work across small, cross-functional teams, which means knowledge-sharing, pairing up with other engineers, product managers, and designers, removing bottlenecks and helping the broader product team hit their goals.
Experience running production systems (deploying, testing, monitoring, debugging) and building with reliability and observability in mind from the start.
Comfort with ambiguity and a startup pace. Our roadmap shifts with what customers need, and you'll help shape it – not just execute it. Which also means you need to be organized to structure code, tasks and projects, prioritizing between quick wins and deeper engineering investments.
How we work
Everyone at Kinter operates by five values. Here's what they look like in this role specifically:
Be Fearless: You'll work in parts of the stack nobody has fully figured out yet, whether that's an undocumented API quirk today or a new agent workflow six months from now. That means moving into the uncertainty instead of waiting for someone else to derisk it first
Just Do It: We're a small team with a product that shipped a few months ago. A working feature you can iterate on beats a perfect plan that takes a quarter, whatever part of the product you're touching
Sweat the Details: A misread chart of accounts, an off-by-one in a journal entry, or a subtle bug in an agent's output can misstate a customer's books. Precision matters everywhere in this product, not just in the integration layer
Obsess Over Customers: You'll spend real time with customers' finance teams, understanding how their close actually works today, before you write a line of code. That habit doesn't change as you move from integrations into other parts of the product
Tell It Like It Is: If an approach won't hold up, whether that's an integration assumption, a product decision, or a piece of scope you think is wrong, we want to hear that early and directly, not after it's live
