Director of Engineering
Director of Engineering
Posted today
SENIORITY
Manager
About the role
- Harden and extend the systems where finance, operations, and commercial data intersect: inventory, reconciliation, ledgers, procurement and fulfillment workflows, and pricing data
- Carry platform volume 4x year over year while keeping the data trustworthy
- Identify where systems strain under volume and ship improvements, making the platform the single source of truth for the business
- Ship the internal tooling that trading, logistics, finance, and sales teams rely on every day, so the company scales volume without adding headcount
- Replace manual spreadsheets with real platform capabilities, then automate them with agentic workflows that measurably remove human time or improve unit economics
- Own AI observability and cost, including per-feature spend tracking and model selection trade-offs
- Build the products and integrations that embed Outlast into how suppliers and buyers already operate
- Decide per case whether an agentic flow or an embedded platform experience serves the customer best
- Measure success by effort removed and time saved for the customer, not features shipped
- Architect, direct, and review AI-generated systems; AI writes most of the code at Outlast
- Stand up the practices that keep AI-written code correct and maintainable: code review, evals for AI features, deploy discipline, and reliability
- Set the standard for how a small team ships enterprise-grade systems with AI leverage
- Lead a small, actively shipping engineering team as a player-coach, and grow it deliberately as the work demands
- Establish the engineering operating system: delivery cadence, review practices, and reliability standards
- Be the engineering partner the rest of the company relies on, translating the workflows operations, finance, and sales struggle with into shipped automation
- Has built systems where finance, operations, and commercial data intersect: inventory, reconciliation, ledgers, procurement and fulfillment workflows, pricing data
- Can describe a system they built across these domains, how it scaled, and what it took to keep the data trustworthy as volume grew
- Has personally shipped AI and agent-powered systems in production, not proofs of concept or demos
- Understands LLM and agent architecture, evals, latency, and cost trade-offs
- Builds primarily by orchestrating AI coding tools: architecting, prompting, reviewing, and shipping AI-written code
- Can describe how AI changed how their team ships and how they keep AI-generated code correct and maintainable
- Track record of building products that non-technical customers actually adopt
- Integrates products into how customers already work, measuring success by effort removed and time saved
- Has been the first or most senior engineering leader at a small company, comfortable doing the work without a platform, QA, or data team behind them
- Ships working systems, owns data correctness as the business scales, and is honest about strengths and gaps
- Based in or willing to relocate to Salt Lake City, working in person with the team
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
