Child Case | HR AI Case
Compensation Case Deep Dive
From Market Data to Decision
This is the kind of case where the number is easy to defend externally, but harder to absorb internally.
Context
RoleSoftware Engineer (Mid)
LocationBudapest
Proposed Salary€48,000
Why This Case Matters
On its own, the offer looks fine. The real question is whether HR can still defend it once peers are taken into account.
Market Benchmark
P25€38,000
Median€45,000
P75€52,000
Compa-ratio1.07
Reading
The offer is 7% above market median but still below P75. Externally, that is a credible number.
Market Positioning
Offer vs Market Range
P25 €38k
Median €45k
P75 €52k
Offer €48k
The offer lands above the median and below the upper quartile, which places it in a competitive but not extreme market position.
Compa-ratio 1.07 = 7% above median
Internal Context
Internal Range€40,000 – €50,000
Peer Average€44,000
Gap vs Peers+€4,000
Reading
The offer is within range, but already above peer average. That is where the case becomes difficult.
Where The Tension Sits
External View
The offer works
The number is above median, below P75, and still inside a reasonable market band.
Internal View
The offer creates pressure
The same number is already ahead of similar peers, so approval would make pay explanation harder later.
Why This Matters
This is not a market problem. It is a consistency problem. That is why the case is harder than the benchmark table suggests.
Decision Framing
Decision Options
Path A
Protect structure now
Adjust the offer downward slightly and keep the case closer to current peer positioning.
Path B
Prioritize hiring speed now
Keep the offer, but accept that HR may need to revisit peer positioning afterward.
My Lean
I would present this as a trade-off, not a single right answer. The question is which consequence the company is more willing to own.
Key Insight
The challenge is not the number itself. The challenge is what that number does to internal equity once it enters the system.