AI Interview

Student Portal

Practice interviews, track your progress

U
Back to reports
Round report · Practice round

Systems Engineer (Ninja)

24 Jun 2026 · 13 min spoken · 13 min planned
This round
66/ 100Fair
Questions
5
1 spoken · 1 coding · 1 MCQ · 1 short · 1 picture MCQ
You spoke
226 w
Level
job ready

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

Experience
Fresher
H
Interviewer
Hemanth
On camera
Resume
MANASA PENUMETCHA Resume.pdf
Taken on
24 Jun 2026
13 min spoken
Practice round13 min
Focus skillsOOP conceptsSQLJava or PythonDebugging
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.

TECHNICAL69FAIRKNOWLEDGE89ACCURACY64DEPTH44REASONING78TECH COMMS68

Tap a segment to see that component in detail.

Selected component
Depth

How far past the surface you can go when probed.

44Needs work

Uneven this round — this is where the marks are leaking.

How you performed

Answers stayed at the surface, so the follow-ups had nowhere to go.

What to fix

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

Proof from your transcript
Interviewer asked: Explain the four pillars of object-oriented programming with an example from your…
“Encapsulation kept entity fields private, Driver inherited from User, notification senders used polymorphism, and…”

Read against depth: Answers stayed at the surface, so the follow-ups had nowhere to go.

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
  • Tied every concept back to the final-year project instead of textbook definitions.
  • Structured SQL answers with an alternative approach for duplicates.
  • Professional, steady delivery suited to a service-company panel.
What to fix before the next round
  • Mention team size and your specific contribution when describing the project.
  • Practise writing code aloud — the string and array questions needed prompting.
  • Add numbers to outcomes: records handled, users, response time.
Practise this round again