Last updated: November 16, 2026
By Tom Kenaley, President and Senior Partner, KORE1
A director of engineering job description should state how many managers report to the seat today, how many manager seats are open, what the director decides alone, and what pay range comes with it. Most postings give a headcount instead, something like “lead a team of 40+ engineers.” That describes an engineering manager’s job, and it pulls engineering managers.
Eleven months. That’s how long a tech lead had been acting as the manager of the third team.
The story below is two searches from this year folded into one, with the details changed. A freight-software company in Chattanooga, Series D, about 190 engineers, posted a “Director of Engineering, Platform” opening in March. Lead a high-performing team of 40+ engineers. Hands-on technical leadership. Twelve years of experience, Go and Kubernetes and Kafka, no pay range. It drew 74 applicants in five weeks, and the VP of engineering who owned the seat told our recruiter that most of them were senior engineers hoping for a promotion or managers who ran a single team. Two finalists made it to the last round. Both withdrew.
The first was a director from a bank’s 60-person engineering group in Charlotte, and she walked away in round three when she learned she would run the fourth team herself. It had no manager. The VP had been covering it on top of everything else. “I thought I was hiring managers,” she said, “not becoming one.” The second, a senior engineering manager from Atlanta, left over the word “hands-on.” In round two the VP mentioned, casually, that the director sat in the incident rotation as the second escalation. Nobody had written that down either. Not once.
None of the facts that mattered were in the posting. The platform group wasn’t 40 engineers, it was 31. It wasn’t four teams with managers, it was two managers, one acting manager, and one team with nobody. Two manager requisitions were open, and one of them had no candidates at all. That was the job. The posting described a person with a technology list. Nothing else.
I’ve placed engineering leaders at KORE1 since 2005, and our director of engineering staffing desk is paid only when a client hires someone we introduced, so a posting that fills itself is a search we lose. Fine. Most of what follows costs an afternoon with your VP and a whiteboard. If the open question is what the seat should pay, the director of engineering salary guide has the tiers. This page is the posting. Nothing more. When the applications arrive, the interview exercises for the director loop take over.

