Why this role exists

Artifact AI is rebuilding accounting from the ground up. Not making the software incrementally better, rebuilding the work itself, so one accountant does what a team used to do and a set of books closes itself in the background while a human stays in the loop.

Two products do the heavy lifting. Arti handles ingestion, matching, reconciliation and journal posting. Omni orchestrates 600+ platforms and lets accountants build agentic workflows using natural language. The integration layer is one of the most important surface area in the product. It is what makes everything else possible. 

We’re backed by a16z, based in London and NYC, and accounting firms run their clients’ month-end on us today. We’re hiring a Product Engineer to own the integration layer end-to-end, with NetSuite as the deep end and the rest of the modern accounting stack alongside it.

The role

• You own the integration layer. Every connector that touches the product is yours: design, build, monitor, maintain. When QBO ships a breaking change, you know before customers do. When we add a new tool, you decide how it plugs in. When a customer’s NetSuite OneWorld setup does something only their NetSuite OneWorld setup does, you are the one who untangles it.

• NetSuite is where the depth lives. SuiteQL, SuiteTalk REST and SOAP, SuiteScript 2.x for the gaps off-the-shelf connectors leave behind, SuiteScript 1.0 when a legacy tenant demands it. Token-Based Auth, OAuth 2.0, role and permission setup, the troubleshooting that comes with all of it. OneWorld is in scope: subsidiaries, classes, departments, segments, intercompany, elimination, multi-currency, consolidation.

• The rest of the stack is also yours. QBO, Xero, Sage Intacct, Bill.com, Ramp, Gusto, Dext, and whatever we add next. You stay ahead of changes to all of them. You set the bar for how we do integrations across the product: data model conventions, sync patterns, observability, customer-facing diagnostics.

• Backend is home. Python, async, the messy distributed parts. But you’ll move into the front-end or the infra when the problem is there. You partner directly with customers (controllers, accounting ops, admins) to understand how their stack is configured and turn that into a reliable mapping.

• You set direction on what you own. Build the code that matters. Push back when you think we’re wrong.

• Pace matters here. Speed and quality pull against each other. The skill is knowing what to spend the day on and what to ship rough and fix Friday. You don't reach for the cleverest tool, the trendiest pattern, or the abstraction that makes you look senior. You pick the boring thing that works, because you've got nothing to prove.

• You use AI to the max, or anything else that makes you 10x. And you know when to put the tools down and get your hands dirty so the shipping bar holds.

• Low ego, high standards. You are kind to the humans on the team and brutal on the work. You do not confuse the two.

Who we’re looking for

There are two profiles that work for this role. We’re open on which.

• Profile A: the NetSuite-deep engineer. You have spent serious time inside NetSuite at the integration layer, ideally in a OneWorld setup. You know the difference between SuiteTalk REST and SOAP and when to reach for SuiteQL. You have written SuiteScript 2.x in anger. You are not intimidated by saved searches, custom records, custom segments, or chart-of-account weirdness. You want to widen into the rest of the accounting stack and own a real product surface, not stay in a consulting or admin lane.

• Profile B: the integrations engineer with accounting depth. You have shipped serious integrations against at least one major ERP (Sage Intacct, Dynamics, QBO at depth, Xero at depth, or similar) and have fluency across several others in the modern accounting stack. You understand multi-entity accounting from the inside (intercompany, consolidation, multi-currency). NetSuite is the gap you want to close, and you have either touched it before or have the appetite to go deep on it fast.

Either way, you have all of these:

• Strong Python and a real comfort with API integration work at depth: auth flows, rate limiting, retries, idempotency, schema drift, the unglamorous parts.

• Hands-on experience building integrations against ERPs or accounting systems where the data model actually matters. You can talk fluently about the chart of accounts, journal structure, multi-entity, multi-currency, and why these are not the same problem in two different tools.

• A history of owning a surface area, not just contributing to one.

Bonus

• Background at an iPaaS or universal connector platform (Codat, Rutter, Merge, ..etc.). If you have built or maintained accounting connectors.

• Background as a NetSuite consultant or admin at a Netsuite partner plus engineering skills to match the role.

• Deep, hands-on experience with non-NetSuite ERPs.

• You have been a founder or founding engineer of a venture-backed company.

• You have shipped agent systems with structured tool-use at scale.

  
  

What this role is not

Not a NetSuite admin role. Not a “we’ll teach you accounting on the job” role. Not an internal-tools job dressed up as a product role. This is product engineering against the hardest data surface in our product, with direct customer impact and real ownership.

What you will not do here

• You will not have a process between you and the work. No JIRA tickets handed down, no PMs gating your access to customers, no architecture review board you have to convince before writing code.

• You will not manage people in this role. This is a senior IC track. If your goal is to run a team of 30, this is the wrong role for you, though we are happy to support a transition into management later for the right person.

• You will not work 9-to-5. We are trying to compress what would normally be a decade of work into two or three years. We expect you are the kind of person who finds that energising rather than alarming. We protect deep-work time aggressively, but we do not pretend the hours are normal.

  
  

Working at Artifact

Artifact's culture is intense and not for everyone. We work hard, we ship fast, and we are direct with each other when something is off. We hire grown-ups and we expect grown-up behaviour. We celebrate wins together, and we do not pretend everything is fine when it isn't.

We are a fit for you if: you are unreasonable about quality, you are happiest when you are shipping, you would rather argue about a design doc than sit through a status meeting, and you have a real, weird, founder-shaped reason to want to spend the next several years rebuilding accounting.

We are not a fit for you if: you want predictable career progression frameworks, heavy processes, formal mentorship structures, or strong work-life-balance signals. There are great companies that offer those things. We are not one of them, and that is on purpose.

How we hire

• Intro call (30 min) Mutual fit, what you have built, what you are looking for.

• Technical deep-dive (90 min). Design System + Pair Programming session.

• Take-home + review (5–8 hours of your time, scheduled how you like). A scoped problem from our actual codebase. 

• Culture round (30 min) Direct conversation about why us, why now, what you and we would not tolerate.

• Reverse interview where you ask anyone on the team anything. We will introduce you to whoever you want to talk to before you decide.

• Offer where there is mutual fit.

We move fast. The whole loop is typically two weeks. If we are slow on you, it is because we are deliberating, we will tell you what is happening.

We are an equal opportunity employer. We hire on the basis of evidence that you can do the work and want to do it here, full stop.

To apply: email careers@getartifact.com with your CV/LinkedIn and one paragraph on the most ambitious thing you have shipped, what was hard about it, and what you would do differently. We read every one of these.