title: @tankots: Companies don't hire the most qualified person. They hire who makes the decision...
author: tankots
content_type: twitter_article
published: 2026-02-03T18:49:16+00:00
source_url: https://x.com/tankots/status/2018758704682930510
word_count: 1621
Companies don't hire the most qualified person. They hire who makes the decision feel easiest.
The recruiting game is rigged - but not in the way you think.
I've hired over 200 employees across three companies and reviewed over 100,000 resumes. Here's what actually happens on the other side of the table.
After reviewing thousands of resumes, you start to see patterns. They blur together - same schools, same companies, same bullet points. 90% of resumes I review are discarded in the first 3 seconds.
But every now and then, someone does something different.
They don't just apply. They show up with work already done. Teardowns of our product, prototypes that solve niche problems, or redesigns without us ever asking.
These people skip the line.
Not because they're gaming the system, but because they've already demonstrated the initiative I'm actually hiring for.
Most candidates ask, "How do I get the job?" But the ones who win ask, "How can I prove myself before they ever meet me?"
This article is about the second question. The intricacies and initiatives have led to my first hires across multiple companies. I'll go over the specific tips, strategies, and examples from my employees to showcase how to land any job you ever apply for.
Here's what actually works:
Effort Comes Before the Application
Most people think the job search starts when you hit "submit."
They focus on the outputs:
Polished resume
Optimized LinkedIn
Practiced interview answers
Tailored cover letter
But those are just
artifacts
. They drive no real value to those employing you, and recruiting becomes a game of how well can I
market
myself instead of how can I
prove
myself. People attach their effort to the application and then wonder why it blends in with everyone else.
By the time you're applying, the game is already over. You either have something to show, or you're just another resume making promises.
The application isn't the beginning. It's the reveal.
"Application" Is the Wrong Word
Applying to something gives off the connotation that you are requesting something from the employer.
But when I look at the people who get hired immediately, that's not what they're doing. They're not applying. They continue to work - except now they point it at a specific company.
I've seen full product recommendations sent through email. Complete mockups of new features were made before they were hired. There's a multitude of examples I can pull from of employees I've hired directly who used this strategy:
A 20-year-old who became one of my best engineers didn't submit an application. He shipped a fully functioning feature in one weekend.
One of my best designers didn't send a resume. She sent a teardown of Wispr's product and all the design changes she would make.
My first GTM hire didn't ask for an interview. He closed three deals and championed Wispr at other companies he worked at.
When you look at it this way, the "application" isn't anything new because they had already started building for the company. This makes it much easier to hire them because you can already envision them as part of the team.
That's the reframe. You're not asking to be evaluated. You're giving them another sample. Another data point. More proof of how you think, how you operate, and how you're like to work with.
Now that we know the overarching strategy, people who get hired this way tend to fall into one of three archetypes:
1. The Builder
Primary differentiator: making things exist.
These people can't help but ship. They see a problem, and their instinct is to solve it - not talk about it, not plan it, not ask for permission. Just build.
They thrive on:
Starting from scratch
Working fast under pressure
Turning ideas into something real
Showing instead of telling
They don't need a job description to start working. They need a problem.
This approach works especially well for:
Engineers
Designers
Writers
Anyone who makes things
The 20-year-old who DM'd me was a builder.
He didn't send a resume. He didn't ask for an interview. He showed up on a Saturday, heard about a project we needed done, and said "I'll start now."
By Sunday morning, he texted me, "Tanay, I just pulled an all-nighter. It's done."
Thousands of lines of code. A fully functioning feature. In 48 hours.
I see a lot of candidates with impressive backgrounds. Staff engineers from Uber. Principal scientists from Meta. Ten, twenty years of experience. That's fine, but it still leaves questions. I don't know how they work day to day. I don't know how they handle ambiguity. I don't know what they're like when there's no roadmap.
Shipping something answers all of that instantly. It shows me how someone thinks, how they move, and what they do when no one's telling them what to do.
That's a builder.
2. The Analyst
Primary differentiator: understanding how things work.
These people are obsessed with systems. They look at a product, a company, a process - and they can't help but pull it apart. They want to know what's working, what's broken, and what everyone else is missing.
Finding inefficiencies others overlook
Seeing patterns across complex systems
Forming strong opinions backed by evidence
Communicating what they see with clarity
They don't need to be asked to evaluate something. They're already doing it.
Product managers
Strategists
Consultants
Operations people
The designer who reached out to us was an analyst.
She didn't send a resume. She didn't ask for a portfolio review. She sent a complete teardown of our product - a deck showing what was broken, why it was broken, and how she'd fix it. Unprompted. Just sent it over.
I see a lot of portfolios. Most of them show me what someone made at their last job. That's fine, but it doesn't tell me much. I don't know what constraints they were under. I don't know if the good ideas were theirs. I don't know how they think.
A teardown shows me exactly how someone thinks. It shows me what they notice, what bothers them, and what they'd prioritize. It shows me their taste. And when the teardown is about my own product, it answers the only question that actually matters: can this person make us better?