The Learning Misconception
In engineering, we often categorize people by tenure: "Junior" (0-2 years), "Senior" (5+ years). But we've all met the "Senior" engineer with 10 years of experience who still needs to be told exactly what to do, and the "Junior" who intuitively understands system design after 18 months. Tenure is a proxy for skill acquisition — and it's a bad one.
The real question is not how long someone has been doing something, but how they process information when solving a problem. Do they reach for a checklist, or do they reach for their intuition?
The Dreyfus Model
In 1980, Stuart and Hubert Dreyfus — a philosopher and a mathematician at UC Berkeley — published research on how humans acquire skills. They studied chess players, pilots, and nurses, and found a consistent pattern: skill development is not a smooth curve. It happens in discrete, qualitatively different stages.
Their central insight: the difference between a beginner and an expert is not just how much they know, but the fundamental nature of how they think.
- Novices rely on strict, context-free rules. "If X, do Y." They need recipes.
- Experts rely on intuition, pattern recognition, and deep contextual awareness. They often cannot fully explain why they made a decision — they just knew.
Understanding this model allows you to tailor how you assign work, write documentation, and structure teams. If you give an Expert a rigid checklist, you insult their intelligence and waste their capability. If you give a Novice a vague goal like "improve system performance," you paralyze them — not because they're lazy, but because they lack the mental scaffolding to decompose the problem.
Interviewers at Staff+ and Engineering Manager levels often ask: "How do you calibrate your communication style across different experience levels on your team?" A strong answer references the principle that novices need rules and recipes while experts need goals and autonomy — and that mismatching the two is a common management failure. Naming the Dreyfus Model signals structured thinking about skill development.