DEV Community

Cover image for I Applied to 59 Tech Jobs in 14 Days. Here's What Actually Happened

I Applied to 59 Tech Jobs in 14 Days. Here's What Actually Happened

Mika Flowers on October 01, 2026

A little over two weeks ago, I started seriously looking for a job in tech again. Not bookmarking jobs. Not tweaking my LinkedIn headline for the...
Collapse
 
annavi11arrea1 profile image
Anna Villarreal •

I noticed a pattern last time I was applying places. I was logging applications in notepad. For roughly every 15 applications I would get some type of response ๐Ÿ˜‚

So i realized it is actually a numbers game. 5 real applications catered to a specific job definitely feels like 50. But I get higher responses when I trailer them.

Collapse
 
mikachu profile image
Mika Flowers •

sis it really is! And DONT even get me started on having to create an account on the employers application portal / website. WHY DO I NEED TO DO THAT

Collapse
 
annavi11arrea1 profile image
Anna Villarreal •

Added layer of "how bad do you want it" I suppose. ๐Ÿ˜… it could be argued, that those jobs might be easier to get, having weeded out lazy people. LOL

Collapse
 
azaleakuts profile image
Azalea •

59 applications in two weeks is honestly a lot of data to work with. What I found most interesting is how much the response rate can tell you about the strategy itself โ€“ whether the problem is the CV, the targeting, or simply the market. Tracking applications this way seems much more useful than just applying endlessly and hoping something sticks.

Collapse
 
sinarezaei profile image
Sina Rezaei •

This is a really interesting way to look at a job search because youโ€™re treating it as a system instead of just an emotional experience.

The part that stood out to me is the distinction between โ€œapplication volumeโ€ and โ€œopportunity generation.โ€ 59 applications sounds like the main metric, but once you separate rejection, screening, interview, silence, and opportunities coming from outside the funnel, the picture becomes much more useful.

Iโ€™d actually take this one step further and track the funnel like a product funnel:

Application โ†’ Viewed โ†’ Response โ†’ Screening โ†’ Interview โ†’ Offer

Then add the source and role type to each step.

For example, if 40 software-engineering applications produce almost no human interaction while 8 technical-writing applications produce an interview, that doesnโ€™t automatically mean โ€œbecome a technical writer.โ€ It tells you where to investigate: positioning, targeting, portfolio evidence, market, or simply sample size.

And the Sinch example makes the whole experiment more interesting. A traditional application funnel can be performing poorly while a โ€œbuild โ†’ publish โ†’ demonstrate โ†’ opportunityโ€ funnel is already producing something tangible.

Thatโ€™s probably the biggest takeaway for me: donโ€™t optimize for the number of applications. Optimize the system that turns your skills and evidence into opportunities.

Collapse
 
build996 profile image
build996 •

The role-type table is the part I'd watch most closely: 42 software applications with one screening and no interview yet, 8 writing ones and an interview request within hours, plus the Sinch work arriving through writing as well. You're right that eight is far too small to conclude anything, but those are two separate paths pointing the same way, which says more than either number alone. A cheap test for the next two weeks would be keeping the volume steady and flipping the mix, so writing and DevRel get a real sample and the comparison stops being 42 against 8. Splitting the 20 week-old silences by role type would also show early whether the gap is real or just noise.

Collapse
 
luke_bennett_ed52405c798e profile image
Luke Bennett •

I think that day i had to take you out yesdrday rember

Collapse
 
coder228 profile image
Frosty228 •

That's a lot, I've been applying relentlessly too. I'm trying for a different company but I didn't actually keep track of my applications, leaving the site that I applied in keep track. I'll make a point to keep track.

Collapse
 
devaland profile image
DEVALAND • • Edited

Thanks for counting instead of guessing. My funnel looks like yours with one difference: I stopped treating an application as a request for a seat. I run a small engineering company, so when I apply, I follow up in writing with what I build and the terms I work on, as a supplier rather than an employee.
Most never answer, same as your 86%. The ones that do answer are already talking about the work, not about whether I fit a checkbox.
And like your Sinch example, everything that actually turned into paid work came from things I had built and published, not from the application form.
I will be curious about your Day 30 numbers.

Collapse
 
luke_bennett_ed52405c798e profile image
Luke Bennett •

Thanks