AI Engineering Systems Lead

AI Engineering Systems Lead
Most engineering orgs are bolting AI onto how they already work. We're rebuilding the work itself.

We believe most of the code in our platform is going to be authored by AI, and that this changes the job of architecture, not just the speed of typing. LLMs are brilliant at producing code that looks right and runs on the first try. They are unreliable at remembering the in variants that keep a large system correct. A platform that only works when the author remembers the rules will quietly rot under AI authorship.

So we made a different bet. We build the machinery that makes the rules impossible to break: deterministic checks, compile-time types, runtime guardrails, and autonomous pipelines that ship code through all of it. We’re well into this work. We need someone to own it and push it to the frontier.

Why Rootstock, why now: Rootstock brings proven depth in ERP and manufacturing — real products, real customers, decades of hard-won domain knowledge. We’re putting that depth behind a clear blueprint for becoming AI Native, with active development underway and the funding to see it through. You’d build alongside a deep bench of senior engineers who have shipped real ERP n sharpens iron.

The role in one line: You own the internal systems that let Rootstock engineers — and our agents — ship production Salesforce code fast and ship it correct.

This isn’t a greenfield daydream. There’s real, running scaffolding for you to take ownership of and extend:

• Autonomous coding pipelines. A bugfix pipeline already turns a Jira ticket into a reviewed Apex/LWC pull request, with an observability layer that scores every run. You’ll deepen it, widen it to new pipeline types, and raise the bar on how autonomously and reliably it ships.
• A root-cause engine, and the evals that keep it honest. One of our most important tools investigates a bug across multiple repos and millions of lines of code to find the actual root cause, grounded in a continuously built specification corpus. Evals run constantly — we pit the current generation against candidate generations and against fixes real engineers actually shipped. You’ll own it and keep pushing it forward.
• A 'Constitution' of enforced architecture. We maintain foundational architectural decision records that bind every repo, on a single thesis: every principle must have a deterministic enforcement seam — a type, a startup check, a CI test, or a hook — never just a doc. You’ll extend this and the runtime that enforces it across the Claude Code session lifecycle.
• TDD tooling that actually changes behavior. A local in-memory Apex test runner lets engineers run the red-green-refactor loop without deploying to an org. You’ll build the tooling that makes test-first the path of least resistance, for humans and agents alike.
• The guardrails. A suite of quality and safety hooks that format, scan, and block bad edits before they land, plus the PR gate that runs the full scanner suite. You’ll decide what the next generation looks like.

• A strong systems and types thinker. You reach for the type system, the lint rule, or the CI test to make a class of bugs unrepresentable, rather than writing a paragraph in a style guide.
• Real fluency with AI-assisted and agentic development. You’ve built with agents, you have opinions about where they break, and you’ve designed around their failure modes.
• Solid programming fundamentals. Competence in Java, JavaScript, or something comparable translates well — strong engineers pick up the rest.
• Comfort building developer tooling, CI/CD, and orchestration: hooks, pipelines, observability. You like making other engineers faster.
• Salesforce and Apex experience is a plus, not a gate. We care more about how you think about platforms than how many years you’ve shipped on any one of them.

• You build things for fun. Have you ever shipped a side project just because you wanted to see if it would work? We want to hear about it.
• You enjoy experiment, trial, failure, and rapid iteration — and you instrument your way out rather than freezing when the first attempt fails.
• You’ve…