Technical Depth Scale

Executive summary#

• Technical depth measures how well someone executes work in a specific domain — from basic awareness to expert mastery
• This is a 0-4 scale that is domain-specific: someone can be level 3 in Python and level 1 in Go
• High technical depth (3-4) reduces rework, improves quality, and enables complex problem-solving
• Most delivery failures happen when complexity exceeds technical depth (e.g., assigning level 2 work to level 1 talent)
• Use work samples and technical exercises, not years of experience, to assess depth

Definitions#

Technical Depth: Mastery of core technical skills within a specific domain, including foundational concepts, advanced techniques, tool proficiency, and best practices application.

What it includes: Domain-specific knowledge, tool proficiency, best practices understanding, debugging capability, code quality awareness.

What it does NOT include: Business context awareness, problem ownership (agency), communication skills, or management ability.

Key distinction: Technical depth is domain-specific — a cloud architect might be level 4 in AWS but level 1 in cybersecurity. Always specify the domain when assessing.

Why this matters#

Business impact#

High technical depth (3-4):

• Reduces rework — gets it right the first time, fewer bugs
• Enables complex work — can handle ambiguous, multi-system problems
• Improves delivery speed — knows patterns, doesn't need constant research
• Reduces technical debt — writes maintainable, scalable code

Low technical depth (0-1) assigned to complex work:

• Creates delivery risk — high error rate, requires extensive review
• Slows projects — frequent blockers, needs hand-holding
• Accumulates debt — quick hacks instead of proper solutions
• Frustrates teams — senior engineers spend time fixing issues
• Creates capability gaps — work complexity exceeds team competency, forcing expensive external help

Cost reality#

A level 3 engineer delivers 3-5x the value of a level 1 engineer in the same domain, even if the salary is only 1.5-2x higher.

Why: The level 3 produces working, maintainable solutions. The level 1 produces code that requires senior review, rework, and often rewrites — consuming team capacity.

The Scale (0-4)#

canonical_block: competency_scale
version: 1.0.0
concept_id: scale.technical_0_4
updated_date: 2026-02-16

scale_name: "Technical Depth"
description: "Mastery of core technical skills within a domain, from foundational awareness to expert standard-setting"
range:
  min: 0
  max: 4

levels:
  - level: 0
    label: "No evidence"
    description: "No demonstrated experience or knowledge in this domain"
    observable_signals:
      - "Cannot explain basic concepts in the domain"
      - "No portfolio work or project examples"
      - "Struggles with foundational terminology"
    assessment_method: "Resume screen typically sufficient to identify"
    anti_signals:
      - "Lists domain on resume but cannot discuss it"
      - "Claims years of experience but no concrete examples"

  - level: 1
    label: "Assisted (Foundational)"
    description: "Can complete structured tasks with supervision and reference materials"
    observable_signals:
      - "Completes tasks following clear instructions or examples"
      - "Asks clarifying questions when requirements are ambiguous"
      - "Uses documentation and Stack Overflow effectively"
      - "Produces working code but requires review for edge cases and best practices"
    assessment_method: "Coding exercise with well-defined requirements"
    anti_signals:
      - "Cannot complete basic tasks even with documentation"
      - "Asks about foundational concepts repeatedly"
      - "Code quality issues in every submission"

  - level: 2
    label: "Independent (Proficient)"
    description: "Can complete typical tasks independently with good quality"
    observable_signals:
      - "Delivers working solutions to standard problems without guidance"
      - "Writes clean, maintainable code following team conventions"
      - "Debugs issues systematically without constant help"
      - "Knows when to ask for help vs. solve independently"
    assessment_method: "Work sample review showing independently completed features"
    anti_signals:
      - "Quality is inconsistent (good days and bad days)"
      - "Avoids unfamiliar areas of the codebase"
      - "Solutions work but violate patterns or create maintenance burden"

  - level: 3
    label: "Advanced (Expert)"
    description: "Can solve complex problems, makes architectural decisions, mentors others"
    observable_signals:
      - "Designs solutions for ambiguous, multi-system problems"
      - "Identifies and addresses non-obvious edge cases proactively"
      - "Evaluates trade-offs between multiple valid approaches"
      - "Code reviews catch real issues (not just style)"
      - "Explains complex concepts clearly to less experienced engineers"
    assessment_method: "Architecture review + portfolio of complex problem-solving"
    anti_signals:
      - "Deep in one area but weak in adjacent areas"
      - "Cannot explain decisions in plain language"
      - "Over-engineers simple problems"

  - level: 4
    label: "Architect / Standard-setter"
    description: "Sets technical direction, defines best practices, recognized domain authority"
    observable_signals:
      - "Defines technical standards adopted by team or organization"
      - "Makes strategic technology choices (frameworks, languages, tools)"
      - "Identifies and solves foundational problems affecting multiple teams"
      - "Recognized externally (conference talks, open source contributions, thought leadership)"
      - "Mentors level 3 engineers to become level 4"
    assessment_method: "Track record of strategic impact + external validation"
    anti_signals:
      - "Deep technical knowledge but poor judgment on trade-offs"
      - "Creates complex systems no one else can maintain"
      - "Thought leader on social media but no shipped impact"

