{"id":680,"date":"2025-12-07T19:40:23","date_gmt":"2025-12-07T19:40:23","guid":{"rendered":"https:\/\/blog.boldprofiles.com\/?p=680"},"modified":"2026-03-22T03:57:38","modified_gmt":"2026-03-22T03:57:38","slug":"how-to-hire-engineers-when-you-cant-compete-on-salary","status":"publish","type":"post","link":"https:\/\/boldprofiles.com\/blog\/how-to-hire-engineers-when-you-cant-compete-on-salary\/","title":{"rendered":"How to Hire Engineers When You Can\u2019t Compete on Salary"},"content":{"rendered":"\n

Read time: 7 minutes<\/em><\/p>\n\n\n\n

TL;DR:<\/strong> Most companies can’t explain why engineers should join them beyond compensation. This constraint exercise forces you to articulate your actual value proposition\u2014or 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.<\/p>\n\n\n\n

\n\n\n\n

Here’s an exercise I give every hiring manager I work with, and most of them hate it:<\/p>\n\n\n\n

“How would you attract engineering talent if every role you’re hiring for paid 10% less than your competitors?”<\/strong><\/p>\n\n\n\n

The immediate response is usually defensive: “But we DO pay competitively!” or “That’s not realistic!”<\/p>\n\n\n\n

And they’re right\u2014it’s not realistic. That’s not the point.<\/p>\n\n\n\n

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?<\/em><\/p>\n\n\n\n

Not just any tech company. Not just any team that pays market rate. YOUR company specifically.<\/p>\n\n\n\n

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<\/a>.<\/p>\n\n\n\n

Why This Exercise Reveals Everything<\/h2>\n\n\n\n

When I work with a company that’s struggling to close candidates, the conversation usually goes like this:<\/p>\n\n\n\n

Me:<\/strong> “Tell me why someone should join your team.”<\/p>\n\n\n\n

Them:<\/strong> “Well, we offer competitive salary, full benefits, 401k matching, flexible PTO…”<\/p>\n\n\n\n

Me:<\/strong> “So does everyone else. What makes you different?”<\/p>\n\n\n\n

Them:<\/strong> “We have a great culture, interesting problems, smart people…”<\/p>\n\n\n\n

Me:<\/strong> “Can you be more specific?”<\/p>\n\n\n\n

Them:<\/strong> [long pause]<\/em><\/p>\n\n\n\n

That pause is the problem. That’s the gap between “we’re hiring” and “we’re successfully hiring.”<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

The Blog Post Challenge<\/h2>\n\n\n\n

Here’s what I tell hiring managers to do after that exercise:<\/p>\n\n\n\n

Write me a blog post about why someone should join your team.<\/strong><\/p>\n\n\n\n

Not HR-approved corporate speak. Not a list of benefits. A real, honest, compelling story about what makes your engineering team special.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

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?<\/p>\n\n\n\n

What This Exercise Actually Reveals<\/h3>\n\n\n\n

I’ve run this exercise with dozens of companies. Here’s what usually surfaces:<\/p>\n\n\n\n

Company A:<\/strong> “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.”<\/p>\n\n\n\n

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\u2014update their stack, address tech debt, and figure out their engineering identity.<\/p>\n\n\n\n

Company B:<\/strong> “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.”<\/p>\n\n\n\n

Now we’re talking. That’s a real value proposition. Some engineers would pay YOU to work in that environment.<\/p>\n\n\n\n

Company C:<\/strong> “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.”<\/p>\n\n\n\n

Perfect. That’s catnip for the right engineer\u2014someone who’s optimization for growth and challenge, not just compensation.<\/p>\n\n\n\n

The Three Types of Responses<\/h2>\n\n\n\n

When companies do this exercise honestly, they fall into three categories:<\/p>\n\n\n\n

“We Have Nothing”<\/strong> – Your only pitch is compensation. Tech stack is legacy, GitHub is empty, best engineers are looking to leave. The fix:<\/em> Build something worth joining before you hire. You can’t recruit your way out of this.<\/p>\n\n\n\n

“We Have Something, But We’re Hidden”<\/strong> – You have real advantages\u2014interesting problems, autonomy, great culture\u2014but nobody knows about it. The fix:<\/em> Make it visible. Start blogging, open source tools, send engineers to speak at conferences.<\/p>\n\n\n\n

“We Know Exactly Who We Are”<\/strong> – You can immediately articulate why an engineer would choose you. These companies rarely struggle to hire.<\/p>\n\n\n\n

What “Attractive to Talent” Actually Looks Like<\/h2>\n\n\n\n

Here are real answers from companies who pass the blog post challenge:<\/p>\n\n\n\n

Technical Challenge:<\/strong> “We reduced latency from 200ms to 8ms while handling 10x traffic. If you want genuinely hard distributed systems problems, this is it.” \u2192 Attracts engineers bored with legacy maintenance.<\/p>\n\n\n\n

Ownership:<\/strong> “Our senior engineer designed and shipped our entire recommendation engine in six weeks. No committees, no endless planning. You own it, you ship it.” \u2192 Attracts engineers frustrated by bureaucracy.<\/p>\n\n\n\n

Technical Growth:<\/strong> “Three mid-level engineers became domain experts this year working on real production problems. No toy projects\u2014you’re building the actual product.” \u2192 Attracts engineers who optimize for learning, especially early in their careers.<\/p>\n\n\n\n

Culture:<\/strong> “Junior engineers can push back on principal engineers if they have better ideas. The best idea wins, regardless of title.” \u2192 Attracts engineers who want to work with smart people who respect them.<\/p>\n\n\n\n

Mission:<\/strong> “Engineers get emails from customers explaining how our features changed their lives. That’s not marketing\u2014that’s why we show up.” \u2192 Attracts engineers who want their work to matter.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

The Connection to Hiring Strategy<\/h2>\n\n\n\n

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.<\/p>\n\n\n\n

The latter group builds better products. They stay longer. They’re more engaged. They’re the missionaries, not mercenaries.<\/p>\n\n\n\n

But you can only attract missionaries if you have a mission worth joining.<\/p>\n\n\n\n

The 10% constraint exercise forces you to find that mission. Or realize you don’t have one yet.<\/p>\n\n\n\n

How to Actually Use This Exercise<\/h2>\n\n\n\n

If you’re a hiring manager, engineering leader, or founder, here’s how to apply this:<\/p>\n\n\n\n

Step 1: Do the constraint exercise<\/strong><\/p>\n\n\n\n

Seriously sit down and answer: “If we paid 10% less than competitors, what would our pitch be?”<\/p>\n\n\n\n

If you’re drawing a blank, keep going. The discomfort is the point.<\/p>\n\n\n\n

Step 2: Write the blog post<\/strong><\/p>\n\n\n\n

Don’t overthink it. Just write 500-1000 words about why someone should join your engineering team. Be specific. Use real examples.<\/p>\n\n\n\n

If you can’t write it, you’ve identified your problem.<\/p>\n\n\n\n

Step 3: Reality check it<\/strong><\/p>\n\n\n\n

Show your draft to your best engineers. Ask them: “Is this accurate? Is this what you’d tell someone considering joining us?”<\/p>\n\n\n\n

If they say no, you’ve got work to do. If they say yes, you’ve got your narrative.<\/p>\n\n\n\n

Step 4: Make it real<\/strong><\/p>\n\n\n\n

Turn that narrative into every hiring touch point:<\/p>\n\n\n\n