AI Interview

Student Portal

Practice interviews, track your progress

U
Back to reports
Round report · Practice round

Software Engineer Intern

04 Jul 2026 · 16 min spoken · 16 min planned
This round
86/ 100Excellent
Questions
3
You spoke
229 w
Level
strong

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

Experience
Fresher
H
Interviewer
Hemanth
On camera
Resume
MANASA PENUMETCHA Resume (1).pdf
Taken on
04 Jul 2026
16 min spoken
Practice round16 min
Focus skillsAlgorithmsSystem design basicsC++ or C#Testing
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.

TECHNICAL83STRONGKNOWLEDGE80ACCURACY88DEPTH80REASONING87TECH COMMS81

Tap a segment to see that component in detail.

Selected component
Knowledge

Core subjects and concepts the role expects you to know.

80Strong

A clear strength this round — keep it at this level under pressure.

How you performed

You named the right concepts confidently and used the correct terminology.

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
  • States complexity and space cost without being asked.
  • Design answer covered caching and async analytics, not just CRUD.
  • Test cases included security and logging, showing production thinking.
What to fix before the next round
  • Sketch the data model in the design answer — key size and collision handling.
  • Say the trade-off you rejected and why, not only the one you chose.
  • Slow the first 30 seconds of each answer; the framing gets rushed.
Practise this round again