Walking a stranger through your final-year project
A product startup, Kalvi Analytics, cares less about your CGPA than about whether you built something and can explain it. Fifteen minutes, one engineer, no slides. They will ask what it does before they ask how it works, and they will notice if you cannot say who it was for.
An intermediate-level session of about 12 minutes. 7 questions, each answered out loud.
Most walkthroughs open with the stack. Three framework names in the first sentence, and thirty seconds are gone before the engineer knows what the thing does. Start instead with whoever had the problem — a hostel mess with no way to predict attendance, a shopkeeper on a paper ledger, whatever yours actually was — then what the project did about it, then how. The 'who used it' question is what separates a built project from a submitted one, and 'my guide and the evaluators' is a fine answer when it is the true one, provided you follow it with what would have to change before a real user touched it. Expect 'why that one?' after every technology you name. 'It was what the tutorial used' is survivable. Inventing a reason you did not have at the time is not.
Angles worth taking
- Open with one sentence a non-engineer would follow, then stop and let them ask the first 'how' — the pause is deliberate.
- Use 'I' for the parts you wrote and 'we' for the parts you did not; the switch is what makes both halves believable.
- Pick one design decision in advance and know the alternative you rejected, plus the single reason you rejected it.
- Name a limitation before they find it: the dataset was small, it slows down past a few hundred rows, the login was never secured.
- Asked about a teammate's module, say so and describe the interface you called rather than reconstructing code you never wrote.
Who is in the room
You play
A final-year student presenting their project in a startup interview
You speak with
A senior engineer at Kalvi Analytics who asks "who used it?" early, and follows every technology name with "why that one?"
Phrases to reach for
These are shown to you before the session starts. They are what you are asked to use, not a list the scorer is checking off.
Ready to speak?
Free to start. You need a TalkDrill account to speak — reading this page does not.
Browse all mock interview roundsThe format
Questions in this round
7
Modes
Learn (guided) · Mock (exam-real)
How a mock interview session works
Pick a round
HR, behavioural, or a role-specific set. Each one tells you how many questions it runs and roughly how long it takes.
Answer out loud
Questions come one at a time and you speak the answer. There is a clock, because a two-minute answer and a five-minute answer are different answers.
Take the follow-ups
Answers get followed up. A vague claim gets pressed on, which is what separates a rehearsed answer from a true one.
Read the report
Structure, evidence, filler and pace per answer, plus the one answer worth recording again before the real thing.
What you're scored on
Every round is assessed the same way, because interviewers are broadly consistent about what a good spoken answer contains.
Explain what the project does and who it is for before any technology is named, own your specific contribution, defend one design decision, and be straight about what it does not do yet.
Structure
Whether the answer has a shape — situation, action, result — or arrives somewhere by accident after ninety seconds.
Evidence
Specifics over adjectives. "We cut it from six days to two" against "we improved the process significantly".
Relevance
Whether you answered the question asked, including the follow-up, rather than the question you prepared for.
Delivery
Pace, filler words, and whether the last third of the answer is as clear as the first.
More mock interview rounds
All mock interview rounds · Placement rounds · All speaking practice