Hire on a shared rubric, not on yesterday's gut feel.
Define what good looks like for every role and level, then rate every interview against the same matrix. Stop debating impressions — start hiring with the evidence in hand.
| Competency | Junior | Mid | Senior | Lead |
|---|---|---|---|---|
| System design | Observes design discussions | Designs single components | Designs end-to-end systems | Sets architectural direction |
| Code quality | Follows existing patterns | Reviews PRs with intent | Mentors team on standards | Owns long-term codebase health |
| Communication | Asks clarifying questions | Speaks up in design reviews | Leads cross-team discussions | Influences org-wide direction |
Per-role matrix — rows are competencies, columns are levels.
The choice
From gut feel to a rubric your team shares.
Most hiring debriefs are stories: who liked the candidate, who didn't, and why. Competency hiring replaces the story with a grid — the same competencies, the same levels, every interview.
Hiring by gut feel
- Debriefs replay impressions instead of evidence.
- Two interviewers rate the same answer three levels apart.
- The bar shifts by mood, by week, or by whoever was loudest in the room.
- New hires miss the signals that mattered six months in.
Hiring by competency
- Every interview rates the same competencies against the same level descriptions.
- Disagreements surface against the rubric, not against each other.
- The bar is a written artifact you can show, not a feeling you defend.
- New interviewers calibrate on day one against the same matrix.
The matrix
One matrix per role, owned by the team that hires for it.
Each job role gets its own grid. Rows are the competencies you care about for that role; columns are the levels you hire at. Every cell describes what good looks like — in plain language your interviewers actually use.
| Competency | Junior | Mid | Senior | Lead |
|---|---|---|---|---|
| System design | Observes design discussions | Designs single components | Designs end-to-end systems | Sets architectural direction |
| Code quality | Follows existing patterns | Reviews PRs with intent | Mentors team on standards | Owns long-term codebase health |
| Communication | Asks clarifying questions | Speaks up in design reviews | Leads cross-team discussions | Influences org-wide direction |
Per-role matrix — rows are competencies, columns are levels.
Per-role, not per-org
Backend, frontend, design, and PM all hire on different things. Each role owns its rubric and its level descriptions.
Concrete level descriptions
No vague labels — every cell carries a one-line description of the expected behavior at that level.
The same rubric for every interviewer
When two interviewers disagree, they argue against the rubric — not against each other's memory of the room.
The walkthrough
From interview to scorecard in one workflow.
Every interview rates the candidate against the competencies in the matrix. The scorecard rolls those ratings up across every phase of the pipeline.
- 1
Tag questions with competencies
Each question in your library is tagged with the competencies it tests, so the scorecard can roll ratings up by competency.
- 2
Rate against a shared scale
Interviewers rate each answer on the scoring scale your team agreed on, with the matrix as the rubric you calibrate against.
- 3
Scorecards roll the matrix up
Every phase contributes to a single competency-level rollup — one scorecard, every interviewer's evidence.
The payoff
Calibration that compounds with every hire.
The matrix is a living artifact. New interviewers calibrate against the same grid your senior team already uses. After-the-fact calibration sessions argue against rows and columns, not against memories — and the bar gets sharper the more you hire.
Onboard interviewers in days, not quarters
New interviewers read the matrix, shadow two interviews, and they're calibrated — because the bar is written down.
Defend every decision with the receipts
Performance reviews, leveling decisions, and even legal challenges have a paper trail back to the rubric the team agreed on.
Ready to hire on a shared rubric?
Build your first competency matrix in under 10 minutes — every interview gets sharper from the next one on.
Free forever for the first hiring seat. No credit card required.