Make the interview a two-way assessment
Your questions are not an afterthought. They help you understand whether this team will let you do good work. Select five that address your biggest uncertainties instead of rushing through a long list.
Ask the recruiter about process and terms, the manager about expectations, and engineers about the daily workflow. Someone not knowing an answer is normal; ask who can clarify it.
Understand the engineering workflow
These questions move the conversation from a list of tools to how the team actually delivers. Follow up with “Can you walk me through the last time that happened?”
- 1. How does a change go from a developer’s machine to production?
- 2. What does a useful code review look like here?
- 3. Who owns incidents, and how are lessons followed up?
- 4. How do you decide between product work and technical debt?
- 5. What is the hardest technical problem the team is facing right now?
Understand management and growth
Listen for clear examples and realistic expectations rather than promises of rapid promotion. A manager should be able to describe success without relying entirely on hours worked or tickets closed.
- 6. What would success look like in my first three months?
- 7. How often do developers receive actionable feedback?
- 8. How are progression and pay reviews decided?
- 9. Who could I learn from, and how does mentoring happen?
- 10. Tell me about a recent disagreement and how the team resolved it.
Understand the working arrangement
These are practical compatibility checks, not signs that you lack commitment. A role that works on paper can feel very different when time zones, travel or support duties are unclear.
- 11. Which hours require everyone to be available together?
- 12. What does remote or hybrid mean for this particular team?
- 13. Is there on-call work, and how are shifts and compensation arranged?
- 14. Why is the position open, and what changed for the team?
- 15. What would you change about working here if you could?
Turn answers into a decision
After the interview, write down the actual answers before memory smooths over the uncomfortable parts. Flag vague commitments and ask for clarification in a short follow-up email.
Avoid treating a single awkward answer as a verdict on an entire business. Look for patterns across people and stages, and confirm any condition that matters to your decision in the written offer.
Illustrative follow-up: “Thanks for the conversation. Could you confirm the expected office days and how on-call shifts are scheduled? Those details will help me assess the role accurately.”
Your next steps
- Pick five questions before the call.
- Ask at least one future teammate about daily work.
- Write down answers immediately afterwards.
- Follow up on unclear commitments.
References and further reading
Put your preferences into practice.
Create a developer profile with your skills, preferred work model and availability.
Join Fliqdev