AI Interview

Student Portal

Practice interviews, track your progress

U
Back to reports
Round report · Practice round

Systems Engineer / Power Programmer

28 Jun 2026 · 15 min spoken · 15 min planned
This round
81/ 100Strong
Questions
5
1 spoken · 1 coding · 1 MCQ · 1 short · 1 picture spoken
You spoke
215 w
Level
job ready

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

Experience
Fresher
D
Interviewer
Deepika
On camera
Resume
Vatsav_Resume.pdf
Taken on
28 Jun 2026
15 min spoken
Practice round15 min
Focus skillsData structuresDBMSJavaProblem solving
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.

TECHNICAL80STRONGKNOWLEDGE78ACCURACY84DEPTH80REASONING80TECH COMMS80

Tap a segment to see that component in detail.

Selected component
Knowledge

Core subjects and concepts the role expects you to know.

78Strong

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

How you performed

You knew the concepts, though a couple were described rather than named.

What to fix

Name the concept before explaining it, so the interviewer hears the term you know.

No clear example in this round

Name the concept before explaining it, so the interviewer hears the term you know.

Before the next round
  • Keep a one-page sheet per subject (OS, DBMS, OOP, networks) and revise it out loud weekly.
  • For every concept, learn the exact term, a one-line definition and one example.
  • Cover the syllabus your target company actually asks about before going wide.
During the interview
  • Name the concept first, then explain it — "This is normalisation, specifically 3NF, because…".
  • If you don't know something, say so and offer the closest thing you do know.
What went well
  • Quantified the query optimisation with a real before/after number.
  • Chose the space-efficient approach and justified it against alternatives.
  • Explained architecture in layers, showing testability awareness.
What to fix before the next round
  • Be crisper on worst-case behaviour of hash maps in modern Java.
  • Practise dry-running code aloud so the interviewer can follow your logic.
  • Mention how you'd verify a fix beyond 'it works now'.
Practise this round again