What a Director of Engineering Does, in Posting Terms
A director of engineering manages engineering managers. They own delivery, hiring, and team structure across three to six teams, answer to a VP of engineering or CTO, and spend most of the week on the people who run the teams, not on the code the teams write.
The title itself is slippery. The Bureau of Labor Statistics has no director of engineering category, and the closest fit for a software seat is computer and information systems managers, a group of about 685,800 jobs with a median wage of $175,140 in May 2025. BLS projects 16 percent growth from 2025 to 2035 and roughly 53,500 openings a year. That’s a fast-growing bucket with every kind of manager in it. At a 40-person startup “director” is an engineering manager with a bigger title. At a public company it can mean a hundred people and a budget with eight figures in it.
Neighbors worth knowing. The seat below is the engineering manager job description template, which covers a single team. The seat above is the VP, and the VP of engineering hiring guide explains where the line falls. Titles like “Head of Engineering” sit anywhere in between. Same words, different jobs, and one more reason to put numbers in the posting. Once the posting is written, the director of engineering hiring process covers the search that follows.
Count the Managers, Not the Engineers
That’s the whole method. It isn’t clever. Sit down with the VP and count three things. How many engineering managers report to this seat today? How many of those are in the chair and doing the job, not acting? How many manager seats are open?
The headcount comes last. A director’s job depends on the manager count. Engineers are just who those managers manage.
Our engineering org chart guide puts the point where a director layer stops being optional at three or more managers reporting to one person who also owns strategy and budget. Below that, you’re usually hiring a manager with a larger title. Above it, the coordination work has outgrown the VP. Either works. They’re different postings, though, and almost every director opening is one of three situations. Which one is yours?
| Situation | What is true on day one | The sentence the posting needs |
|---|---|---|
| Building the layer | Zero or one real manager, with team leads acting in the gaps | “Two of four teams have a manager today. You’ll hire the other two in your first six months.” |
| Running the layer | Three to five managers in seat, most with a year or more in the job | “Four managers report to you. You own calibration, the hiring plan, and the cross-team roadmap.” |
| Repairing the layer | Managers have left, or two of them stopped trusting each other | “Two of four manager seats turned over in the past year. You’ll find out why.” |
The Chattanooga company was in the first row and wrote the second. Anyone who has run a team of managers hears the difference in about four seconds. People who have only ever managed engineers don’t hear it at all. They’re exactly who the “40+ engineers” line collects.
Repair postings are hard. A director who inherits two departures wants to know why before accepting, and the honest answer in the posting is better than the one they dig up on Glassdoor, so say it. If you can’t say it plainly, say less. Just don’t pretend row three is row two. Candidates talk. Mostly to whoever left.
Say What the Director Decides Alone
The finalist from Atlanta didn’t object to being on call. He objected to learning about it in round two. Fair. A posting that names the decisions this seat owns, and the ones it doesn’t, saves the call where somebody finds out the director can’t actually hire.
| Decision | Ask the VP who holds it today | What goes in the posting |
|---|---|---|
| Hiring, promoting, and exiting the managers | Director, with VP sign-off on offers, or the VP alone | Whether the director makes the call or recommends it |
| Headcount inside the approved budget | Usually the director moves open reqs between teams, and finance approves new ones | The budget figure and who can add a req |
| Architecture and technical standards | Often a staff or principal group, with the director as a tiebreaker or as a bystander | Which one, in a single sentence |
| Roadmap fights with product | Director and a product leader, VPs break ties | Who the counterpart is, by title |
| Incidents and on-call | Who gets paged, who runs the postmortem, who gets called after two hours | Yes or no on the rotation, stated outright |
Check the first row first. Hiring and firing the managers is the decision that makes the seat a director’s seat, or doesn’t. Some companies hand over the title and keep the power with the VP. A candidate who has run a manager performance process before will ask on the first call. Better the posting says so.

