A competency map defines what a role must be good at and what separates each level from the one above it. Enter a role, a level and the team's shape to get one: the competencies that matter, four proficiency tiers each, and what moving up a tier actually looks like. Free, no signup.
It answers two questions that otherwise get answered inconsistently: what does this role need to be good at, and what separates someone at this level from the level above. That makes it the backbone of hiring bars, promotion decisions and growth conversations — three things usually decided with three different unwritten standards.
Most frameworks describe competencies well and levels badly, using words like "advanced" and "expert" that mean nothing without behaviour attached. A useful tier says what the person does without help, what they do with support, and what they do not yet do — which is checkable in an interview and in a performance review.
Once levels are defined behaviourally, the hiring bar stops being a feeling. "Tier 3 on system design, tier 2 on incident response" is a bar you can interview against and disagree about productively before a candidate is in the room.
A framework only pays off if interviews actually assess against it. Build a rubric from the competencies, then let AI interviews assess every candidate against the same tiers with evidence attached to each score.
Related: Scorecard generator · Job description generator