Mental health in software engineering

Unrealistic deadlines, shifting priorities, and “everything is critical”

• Many describe leaders promising impossible features or contradictory “top priorities” to clients, then demanding “make it happen.”
• Common pattern: sales over‑promise (often without consulting engineering), then push emergency crunch to save the deal.
• Several argue you must enforce queues, WIP limits, and explicit tradeoffs (“yes, but then X slips”) to avoid chaos and burnout.
• Others say this isn’t “business uncertainty” but plain leadership incompetence and lack of prioritization.

Leadership, management, and the cost of bad culture

• Recurring theme: technically strong managers who micromanage, don’t trust the team, and take on all the work themselves, burning out and cascading stress downwards.
• Some see this as an individual failure; others blame organizations for promoting ICs into management with little training and for rewarding deadline‑driven heroics.
• Strong emphasis that good leaders shield teams from pressure, say “no,” clarify tradeoffs, and accept “good enough,” rather than chasing perfection and martyring themselves.

Burnout, quitting, and financial buffers

• Multiple stories of engineers trapped between impossible demands and fear of unemployment; some eventually quit abruptly and later saw the company fail anyway.
• Several stress the value of savings and support networks to be able to walk away; others note many people (kids, mortgages, weak job markets) can’t just leave.

Mental health days, stigma, and policy

• Disagreement on whether you “can” say “I need a mental health day.”
  • Some report open, supportive cultures where this is normal and even explicitly covered as “wellbeing leave.”
  • Others say they must hide it as generic sick or PTO, fearing stigma or being managed out.
• General consensus: reason is nobody’s business unless you choose to share it.

Industry‑specific stressors

• Factors cited: constant cognitive load, long sitting hours, blurred work/life boundaries, endless sprints, changing requirements, on‑call for fragile systems, and lack of real finish lines.
• Debate over whether software is uniquely bad vs. just another high‑stress white‑collar field; several argue comparisons are unhelpful and each profession has its own pathologies.

Coping strategies and structural ideas

• Personal: strict boundaries on hours, saying no, finishing what’s started, exercise, sleep, and disconnecting after work.
• Structural: better estimation and Kanban‑style flow, realistic management training, dual IC/manager tracks, unions (controversial), and contracting for more autonomy.
• Widely shared view: human well‑being is more important than any “critical” feature or startup.