Promotion and Compensation Conversations

Scenario

Example organisation: a senior engineer asks for promotion to staff. The manager says "maybe next cycle" without specifics. Another engineer discovers a newer colleague earns more for the same role and asks for a raise; the manager says compensation is "confidential" and ends the conversation. Both engineers start interviewing elsewhere.

What you see on the team

• Vague promotion promises ("next cycle", "keep doing what you're doing").
• Promotion cases written at the last minute, based on reputation.
• Pay conversations avoided or shut down.
• Regretted departures over growth or pay.

The common mistake

Treating promotions and pay as topics to avoid until forced, and handling them with vague promises instead of evidence, honesty and a plan.

Why it happens

Managers often lack control over budgets and promotion committees, so they avoid committing. But vagueness feels like evasion; engineers fill the silence with market offers. Data on pay (such as Levels.fyi) is widely available to engineers, so avoiding the topic doesn't keep it private.

The playbook

Promotions

• Use the career ladder: map evidence to the next level's expectations over a sustained period.
• Build the case continuously from your notes; share drafts with the engineer.
• If "not yet": say exactly which dimension is missing, with examples, and agree a plan and timeline you can actually influence.

Promotion case - Staff Engineer (summary)
Scope: led pipeline migration across 12 product teams (Q1-Q3).
Technical: designed self-service deploy kit; 40 services migrated without platform team effort.
Delivery: finished 2 weeks before CI contract end; weekly forecasts to leadership.
People: mentored 2 engineers to own platform components; ran design reviews org-wide.
Evidence links: design doc, ADRs 12-14, migration dashboard, peer feedback (5).

Compensation

• Know your company's pay bands and process; be transparent about what you can and can't share.
• Listen to the concern and collect data (role, level, market data, internal equity).
• Advocate with your manager/HR using data; give a clear answer and timeline.
• Never promise a raise you don't control.

What to say

Promotion "not yet":

"You're clearly at senior and strong on technical depth. For staff, the gap is cross-team scope — so far your projects have been within the platform team. The CI migration touches all twelve product teams; if you lead it, that's the evidence the committee looks for. Let's review progress monthly, and I'll draft the case with you as we go."

Pay concern:

"Thank you for raising it — it's a fair question. I can't share others' salaries, but I can check where you sit in the band for your level and compare with market data. I'll come back to you within two weeks with what I found and what I can do."

Trade-offs

• Transparency is limited by company policy and privacy; be clear about those limits.
• Promising timelines you don't control damages trust; promise actions you do control.
• Retention offers can fix pay but not growth; understand the real reason someone is unhappy.

Signals it's working

• Engineers know where they stand relative to the next level.
• Promotion cases are written with evidence well before committees.
• Pay concerns get a data-based answer within a stated time.
• Fewer regretted departures over growth or pay.

Key points

• Promotions: evidence against the next level, built continuously; specific "not yet" with a plan.
• Pay: know the bands and process, listen, use data, advocate, answer within a stated time.
• Be transparent about limits; never promise what you don't control.
• Understand whether the real issue is pay, growth or something else.