Staying at the surface
"I was responsible for the migration" is where a deep dive starts, not where it ends. Be ready to explain the architecture, the numbers, the dead ends and who disagreed with you.
Hiring stage Stage 3 of 5
This is the round where someone who knows the work checks whether you can actually do it. Expect fewer generic questions and more "walk me through exactly how you did that", followed by a problem from their real backlog.
The manager describes the team and what it is struggling with right now. Listen closely: this tells you which parts of your experience to bring up for the rest of the hour.
One or two projects from your resume, taken apart: your role, the options you considered, the trade-offs, the numbers and what you would do differently.
A short scenario typical for the role, said out loud: a metric that dropped, a frustrated client, a deadline that slips. They care about your reasoning more than a perfect answer.
How you would get up to speed and what you would deliver early. Then your questions, which the manager uses to judge how seriously you think about the job.
Pick a project on your resume and walk me through it from the start.
What they are checking: Whether you understand the work end to end or only your small piece of it.
What was the hardest decision on that project, and what were the alternatives?
What they are checking: Whether you think in trade-offs and can explain why you chose one option over another.
What would you do differently if you ran it again?
What they are checking: Whether you reflect on your work honestly and grow from it.
Here is a situation we are dealing with right now. How would you approach it?
What they are checking: How you structure an unfamiliar problem and what questions you ask before solving it.
What would you focus on in your first 90 days?
What they are checking: Whether you would learn before changing things and still deliver something early.
How do you like to be managed, and how do you keep your manager informed?
What they are checking: Whether your working style will fit theirs without constant friction.
Tell me about a time you had to deliver with fewer resources than you needed.
What they are checking: How you cut scope, negotiate and protect quality under real constraints.
What the interviewer sounds like in Prova
"I was responsible for the migration" is where a deep dive starts, not where it ends. Be ready to explain the architecture, the numbers, the dead ends and who disagreed with you.
Solving the case before asking a single question looks confident but often solves the wrong problem. Ask one or two clarifying questions, say your approach, then go.
Promising to rebuild their process in month one tells the manager you will not listen. Show a plan that starts with learning and still ships an early, visible win.
HR checks behavior and fit with structured questions. The hiring manager checks whether you can do this specific job: they go deep into your projects, give you a realistic problem and judge your reasoning as a future colleague.
Pick the two projects most relevant to the posting and prepare each one in detail: the goal, your role, key decisions and alternatives, the result in numbers and what you would change. Say it out loud at least once, because written notes hide the gaps.
Say what you would need to find out and how you would find it, then give your best hypothesis. A clear process with an honest "I'd want to check this first" usually beats a confident guess.
Select the Hiring manager interview stage and paste the job posting and your resume. The AI manager asks about your projects in depth, gives you a short case for your role and level, and asks about your first 90 days. The review shows where your answers stayed too general.