Director of Engineering

What You Will Do:

The role

Run the engineering org day-to-day, reporting to the engineering leader. This is a fast-moving train — real timelines, real customers, working software demoed every Friday.

You own delivery across all squads, the hiring pipeline, and the standards that keep a senior-IC team shipping fast without ceremony.

This is not a body shop and you don't run it like one: it's a startup environment inside a bigger company, and the plan will change under you — new tech, new priorities, new customer asks. You absorb the change, re-plan in hours not weeks, and keep the train moving.

What you'll own

Delivery — timelines and quality, both, no trade-off allowed to hide weekly

Friday demos of working software (show-me culture: if it doesn't run, it didn't happen)

Tech-lead and squad performance

Hiring (you personally own the funnel and the bar)

Translating business requirements into technical scope the squads can build

Cross-squad dependencies and the engineering operating rhythm ·

Escalation path for blocked work — you move it, not track it.

Who you are.

A delivery persona with a show-me mentality.

You trust demos, not status decks. A self-starter with grit who has run fast trains before and likes winning.

You've kept the respect of very senior engineers because you're still technically credible in the room.

You challenge an architecture, and they listen.

You use AI tools yourself, daily, and expect the org to use them to multiply velocity.

What You Will Bring;

10+ years engineering leadership in SaaS or platform companies; at least one stint scaling an org from 30 IC engineers — ideally in a startup or startup-speed environment.

Delivery-first track record: shipped on aggressive timelines at a weekly cadence without letting quality slip. You can point to the dates you hit.

Hands-on enough to read Go, Python, and TypeScript and call architecture out in review — you have not stopped being an engineer. High-level engineers respect you because of it.

Strong working knowledge of the modern AI stack — LLMs, SLMs, RAG, knowledge graphs, agents, fine-tuning/training, eval. Not a researcher, but you can engage on all of it, make build-vs-buy calls, and smell a bad AI design.

Captures business requirements from executives and customers and translates them into technical needs the squads execute — you're the bridge, in both directions.

Change is your default state: you re-plan around shifting tech and priorities quickly and manage the team through it without drama.

Loves hiring. Has a bar and holds it. Can tell an A from a B from a C in 30 minutes.

Drives AI-assisted engineering (Claude Code-class tooling) across the org as a velocity multiplier — and measures the gain.