Why I almost quit job hunting at week 3 (and what actually got me unstuck)

Published: (June 19, 2026 at 10:06 AM EDT)
4 min read
Source: Dev.to

Source: Dev.to

Everyone says the fix for a bad job search is to apply to more jobs. That’s the wrong diagnosis. Applying more isn’t the problem. The problem is that the process is designed to drain you until you stop. And it works. I sent out 34 applications in three weeks, got 2 responses, and by week 3 I was opening LinkedIn, staring at listings, and closing the tab without applying anything. Not because I didn’t want a job. I needed one badly. I just couldn’t make myself do it anymore. I thought I was lazy. Turns out I was hitting something well-documented in psychology. Every rejection gets logged by your brain as a small failure. Even a silent one. After 20 or 30 of those in a row, your brain quietly builds a rule applying equals pain, avoid it. Psychologists call this rejection sensitivity. It’s not a character flaw. It’s a survival mechanism. Your brain is treating a recruiter’s silence the same way it treats physical danger. It doesn’t care that you need rent money. On top of that, every single application is a decision gauntlet before you even open the form. Do I tailor this resume or use my standard one? Is this company worth a custom cover letter? Do I apply even though I only match 7 of the 10 requirements? Roy Baumeister’s research on decision fatigue shows that decision quality drops the more choices you make back to back. By application 10, I was making worse calls than on application 1. The whole thing felt twice as hard, even when the jobs were similar. That’s not weakness. That’s a brain running out of fuel. And then there’s the number nobody tells you. Most developers who actually get hired applied consistently for 6 to 12 weeks. Not 3. Six to twelve. I was quitting right before the curve turned. Before week-1 applications started coming back. Before my interview answers sharpened from repetition. The pain is usually highest right before it starts working. That timing is brutal and almost nobody warns you about it. What got me moving again wasn’t motivation. It was removing decisions from the process entirely. I locked in one resume for 80% of jobs and stopped agonizing over it. I started tracking everything in a spreadsheet so my brain stopped burning energy trying to hold 40 open applications in memory at once. And I stopped writing cover letters from scratch. I started using ApplyJobGPT instead paste the job description, get a solid tailored draft in seconds, spend 5 minutes making it sound like me. That one change alone got me from 4 or 5 applications a week to 12 or 15. The bottleneck was never effort. It was the part of the process that felt the most exhausting, quietly killing my momentum every time I sat down to apply. I also switched from daily targets to a weekly quota. Missing one day on a daily streak feels like the whole system is broken. A weekly quota means I can apply 12 on Saturday, zero on Tuesday, and still hit my number. Streaks are fragile. Quotas aren’t. Job hunting is designed to feel like you’re failing even when you’re doing everything right. The feedback loop is slow. Rejection is high by design. You can be a genuinely strong engineer and go weeks without a single response. That’s not a reflection of your skills. That’s just the volume and randomness of the process working exactly as intended. What got me through wasn’t a better resume. It was treating it like a systems problem and building something I could run for 10 weeks without burning out. The bad news nobody tells you this when you’re in week 3 staring at a closed tab and the good news now you know.

0 views
Back to Blog

Related posts

Read more »

Speculative Decoding on Mobile GPUs

--- title: 'Speculative Decoding on Mobile GPUs: Draft-Verify LLM Pipelines with Vulkan Compute' published: true description: 'Build a speculative decoding pipe...