Read time: 7 minutes
TL;DR: Most companies can’t explain why engineers should join them beyond compensation. This constraint exercise forces you to articulate your actual value proposition—or realize you don’t have one yet. When you lead with money, you attract mercenaries. When you lead with challenge, growth, and impact, you attract missionaries. The 10% question reveals which one you’re set up for.
Here’s an exercise I give every hiring manager I work with, and most of them hate it:
“How would you attract engineering talent if every role you’re hiring for paid 10% less than your competitors?”
The immediate response is usually defensive: “But we DO pay competitively!” or “That’s not realistic!”
And they’re right—it’s not realistic. That’s not the point.
The point is that this constraint forces you to answer the one question most companies can’t: Why would a talented engineer actually choose YOUR team?
Not just any tech company. Not just any team that pays market rate. YOUR company specifically.
If you can’t answer that question convincingly, you’re going to lose every hiring battle to someone who can. And throwing more money at the problem won’t save you.
Why This Exercise Reveals Everything
When I work with a company that’s struggling to close candidates, the conversation usually goes like this:
Me: “Tell me why someone should join your team.”
Them: “Well, we offer competitive salary, full benefits, 401k matching, flexible PTO…”
Me: “So does everyone else. What makes you different?”
Them: “We have a great culture, interesting problems, smart people…”
Me: “Can you be more specific?”
Them: [long pause]
That pause is the problem. That’s the gap between “we’re hiring” and “we’re successfully hiring.”
The $5K constraint exercise reveals that gap immediately. Because when you can’t lean on “highest offer wins,” you’re forced to articulate your actual value proposition. And most companies discover they don’t have one.
The Blog Post Challenge
Here’s what I tell hiring managers to do after that exercise:
Write me a blog post about why someone should join your team.
Not HR-approved corporate speak. Not a list of benefits. A real, honest, compelling story about what makes your engineering team special.
Can’t think of anything? That’s your answer. That’s the problem we need to solve before you waste another dollar on job postings.
This isn’t about writing pretty marketing copy. It’s a diagnostic tool. If you can’t articulate why your team is special, how will a recruiter sell it? How will a candidate figure it out during an interview?
What This Exercise Actually Reveals
I’ve run this exercise with dozens of companies. Here’s what usually surfaces:
Company A: “We can’t think of anything compelling. Our tech stack is outdated, our best engineers are frustrated, and honestly we’re not sure why anyone would be excited to join.”
Brutal honesty, but that’s progress. You can’t fix a problem you won’t acknowledge. This company needed to clean house before they could hire—update their stack, address tech debt, and figure out their engineering identity.
Company B: “Our advantage is speed. Engineers can ship features in days that would take months at a big company. We give people autonomy to make architectural decisions without committees.”
Now we’re talking. That’s a real value proposition. Some engineers would pay YOU to work in that environment.
Company C: “We’re solving genuinely hard technical problems in [specific domain]. Most of our engineers were bored at their last jobs. This is where they come to be challenged.”
Perfect. That’s catnip for the right engineer—someone who’s optimization for growth and challenge, not just compensation.
The Three Types of Responses
When companies do this exercise honestly, they fall into three categories:
“We Have Nothing” – Your only pitch is compensation. Tech stack is legacy, GitHub is empty, best engineers are looking to leave. The fix: Build something worth joining before you hire. You can’t recruit your way out of this.
“We Have Something, But We’re Hidden” – You have real advantages—interesting problems, autonomy, great culture—but nobody knows about it. The fix: Make it visible. Start blogging, open source tools, send engineers to speak at conferences.
“We Know Exactly Who We Are” – You can immediately articulate why an engineer would choose you. These companies rarely struggle to hire.
What “Attractive to Talent” Actually Looks Like
Here are real answers from companies who pass the blog post challenge:
Technical Challenge: “We reduced latency from 200ms to 8ms while handling 10x traffic. If you want genuinely hard distributed systems problems, this is it.” → Attracts engineers bored with legacy maintenance.
Ownership: “Our senior engineer designed and shipped our entire recommendation engine in six weeks. No committees, no endless planning. You own it, you ship it.” → Attracts engineers frustrated by bureaucracy.
Technical Growth: “Three mid-level engineers became domain experts this year working on real production problems. No toy projects—you’re building the actual product.” → Attracts engineers who optimize for learning, especially early in their careers.
Culture: “Junior engineers can push back on principal engineers if they have better ideas. The best idea wins, regardless of title.” → Attracts engineers who want to work with smart people who respect them.
Mission: “Engineers get emails from customers explaining how our features changed their lives. That’s not marketing—that’s why we show up.” → Attracts engineers who want their work to matter.
Notice what’s missing? Compensation. Ping-pong tables. Free lunch. These are substantive reasons to choose one company over another. And none of them cost extra money.
The Connection to Hiring Strategy
When you lead with money, you attract people who are motivated by money. When you lead with challenge, growth, and impact, you attract people who are motivated by those things.
The latter group builds better products. They stay longer. They’re more engaged. They’re the missionaries, not mercenaries.
But you can only attract missionaries if you have a mission worth joining.
The 10% constraint exercise forces you to find that mission. Or realize you don’t have one yet.
How to Actually Use This Exercise
If you’re a hiring manager, engineering leader, or founder, here’s how to apply this:
Step 1: Do the constraint exercise
Seriously sit down and answer: “If we paid 10% less than competitors, what would our pitch be?”
If you’re drawing a blank, keep going. The discomfort is the point.
Step 2: Write the blog post
Don’t overthink it. Just write 500-1000 words about why someone should join your engineering team. Be specific. Use real examples.
If you can’t write it, you’ve identified your problem.
Step 3: Reality check it
Show your draft to your best engineers. Ask them: “Is this accurate? Is this what you’d tell someone considering joining us?”
If they say no, you’ve got work to do. If they say yes, you’ve got your narrative.
Step 4: Make it real
Turn that narrative into every hiring touch point:
- Update your job descriptions to focus on challenge and growth, not just requirements
- Train your recruiters to lead with mission and impact, not compensation
- Create content that proves your claims (engineering blog, open source, conference talks)
- Make sure your interview process reinforces what you’re promising
Step 5: Measure it
Track whether candidates are choosing you over higher offers. If they’re not, your narrative isn’t compelling enough yet.
The Point Isn’t to Underpay People
Let me be crystal clear: this exercise is not an excuse to lowball candidates.
You should absolutely pay people competitively. If your compensation isn’t in the ballpark of market rate, none of this matters. Money is the table stakes.
But here’s the reality: there’s always someone who can pay more than you. Always.
Even if you’re Google, there’s a hedge fund or a hot startup flush with VC money that will outbid you. You cannot win every hiring battle on compensation alone.
You need to give people a reason to choose you beyond the paycheck. That’s what this exercise uncovers.
When compensation becomes your primary recruiting message, you’re advertising that the work itself isn’t compelling enough. You’re building a team of mercenaries, not missionaries. Understanding what actually motivates candidates is the difference between closing offers and losing talent.
What Success Looks Like
When you’ve done this work successfully, recruiting changes:
- Candidates ask thoughtful questions about technical challenges, not just compensation
- Engineers take your offer even when they have higher competing offers
- Your recruiters can close candidates based on fit and mission, not just money
- Your best people recruit their talented friends because they’re genuinely excited about the work
- Your interview-to-offer acceptance rate improves dramatically
Most importantly, you stop feeling like you’re begging talented people to join you. Instead, you’re having conversations about mutual fit—about whether this opportunity aligns with where they want to go in their career.
That’s when recruiting stops being a battle and starts being a conversation.
The Bottom Line
Before you post another job description, before you raise your salary bands again, before you complain about how impossible it is to hire engineers in 2026—do this exercise.
Answer the question: “Why would someone join us if we paid 10% less?”
If you can’t answer it convincingly, you don’t have a hiring problem. You have a “being worth joining” problem.
And no amount of money will fix that.
The good news? Once you solve it, recruiting becomes exponentially easier. You start attracting people who want to be there, not people who are just chasing the highest offer.
Those are the people who build great companies.
