Technical screening questions
Ask for one example per question and listen for specifics.
- How do you decide what the team does not do? A good answer: Link work to goals, say no with reasons and agree it with product.
- How do you give difficult feedback? A good answer: Specific, timely and with a clear path to improve.
- How do you measure delivery without gaming it? A good answer: A small set of outcomes and flow measures, discussed with the team.
- How do you hire an engineer? A good answer: A structured process, consistent questions and a clear bar.
- What do you do when two senior engineers disagree? A good answer: Hear both, tie the decision to goals and decide or escalate.
Quick screening questions
Use these when you have only a few minutes.
- How many engineers did you manage and how did the team change?
- How do you handle an underperforming engineer?
- How do you stay close enough to the code to judge a design?
What separates the levels
Match the level to the requirement before you submit.
- Mid: manages one team.
- Senior: manages several teams or managers.
- Director level: sets strategy across groups.
Red flags
Any of these is a reason to probe further.
- No example of coaching someone.
- Has not hired.
- Dismisses technical detail.
Tools you should hear mentioned
An Engineering manager with real experience usually names several of these without prompting.
- Jira or similar
- Roadmaps
- One-on-one notes
- Metrics dashboards
- Code review tools
- Hiring tools
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should an Engineering manager screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.