Hiring and leveling shape your team for years, not just this quarter. One weak hire multiplies on-call load and review debt. A fuzzy ladder turns promos into politics. You do not need to run HR to run a fair, high-signal eng process.
Treat hiring like product work. The role is the problem, the scorecard is the acceptance test, the loop is the UX, and onboarding is activation. Treat leveling as a shared language for scope, not a personality contest.
Role design before the job post
- Name the outcomes the seat must own in 6-12 months.
- List must-have skills vs teachable skills.
- Decide level band (e.g. mid/senior) and why the work needs that altitude.
- Write a one-page scorecard: 4-6 attributes with observable signals.
- Align with your manager on headcount, timeline, and compensation constraints early.
Problem decomposition, code quality under time pressure, collaboration, ownership, system design judgment, and communication. Each needs a strong / mixed / weak signal definition.
Hiring loop that produces signal
Debriefs should start from evidence: In the design prompt they skipped failure modes beats felt junior. The hiring manager (often you) is responsible for calibration and bias checks: who got the benefit of the doubt, and why?
- Screen for motivation and basics; do not burn panel time on obvious mismatches.
- One structured coding or work-sample session tied to real work shape.
- One design or architecture conversation for senior+ seats.
- One values / collaboration interview with concrete scenarios.
- Same core questions per candidate at a level so comparisons are fair.
- Written feedback within 24 hours using the scorecard, not vibes.
Leveling and career ladders
A useful ladder describes scope of impact, ambiguity handled, and influence radius. It should not be a checklist of buzzwords. Map your company ladder to plain language your team can use in 1:1s.
- Junior: delivers well-scoped tasks with guidance; learns systems.
- Mid: owns features end-to-end; reliable reviews; mentors informally.
- Senior: multi-sprint outcomes; design judgment; unblocks others.
- Staff+: multi-team or multi-quarter technical direction; multiplies org.
- Lead/EM: people + delivery systems; hiring; cross-functional outcomes.
- Publish what meets vs exceeds looks like for the next cycle.
- Separate promotion evidence (sustained scope) from stretch assignments (temporary).
- Never surprise someone in calibration: ongoing feedback first.
- Document promo packets with outcomes, not only activity lists.
Growth conversations and tough calls
Not every strong IC wants management. Offer dual paths when your org supports them. When performance gaps appear, use written expectations, support, and timelines. Avoid indefinite almost-there limbo.
You hire systems of work, not heroes. Level people for the problems you need solved next year.
Would you defend this hire/promo decision with the same evidence if the candidate background were different? If not, fix the process before the decision.