Culture is what happens under pressure
Most teams can describe an appealing culture when everything is going well. You learn more by asking what happens when a release breaks, a deadline slips or two engineers disagree.
Ask for a recent example and what the team changed afterwards. A healthy answer can acknowledge a mistake without turning the discussion into blame. This is a useful signal, not a guarantee of your future experience.
Green flags worth investigating
Look for practices that support sustainable delivery and learning. The exact tools can differ; what matters is whether the team can explain why its process works.
- Clear ownership, with someone responsible for decisions and follow-up.
- Code review that improves work without humiliating people.
- An onboarding plan that includes access, context and a realistic first task.
- Incident learning that produces concrete changes.
- Managers who can explain priorities and protect focus time.
Red flags that need a follow-up
A warning sign is a reason to ask another question, not an excuse to label a company publicly. Context matters: a small team may have lightweight processes, while a regulated organisation may need more formal controls.
- “We are always in crunch mode” without a plan to change it.
- The role changes substantially between interviews.
- No one can explain who sets priorities or resolves conflicts.
- Reasonable questions about hours or compensation are treated as disloyal.
- A take-home task resembles unpaid production work and has no clear time limit.
Distinguish constraints from dysfunction
Legacy systems and technical debt do not automatically mean a bad employer. Ask whether the team understands its constraints, has permission to improve things and can name recent progress.
Similarly, a busy on-call rotation may be reasonable for some products if responsibilities, escalation and compensation are explicit. The risk is hidden work or expectations that keep changing.
Check your interpretation with another person
Ask to meet a future colleague and compare their account with the manager’s. You can also ask contacts about their direct experience, while remembering that one person’s team or period of employment may not represent the whole business.
Write down what would have to be true for you to accept the role. If a critical concern remains unresolved, treat it as uncertainty rather than optimistically assigning it a green flag.
Your next steps
- Ask about a recent incident.
- Check onboarding and review practices.
- Clarify any recurring overtime or on-call work.
- Compare answers from more than one person.
References and further reading
Put your preferences into practice.
Create a developer profile with your skills, preferred work model and availability.
Join Fliqdev