Internal Interview Questions for a Department Head Promotion

At a small company, department head is usually the last promotion before the owner. The person taking it stops optimizing their own function and starts making tradeoffs against other functions, often ones they do not fully understand.

That is the real shift. A first-line manager advocates for their team. A department head has to be able to lose an argument on behalf of the business and then explain the outcome to their people without resentment. They also take on budget, which most internal candidates have never held.

So the interview tests four things: whether they can think past their own function, whether they can own a number, whether they handle cross-functional conflict without escalating everything to you, and whether they will tell you bad news early.

1. "Your department needs two more people. Sales needs one. There is budget for one. Make the case, then argue the other side."

Strong: makes a genuine case for the other function, and can articulate the business logic that would justify losing.
Weak: cannot argue the other side seriously. This predicts a department head who treats every allocation as a loss.

2. "You are given a budget number you think is too low. What do you do?"

Strong: comes back with what the number buys and what it does not, in specifics, and asks which of the tradeoffs is acceptable.
Weak: accepts it and quietly under-delivers, or refuses without translating the shortfall into consequences.

3. "A peer in another department is blocking your team. How do you handle it?"

Strong: goes to the peer directly first, tries to understand the constraint, and escalates only with a specific ask.
Weak: escalates to you immediately, or goes around the peer. Both create the cross-functional friction you will spend the next year managing.

4. "Something in your department is going badly. When do I hear about it?"

Strong: early, with a plan attached and an explicit statement of what they need from you.
Weak: once they have fixed it. At department scale, late notice removes your ability to help while the problem is still small.

5. "How would you decide what your department stops doing?"

Strong: has a method and is willing to name something current that should stop, including things they built.
Weak: only adds. A department head who cannot subtract will grow headcount forever.

6. "One of your managers is not working out. Walk me through it."

Strong: describes coaching first, with a specific gap and timeline, and is willing to reach a decision rather than tolerate it indefinitely.
Weak: either tolerates indefinitely or moves straight to removal. Managing managers is the skill and both extremes avoid it.

7. "What does your department look like in two years, and what would have to be true?"

Strong: a specific picture with dependencies named, including things outside their control.
Weak: a bigger version of today, or a vision with no stated dependencies.

8. "What do you think I am wrong about?"

Strong: has an actual answer, delivered respectfully. This is the single most useful question in the set.
Weak: deflects. A department head who will not disagree with you is a department head who will let you make a mistake, and at this level that is the main thing you are buying protection against.

• Business-level thinking. Can they argue against their own function. Questions 1 and 5.
• Number ownership. Can they translate a budget into tradeoffs. Question 2.
• Peer conflict resolution. Do they solve laterally before escalating. Question 3.
• Early disclosure. Do you hear about problems while they are still small. Question 4.
• Managing managers. Can they coach and also decide. Question 6.
• Willingness to disagree with you. Question 8, weighted heavily.

At this level, the last dimension matters more than most owners expect. Every layer you add between yourself and the work reduces what you see directly. A department head who will not tell you that you are wrong makes that reduction dangerous rather than merely inconvenient.

Department head candidates are usually a small pool you know very well, which makes structure more important rather than less. Familiarity is precisely what makes an unstructured decision drift toward whoever you are most comfortable with.

Publish the competencies, the format, and give two weeks rather than one, since the budget and cross-functional questions genuinely benefit from preparation. Include someone outside the department in the process, even informally. At this level you are assessing how the person operates with peers, and a peer's read is information you cannot generate yourself.

At this level the runner-up is usually a first-line manager who now reports to the person who got the role. That is the hardest configuration in this entire library, and it needs handling within a day.

Be specific and be honest about the path. "Where the gap was is the cross-functional dimension, particularly the question about a peer blocking your team. You went to escalation faster than I need at that level." Then address the reporting relationship directly rather than hoping it settles: acknowledge that it is awkward, say what you expect from both of them, and check in on it at two weeks and six.

The person who got the role also needs the guidance in managing former peers, and specifically the section on the candidate who applied for the same job. That conversation is theirs to run, not yours.