Mercer and Korn Ferry are two of the most widely used names in compensation benchmarking and job evaluation.

Both can help organisations answer an apparently simple question:

What should we pay for this job?

But Mercer and Korn Ferry do not necessarily approach that question in exactly the same way.

This becomes particularly important when an organisation uses one provider for salary benchmarking and another for job architecture or job evaluation. A role that appears to sit at one level under a Mercer framework may not translate neatly into a Korn Ferry level or grade.

That does not mean one methodology is wrong.

It means compensation professionals need to understand what each framework is measuring before attempting to compare the results.

Mercer vs Korn Ferry at a glance

At a practical level, the distinction can be thought about like this:

The important point is that salary benchmarking and job evaluation are related, but they are not the same exercise.

Understanding that distinction makes comparing Mercer and Korn Ferry much easier.

Market pricing vs job evaluation

Suppose an organisation has a Finance Manager.

There are two different questions it could ask.

The first is:

What are other organisations paying Finance Managers with comparable responsibilities?

That is primarily a market-pricing question.

The second is:

How large or complex is this Finance Manager job relative to other jobs inside our organisation?

That is primarily a job-evaluation question.

A robust compensation framework often needs both perspectives.

External market data tells us how competitive the organisation's pay is.

Job evaluation and architecture help determine how jobs relate internally.

This is one reason Korn Ferry's Hay methodology frequently enters conversations about grading and job architecture.

What is the Korn Ferry Hay methodology?

Korn Ferry's Hay methodology is a structured approach to evaluating the relative size of jobs.

Rather than simply saying:

"This person is a Finance Director, therefore this must be a senior job."

the methodology considers characteristics of the job itself.

At a high level, the framework considers factors including:

• know-how;
• problem solving; and
• accountability.

The purpose is to create a systematic way of comparing jobs that may otherwise be difficult to compare.

For example, how should an organisation compare:

• Head of Engineering;
• Finance Director;
• Regional Sales Director; and
• Head of Operations?

Their functions are completely different.

Job evaluation provides a common framework for considering their relative organisational weight.

This is fundamentally different from searching a salary survey for four job titles.

Where Mercer fits

Mercer also provides job architecture, job evaluation and market-pricing capabilities.

In day-to-day compensation work, Mercer market data may be used to establish external reference points across a large range of functions and geographies.

The practical workflow might therefore involve identifying:

Job family → job → career level → relevant market → compensation percentile.

For example, an organisation could identify a role as:

Finance → Financial Planning & Analysis → Manager → appropriate management level

and then examine market compensation for the corresponding survey population.

The quality of the resulting benchmark depends heavily on whether the organisation has matched the job and level correctly.

Why Mercer and Korn Ferry levels do not automatically match

This is where compensation teams can run into trouble.

Imagine an organisation receives:

Mercer: Career Level M3

and

Korn Ferry: Grade 18

It can be tempting to create a spreadsheet saying:

Mercer M3 = Korn Ferry Grade 18

and then apply that relationship throughout the organisation.

That can be dangerous.

The two frameworks may classify jobs using different methodologies and definitions.

A crosswalk can be useful operationally, but it should normally be developed by analysing actual jobs rather than assuming that every level has a universal one-to-one equivalent.

In other words:

Similar-looking levels are not necessarily equivalent levels.

A practical example

Consider two Finance Director roles.

Finance Director A

The role:

• manages five employees;
• supports one country;
• reports to the CFO;
• owns budgeting and forecasting;
• has limited strategic decision authority.

Finance Director B

The role:

• manages 40 employees;
• operates across eight countries;
• reports to the Group CFO;
• owns major investment decisions;
• influences enterprise strategy.

Both employees have the title Finance Director.

A title-based benchmarking approach could place them against the same survey job.

A proper job-evaluation exercise would quickly identify that these jobs have substantially different organisational scope.

Market pricing should reflect that difference as well.

This illustrates one of the most important principles in compensation:

Benchmark the job, not the title.

How Mercer and Korn Ferry can produce different salary benchmarks

Even after you have identified apparently comparable jobs, the market figures can differ.

Suppose the results are:

Which number is correct?

Potentially all of them.

The difference could result from several factors.

1. Survey participants

The organisations contributing compensation information may differ between the two datasets.

If one survey contains more large multinational organisations, for example, the resulting benchmark may differ from a dataset containing a broader mix of employers.

2. Job matching

The Mercer survey job selected may not represent exactly the same responsibilities as the Korn Ferry benchmark.

Even small differences in scope can matter at senior levels.

3. Level matching

A Mercer career level and a Korn Ferry job grade should not be treated as equivalent simply because they appear to occupy similar positions within their respective structures.

Always compare the underlying definitions.

4. Market filters

Check whether both datasets use the same:

• country or city;
• industry;
• organisation size;
• revenue category; and
• other relevant peer-group criteria.

A highly filtered technology-company market should not automatically be compared with a broad general-industry market.

5. Compensation definitions

This sounds obvious, but it causes surprisingly large benchmarking errors.

Confirm whether you are looking at:

• base salary;
• actual total cash;
• target total cash;
• short-term incentive;
• long-term incentives; or
• total direct compensation.

A base-salary median from Mercer should not be compared with a total-cash median from Korn Ferry.

