AI Interview

Student Portal

Practice interviews, track your progress

U
Back to reports
Round report · Practice round

Associate Software Engineer

20 Jun 2026 · 12 min spoken · 12 min planned
This round
68/ 100Fair
Questions
4
You spoke
197 w
Level
developing

Mixed round — this report covers both your technical depth and HR readiness.

Experience
Fresher
D
Interviewer
Deepika
On camera
Resume
MANASA PENUMETCHA Resume (1).pdf
Taken on
20 Jun 2026
12 min spoken
Practice round12 min
Focus skillsJavaScriptSQLGitWeb basics
Technical

Technical depth in this round

The five components behind your technical score, each judged on this round only.

Breakdown

Component breakdown

Each petal is one component — the longer the petal, the stronger this round.

TECHNICAL66FAIRKNOWLEDGE63ACCURACY68DEPTH60REASONING63TECH COMMS74

Tap a segment to see that component in detail.

Selected component
Depth

How far past the surface you can go when probed.

60Fair

Solid, but one more level of depth wins the round.

How you performed

You went one level deep; the second level of 'how' and 'what breaks' was missing.

What to fix

Add one layer — how it works internally, and when it breaks down.

Proof from your transcript

Interviewer asked: Let's do fundamentals. Explain the difference between var, let and const.

“var is function-scoped and hoisted, let and const are block-scoped. const can't be reassigned,…”

Read against depth: You went one level deep; the second level of 'how' and 'what breaks' was missing.

Before the next round
  • For each favourite topic, prepare three follow-up levels: what, how, and what breaks.
  • Learn one internal detail per concept (how an index works, how GC decides, how TCP retries).
  • Practise trade-off questions: two options, when each wins, and why.
During the interview
  • Answer the question, then add one layer of depth unprompted — it invites a good follow-up.
  • When probed further, slow down and reason instead of repeating the first answer.
What went well
  • Clear, structured answers with concrete examples from real projects.
  • Calm pace and good listening — waited for the full question before answering.
  • Honest about the debugging process, including the initial wrong assumption.
What to fix before the next round
  • Quantify impact more — user counts, load times, time saved.
  • Tighten the introduction; the opening answer could be two sentences shorter.
  • Explain the 'why' behind technical choices, not only the 'what'.
Practise this round again