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.