6. Effective date

Compensation surveys may represent different effective dates.

If one dataset reflects compensation several months later than another, some difference may simply represent market movement.

Survey data should therefore be aged to a common reference date before comparison where appropriate.

How to compare Mercer and Korn Ferry properly

A practical comparison should start with the methodology rather than the numbers.

For each job, create a simple benchmarking record.

Then review the difference.

For example:

Variance = Korn Ferry P50 ÷ Mercer P50 − 1

If Mercer shows $200,000 and Korn Ferry shows $212,000:

$212,000 ÷ $200,000 − 1 = 6%

A 6% difference does not automatically require action.

The next question is why the difference exists.

Do not automatically average the two surveys

One common response to conflicting market data is:

"Mercer says $200,000 and Korn Ferry says $212,000, so let's use $206,000."

Mathematically, that works.

Methodologically, it may not.

Averaging the numbers assumes that both observations deserve equal weight.

That may not be true.

Suppose Mercer has an excellent job match and a highly relevant participant population, while the Korn Ferry match is relatively broad.

Mercer might deserve greater weight.

Alternatively, the Korn Ferry job evaluation may provide a particularly strong indication of job size while the Mercer match is less precise.

The organisation should understand those differences before creating a blended benchmark.

When a blended market approach can work

Using several survey sources can still be good practice.

The difference is that the methodology should be deliberate.

An organisation might decide:

• Mercer: 50% weighting
• Korn Ferry: 50% weighting

Or:

• Mercer: 70%
• Korn Ferry: 30%

The weighting should reflect factors such as data quality, job match, sample relevance and the organisation's compensation philosophy.

Most importantly, the approach should be consistent.

Changing the weighting from job to job simply because one source produces a preferred answer undermines the credibility of the benchmarking process.

Job evaluation does not determine salary

This distinction is particularly important when working with Korn Ferry Hay grades.

Suppose job evaluation concludes that two roles are of comparable organisational size.

That does not necessarily mean the market pays them the same amount.

Consider:

Job A: Finance Manager

Job B: Cybersecurity Manager

Internally, the jobs might be evaluated at a similar organisational level.

Externally, cybersecurity skills might command a substantial market premium.

This creates the classic tension between:

internal equity and external competitiveness.

Job evaluation helps answer:

How large is this job internally?

Market benchmarking helps answer:

What does the external labour market pay for this capability?

A mature compensation framework considers both.

A useful way to combine job evaluation and market pricing

A practical compensation process might work as follows.

Step 1: Evaluate the job

Determine the relative size and organisational scope of the position.

Step 2: Place it within the job architecture

Identify the appropriate career level or grade.

Step 3: Identify external survey matches

Select appropriate Mercer, Korn Ferry or other market benchmarks.

Step 4: Compare market observations

Review P25, P50 and P75 rather than relying on a single number.

Step 5: Investigate material differences

Check job match, level, market population, compensation definition and effective date.

Step 6: Establish the market reference

Select or blend the most relevant observations according to a documented methodology.

Step 7: Build the salary range

Translate the market reference into an internal salary structure.

Step 8: Position individual employees

Only then consider experience, performance, proficiency, internal equity and other individual factors.

This separates three decisions that organisations frequently mix together:

How big is the job?

What does the market pay for the job?

What should we pay this particular employee?

They are not the same question.

Mercer vs Korn Ferry: which should you use?

There is no universal answer.

Mercer may be particularly useful when an organisation wants broad market-pricing information across functions, industries and geographies.

Korn Ferry may be particularly attractive where an organisation places significant emphasis on formal job evaluation, grading and architecture alongside market compensation data.

Large organisations may use both.

For example, an organisation could use a structured job-evaluation methodology to establish internal job relationships while using multiple salary surveys to validate external market competitiveness.

The choice therefore should not be framed simply as:

Mercer or Korn Ferry?

A better question is:

What compensation decision are we trying to make, and which methodology gives us the strongest evidence for that decision?

Five mistakes to avoid

1. Creating an automatic Mercer-to-Korn-Ferry level crosswalk

Crosswalks can be useful, but validate them against actual jobs.

2. Benchmarking titles instead of job content

A Director in one organisation can be equivalent to a Manager, Senior Director or even VP elsewhere.

3. Assuming job grade equals market value

Internal job size and external scarcity are different concepts.

4. Selecting whichever survey gives the preferred result

The methodology should determine the benchmark, not the desired salary outcome.

5. Treating market median as an employee's required salary

P50 is a statistical market reference, not a rule saying every employee should be paid at P50.

The practical takeaway

Mercer and Korn Ferry can both provide valuable foundations for compensation decisions, but the real value comes from understanding what the data and methodologies are telling you.

When the two produce different results, do not immediately ask:

"Which number should we use?"

First ask:

Are the jobs genuinely comparable?

Are the levels equivalent?

Are we looking at the same labour market?

Are the compensation definitions and effective dates consistent?

Are we measuring internal job size or external market value?

Once those questions are answered, differences between Mercer and Korn Ferry become much easier to interpret.

Ultimately, good salary benchmarking is not about finding the provider with the "right" salary number.

It is about combining job architecture, internal equity and external market evidence into a compensation framework that can be explained, applied consistently and defended.