Customer Engineering Lead

Customer Engineering Lead

Bellevue
• Dallas

Deployment & Transformation

In office

Full-time

Auger is the autonomous operating system for supply chains — the layer that finally allows disparate systems like ERP, WMS, and TMS to work together instead of against each other.

Most supply chain software surfaces problems and waits for a human to act. Auger solves them. Our AI detects disruptions, evaluates trade-offs, and executes decisions automatically — moving from signal to action in seconds, not weeks. We eliminate the Coordination Tax: the billions in capital and time lost when disconnected systems force the best people in the business to become the Human API between planning and execution.

At Auger, we design autonomy into our systems. We expect the same from our people.

That means:

• Clear ownership, not decision by consensus
• First principles over inherited patterns
• Shipping systems, not slide decks
• Fast feedback from reality, not opinions

If you want to build, ship, and iterate against reality, Auger is for you.

Auger was founded by Dave Clark and is backed by $150M from Oak HC/FT and Eclipse Capital. Our team works from Bellevue, WA and Dallas, TX.

Auger becomes real to a customer on one day: when it goes live in their environment, runs on their data, and starts executing decisions autonomously. Getting it to that day is your job.

You own the technical path from signed scope-of-work to go-live: the data sources and access architecture, the integration, the write-back, the testing, the go/no-go call, and the cutover. You work inside a Customer Transformation pod alongside the Customer Transformation Lead, the Product Lead, and the Supply Chain Data Scientist. You are the engineering voice in that room and the connective tissue between the customer's IT and data organization and Auger’s engineers who are building for them.

Engineers, data engineers, and QA join the account for the length of the engagement, and the roster changes with each one, so you end up working across most of Auger engineering and knowing exactly who to pull in when something has to move today. You will be context switching across multiple projects getting delivered for the customer, each with its own timeline, blockers, and stakeholders, and the ground will shift under you regularly.

The job is absorbing that volatility without losing the thread on any single project.

This is a hybrid of technical program management and engineering management. You are technical enough to read the code, challenge an architecture, and know when an estimate is fiction. You are operational enough to hold a launch date across several internal teams and a customer IT organization that has never moved this fast.

The people who thrive here are decisive under ambiguity, comfortable moving from an architecture review to an executive escalation in the same afternoon, and constitutionally unable to let a blocker sit for a week. They do not forward problems. They bring the problem, the options, and the call they are making.

• Own the technical launch plan. Build and defend the end-to‑end engineering schedule for each deployment: dependencies, owners, dates, and what happens when someone misses. Once finalized, track the progress made by the team against the plan.
• Define what data we need and how we get it. Run the context and data inventory process, identify every required source, and drive read access architecture design with the customer's data and IT teams.
• Direct the engineering pod. Lead a rotating set of dotted‑line engineers, data engineers, and QA across the account. Assign the work, set the bar, unblock daily, and step in when a workstream slips.
• When a requirement is unclear or in tension with what's technically achievable, work it through with Product until it's resolved — don't let ambiguity reach engineers mid-execution
• Surface concerns the moment you see them before its undeniable — a number that doesn't add up, a decision drifting from what was agreed, a risk no one's naming yet.
  
  Own testing end to end. Internal dogfooding, Auger testing, and joint customer testing. Find the failures that would surface at go‑live…