Why Your Job Posting Attracts the Wrong People
Hook: Your job posting says you want a "rockstar engineer who thrives in fast-paced environments." You're getting exactly what you asked for. That's the problem.
Let's read a typical job posting:
We're looking for a senior rockstar engineer to join our fast-paced, dynamic team. You'll wear many hats, move fast, break things, and 10x our productivity. Must have 8+ years of experience and be comfortable with ambiguity.
What does this actually communicate?
"Rockstar" → We want individual heroes, not team players.
"Fast-paced" → We're chaotic and probably understaffed.
"Wear many hats" → We don't have clear roles or boundaries.
"Move fast, break things" → We don't value quality or sustainability.
"10x" → We have unrealistic expectations.
"Comfortable with ambiguity" → We don't know what we're doing.
This posting will attract candidates who thrive in chaos—or are desperate enough to tolerate it. It will repel the people who value craft, sustainability, and thoughtful work.
Your job posting is a filter. Make sure it's filtering for what you actually want.
What Different Archetypes Respond To
Tall Stalks (Systems Thinkers)
They respond to:
- Descriptions of complex systems to think about
- Long-term technical challenges
- Explicit time for design and architecture
- Mention of cross-team influence
They're repelled by:
- "Fast-paced" (suggests no time for thinking)
- "Execution-focused" (suggests no room for design)
- Vague scope (they want to know what systems they'll own)
Nitrogen Fixers (Mentors)
They respond to:
- Explicit mention of mentorship expectations
- Junior team members to develop
- Learning culture descriptions
- Recognition for growing others
They're repelled by:
- "Self-directed individual contributor" (no one to teach)
- All-senior team composition (no one to develop)
- Output-only metrics (teaching is invisible)
Ground Cover (Reliable Executors)
They respond to:
- Clear expectations and scope
- Stable, well-defined work
- Recognition for consistency
- Realistic workload descriptions
They're repelled by:
- "Ambiguity" and "constant change"
- "Wearing many hats"
- Expectation of heroics
- 10x mythology
Pollinators (Connectors)
They respond to:
- Cross-team collaboration description
- Multiple teams to work with
- Travel or remote connection opportunities
- Relationship-building mentioned as valuable
They're repelled by:
- Siloed team descriptions
- "Individual contributor"
- No mention of organizational context
- Head-down work expectations
Deep Roots (Knowledge Holders)
They respond to:
- Long-tenured team descriptions
- Complex systems with history
- Expectation of depth over breadth
- Stability and continuity
They're repelled by:
- "Move fast" (suggests churn)
- Constant pivoting
- Startup volatility
- New stack every year
Fast Growers (High-Potential Juniors)
They respond to:
- Explicit learning opportunities
- Mentorship availability
- Growth path descriptions
- Stretch opportunities
They're repelled by:
- "10+ years experience required"
- No mention of development
- Expectation of hitting ground running
- No visible seniors to learn from
Rewriting the Job Posting
Instead of the generic "rockstar" posting, try archetype-specific language:
For a Nitrogen Fixer Role:
We're looking for a senior engineer who finds meaning in developing others. You'll mentor two junior engineers, lead knowledge-sharing sessions, and help shape our team's learning culture. You'll spend about 30% of your time on direct mentorship, with explicit recognition for the growth of your mentees.
For a Ground Cover Role:
We're looking for a reliable engineer who takes pride in consistent, quality execution. You'll own a core part of our system, maintaining it, improving it incrementally, and ensuring it stays stable as the product scales. We value sustainability over heroics.
For a Tall Stalk Role:
We're looking for a systems thinker who sees patterns across teams. You'll have explicit time (20%+) for design and architecture work, influence over how our systems evolve, and the expectation that you'll think about second-order effects that others miss.
Each of these attracts a different person. That's the point.
The Honesty Principle
The most effective job postings are honest about tradeoffs.
If your company is chaotic, say so—and say who thrives in that chaos. Some people genuinely love it.
If the role is 90% maintenance, say that—and say why maintenance matters and how it's recognized. Some people want exactly that.
If you're early stage with lots of ambiguity, own it—and describe the upside of shaping things from scratch.
Honesty filters effectively. Deception gets people in the door who won't stay.
What Not to Say
"Rockstar" / "Ninja" / "10x" → Signals you value individual heroics over team function.
"Work hard, play hard" → Signals you expect overwork.
"Family" → Signals boundary violations.
"Fast-paced" (without context) → Signals chaos.
"Wear many hats" (without context) → Signals unclear roles.
These aren't inherently bad—but they've been overused to paper over dysfunction. Be specific about what you actually mean.
The Test
Before posting, ask:
Would the person we actually need find this compelling?
If you need a reliable maintainer but your posting reads like you want a startup cowboy, you've already failed.
Would someone read this and know what they're signing up for?
If your posting is generic enough to describe any engineering role, it's not describing your engineering role.
Does this attract the archetype we're missing?
If your team needs a mentor and your posting attracts more lone wolves, your posting is the problem.
Your job posting is often the first filter. Make it work for you, not against you.
Next in series: "The Onboarding That Actually Works"