Should You Hire a VP or a Director?
Hire a Director when you need a strong individual contributor and functional leader who executes and manages a small team. Hire a VP when you need someone with broad authority to build and own a function — including hiring, strategy, budget, and cross-functional accountability. The most common mistake is hiring a VP when a Director is the right scope, creating an executive who is underutilised or disengaged because the role does not match the title.
The VP vs Director question is the most common scoping mistake in startup executive hiring. Companies use VP titles to attract candidates, then discover the role is actually Director-level scope. The result: the hired VP finds the role beneath their expectations, underperforms, and exits early. Getting the title right starts with getting the scope right.
Role Comparison
| Dimension | Director | VP |
|---|---|---|
| Team size | Individual contributors + 2–5 direct reports | Multiple team leads or managers, larger team |
| Budget ownership | May have budget responsibility | Owns the functional budget |
| Strategic authority | Executes strategy set above | Sets and owns function strategy |
| Hiring authority | May interview and recommend | Owns hiring decisions in the function |
| Reports to | VP or C-suite | C-suite or CEO |
| Typical base (Series B) | $160K–$220K | $220K–$320K |
Signs You Need a Director, Not a VP
You need a Director when: - The function has 3–6 people and does not need cross-functional ownership - You want execution and strong management, not strategy ownership - The budget and P&L ownership sits with the CEO or COO - A VP in this role would be bored or disengaged - You have plans to hire a VP above this person in 12–18 monthsSigns You Need a VP, Not a Director
You need a VP when: - The function needs to be built and owned independently - You want cross-functional authority and budget ownership in this person - The function is a primary growth driver and needs executive-level leadership - You will not have a C-suite layer between this person and the CEO in this function - The scope requires strategic vision, not just strong executionTitle Inflation Consequences
Using VP when you mean Director causes: - Attracting candidates who expect VP-level scope — and leave when they don't find it - Paying VP compensation for Director-level work - Creating confusion when you later want to hire a 'real' VP above the current person - Setting compensation precedent that constrains future hiring flexibilityFrequently Asked Questions
Can a Director become a VP internally?
Yes, and this is often the right path. Hire a Director with high potential for the current scope, set a clear promotion path, and promote them when the function grows to VP-level scope.
Is it okay to use a VP title if the scope is Director-level to attract better candidates?
This is a common but risky approach. You attract VP-calibre candidates who discover the scope is Director-level — they either accept it and disengage, or decline and you have wasted the interview process. Use the title that matches the scope.
How do I tell a candidate the role is Director and not VP without losing them?
Be direct about the scope and what makes it compelling at this level: the growth opportunity to build something meaningful, the path to VP as the function grows, and the compensation. Strong candidates who understand the real opportunity will respond to honesty better than to a title mismatch.
Facing This Decision Now?
A 20-minute confidential search assessment with Manas Majhi covers your specific situation — not a sales call.
Request a Search Assessment →