"Where do you see yourself in 5 years?" "What's your biggest weakness?" These questions are clichés because they're useless. They produce rehearsed answers that tell you nothing about how someone works, thinks, or collaborates. Yet hiring managers continue to ask them, wasting valuable interview time and learning nothing useful about candidates.

What to ask instead

Focus on specific, behavior-based questions anchored in real experience. Ask about a time the candidate dealt with a technical disagreement, a project that failed, or a complex system they designed. These questions reveal how someone thinks, communicates, and handles challenges — the behaviors that actually predict job performance.

Good interview questions should feel like a conversation, not an interrogation. They should give the candidate room to demonstrate their thinking process and problem-solving approach. Replace generic questions with ones that probe real engineering situations and decisions.

MR

Maria Rodriguez

Head of Engineering

Maria leads engineering at DevPass. She's a former staff engineer at GitHub and has interviewed over 500 candidates.

Stay Updated

Get notified about new posts

Join our newsletter for the latest insights on developer hiring, career growth, and building in public.

No spam. Unsubscribe anytime.