Define clear job leveling rubrics from junior to lead

Convert flat role descriptions into a distinct, four-tier behavioral competency rubric. Paste your raw role duties to build transparent career growth paths.

You getRole Competency Matrix, level-by-Level Behavioral Anchors and common Failure Modes / Anti-Patterns for each tier

Prompt

Prompt
Act as a compensation and talent development specialist. Using the role description provided below, construct a rigorous role-leveling rubric across four progressive tiers: Junior (L1), Mid-Level (L2), Senior (L3), and Lead (L4).

- Clarify expectations using observable behaviors, scope of ownership, and autonomy rather than years of experience.
- Map competencies across four universal dimensions: Execution & Autonomy, Problem Complexity, Influence & Collaboration, and Strategic Impact.
- Include explicit "what good looks like" indicators and anti-patterns for each level to prevent subjective evaluation.
- Ensure each tier represents a measurable shift in scope: from task delivery to system ownership to organizational leadership.

Output format:
1. Role Competency Matrix (Markdown table: Level, Scope Summary, Execution, Collaboration, Strategic Impact)
2. Level-by-Level Behavioral Anchors (detailed bullet points of expected behaviors)
3. Common Failure Modes / Anti-Patterns for each tier

Role details are below:

Example output

Example for: Software Engineer job description

1. Role Competency Matrix
LevelScope SummaryExecution & AutonomyInfluence & CollaborationStrategic Impact
L1 (Junior)Well-defined tasksRequires task-level guidance; follows coding standardsCollaborates within immediate sprint teamFocuses on personal productivity and code quality
L2 (Mid)Defined featuresIndependent on user stories; manages ambiguity within a featurePartners across engineering and design directlyImproves service reliability and velocity of the squad
L3 (Senior)Multi-team systemsLeads system architecture; resolves unblocked technical problemsMentors junior engineers; aligns roadmap with ProductDrives technical decisions that reduce broad tech debt
L4 (Lead)Org-wide initiativesSets technical vision; handles ambiguous cross-org architectureInfluences staff leaders and unblocks multiple squadsAligns technology choices with multi-quarter business goals
2. Level-by-Level Behavioral Anchors
  • Junior (L1): Writes clean, unit-tested code. Flags blockers in daily standups promptly. Proactively reviews team pull requests to learn patterns.
  • Mid-Level (L2): Breaks down medium features into actionable tasks. Handles bugs in production without direct supervision. Proactively communicates timeline risks.
  • Senior (L3): Designs resilient systems handling edge cases. Authors clear architectural decision records (ADRs). Solves root-cause operational issues and conducts thorough peer reviews.
  • Lead (L4): Identifies architecture bottlenecks before they impact business metrics. Drives consensus across disagreeing leads. Mentors L2/L3 engineers toward promotion.
3. Common Anti-Patterns
  • L1: Spinning wheels alone for days instead of asking for help after 30 minutes of being blocked.
  • L2: Delivering isolated features without testing interactions across integrated upstream services.
  • L3: Over-engineering complex solutions to simple problems without weighing business delivery speed.
  • L4: Acting as an architectural gatekeeper who slows down team momentum instead of empowering teams.
Written by AI from this prompt. Your results will vary.

Paste your job description, current responsibilities, and department context right after the prompt text in ChatGPT, Claude, or Gemini. Ask to align it with your specific review cycles afterwards.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in HR & Management
HR & Management

Run a structured midpoint intern review

Run a clear 45-minute midpoint feedback conversation with an intern. Identifies key accomplishments, course corrections, and skill milestones before the final evaluation.