Prova

Interview questions

Software engineer interview questions

The coding round gets the attention, but many offers are won or lost in the conversations around it. Interviewers want to hear you explain a system you built, a decision you would make differently, and how you behave when production breaks.

Rehearse this interview by voice2 minutes without an account, 3 more after sign-up. No card.

Questions by stage and what a strong answer includes

  1. 01

    Tell me about your current stack and what you personally own.

    Strong answer: Languages, frameworks and infrastructure, and a clear line between what you built and own and what the team does. Recruiters use this to route you to the right loop.

  2. 02

    What kind of team and problems are you looking for next?

    Strong answer: A specific direction such as backend scale, product engineering or infrastructure, linked to what this company does.

  1. 03

    Tell me about a production incident you were involved in.

    Strong answer: What broke, how you found it, what you did to mitigate first, the root cause, and the follow-up fix and postmortem actions. Calm and blameless.

  2. 04

    Describe a technical disagreement with a teammate.

    Strong answer: The two positions, how you tested or measured to decide, and how you committed once a decision was made, even if it was not yours.

  3. 05

    Tell me about a time you shipped something with known shortcuts.

    Strong answer: Why the trade-off made sense, how you documented the debt and the plan to pay it down, and whether you actually did.

  1. 06

    Walk me through the most complex project you built.

    Strong answer: Problem, constraints, architecture, your specific decisions, what went wrong and the measurable outcome. Be ready for follow-ups at any level of detail.

  2. 07

    Design a URL shortener or a notification service.

    Strong answer: Clarify requirements and scale first, then data model, API, storage, caching, failure modes and trade-offs. Talk through choices instead of drawing a perfect diagram silently.

  3. 08

    What do you look for when reviewing someone else's code?

    Strong answer: Correctness, readability, tests, edge cases and consistency, delivered as kind, specific comments. Shows you raise the bar for the team, not just yourself.

  4. 09

    How do you decide when something is tested enough?

    Strong answer: Risk-based testing: critical paths and edge cases, the balance of unit and integration tests, and how monitoring complements tests in production.

  1. 10

    Where do you want to be technically in three years?

    Strong answer: A believable growth path, for example deeper ownership of a domain or moving toward tech lead, connected to what this role offers.

  1. 11

    What compensation are you targeting, and how do you think about equity?

    Strong answer: A researched total compensation range for the level and location, understanding of vesting and how equity is valued, and willingness to discuss the mix.

One answer, before and after

Tell me about a production incident you were involved in.

Weak answer

We had an outage once and the whole team jumped on it. I helped debug and we fixed it in a few hours. Incidents happen, you learn from them.

Strong answer in STAR

Situation
I was on call for a checkout service handling about 200 orders a minute at peak. After a Friday deploy, error rates on payment confirmation jumped from under 0.1% to about 8%.
Task
As on-call, I had to stop customer impact first and then find the root cause.
Action
I checked the deploy timeline against the error graph, rolled back the release within 12 minutes of the first alert, and confirmed errors returned to baseline. Then I reproduced the bug locally: a new retry wrapper was retrying non-idempotent payment calls on timeouts. I fixed it with an idempotency key, added an integration test for the timeout path and wrote the postmortem.
Result
Customer impact lasted about 15 minutes and no duplicate charges reached customers after refund checks. The postmortem led to a team rule that every external call wrapper needs an idempotency review, and we added an alert on payment error rate per deploy.

Why it works

The weak answer hides in 'the team' and gives no detail. The strong one shows mitigation before investigation, a precise root cause and lasting prevention. The numbers are illustrative: use your own incident.

How a practice session works

  1. 01

    Pick a stage, paste the job posting

    Recruiter screen, HR interview, hiring manager, final round or offer talk. Add the posting and your resume so the questions are about your role, not generic.

  2. 02

    Talk it through by voice

    The interviewer speaks the language you chose, interrupts, follows up and digs into details like on a real call. If the connection drops, you pick up where you stopped.

  3. 03

    Get the review and drills

    A score, 7 skills, what you said next to a stronger way to say it, plus pace, filler words and talk share. Weak spots turn into short drills.

Rehearse this interview by voice

Related roles