All 12 questions
Prefer a list? Here is every card with what the manager is checking.
Walk me through your most challenging project.
What they're checking: Ownership, the decisions you made and whether you understand the trade-offs.
How to answer: Pick one project and use STAR: the problem, your part, one or two key decisions and why, and the result with a number if you can. Expect follow-ups like "What would you do differently?", so know the details.
How do you prioritise when everything is urgent?
What they're checking: Judgement and communication under pressure.
How to answer: Explain a method: list the tasks, rank them by impact and deadline, agree the order with your manager, and say what will slip and when. A short real example makes it credible.
Tell me about a time you disagreed with your manager.
What they're checking: Whether you can disagree respectfully and still deliver.
How to answer: Describe raising the concern privately, with data, and listening to their reasons. Then say what was decided and that you committed to it fully, even if it wasn't your idea. Never make your manager the villain.
What would you do if a teammate wasn't pulling their weight?
What they're checking: Maturity: solving it with the person before escalating.
How to answer: Talk to them privately first and ask what's going on: there may be a reason. Offer help or a clearer split of work. Only if it continues and affects delivery, raise it with the lead, focusing on the work, not the person.
What would you do if you realised you'd miss a deadline?
What they're checking: Honesty and early warning.
How to answer: Tell your manager as soon as you know, not on the day. Bring options: what can be delivered on time, what needs more days, or what help would close the gap. Then share what you changed so it doesn't happen again.
Tell me about a mistake you made and what you learnt.
What they're checking: Accountability and learning.
How to answer: Choose a real but recoverable mistake. Own it in one line, explain how you fixed it, and finish with the change you made to your process. Avoid blaming others or picking a fake "mistake" like working too hard.
How do you handle criticism of your work?
What they're checking: Whether you're coachable.
How to answer: Say you ask questions to understand it, thank the person and act on it, then give a short example: feedback you got, what you changed and the result. Showing you seek feedback is even better.
Describe a time you went beyond your role.
What they're checking: Initiative and ownership.
How to answer: Share something you noticed and fixed without being asked: automating a manual step, improving documentation, helping a new joiner. Say what it saved or improved, and that you kept your manager informed.
How would you explain a technical problem to a non-technical person?
What they're checking: Communication with clients and managers.
How to answer: Use an analogy, focus on the impact and the next step, and skip jargon. Show it: for example, explain an outage as "the system that checks passwords was overloaded, so logins failed for 20 minutes; we've added a backup".
Are you comfortable with relocation, shifts or a service bond?
What they're checking: Practical fit, and honesty.
How to answer: Answer honestly. If you're open, say so; if you have a constraint, state it calmly and ask for details (how often, how long, which locations). Agreeing to everything and backing out later is worse than a clear answer now.
Where do you see yourself in three years, and how does this role fit?
What they're checking: Ambition that lines up with the job.
How to answer: Describe growth that this role can realistically give, like owning a module or leading a small team, and link it to what you'd learn here. Avoid plans that suggest you'll leave soon.
What would your first 90 days look like?
What they're checking: Whether you'd ramp up thoughtfully.
How to answer: First month: learn the product, codebase or processes and the people. Second: take on real tasks and deliver small wins. Third: own an area and suggest one improvement. Keep it humble: you'd adjust once you know the team's priorities.
What the managerial round is about
Managers want to know how you'll behave on a normal working day: how you prioritise, handle pressure, work with people and own mistakes. Answer with real examples, using the STAR answer builder to structure them, and keep a calm, honest tone.
Frequently asked questions
What is a managerial round?
An interview with the person you'd report to, or another manager, usually after the technical round. It checks how you work with people, prioritise and handle problems, through behavioural questions like "Tell me about a time you disagreed with your manager".
How should I answer managerial questions?
With a short, real story: the situation, what you had to do, what you did and the result. The STAR method keeps it structured. Stay positive about past teams and managers.
What if I'm a fresher with no work experience?
Use college projects, internships, hackathons, fests or part-time work. The interviewer cares about how you behaved, not where.