Ask HN: What are your personal red flags when you're interviewing at a company?

Hacker News Discussion ↗

Workload, Hours, and On‑Call

  • Routine overtime, weekend work, late‑evening interviews, and “we hustle / save the day” narratives are major red flags.
  • Required on‑call, frequent 3am pages, or crisis firefighting as normal practice signal poor planning.
  • Expectations to attend many after‑hours “social” or “happy hour” events are seen as intrusion on personal life.

Interview Process & Candidate Treatment

  • Time‑intensive take‑home projects (4–6+ hours, multiple case studies) are widely criticized as exploitative, especially when uncompensated or used as early screens.
  • Some prefer well‑scoped, short (≤1h) take‑homes over LeetCode or live coding; others reject any tests as distrustful or biased toward people without other obligations.
  • Negative signals: many short rounds with many teams, rigid templates, “gotcha” trivia, whiteboarding with silent or combative interviewers, cameras off, interviewers distracted or late, or not knowing the role.
  • Outsourcing technical screens, automated/chatbot steps, or demanding work on unfamiliar tech despite prior agreements (e.g., specific framework/OS) are seen as disrespectful.
  • Lack of time for candidates’ questions, or evasive answers, is a strong red flag.

Culture, Management, and Values

  • Phrases like “we’re a family,” “work hard, play hard,” “ninjas/rockstars,” or “mission over money” often indicate unhealthy expectations or underpay.
  • Mocking side projects, displaying arrogance or power‑tripping, or signaling intolerance of dissent or alternative solutions are red flags.
  • Signs of dysfunction: co‑CEOs with conflicting visions, many management layers, internal communication chaos, nepotism, or leaders threatened by strong candidates.
  • Emphasis on face time, open offices, hot‑desking, “frat bro” alcohol culture, dress codes (e.g., suits in casual tech) and lack of remote flexibility can indicate poor fit or outdated thinking.

Technical Practices and Environment

  • Lack of tests, fragile release processes, no CI/CD, monolithic databases for many services, very old tech stacks, or “if it ain’t broke we never change” attitudes suggest low engineering maturity.
  • Outdated or poor equipment, worn offices, or lax security (e.g., no badges) are read by some as negative; others see them as neutral or even signs of a stable, product‑focused company.

Compensation, PTO, and Career Stage

  • Low offers justified by “belief in the mission,” rigid compensation structures, or non‑negotiable boilerplate (especially restrictive clauses) are major warning signs.
  • Unlimited PTO is ambiguous: acceptable only when people demonstrably take substantial time off.
  • Several posters caution early‑career folks that being this selective may not be realistic; trade‑offs can make sense to build experience.