Pay Compression After Twelve Months of Negotiated Offers
A 380-person software company has grown from 90 to 380 employees in four years. Pay has never been structured: each offer was negotiated individually by the hiring manager and approved by the CEO. In the past 12 months the company hired 14 senior engineers at market rate, and several tenured engineers at the same level now earn 8–15% less than the people they mentor. Two tenured engineers resigned in the last quarter; both cited pay in exit interviews, and one named a new hire's salary. A pulse survey shows 41% favourable on "my pay is fair for my work" against a 68% external benchmark. The CFO has approved a 3.2% merit budget for the coming year, while market data for engineering roles shows 4.5% movement. Annual payroll is $9.8M, and there is no job architecture, no salary ranges and no documented pay decision criteria. The CEO is wary of creating an entitlement culture and wants any fix to be self-funding.
1. The CEO will approve only the 3.2% merit budget. How do you allocate it, and what makes the allocation defensible?
Read the worked answer
Do not spread 3.2% evenly. A flat increase preserves the compression exactly, spends the whole budget and fixes nothing.
Diagnose the shape of the problem. Compression here is concentrated: engineers at the same level, doing comparable work, with an 8–15% gap. That is a retention and equal-pay exposure, not a morale issue, and it justifies targeted money rather than general money.
Allocation. Carve out roughly 1.5–2.0 points of the 3.2 for named adjustments: engineers more than 5% below the midpoint of their level who are rated at or above expectations. Fund the remainder (1.2–1.7 points) as merit for everyone else. Where the pool falls short, use vacancy savings and the recruiting budget - replacing one senior engineer typically consumes 50–100% of annual salary in agency fees, hiring-manager time and ramp.
Make it defensible. Write the criteria down before managers see the list; require a one-line rationale per adjustment; do not let managers negotiate individual amounts, because negotiation is what created the problem. Publish ranges for the next hiring cycle so new offers stop re-opening the gap.
What not to do. Do not cut new hires' pay, do not promise retroactive correction, and do not label an internal adjustment a market movement unless it is benchmarked.
2. How do you communicate the outcome to tenured engineers whose adjustment is smaller than they hoped, without disclosing other people's pay or promising next year?
Read the worked answer
Communicate the framework, not the spreadsheet. Managers deliver the message, briefed with a one-page script and an FAQ, in the same week across all teams so no group hears it second-hand.
What to say. The company has moved to defined levels and ranges; pay decisions now follow documented criteria; this cycle closes part of the gap and the remainder is addressed through the normal review cycle as market data and budget allow. State plainly that you will not discuss any individual's pay, including the person they are comparing themselves to, and hold that line consistently.
What not to say. Do not promise a correction date, do not confirm or deny a rumoured new-hire salary, and do not apologise in a way that implies the adjustment was arbitrary. Anyone who believes their pay is wrong needs a route: a review request with a documented process and a response deadline.
Handle the leak directly. Assume the new hire's salary is already known. Denying it destroys credibility; confirming it breaches confidentiality. The defensible position is that some recent offers were above the internal rate, that this is exactly what the adjustment addresses, and that future offers will sit inside published ranges.
3. What evidence would you assemble to return to the CFO for additional funding in the next cycle?
Read the worked answer
Build the case in the CFO's language: cost avoided, not fairness asserted.
Cost of the status quo. Regretted engineering attrition over 24 months - headcount, average time-to-fill, agency and referral spend per replacement, and estimated productivity loss (typically three to six months to full contribution at senior level). Anchor it with the two recent resignations as realised cost, not forecast.
Exposure. Count of employees below range minimum by level and by demographic category. Where pay transparency or equal-pay reporting obligations apply, quantify disclosure risk and the remediation timeline; compression concentrated in a protected category carries disproportionate cost.
Forward cost. Model three scenarios - full correction now, phased over two cycles, do nothing - with the turnover assumption stated explicitly, and show the break-even point: how many avoided resignations fund the adjustment.
Precedent. Market movement of 4.5% against a 3.2% budget means the gap compounds annually if left alone; the cheapest cycle to fix it is this one.
One page, one recommendation, one number. Appendices carry the detail.