Job leveling is an important step when building a compensation philosophy. The process of job leveling isn’t easy, but it’s important to get it right. Titling employees is one of those tricky areas.
There’s an open debate on the best practices for job titling, notably with Marc Andreesen and Mark Zuckerberg arguing for opposite camps. One side believes that titles are the cheapest form of compensation and should be given out freely to give a competitive advantage. The other side is more strict about granting high-level titles in order to implement proper leveling and ensure titles are meaningful and fair.
No matter which camp you fall into, there is one thing we can probably agree on: the “Head of” job title is confusing. What the heck does the “Head of” title mean? Let’s explore the data to find out.
Consider roles like Head of Marketing, Head of Analytics, Head of Sales, and so on. These “Head of” job titles are fairly common, but the standard leveling frameworks fall short here.
Where does your company land on using the “Head of” job title? It’s likely your organization falls into one of three buckets:
When we think of “Head of” positions, are these roles aligned with a Senior Manager, a Director, or a VP? The answer can mean tens of thousands of dollars in difference for an employee’s compensation, and set a very different bar for the level of work expected.
We looked at Pave's dataset to analyze all “Head of” incumbent data points across 8,500+ customers. The findings show that a “Head of” can be any level from Senior IC or Manager to Director/Senior Director or Executive, and the breakdown varies somewhat by company size.
That said, a majority of the time, a “Head of” employee is leveled as a Director/Senior Director (M5-M6) by their organization. This is especially pronounced in companies with 3,000+ employees, where 69% of “Head of” leaders sit at the Director level.
{{mid-cta}}
If the majority of employees with a “Head of” title are leveled as Directors, why not just give them that title? There are a couple potential reasons organizations might do this:
It could also be a recruiting tool to attract candidates when competing against Director roles elsewhere. Pave data finds that when normalizing by family, level, and market tier (US only), there is a ~9% premium for employees with "Head of" in their title over employees with "Director" in their title.
The next logical question is around “Head of” vs Director when it comes to salary. So, do “Heads Of X” get paid a salary premium to “Directors of X”? Or does “Head Of” compensation generally map one-to-one with Director compensation?
We looked at ~10,000 employees with the title “Head Of”, “Director”, and “VP” in USA Tier 1 markets. We decided to only look at one locale to take location (mostly) out of the equation as a potential confounding variable. Next, we looked at the median base salaries for all employees with the title “Director” vs. “Head Of” vs. “VP/Vice President”.
Lastly, we broke down the results by job family. E.g. Does a “Head of Sales” err more towards “VP of Sales” whereas “Head of Design” errs more towards “Director of Design”? (Hint–the answer is yes to both.) This analysis is based on plain-text title matching rather than on actual mapped levels.
As we can see, in general, "Head of" titles tend to be paid more than directors but less than VPs. Interestingly, a “Head of X” in the R&D world (Design, Engineering, Product) tends to get paid closer to “Director”. In other departments however, a “Head Of X” tends to get paid somewhere in between “Director” and “VP”. One interesting potential outlier is “Head of Sales”, which generally gets paid a similar salary rate to “VP of Sales”.
While this data helps us to demystify some of the questions around “Head of” vs Director, being thoughtful about titles and levels is key for compensation leaders. When you’re undertaking a benchmarking exercise at your organization, Pave Market Data is a great place to begin. Sign up for free today.
View cash and equity benchmarks from 8,500+ companies with Pave's free Market Data product.