Customer Engineering Lead

Build at Auger

• Clear ownership, not decision by consensus
• First principles over inherited patterns
• Shipping systems, not slide decks
• Fast feedback from reality, not opinions
• 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 while there is still time to fix them.
• Drive go/no-go, cutover, escalation. Make the launch call on evidence, run the cutover with the customer's tech team, and own technical escalation and SLA support after.
• Translate between customer IT and Auger engineering. Serve as the single technical voice to the customer's data, IT, and security organizations. Turn their systems reality into requirements our engineers can build from without a follow-up meeting.
• Force technical tradeoffs to a decision. Scope, sequencing, build versus configure, what ships at launch and what does not. Make the call, state the cost, and move.
• Stay in the detail. Read the code, review the designs, inspect the data, validate the integration yourself. You do not accept status as evidence.
• Close the loop with Product and Engineering. Feed recurring customer friction back into the platform so the next launch is faster than this one.
• 5+ years across engineering, technical program management, or engineering management, including hands-on software or data engineering experience.
• Track record delivering complex technical programs for enterprise customers across multiple teams you did not manage.