I’ve watched too many solid engineers walk into a new job like it’s a honeymoon suite and walk out three months later looking like they’ve been through a trash compactor. The codebase was fine. The tech stack was fine. The team, on paper, was fine. But the culture? That was a slow-burning tire fire they didn’t smell until the smoke was in their lungs.
We treat engineering culture like it’s soft stuff. HR fluff. But a broken culture will wreck your ability to ship working software faster than a Kubernetes misconfiguration. It’s the real technical problem. So let’s get blunt. I’ll walk you through the exact red flags to hunt for during an interview loop, before you sign anything that locks you into a daily standup from hell.
The Interview Itself Is the First Commit Log
You cannot ask, “Hey, is your culture toxic?” because nobody will say yes. They’ll hand you a slide deck about pizza Fridays and psychological safety. You need to read what the interview process does, not what the job description says.
The All-Day Gauntlet of Unpaid Labor
If they ask you to build a fully functional microservice as a “take-home project” that will take twenty hours, they’re not testing your skills. They’re testing how much disrespect you’ll swallow before you’ve even gotten a badge. A legit shop gives a bounded, time-boxed problem that respects your weekend. A toxic shop treats your personal time like a free staging environment. Run a quick calculation: if the project’s scope exceeds what a salaried developer would do in a normal sprint day, you’re being harvested, not evaluated.
Interviewers Who Clearly Hate Each Other
Watch the panel dynamics. Do they interrupt each other? Roll their eyes when a colleague speaks? Do they contradict the company values poster on the wall in real time? I once sat in an interview where the CTO and the senior architect started a passive-aggressive argument about monorepos while I was mid-sentence answering a totally unrelated question. That wasn’t a culture of “healthy debate.” That was a team that had bled resentment into every Slack channel and couldn’t even hide it for forty-five minutes. If they can’t fake professionalism for a candidate, imagine them during an outage.
The Evasive Answer Tango
Ask direct questions. “How do you handle on-call incidents?” “What was the last production outage you had, and what changed afterwards?” A healthy team will tell you the story. They’ll be a little embarrassed but detailed. A toxic team will give you a word salad. “We have a blameless culture so we prefer not to dwell on specifics.” Translation: We have a blame-full culture and we’ve been legally advised to shut up. If you hear more jargon than a corporate earnings call, your bullshit detector should be screaming.
Language That Reveals a Broken Compiler
Words are cheap, but the specific phrases a company uses are dead giveaways. Pay attention to the gap between what they say and what a functioning engineering org actually does.
“Work Hard, Play Hard”
This one means “work hard, and then work slightly less hard at a mandatory happy hour where you’re still judged for not being a culture fit.” It’s a euphemism for no boundaries. Real engineering cultures don’t need slogans about how hard they grind. The code quality, the test coverage, the deployment frequency—those are the receipts. A team that’s proud of its output doesn’t lead with how late the Slack notifications buzz.
“We Move Fast and Break Things”
If you hear this unironically in 2024, you’re dealing with a team that hasn’t learned a single lesson in a decade. Moving fast without breaking things is the entire point of modern software delivery. This phrase is often code for “we skip code review when the PM is stressed, and then we spend every Friday unfucking the database.” Ask them about their rollback strategy. If they laugh nervously, you have your answer.
“Family”
I’m going to be direct: a company is not a family. A family doesn’t fire you in a Zoom call when the quarterly numbers dip. A family doesn’t put you on a performance improvement plan because you took parental leave. When a company calls itself a family, they’re usually trying to guilt you into emotional overtime. A professional team uses the word team. They offer respect and clear expectations, not a dysfunctional Thanksgiving dinner dynamic where the CTO is the passive-aggressive uncle.
Structural Red Flags in the Codebase of the Company
You can often get a read on the engineering culture by probing the edges of how they work, not just the tech stack.
The Hero-Driven Development Cycle
Ask: “Who knows the most about the authentication system?” If they point to a single person—“Oh, that’s all Dave, he’s a wizard, he’s been here forever”—you’re looking at a bus factor of one. That’s not a wizard. That’s a single point of failure who has likely built a kingdom of unmaintainable shell scripts to guarantee job security. A toxic culture enables this because management loves the myth of the 10x developer who saves the day. A functional culture treats heroism as a process failure and documents the hell out of everything so Dave can go on vacation without the pager going off.
Promotion Paths Paved with PowerPoint
Dig into how engineers get promoted. If the answer revolves around launching features and visible impact, but nobody mentions reducing tech debt, improving test runtimes, or mentoring juniors, you’re looking at a feature factory. That culture rewards the loudest person in the room, not the person who stopped the database from keeling over at 3 a.m. by quietly refactoring the connection pool. You’ll end up in a team where the core infrastructure rots while everyone scrambles to ship the CEO’s pet project.
The Meeting Parasite Load
Ask a simple question: “How many recurring meetings does a typical engineer have per week?” If the number is above ten, the company is paying for expensive furniture. You’re not going to write code. You’re going to attend status syncs about status syncs. This is a classic sign of a culture that values the appearance of work over work itself. The meetings exist so managers can justify their existence by “aligning” things that were already aligned.
Questions That Make Them Sweat
You need to flip the interview. Stop performing and start diagnosing. Here are the questions I would ask in the final round to get a real signal.
1. “Tell me about a time someone broke production and what the next day looked like.” Listen for whether the person who caused the outage was supported or shamed. Listen for whether a root cause analysis happened or whether a new “policy” was just emailed out in all caps.
2. “When’s the last time you deleted code and celebrated?” An engineering team that never removes dead features or deprecated endpoints is drowning in complexity. A team that celebrates deletion understands that engineering is about managing entropy. If they look at you like you have three heads, they’ve never pruned a branch in their lives.
3. “How does the team decide what not to build?” The ability to say no is the most important technical skill. If the answer is “we build whatever the product team puts in the roadmap,” engineers are just assembly-line workers. A healthy culture has engineers in the room when priorities are set, pushing back with data. A toxic one has developers who mutter “this is stupid” while typing git push.
What a Healthy Culture Actually Smells Like
So you don’t think I’m just a cynic, here’s the flip side. Good cultures aren’t perfect, but they don’t hide.
You’ll hear engineers disagree openly and then grab coffee afterwards. You’ll see pull request comments that are tough on the code but respectful to the author. You’ll notice that meetings start with a clear purpose and end with a decision, not a “let’s circle back.” The on-call rotation will have a sane escalation policy and a budget for fixing the things that caused the pages. People will use their vacation days and not post about #hustle from the beach.
The difference between a toxic culture and a productive one isn’t a mystery. It’s just whether the company treats engineers as creative problem solvers or as interchangeable cogs in a Jira assembly line. Your job in the interview is to figure out which one you’re walking into.
Frequently Asked Questions
What’s the single biggest red flag in an engineering interview?
Disrespect for your time. If they reschedule last-minute without a real apology, keep you waiting twenty minutes in a lobby without an update, or give you a take-home assignment that’s clearly actual product work, the pattern is already set. They’re telling you exactly how they’ll treat you when you’re an employee with less bargaining power.
Can a toxic engineering culture be fixed from the inside?
Rarely by a new hire. Culture change requires a leadership team that sees the problem and is willing to lose some “high performers” who are actually just bullies. As a new engineer, you don’t have the political capital to change that. You can try if you’re joining as a VP or Director, but as an individual contributor, you’re more likely to burn out trying to fix a broken system than to actually fix it.
How do I evaluate culture in a remote interview?
It’s harder, but not impossible. Ask to see a sprint retro board or a post-incident review document. The artifacts of how they communicate asynchronously are more telling than a live video call. Also, ask for a short chat with a potential peer without the manager in the room. If the company refuses, that’s your answer.
Is a “fast-paced” environment always a red flag?
Not if it’s paired with strong boundaries. Fast-paced can mean the team ships daily and gets quick feedback, which is great. The red flag is when “fast-paced” means “we set arbitrary deadlines and then blame engineers for not meeting them.” Ask about how deadlines are set. If engineers are part of the estimation process and there’s a track record of adjusting scope instead of demanding overtime, you’re in a good fast place. If not, you’re in a burnout factory.
The next time you’re in an interview, don’t just try to impress them. Interrogate the system. The worst bug you’ll ever debug is a company that’s rotting from the inside, and no amount of free snacks can fix that.
