She beat out two candidates from Top 10 CS programs. When I asked the founder why, he shrugged: "She'd already built something people used. The other two had impressive credentials but I couldn't tell from their resumes whether they could actually ship."
This isn't an anecdote about one quirky founder. It's a pattern. Skills-based job postings in tech are up 30% year-over-year, and startups are leading the shift.
Why startups moved first
Big tech can afford to use degrees as a filter because they get 10,000 applications per role. Stanford CS is a rough but functional proxy for "this person can probably code." When you're drowning in resumes, rough proxies save time.
Startups don't have that problem. They have the opposite problem: not enough qualified applicants. A Series A company with 30 employees can't afford to reject good engineers because they went to the wrong school or took a non-traditional path. Every wrong hire costs months. Every missed hire costs momentum.
So they evaluate differently. And what they look for is both simpler and harder to fake than a diploma.
What actually matters
1. Can you build things that work?
Not in theory. Not on a whiteboard. In production, with real users, dealing with real edge cases. This is why public proof of work carries so much weight at startups. A deployed project — even a small one — answers the question in a way that no interview loop can.
It doesn't have to be impressive in scale. I've seen candidates get hired based on:
- A Chrome extension with 50 users that solves a niche problem
- Contributions to an open-source project they genuinely use
- A blog post walking through how they debugged a gnarly production issue
- A personal site that's clearly more than a template — something they actually designed and built
The common thread is evidence. Not claims, not credentials — evidence that you've written code that runs somewhere other than your laptop.
2. Can you think through ambiguity?
According to a 2025 survey of talent acquisition leaders, 73% ranked critical thinking as the #1 skill they look for. AI skills — the thing everyone is obsessing over — ranked fifth.
At a startup, you won't get detailed specs. You'll get half-formed ideas, contradictory requirements, and a deadline that moved up by two weeks. The people who thrive are the ones who can take an unclear problem, break it down into pieces, make reasonable tradeoffs, and ship something that mostly works — then iterate.
This is very hard to screen for in interviews. But some founders try by giving open-ended system design problems with no single right answer: "How would you build X if we had three engineers and needed to launch in six weeks?" They're not looking for the optimal architecture. They're looking for how you handle constraints and make decisions without perfect information.
3. Do you move fast?
Speed is a real cultural value at most startups, not just a slogan. And it shows up even before you're hired. Response time to interview scheduling, how quickly you complete a take-home, whether you follow up proactively — all of these get noticed.
Data from startup recruiting platforms shows that candidates with faster response times have meaningfully higher close rates. It's not that responding in 2 hours instead of 2 days makes you more talented. It's that startups interpret speed as a signal of genuine interest and work style compatibility.
If you're dragging your feet through a startup's interview process, they're going to wonder how you'll move once you're actually building the product.
4. Do you actually want to be here?
This one sounds fluffy, but it matters enormously at small companies. At a 2,000-person company, one disengaged employee is noise. At a 15-person startup, they're a culture problem.
Founders look for candidates who know what the company does, have used the product (or tried to), and can articulate why this specific company is interesting to them. It's not about performative enthusiasm — it's about genuine curiosity.
The easiest way to demonstrate this: say something specific. "I tried your API and noticed the webhook retry logic is aggressive — I'd be curious to hear the thinking behind that" is worth more than any amount of "I'm passionate about your mission."
What this means for your job search
If you have a CS degree from a strong program, great. It won't hurt you. But it's not doing as much heavy lifting as it used to, especially at companies under 200 people.
If you don't have a traditional background, the path is clearer than ever: build something, put it in public, and apply to companies where you can speak specifically about why you want to work there. The startup world has never been more open to non-traditional candidates, as long as those candidates can show — not just tell — what they're capable of.
The degree gets you into the building. The work gets you the job. And increasingly, you don't even need the degree for the first part.
