Hiring for Polyculture: Beyond the Senior Engineer Fetish
Hook: Your hiring strategy is "hire the best senior engineers we can afford." It's also why your team is dysfunctional. Here's a better way.
Let's talk about the most common hiring mistake in tech.
Company has growth. Company needs engineers. Recruiter says: "What level are we hiring for?" Manager says: "Senior. We need senior engineers. The more senior, the better."
This is how you build a team that looks great on paper and fails in practice.
The Senior Fetish
Everyone wants senior engineers. They're "better." They need less management. They hit the ground running. They're... senior.
The result? Teams that are all seniors.
And teams that are all seniors are dysfunctional in predictable ways:
Nobody wants to do the "basic" work. Seniors want "senior-level" problems. But most work isn't senior-level. It's just... work. When everyone's senior, the basic work feels beneath everyone.
Everyone wants to lead. Seniors are often hired for their leadership potential. Put six leaders in a room with no followers and watch the conflicts multiply.
There's no one to mentor. Seniors often find meaning in developing others. Without juniors, that avenue is closed. Meaning disappears.
Costs explode. Senior engineers are expensive. A team of eight seniors costs more than a polyculture of three seniors, three mid-levels, and two juniors—and often produces less.
Homogeneity increases. "Senior" often means "10+ years of specific experience." That filters for a narrow demographic with narrow experiences, limiting diversity of thought.
The Polyculture Alternative
Instead of "hire the most senior engineers possible," try: "hire for ecosystem completeness."
A polyculture team might look like:
- 1-2 Tall Stalks (systems thinkers, architects)
- 1-2 Nitrogen Fixers (mentors, teachers)
- 2-3 Ground Cover (reliable executors)
- 1 Pollinator (cross-team connector)
- 1 Deep Root (institutional knowledge holder)
- 1-2 Fast Growers (high-potential juniors)
This mix is intentional. Each archetype provides what others lack:
- Seniors provide experience; juniors provide fresh eyes
- Architects provide vision; implementers provide reality checks
- Mentors provide development; learners provide meaning
The ecosystem is healthier than the monoculture.
How to Hire for Polyculture
1. Assess your current mix. Before hiring, map your current team to archetypes. What do you have too much of? What's missing?
2. Hire for gaps, not prestige. If you have five architects and zero mentors, don't hire another architect just because they're impressive. Hire the mentor you actually need.
3. Define roles by contribution, not level. Instead of "Senior Engineer," define what you actually need: "Someone who can mentor juniors and simplify complex systems." That might be a senior, or it might be a mid-level with teaching skills.
4. Value growth potential. Fast Growers aren't senior yet—but they will be. Hiring for potential, not just current capability, builds long-term strength.
5. Interview for archetype, not just skill. Technical interviews test technical skill. Add interviews that test: systems thinking (Tall Stalk), teaching ability (Nitrogen Fixer), reliability (Ground Cover), connection skills (Pollinator), depth (Deep Root), growth velocity (Fast Grower).
The Uncomfortable Questions
Before your next hire, ask:
Do we actually need another senior? Or do we need someone who will do the work seniors don't want to do?
What archetype is our weakest? And is this hire going to address that weakness, or reinforce our existing strengths?
Can our current team absorb this hire? Adding a senior to a team that can't give them interesting problems is a waste. Adding a junior to a team with no mentors is cruel.
Are we hiring for prestige or for function? Senior hires look impressive. Polyculture hires work.
The Diversity Connection
Polyculture hiring often increases demographic diversity as a side effect.
Here's why: "Senior engineer with 10+ years of specific experience" filters for people who've had specific career paths. Those career paths have historically been more available to some demographics than others.
"Person who can mentor effectively" or "person growing rapidly" or "person who connects teams well"—these filters are less correlated with traditional career paths. They open doors to people who took different routes.
Polyculture doesn't replace intentional diversity efforts. But it often amplifies them.
The ROI of Juniors
Here's a number that might surprise you:
A healthy polyculture with two juniors often produces more than an all-senior team of the same size.
Why?
- Juniors handle the work that seniors find beneath them
- Seniors are more engaged when they have people to mentor
- Fresh perspectives catch problems that experienced eyes miss
- Lower cost means larger teams for the same budget
- Fast Growers become valuable quickly and stay longer
Juniors aren't a burden. They're an investment—if you create the conditions for them to thrive.
The Hiring Mindset Shift
Old mindset: "Get the best individuals we can afford."
New mindset: "Build the healthiest ecosystem we can design."
The first mindset optimizes for individual talent. The second optimizes for collective function.
Talent matters. But talent composition matters more.
Build a polyculture.
Next in series: "The Interview That Finds Archetypes"