Questions to ask when you're interviewing the company
An interview is a two-way street: you're deciding whether to join them as much as they're deciding about you. The questions you ask signal how you think — and, more importantly, they're how you avoid walking into a job you'll want to leave in six months.
Good questions are specific and a little pointed. Here are the ones worth asking, and the answers worth listening for.
About the work and the codebase
Get concrete about what you'd actually do: 'What would my first few months look like?', 'What state is the codebase in — greenfield, mature, or a lot of legacy?', 'How do you ship — how often do you deploy, and what does the pipeline look like?', and 'Is there an on-call rota, and how's it compensated?'
These cut through the sales pitch to the day-to-day reality. Vague or uncomfortable answers about the codebase or deployment usually mean the reality is messier than the advert suggested.
About the team and how it runs
Ask how the team is structured and how decisions get made: 'How big is the team and who would I work with most closely?', 'How do you do code review?', 'How are technical decisions made — top-down or by the engineers?', and 'How does the team handle disagreement?'
You're trying to picture a normal Tuesday. How a company talks about code review and disagreement tells you a lot about whether it's a healthy place to be an engineer.
About growth and why the role exists
Two of the most revealing questions: 'Is this a new role or a backfill — and if someone left, why?', and 'What does success look like in this role after six months?' Follow with how progression and promotion actually work.
The 'why is this role open?' question is the single most useful one you can ask. A confident, honest answer is reassuring; evasiveness about why the last person left is worth paying attention to.
Red flags to listen for
Listen as much as you ask. Watch for answers that are all vibe and no substance ('we're fast-paced', 'we're like a family', 'we work hard and play hard'), reluctance to talk specifics about the codebase or on-call, no clear answer on progression, and any dodging of why the previous person left.
None of these is fatal on its own, but a pattern of them is a warning. If you're job-hunting while employed, our guide to searching confidentially covers keeping it discreet, and preparing for the interview itself covers the other side of the table.
Frequently asked questions
What questions should I ask at the end of an interview?
Ask specific ones about the work, the team and why the role exists — for example what your first months would look like, the state of the codebase, how decisions are made, and whether the role is new or a backfill. Specific questions signal genuine interest.
Is it okay to ask about salary in an interview?
Yes, though it's usually best raised once there's mutual interest — often with the recruiter rather than in a technical round. Asking the budgeted range early is reasonable and saves everyone time.
What are red flags to watch for in a job interview?
Vague, all-vibe answers, reluctance to discuss the codebase or on-call specifics, no clear progression path, and evasiveness about why the last person left. A pattern of these is worth taking seriously.
Tech recruitment without the noise
Free to join for techies and companies. Anonymous until it matters, and a flat 10% only when a hire actually happens.