5 Comments
User's avatar
Jade Truong's avatar

Treating the person as the unit is exactly right. When my first company lost its funding, I called everyone I knew to place nine developers, engineers and architects, and every one of them landed somewhere. A founder who keeps a living list of great people, long before a role exists, hires faster on the way up and takes care of people faster when the ground moves.

Ivi Pauli, PhD's avatar

Akash, there's something in these hiring practices that I'd love to see explored further.

So much emphasis on exceptional talent, obsession, urgency, and the capacity to push through difficult problems. I understand why these qualities are attractive to founders building under enormous pressure.

But coming from biology, I keep thinking about the other side of that equation.

How do these companies distinguish people who can perform exceptionally under intense demands from people who can sustain that performance without eventually paying a significant physiological cost?

Long hours and urgency can be part of building something ambitious. But recovery, adaptation, and human limits don't disappear because the mission is exciting.

I'd be fascinated to see a companion playbook on how these companies retain and sustain the exceptional people they work so hard to recruit.

Mohamed F. Ahmed's avatar

The talent dispersion point tracks with something I've watched up close: two people who really know how to direct AI tools now outperform a team of six who don't, and the gap keeps widening. That changes the hiring question entirely. You're not screening for raw skill anymore, you're screening for judgment about what to ask for and when to trust the output.

Shortlisted by Kat's avatar

The section I'd point founders to first is A2, asking every candidate the same questions. The Turbopuffer question about understanding two to four levels below the abstraction is a great example, because it's one question you can ask everyone and compare fairly. Where I'd be more careful is copying the week-long work trials. Cursor can ask for that because so many people want to join, but for most startups a full week is a big ask from someone who already has a job, and a well-planned couple of hours on a real problem from your own codebase gives you most of the same signal. Did any of the founders talk about how many strong candidates drop out at the work-trial stage?

Martin Alen's avatar

Akash, could the next hiring advantage be making it easier for exceptional people to tell you what would make them say yes?

A resume shows past work. It rarely explains the problem someone wants to tackle next, their conditions for moving, or what they could contribute beyond their current title.

That’s the gap I’m building SHシFT around, starting with hiring.

People declare: “I can and will do this, on these terms.” Founders declare the problem they need solved, what they can offer and their constraints. Both sides check the understanding and agree before an introduction. Someone needn’t be job-hunting to participate.

The principle is to establish what matters before optimising what happens next.

The MVP is being built now. I can offer an early walkthrough and, once ready, a small test around one founder’s hiring need: does knowing both sides’ intentions and conditions change who the founder or recruiter approaches, or the opportunity they propose?

Would you give me 20 minutes to challenge the idea and identify a useful case?