Put a Number on Hands-On
In the director postings we read, “hands-on” means a different thing every time. Code in the critical path. Reviewing architecture. Being the person who can read a stack trace at 2 a.m. The on-call rotation. All four are legitimate. They’re not the same job.
Put a number on it, or at least a tier. “You won’t write production code. You’ll review design documents for the platform group and join the incident bridge if an outage runs past two hours.” That sentence tells a candidate more than the word hands-on ever will. Specific beats vague. For the reasoning behind a number, Kris Drouet’s piece on how much engineering managers should code makes that argument at length.
Outcomes work the same way. “Drive engineering excellence” means nothing at all. Pick two or three delivery measures and say so. DORA, the research program behind the most widely used delivery metrics, now tracks five software delivery metrics. Three measure throughput (change lead time, deployment frequency, and failed deployment recovery time) and two measure instability (change fail rate and deployment rework rate). A director who can talk about which two matter for your platform is a director who has done this before, and if your team measures none of them, the posting is a good place to admit it.
Credentials Worth a Line
None, honestly.
No certification predicts whether someone can run managers. A posting that demands a PMP or a SAFe credential mostly signals a process-heavy shop, which some candidates want and plenty avoid. A bachelor’s degree in computer science or equivalent experience is the standard ask, and “equivalent experience” is carrying real weight in it. If your regulated environment needs something specific, say a security clearance or SOC 2 experience, name that one and skip the rest.
The Director of Engineering Job Description Template
Replace every bracket. Text in parentheses is a note to you, so delete it before posting. If a bracket stumps you, go back to the three counts.
Job Title
[Director of Engineering / Director of Engineering, Platform / Director, Software Engineering, Payments] (Add the product area. It tells candidates which managers they’d inherit.)
About the Role
[Company] [does what] for [customers]. You’ll lead [N] engineering teams in [the product area], working through [N] engineering managers and reporting to [the VP of Engineering / the CTO]. The job is [on-site in (city) / hybrid, (N) days a week in (city) / remote within (states)].
The Seat Today
- [N] engineering managers report to this role. [N] are in the seat and [N] are acting.
- [N] manager requisitions are open. [Describe where the search stands.]
- [N] engineers in total across [N] teams.
- [One sentence of honest history, such as “The last director left in (month) and the VP has covered the gap since.”] (Delete if the seat is new.)
What You’ll Own
- Delivery for [the group] against the [quarterly / half-year] roadmap, measured by [two of the five DORA metrics, or your own measures]
- The hiring plan for [N] open roles in the next [six / twelve] months, including the manager seats
- Calibration, promotion cases, and performance management for your managers
- Team structure and the reporting lines under you
- [An engineering budget of $(amount) / headcount planning with finance]
What You’ll Decide
You [hire, promote, and exit / recommend the hiring, promotion, and exit of] your managers. You move open requisitions between teams inside the approved budget, and [finance / the VP] approves anything new. Architecture decisions go through [the architecture group / staff engineers], where you [chair / join / stay out of] the discussion. When the roadmap collides with product, you and the [VP of Product / Head of Product] settle it, and [the VP] breaks any tie.
What You Won’t Do
[You won’t write production code. / You’ll write code only for prototypes.] [You’ll / You won’t] be in the on-call rotation. [You’ll join the incident bridge if an outage runs past (two) hours.] (State it. This is the line that cost the Atlanta finalist.)
What We’re Looking For
- [8+ / 10+ / 12+] years in software engineering, with [3+ / 5+] years managing other engineering managers
- You’ve hired a manager, coached one through a hard year, and let one go
- Experience running delivery across [three or more] teams that depend on each other
- Working knowledge of [the stack, for example Go, Kubernetes, and Kafka], enough to review designs and challenge a roadmap, not to write the code yourself
- You can explain a missed date to a [VP / CEO / board] in a way that keeps their trust
- [Experience in (logistics / healthcare / fintech / regulated industries)] (Delete if the domain doesn’t matter.)
Nice to Have
- [Experience hiring managers into a team that has never had them]
- [Experience with (SOC 2 / HIPAA / PCI) in an engineering organization]
- [A bachelor’s degree in computer science or equivalent experience]
Pay and Benefits
The base salary range for this role is $[low] to $[high], [plus (bonus target) and (equity)]. Where an offer lands in the range depends on [experience and location]. Benefits include [medical, dental, and vision / 401(k) with (match) / (N) days of paid time off / (parental leave) / (a learning budget)]. (Say the other compensation too, such as bonus and equity. Delaware will require both the range and a general description of benefits.)
How to Apply
[Apply link or contact]. [Company] is an equal opportunity employer and provides reasonable accommodations to qualified applicants. To ask for one, contact [name or address].
Setting the Range, and Delaware’s New Rule
Our director of engineering salary guide already publishes the tiers, so these line up with it, and base salary for a tech or tech-adjacent employer in 2026 breaks into three bands that swing much wider in total once equity and bonus arrive.
| Seat | Base range to post | What the manager count usually shows |
|---|---|---|
| First-line director | $185,000 to $235,000 | Two to four teams, often one or two acting managers |
| Second-line director | $220,000 to $280,000 | Four to eight teams with a working layer of managers |
| Senior director | $255,000 to $320,000 | A product line or a platform organization |
One mistake I see often is a posting that spans the whole table. “$185,000 to $320,000” is honest about nothing. It also happens to be the kind of range one new law singles out, because its text makes the breadth of the range part of the good-faith test. For a specific city or a quick check, our salary benchmark assistant is faster than any table.
Now Delaware. Nothing is in force yet, which is what makes it interesting. House Bill 105 became law on September 26, 2025, and the enacted text, Chapter 228 of Volume 85 of the Laws of Delaware, adds a new section 709C to Title 19. It takes effect two years after enactment, so September 26, 2027. Employers with 26 or more employees must put an hourly or salary range, set in good faith, plus a general description of benefits and other compensation, in postings for jobs located in Delaware and for non-international remote jobs offered by a Delaware-based employer.
What stands out for a director seat? Four things.
It covers internal postings as well as external ones, which matters if you promote your best manager. The statute says plainly that “the breadth of the hourly or salary compensation range provided is one factor relevant to the analysis of whether an employer has complied in good faith.” Temporary, interim, or acting job opportunities that require an immediate hire are exempt, so an interim director covering a gap isn’t posted the same way as the permanent seat. And employers have to keep job descriptions and wage-rate history for at least three years and hand them to the Department of Labor on request, which makes the posting you write today a record. A first violation gets a written warning. After that the civil penalty runs $500 to $10,000 per violation, and one job counts once no matter how many times it is reposted.
The Department of Labor has to write regulations before then, so some of this may move. Ask counsel. But a Wilmington company hiring a remote director who lives in another state is exactly the case where I’d print the range everywhere and stop reading statutes.

