Joseph Khan All articles
Career Reflections

One Hundred Interviews of Silence: What Actually Happened When Recruiters Found (or Didn't Find) My Website

Joseph Khan
One Hundred Interviews of Silence: What Actually Happened When Recruiters Found (or Didn't Find) My Website

Photo: (CC-BY-SA-4.0), CC BY-SA 4.0, via Wikimedia Commons

I rebuilt my portfolio site three times before I ever sent out a single application with it on my resume. Three. Rebuilds. Weeks of tweaking typefaces, arguing with myself about dark mode, writing a bio that made me sound like a person and not a LinkedIn parody.

So when I finally started interviewing, I had a quiet hope: someone, somewhere, would look at my site and say "wow, this guy gets it."

Instead of hoping, I decided to count. For every interview cycle over roughly fourteen months — 100 of them, counting phone screens through final rounds — I kept a note afterward: did anyone mention the website? What did they say? Did I advance?

Here's what the data actually showed.

The Headline Number: 23 Out of 100

Twenty-three interview cycles included some mention of my site. That's it. Just under a quarter.

And before you ask — no, I didn't count the times I awkwardly brought it up myself. ("So, uh, I actually built my portfolio from scratch, it's josephkhan.me, just in case..." We've all done it. Those don't count.) This was only when a recruiter, hiring manager, or interviewer brought it up unprompted.

Of those 23 mentions, the breakdown looked like this:

Twenty-three percent sounds underwhelming. But the interesting part wasn't the frequency. It was the timing.

The Website Didn't Get Me Interviews. It Got Me Second Chances.

Here's the pattern that surprised me: my site almost never came up in first-round screens. Recruiters are skimming for keyword matches and salary expectations, and a URL in the header of a resume is wallpaper to them.

Where it showed up was rounds two and three — after someone had already decided I was worth a deeper look. Eight of the eleven interviewer mentions happened after I'd passed a technical screen. In other words, the site wasn't a door-opener. It was a tiebreaker.

And the correlation with advancing was real, if modest. In interview cycles where the site came up, I advanced to the next round about 65% of the time. In cycles where it didn't, closer to 40%. That's not a superpower — plenty of other factors were in play — but it's not nothing.

What People Actually Said (Verbatim, More or Less)

I jotted down quotes after every mention, and they fell into three buckets:

The vibe check: "Your site is clean, I like it." Said fast, meant politely, forgotten instantly. This was maybe half the mentions.

The project dig: "I read your write-up on the migration tool — how did you handle the idempotency issue?" This happened four times, and every single time it turned into my best conversation of the interview. When an interviewer shows up having read your work, you're not answering trivia anymore. You're talking shop.

The credibility play: One hiring manager told me straight up: "Honestly, the site is why you're in this room. Half the resumes we got had no proof anyone could look at." That one stung and thrilled me at the same time.

The Weekend Redesign: Worth It?

So was all that agonizing over my portfolio worth it? My honest answer: the existence of the site was worth far more than any of the redesigns. Nobody in 100 interviews commented on my font choices, my animations, or whether the hero section loaded in under a second. Not one person.

What mattered was that projects existed, were explained in plain English, and had links to live demos. That's it. That's the whole formula.

If I could go back, I'd tell myself: build it once, keep it honest, and spend the reclaimed weekends actually building things worth showing. The site is the receipt, not the product.

Three Takeaways for Your Next Application

  1. Put the URL on your resume, but calibrate expectations. It's a background check, not a billboard. It works when someone's already curious about you.
  2. Write about your projects like a human explaining them to a coworker. The four interviews where someone quoted my writing back to me were the four I walked out of feeling like I'd won something.
  3. Stop redesigning. Seriously. Round four of your portfolio theme has never once been mentioned in an interview. I have the data.

A hundred interviews later, the site didn't get me hired — but it made me harder to forget, and in a market where hiring managers are skimming hundreds of near-identical resumes, harder-to-forget is a real, measurable edge. Even if it only shows up 23% of the time.

All Articles

Related Articles

40 Applications, One Spreadsheet, Zero Mercy: What a Year of Tracking My Own Job Hunt Actually Showed

40 Applications, One Spreadsheet, Zero Mercy: What a Year of Tracking My Own Job Hunt Actually Showed

Two Years of Doing the Math on the Job I Didn't Take

Two Years of Doing the Math on the Job I Didn't Take

Six Months of Refusing 'Rockstar' and 'Ninja' Jobs: A Field Report on Who Actually Called Back

Six Months of Refusing 'Rockstar' and 'Ninja' Jobs: A Field Report on Who Actually Called Back