Ask HN: Why am I suddenly unemployable?
Amid a sharp tech downturn, an experienced UK software developer who once attracted frequent recruiter interest now struggles to get interviews, prompting peers to dissect both résumé strategy and broader market forces. Commenters highlight common CV pitfalls — unclear job titles, non-chronological layouts, lack of quantified impact, weak signaling of specializations and soft skills, and formats that confuse automated screening tools — and suggest tailoring applications, expanding to multiple pages, and emphasizing business outcomes over task lists. At the same time, many argue the deeper cause is structural: post‑pandemic overhiring, higher interest rates, outsourcing, and a flood of laid‑off engineers have made hiring far more selective, leaving even strong candidates underemployed.
State of the Tech Job Market
- Many report a sharp drop in interviews and recruiter outreach compared to 2020–2022; some strong candidates are unemployed for many months.
- UK, US, and Canada are all described as “brutal” markets, with more applicants than roles, particularly for senior devs.
- Several note that tech is in its worst downturn since the dot-com era; some compare it to 2008–2009.
- Common explanations in the thread: post‑pandemic over‑hiring, mass layoffs flooding the market, high interest rates, hiring freezes, and companies optimizing for profitability.
- Some roles and postings are described as “fake” or extremely slow-moving, with ghosting even late in processes.
Resume / CV Content & Structure
- Core critique: the CV lists tasks and tech (“worked on”, “used X”) but not impact or outcomes; readers want business value, metrics, and clearer achievements.
- Repeated advice to:
- Add a short summary / objective at the top (who you are, what you’re looking for).
- Use strict reverse-chronological, single-column layout; current multi-column format is seen as confusing and obscuring history.
- Include job titles, months/years, and location; missing titles and dates raise red flags.
- Add a clear skills section (languages, frameworks, cloud, etc.) instead of repeated “used X” bullets.
- Fix typos and thin fonts; attention-to-detail matters more in a tight market.
- Consider 2–3 pages given long experience; one-page constraint is now seen as harmful by many.
Positioning, Skills, and Specialization
- CV gives no strong focal point; reviewers can’t tell if this is a graphics/game dev, web/full‑stack dev, or ML/AI engineer.
- Suggestions:
- Create separate, tailored CVs (e.g., a 3D graphics–focused one) and tailor per job.
- Emphasize standout niche strengths (e.g., 3D/graphics, Django) rather than generic “software developer”.
- Some advocate learning Rust, ML/AI, quantum computing; others warn against pure hype‑chasing and note limited Rust jobs outside crypto.
- Lack of visible cloud/DevOps, architecture, business context, or leadership experience on the CV is seen as a weakness for senior roles.
Hiring Process, Recruiters, and ATS
- Reports of recruiters calling, promising to send specs, then never following up.
- Some recruiters prefer DOC/DOCX for easy template editing; others insist PDF is safer and parses fine.
- Strong emphasis on ATS/keyword matching:
- Avoid complex layouts and graphics.
- Ensure parsers can correctly read roles, dates, and skills.
- Several recommend networking, referrals, communities, and previous employers over mass applications.
Systemic / Economic and Cultural Commentary
- Some argue the main issue is macroeconomics and “end‑stage capitalism”: layoffs to boost stock, outsourcing enabled by remote work, and a flooded candidate pool pushing wages down.
- Others counter that overall living standards and macro indicators look fine; the pain is concentrated in tech.
- Debate over “impact bullets”: some see them as necessary evidence of value; others say the numbers are often unverifiable or outright fabricated, but still rewarded.
- Ageism, short tenures, and gaps are mentioned as additional hidden filters in a surplus‑talent market.
Coping Strategies and Mindset
- Advice includes:
- Keep learning and “always be learning” (especially AI-adjacent tools).
- Refresh CV with professional help if needed.
- Lean on networks, HN “Who’s Hiring”, and freelance/contract work where possible.
- Accept that even very good engineers are struggling; it’s “not just you.”