What Engineering Leaders Ask Before They Post
“Director of Engineering” or “Head of Engineering” in the title?
Use “Director of Engineering” when the seat manages managers. “Head of Engineering” says nothing about level, so it draws engineering managers, directors, and VPs in about equal measure.
Add the product area after the title. It filters better than the title does. Try it.
How many engineers should the posting say the director leads?
Give two numbers, managers and engineers, such as “four managers and 31 engineers.” The manager count tells a candidate what the job is, and the engineer count only tells them how big the building is.
Round up to 40 and somebody will count in round three. They always do.
Does the director carry a pager?
Short answer, usually not as the first responder. In the searches we run, most directors sit one or two steps above the rotation, and the posting should say which step. What matters is that it’s written down.
Where the director is the second escalation, as at the Chattanooga company, say “joins the incident bridge after two hours” in the posting and keep the exact threshold. Candidates accept an honest pager more readily than a surprise one.
Promote our best manager or post the job?
Do both. Post it internally with the same range you would post externally, and compare. A promotion that survives an outside search is easier for everyone, including the person promoted.
The new director’s first quarter is another matter, and our guide to the first 90 days for a new engineering leader covers it. Delaware will require the range on internal postings too once the law takes effect.
Does Delaware’s pay rule cover an interim director?
Temporary, interim, and acting job opportunities that require an immediate hire are exempt from the posting requirement, according to the enacted text. The Department of Labor may write regulations for them, so check before relying on it.
Contract or direct hire for a director of engineering?
Direct hire, almost always. A director builds a management layer, and that takes a year or more. Contract fits interim cover while the permanent search runs.
The permanent seat belongs with direct hire staffing, and contract staffing covers the gap. Our fractional and interim engineering leadership team handles those cover roles, which is a common way to keep a director seat from sitting empty for a quarter.
Send the Counts With the Posting
The Chattanooga company reposted in June with the manager count, the open requisitions, the decision list, the on-call sentence, and a range of $215,000 to $255,000. Twenty-nine people applied. Down from 74. Better ones, too. The director they hired had run a 55-person group at a regional health insurer in Franklin, Tennessee, and in her first week she asked which of the two open manager seats was already being interviewed. One had two finalists. The other had nobody. She started with the second. Of course she did.
If you want a second read on your draft, send it to our recruiters with your org chart, and we’ll tell you which of the three situations it describes and whether the range matches the manager count. KORE1’s recruiters average more than 15 years on the desk, and 92 percent of the people we place are still in the job twelve months later. A posting that tells the truth about the seat helps that number more than anything we do on our end. For the layer above, the engineering staffing agency page covers the rest of the engineering leadership searches we run.

