Let me tell you about two very different hiring experiences that perfectly capture what’s broken\u2014and what actually works\u2014in startup recruiting.<\/p>\n
Company A: A seed-stage Web3 startup hired 3 exceptional engineers (two MIT grads, one CMU) in under 30 days. No job description. Website still under construction. Zero algorithmic brain teasers.<\/p>\n
Company B: Spent 6 months “searching for the perfect candidate” and rejected someone who scored 3\/3 on their technical screen because they didn’t like the resume formatting.<\/p>\n
The difference? One company knew exactly what they wanted. The other got trapped in hiring theater.<\/p>\n
That Web3 startup’s process was refreshingly simple:<\/p>\n
Result: 4 offers out of 5 profiles, following Paul English’s Seven-Day Rule<\/a> of making offers within a week.<\/p>\n I once had a Staff-level engineer rejected after meeting the CEO. The reason? “He didn’t seem passionate enough about our product.”<\/p>\n This candidate’s response: “I definitely didn’t have a passion for making widgets at my last companies either. He’s the leader\u2014he needs to believe. I’m a coder who’s willing to take equity as part of my pay. How much more motivated do I have to pretend to be?”<\/p>\n This is the “cultural alignment” trap. Most companies can’t define what they mean by culture fit, but they’ll reject great candidates over this ethereal concept.<\/p>\n A brilliant engineer friend walked out of an interview at a top-5 bank, telling the interviewer: “I’m not doing pointless exercises on the whiteboard with you.”<\/p>\n The hiring manager called me in disbelief\u2014no one had ever walked out before. But here’s the thing: I’d explicitly told him this candidate was perfect but couldn’t handle typical brain-teaser nonsense. The manager had agreed to skip the whiteboard games.<\/p>\n What was he expecting?<\/p>\n The candidate’s take: “You spend weeks studying for interviews, get grilled by people fresh out of college, then join and spend your time moving buttons three pixels to the right.”<\/p>\n This perfectly captures why companies complain about not finding good engineers while eliminating people who could 10x their products.<\/p>\n Great candidates generate strong reactions from your team. Lukewarm enthusiasm = wrong fit.<\/p>\n Warning:<\/strong> Multiple candidates have told me they felt companies were using interviews for free consulting on scaling\/architecture problems. They’d spend hours on the company’s actual technical challenges, then never hear back. If both candidates and recruiters smell something fishy, examine your process.<\/p>\n 4-6 people maximum. Same-day decision meeting. Thumbs up or down\u2014no maybes.<\/p>\n Look, cultural alignment and technical tests aren’t always wrong. But be honest about why you’re using them.<\/p>\n Cultural alignment makes sense when:<\/p>\n Technical tests make sense when:<\/p>\n Skip both when you can’t explain what you’re testing for.<\/p>\n Here’s what’s accelerating everything: AI tools like Cluely<\/a> now provide real-time interview assistance, making traditional Q&A obsolete.<\/p>\n The questions need to change<\/strong>\u2014from “Do you know this answer?” to “Let’s discuss ideas and have a dialogue.” Talk through problems, explain reasoning, show genuine curiosity about challenges.<\/p>\n Successful hiring managers I work with focus on continuous improvement in candidates’ career trajectories. They’re not looking for perfect answers\u2014they’re looking for people who learn, adapt, and get better over time.<\/p>\n AI might actually make hiring more authentic. You can’t fake genuine curiosity or deep thinking about real problems.<\/p>\n The most successful hiring approaches share common themes:<\/p>\n Brian Chesky (Airbnb) spent 5 months on his first engineering hire, asking: “Do I want to work with a thousand more people like this?” His key insight: “Need evidence to hire people, not to eliminate them.”<\/p>\n Keith Rabois (PayPal, Square) focuses on people who can “take a project and run with it completely”\u2014looking for ability to explain complex ideas simply and resourcefulness, not algorithm memorization.<\/p>\n Joel Spolsky warns explicitly against brain teasers, focusing instead on candidates who are “smart and get things done” with his rule: “If it’s a maybe, it’s a no.”<\/p>\n Notice what’s missing from these billion-dollar company approaches? Culture fit theater and whiteboard gymnastics.<\/p>\n The best engineers have options. While you’re optimizing for the perfect process, they’re accepting offers from companies that respect their time and know what they want.<\/p>\n Stop hiring like you’re afraid of making a mistake. Start hiring like you’re afraid of missing the person who changes everything.<\/p>\n The market rewards clear thinking and bold decisions. Your next great engineer is out there\u2014are you ready to hire like you mean it?<\/p>\n Paul English – “Hiring Religion”<\/a> – The seven-day rule that changes everything<\/p>\n Paul Graham – “Hiring is Obsolete”<\/a> – Why traditional hiring models are breaking down<\/p>\nThe Feedback That Says Everything<\/h3>\n
The Whiteboard Walk-Out<\/h3>\n
The Solution: Five Principles That Actually Work<\/h2>\n
1. Know Your Non-Negotiables (For Real)<\/h3>\n
\n
2. If It’s a Maybe, It’s a No<\/h3>\n
3. Design for Speed, Not Coverage<\/h3>\n
\n
4. Interview for Reality, Not Theater<\/h3>\n
\n
5. Trust Your Team’s Binary Judgment<\/h3>\n
When the Rules Actually Make Sense<\/h2>\n
\n
\n
The Future: Hiring in the Age of AI<\/h2>\n
What the Best Founders Actually Do<\/h2>\n
Your Move<\/h2>\n
Further Reading<\/h2>\n