Key Takeaways
- Kush Bavaria builds Ornn by hiring former college athletes instead of typical Silicon Valley tech hires.
- Startup communication breaks down as headcounts hit 20 to 30 people; athletes counter this because field sports demand continuous, real-time vocal coordination.
- Competitive drive shows up in shipping velocity: when rivals launch a feature, athlete-engineers demand to match and deploy it by tomorrow.
- The work rhythm requires extreme physical stamina, spanning 60 to 80 hours a week, including 100-hour weeks Bavaria logs with an engineer named Will.
- Bavaria vets candidates outside conference rooms by taking them to dinners and engineering uncomfortable situations to test their composure.
Why Fast Teams Stall at 30 People
Bavaria noticed a familiar trap when startups grow from early prototypes to teams of 20 to 30 people. Urgency slows down. Direct talk gets replaced by bureaucratic politeness, and teams create layers of middle management just to pass information across desks.
Bavaria solved this by changing who sits in the seats: “So, we like care so deeply about like culture of the team that we've hired people and the people that we've hired are all like ex- college athletes um or have played some sort of sport growing up.” (play from 1:01:50)
Athletic teams survive on vocal, unfiltered communication. On a court or pitch, you do not write a memo or wait for a weekly sync to call out a missed assignment. You shout in real time. Bavaria brings that exact reflex into Ornn: “It turns out the best like communicators are like college athletes because what do you do when you play a sport? You're just like communicating all the sing every single time.” (play from 1:02:32) When technical problems emerge or market dynamics shift, former athletes speak up immediately without worrying about hurting feelings.
Hatred of Losing Beats Desire to Win
Silicon Valley often talks about mission alignment, but Bavaria looks for something harsher: candidates who despise being beaten.
“And the second thing is like you are so competitive that you hate like losing,” (play from 1:02:40) Bavaria explains. “Like you want to find people that are like competitive enough that if you tell them, 'Hey, competitors launched this feature. Why don't we have it?' They're like, 'It's we have it tomorrow.'” (play from 1:02:44)
That intensity matters because building a financial exchange and futures market for AI compute demands brutal endurance. Startups in fast-moving infrastructure cannot survive on standard 40-hour schedules. Bavaria is candid about the hours required at Ornn: “You end up spending 60 hours, 70 hours, 80 hours a week with these people. Sometimes with our like engineers sometimes, uh there's a guy named Will on our team. we spend like a 100 hours a week together.” (play from 1:01:20) That workload breaks people who treat engineering as a relaxed desk job. It fits people who spent four years conditioning through dawn practices and two-a-days.
The Dinner Stress Test
Resumes tell you nothing about how an engineer behaves when exhausted, insulted, or off-balance. Whiteboard interviews measure algorithmic recall, not grit under pressure.
To filter out people who crumble when things go wrong, Bavaria moves the interview process into unpredictable environments: “The interviews we like take people dinners and like weird uncomfortable situations to see how they like interact or act.” (play from 1:03:56)
Watching a candidate handle social awkwardness, unexpected friction, or bad restaurant service reveals their default operating system. You see whether they adapt and keep their cool, or become defensive and entitled. If someone cannot handle an awkward dinner, they will not survive a 100-hour week when production infrastructure crashes at 2:00 AM.
What to Do With This
Stop screening candidates purely through static technical screens and polite Zoom chats. For your next critical hire, design an off-script evaluation test this week: take the finalist to dinner, deliberately put them in an ambiguous or slightly uncomfortable setting, and observe how they communicate when their guard drops. Check whether they speak up instantly about friction or wait for permission.