The Interview That Finds Archetypes
Your interviews test whether candidates can code. They don't test whether candidates will make your team better. Here's how to fix that.
Standard tech interviews have a problem.
They test algorithmic thinking on a whiteboard. They test whether candidates can invert a binary tree, reverse a linked list, or implement breadth-first search under pressure.
These tests identify people who can... invert binary trees under pressure.
Is that what you actually need?
What Standard Interviews Miss
They miss collaborative ability. Most software is built by teams. Standard interviews are individual performances. Someone who aces a solo whiteboard challenge might be terrible to work with. They miss teaching ability. Nitrogen Fixers are invaluable, but nothing in a standard interview tests whether a candidate can explain things clearly or develop others. They miss systems thinking. Tall Stalks see patterns across systems. Whiteboard algorithms test thinking within a single function, not across architectures. They miss reliability. Ground Cover provides consistent, dependable execution. Standard interviews favor cleverness over reliability. They miss connection skills. Pollinators thrive by building relationships across teams. No part of a standard interview tests this. They miss institutional knowledge potential. Deep Roots accumulate expertise over years. Standard interviews test current knowledge, not capacity to develop depth. They miss growth velocity. Fast Growers are valuable for how quickly they learn. Standard interviews test what they've already learned.
Interviewing for Archetypes
Here's how to add archetype detection to your interview process:
For Tall Stalks (Systems Thinkers)
The prompt: "Tell me about a time you identified a systemic problem that looked like individual incidents." What you're looking for: Can they zoom out? Do they see patterns across teams or systems? Do they think about second-order effects? Alternative: Give them a real architectural problem from your company. Don't ask them to solve it—ask them to describe how they'd approach understanding it.
For Nitrogen Fixers (Mentors)
The prompt: "Teach me something you know well. Assume I know nothing about it." What you're looking for: Do they adjust to your level? Do they check for understanding? Do they find joy in the teaching itself? Alternative: Ask about times they helped someone grow. Watch whether they light up describing it or treat it as duty.
For Ground Cover (Reliable Executors)
The prompt: "Tell me about a long-running project you maintained. How did you stay engaged over time?" What you're looking for: Do they take pride in maintenance work? Do they understand the value of consistency? Do they have staying power? Alternative: Pair programming on a real, unglamorous bug from your codebase. Watch whether they approach it with care or impatience.
For Pollinators (Connectors)
The prompt: "Describe a time you helped two teams or people who didn't know they needed each other find each other." What you're looking for: Do they naturally create connections? Do they remember people and contexts? Do they get energy from bridging gaps? Alternative: In the interview day, introduce them to several people. Watch whether they ask questions and make connections, or just perform.
For Deep Roots (Knowledge Holders)
The prompt: "Tell me about a system you knew better than anyone else. How did you get there? How did you share that knowledge?" What you're looking for: Do they have the patience for depth? Do they document and transfer, or hoard and bottleneck? Alternative: Ask about something they've spent years understanding. Watch for depth and care in the explanation.
For Fast Growers (High-Potential Juniors)
The prompt: "What's something you learned recently that changed how you think? How did you learn it?" What you're looking for: Learning velocity. Meta-learning awareness. Ability to describe their own growth. Alternative: Give them a problem in a domain they don't know. Watch how quickly they orient and what questions they ask.
The Mixed Interview
Best practice: include archetype questions alongside technical assessment, not instead of it.
A complete interview process might include:
1. Technical screen (can they code?)
2. System design (can they think architecturally?)
3. Archetype interview (what role will they play on the team?)
4. Culture interview (will they thrive here?)
The archetype interview should be conducted by someone who understands what you're actually looking for—not just "does this person seem smart?"
Watching for Fit, Not Just Quality
Remember: you're not just assessing whether someone is "good." You're assessing whether they fill a gap in your ecosystem.
A brilliant Tall Stalk is still a bad hire if your team already has three architects and no implementers.
A "merely competent" Ground Cover might be exactly what you need—someone who will reliably do the work that's piling up.
Quality matters. Fit matters more.
The Culture Signal
What you interview for signals what you value.
If you only test algorithmic coding, you're signaling: we value algorithm skills.
If you test teaching ability, you're signaling: we value knowledge transfer.
If you test systems thinking, you're signaling: we value seeing the whole.
The interview is a message to candidates about who you are. Make sure it's sending the right one.
Calibrating the Process
After implementing archetype interviews:
Track outcomes. Did people you hired as Nitrogen Fixers actually mentor? Did predicted Fast Growers actually grow quickly? Calibrate your detection over time. Train interviewers. Archetype detection requires different skills than technical assessment. Invest in training interviewers to see these qualities. Adjust weighting. How much should archetype fit matter versus raw technical skill? This depends on your team's current composition. There's no universal answer.
The Goal
The goal isn't to put people in boxes. People are complex; archetypes are simplified models.
The goal is to think about hiring as ecosystem building rather than talent accumulation.
You're not just asking "is this person good?" You're asking "does this person make our team better?"
That's a different question—and it requires a different interview.
Next in series: "Why Your Job Posting Attracts the Wrong People"