Ask HN: Devs/data scis who pivoted to a new career in 30s/40s, what do you do?

Hacker News Discussion ↗

Many mid-career software engineers and data scientists are reassessing their paths in their 30s and 40s, weighing high pay and comfort against burnout, instability, and a lack of meaning. Contributors describe pivots into teaching, small business ownership, government and academic roles, creative work, and adjacent technical fields, often enabled by prior savings or lower financial needs. A recurring theme is that successful transitions require accepting reduced income and seniority, leveraging existing skills and networks, and being clear whether the urge to switch stems from genuine new interests or from trying to escape broader life dissatisfaction.

Why pivot from dev/data science?

  • Many are motivated by burnout, politics, on-call stress, unstable projects, and “Sword of Damocles” anxiety.
  • Some feel unfulfilled by corporate work and crave tangible, people-facing or physically active roles.
  • Others are pulled by long-standing interests (hard science, music, art, education, policy, geography, etc.) and want closer alignment with intrinsic motivations.

Financial, age, and family constraints

  • Dev/data roles often pay enough to make big pay cuts thinkable; many other fields don’t.
  • Family obligations (kids, mortgage, college costs) are a major brake on radical pivots; some set explicit deadlines tied to things like FAFSA.
  • There’s concern about ageism in tech; some note tech is unusually biased against older workers compared to other professions.

What counts as a “career change”?

  • Debate over definitions: some count any major life-direction job change; others reserve “career change” for moves requiring new, specialized skills.
  • Data cited: job changes are common, but official stats don’t define “career change,” so claims like “3–4 career changes” are contested.

Common destination careers and paths

  • Teaching (especially private high schools) and academia-adjacent data roles.
  • “Hard science” and research support, often via grad school later in life.
  • Small business ownership: cafes, bookstore-cafes, hotels, farms; success tied to careful market research and willingness to accept lower but more controllable stress.
  • Creative work: generative art, music, AV/installation work, newsletters, topic-focused journalism.
  • Government and civil service roles for better work–life balance and clearer boundaries.

Experiences moving into or back into tech

  • Some pivot into dev or data roles later (from IT, science, infra) by taking lower-level or niche jobs, contract roles, or leveraging side projects.
  • Tactics include “dumbing down” resumes, targeting backend/ops roles where infra skills are valued, and accepting starting from the bottom.

Advice and cautions

  • Don’t pivot on vague dissatisfaction alone; address underlying life issues first.
  • Build savings to create leverage and tolerate pay cuts or breaks.
  • Prefer visible landing spots (clear roles, markets, demand) over blind leaps.
  • Recognize that both desk jobs and manual/retail work have serious downsides; know your temperament.