How it works#

The technical progression#

Technical depth develops through cycles of learning, practice, and feedback:

Key mechanism: Pattern recognition + judgment#

Technical depth combines:

1. Foundational knowledge — understanding core concepts and principles
2. Pattern recognition — knowing solutions to common problems
3. Tooling proficiency — effective use of frameworks, libraries, and systems
4. Judgment — when to apply standard patterns vs. custom solutions

Example: A level 2 Python engineer knows how to write a web API. A level 3 engineer knows when to use async vs. sync, how to structure for scale, and what trade-offs exist. A level 4 engineer defines the API framework the team uses.

Example: CaseCo Mid#

Key insight: Match technical depth to work complexity. Overstaffing (level 4 doing level 2 work) wastes money. Understaffing (level 1 doing level 3 work) creates delivery risk.

Action: Technical Assessment Framework#

Use this framework for interviews and work sample reviews:

Level 1-2 Assessment (Foundational/Proficient)#

Coding exercise (60-90 minutes):

Task: Build a REST API endpoint that accepts a JSON payload, validates it,
stores data in a database, and returns a confirmation.

Requirements:
- Use [team's language/framework]
- Include input validation
- Handle error cases
- Write basic tests

Evaluation:
- Does it work? (Y/N)
- Code quality: readable, follows conventions?
- Error handling: edge cases covered?
- Tests: meaningful coverage?

Scoring:

• Level 1: Works with prompting, quality issues, incomplete tests
• Level 2: Works independently, clean code, good tests

Level 2-3 Assessment (Proficient/Expert)#

Architecture exercise (90 minutes):

Scenario: Design a real-time notification system for a mobile app with
100K daily active users.

Requirements:
- Users receive push notifications for specific events
- Must handle notification delivery failures
- Should be cost-effective at scale
- Discuss technology choices and trade-offs

Evaluation:
- Architecture: sensible technology choices?
- Trade-offs: identifies pros/cons of approaches?
- Scale: considers costs, failure modes, monitoring?
- Communication: explains decisions clearly?

Scoring:

• Level 2: Functional design but missing scale/cost considerations
• Level 3: Comprehensive design with trade-off analysis

Level 3-4 Assessment (Expert/Architect)#

Portfolio review + strategic discussion:

Review:
1. Show me a complex system you designed
2. What were the key technical decisions?
3. What trade-offs did you make and why?
4. What would you do differently today?

Strategic questions:
1. How do you evaluate new technologies?
2. Describe a time you prevented a major technical problem
3. How do you balance speed vs. quality?
4. How do you mentor less experienced engineers?

Scoring:

• Level 3: Deep technical knowledge, solid judgment, mentors effectively
• Level 4: Strategic vision, sets standards, recognized authority

Pitfalls#

Next#

• Business Scale — Evaluate business context awareness
• Agency Scale — Understand problem ownership
• Complexity & Experience — Match technical depth to work complexity
• Competency Model — See how technical depth combines with business + agency
• Technical Interview Templates — Full assessment exercises and rubrics

What decisions this enables#

• Which technical level to require for a specific project role, based on work complexity not title
• Whether to upskill internally or partner externally when a level gap exists
• How to staff a team across complexity levels to balance cost and delivery risk
• When a senior-titled engineer is actually operating at a lower technical level than the role demands
• How long to budget for domain transfer when moving an engineer to an adjacent technology

FAQs#