Ask HN: I have been unemployed for 2y. 15 years of experience, US. What to do?
A veteran U.S. software engineer with a two‑year employment gap describes burning through savings and even considering pizzeria work, prompting others to weigh in on how hard it has become to get hired in tech. Commenters highlight broken hiring funnels flooded by AI‑generated resumes, the growing importance of personal networks and referrals over cold applications, and deep disagreement over whether to “explain” or quietly disguise long gaps. Suggestions range from reframing the gap via projects, consulting or volunteering, to pivoting into adjacent fields (defense, IT, data centers) or even skilled trades, reflecting broader anxiety that traditional SWE roles are shrinking and evolving under AI.
Job Market & Hiring Dynamics
- Many report long-term unemployment (1–4+ years), even with substantial experience.
- Cold applications are described as nearly useless due to resume spam, AI-written CVs, and fraud (e.g., overemployed or foreign “ghost workers”).
- ATS filters heavily weight continuous employment and keywords, often blocking legitimate candidates before humans see them.
- Hiring pipelines at larger firms are seen as overloaded, risk-averse, and often optimized for “good enough” rather than “best.”
Resume Gaps and Honesty vs Lying
- Concern: a 2-year gap is perceived as a red flag, suggesting “nobody else would hire you,” even though layoffs are common.
- Some argue gaps are explainable (family, burnout, caregiving, startups, sabbaticals) and should be treated as normal; they blame stigma and lazy heuristics.
- A significant faction explicitly advises lying: extend previous jobs, invent consulting/LLC/startup work, invoke NDAs, or backfill with a friendly “startup” that claims you.
- Others strongly oppose this, on ethical grounds and due to background checks, clearances, and risk of later termination if lies are discovered.
Networking and Referrals
- Strong consensus that most success now comes via:
- Former colleagues and managers.
- Referrals inside target companies.
- Recruiters with existing relationships.
- Meetups, conferences, local business networking.
- Referrals are framed as a practical shortcut past broken front doors, not (necessarily) unfair nepotism.
- Some note that introversion and lack of network make this advice hard to execute, but still see it as necessary.
Alternative Career and Income Options
- Several stories of pivoting to trades (plumbing, electrician, electro-mechanic, diesel, construction), school-district IT, public sector, or government/defense tech (especially near DC).
- These often involve pay cuts but more job security and tangible, satisfying work.
- Others suggest actuarial paths, teaching, data center/robotics, or local management (e.g., “be really good at running the pizzeria”).
Self-Employment, Consulting, and Projects
- Suggestions: form an LLC, do even small consulting, be a fractional CTO, or “tech person” for SMBs.
- Many warn that finding clients and marketing yourself is extremely hard; feast-or-famine is common.
- Building personal or AI-powered projects/startups can:
- Keep skills sharp.
- Provide a concrete story to explain the gap.
- Occasionally lead to revenue.
- Skeptics note portfolios get little attention; without users or revenue, they may not move the needle.
AI, Skills, and the Future of SWE
- Split views:
- One camp claims “coding is not a job anymore,” that AI writes better/faster code, and SWE roles are shrinking; they urge focusing on AI orchestration, architecture, and domain/business skills.
- Another camp reports poor LLM code quality in practice and sees ongoing need for real engineering, design, and DevOps.
- Some say portfolios and code challenges are devalued because AI can generate them; others still value serious shipped projects and “high-agency” end-to-end work.
Explaining the Gap & Presentation
- Advice to frame the gap positively: sabbatical, family care, burnout recovery, travel, startup attempt, or focused learning (including AI).
- Avoid badmouthing previous employers; that reads as a red flag.
- Polish English, LinkedIn, and CV details; include tech used and responsibilities, not just employer size.
Emotional Tone
- Thread mixes empathy, shared hardship, and pragmatic realism.
- Some are openly pessimistic about the future of cushy SWE roles; others insist good engineers are still needed, especially if flexible on role, pay, or domain.