AI interview practice for campus placements
Stop freezing in your campus placement interview.
Practise out loud with an AI interviewer who has read your resume, pushes back like a real panel, then tells you exactly what to say instead.
First interview free. No card needed.
Built for Indian English. Hindi-English mixing is fine. Your accent is never scored.Sign up on your phone; do the interview on a laptop with Chrome or Edge and a mic.
- free to start, no card needed
- 1 interview
- sessions across 4 round types
- 5–30 min
- category scores in every report
- 7
Practise HR, technical and resume rounds. Fail ten interviews here before the one that matters.
- 01
Upload your resume
PDF or Word. Sarah reads every project, internship and skill you listed before the call starts.
- 02
Choose the round
General Placement, Technical, HR or Resume-based. Beginner to Hard, 5 to 30 minutes.
- 03
Talk to Sarah
A live call. She asks, you answer out loud, she follows up. No typing, no multiple choice.
- 04
Get your report
Verdict, scores, and a better answer for every question, written the way you would actually say it.
Sarah interviews like a panel that did its homework.
She asks about your resume, not a question bank
Every question starts from something you listed. The final-year project, the internship, the skills you claimed.
SarahTell me about the retry logic in your payments internship. Why did the first version fail?
She follows up and challenges
A vague claim gets a second question. She wants the number, the decision, the trade-off.
SarahYou said the model was quite accurate. Accurate compared to what?
She adapts to how you are doing
Strong answer, harder question. Struggling, she slows down and rephrases. A fair panel, not a quiz.
SarahLet us take a simpler case first. Two users update the same row in the same second. What happens?
She understands Indian English
Hindi-English mixing, regional accents, "basically" and "only". She follows all of it, and your accent is never scored.
SarahGot it, so the cron job was the real issue. Keep going.
Hear her
Natural voice, built for volume. What most students and cohorts run.
Read the transcript
- SarahHi, I'm Sarah, and I'll be taking your interview today. To start, tell me a bit about yourself.
- CandidateHi Sarah, I'm John Doe, a final year computer science student at Sunrise Institute of Technology with a CGPA of 8.4. I've worked on projects like Campus Connect, a student networking platform, where I was the lead full stack developer, and LeafScan, a plant disease detection web app where I focused on machine learning and backend development. I also completed an internship at Bright Apps, building dashboards and optimizing query performance.
- SarahOkay, John. Could you tell me more about your role as the lead full-stack developer for CampusConnect? What specific parts did you build yourself?
- CandidateAs the lead full-stack developer for Campus Connect, I was responsible for the entire development process, from designing the architecture to implementing features. I built the real-time chat functionality using Socket.io, developed the event RSVP system, and handled the integration of the front-end with the back-end using Next.js and Node.js. Additionally, I worked with PostgresQL to manage the database, ensuring smooth data handling for users across the three campus clubs.
- SarahGot it. You mentioned optimizing a slow report query during your internship at BrightApps. Could you walk me through the steps you took to identify the bottleneck and then improve its performance from 4 seconds to 300 milliseconds?
- CandidateTo identify the bottleneck during my internship at BrightApps, I first analyzed the query execution plan to pinpoint areas where the process was slowing down, such as stable scans or inefficient joins. I then optimized the query by adding appropriate indexes and rewriting parts of the SQL to reduce complexity. Additionally, I reviewed the database schema for any normalization issues that could improve performance. These steps combined significantly reduced the execution time from 4 seconds to 300 milliseconds.
- SarahOkay. When you say you "rewrote parts of the SQL to reduce complexity," could you give a concrete example of a change you made and why it improved performance?
- CandidateOne example of a change I made was replacing a subquery in the where clause with a join operation. The original subquery was causing multiple executions for each row, which significantly slowed down performance. By switching to a join, I eliminated those repetitive calculations and allowed the database to optimize the query more effectively. This change helped reduce the overall query complexity and improved performance considerably.
- SarahRight. And how did you measure the impact of these changes to confirm the 300-millisecond improvement? What tools or methods did you use?
- CandidateI measured the impact of the changes by using the built-in query analysis tools in PostgreSQL, specifically by checking the execution time before and after the optimizations using the explain analyze command. This provided detailed insights into how long each part of the query was taking to execute. Additionally, I ran multiple test cases with typical data loads to ensure consistent performance improvements. The combination of these methods confirm the reduction in execution time to 300 milliseconds.
- SarahOkay. Moving on to your LeafScan project, you used TensorFlow for classifying leaf images. Can you describe how you handled data augmentation for your image dataset, and why it was important for this specific application?
- CandidateFor the leaf scan project, I handled data augmentation by applying techniques such as rotation, flipping, scaling, and color adjustments to the training images. Data augmentation was crucial for this application as it helped increase the diversity of the training set, which improved the model's ability to generalize and recognize plants under various conditions and angles. By creating a larger and more varied dataset, I was able to enhance the model's accuracy in classifying leaf images and suggest appropriate treatments for different plant diseases.
Real-time conversational voice: interruptions, follow-ups, the closest to a live panel.
Read the transcript
- SarahHi John, this is Sarah from the interview. This is a general round, about five minutes, and we’ll start with a brief introduction. Tell me a bit about yourself, your background, interests, and what you’ve been building lately.
- CandidateHi Sarah, I’m John Doe, a final-year Computer Science student at Sunrise Institute of Technology, where I’ve maintained an 8.4 CGPA. I’m passionate about full-stack development and have recently worked on CampusConnect, a networking platform for students, where I led the development using Next.js and Node.js. I also developed LeafScan, a plant-disease detection web app utilizing machine learning with TensorFlow. In my recent internship at BrightApps, I focused on optimizing performance and implementing CI checks for React and Node dashboards.
- SarahOkay, let’s focus on CampusConnect since you mentioned it. Out of curiosity, what parts did you build yourself from scratch, and what was the hardest bug you ran into while implementing it?
- CandidateIn CampusConnect, I built the entire user authentication system and the real-time chat feature from scratch using Socket.io. The hardest bug I encountered was related to message synchronization, where messages were not consistently appearing in real-time for all users. After extensive debugging, I discovered an issue with how we were managing WebSocket connections, which I resolved by refining our event handling logic to ensure messages transmitted correctly across all clients.
- SarahGot it. You mentioned fixing message synchronization and the WebSocket connection handling. What exactly did you change in that event handling logic, and how did you verify that all clients were consistently seeing identical messages?
- CandidateI modified the event handling logic to ensure that each message sent from a user was acknowledged by the server before broadcasting it to other connected clients. I implemented an event confirmation system that allowed the server to track which messages had been sent and received. To verify consistency, I set up automated tests that simulated multiple users sending and receiving messages simultaneously, and I monitored the logs to ensure that all clients displayed identical messages in real-time. This thorough testing confirmed that our synchronization issue was resolved.
- SarahNice, that sounds solid. Let’s switch topics. For LeafScan, you mentioned a CNN and TensorFlow. How did you train and evaluate the model, and what kind of accuracy or confidence did you achieve before you felt comfortable shipping it?
- CandidateFor LeafScan, I trained the CNN model using a dataset of plant images labeled with various diseases. I used TensorFlow to build and optimize the model, experimenting with different architectures and hyperparameters. After multiple training iterations, I achieved an accuracy of around 92% on the validation set. I felt comfortable shipping the model after extensive evaluation, including cross-validation and confusion matrix analysis, which confirmed its ability to generalize well across unseen data.
- SarahOkay, 92 percent, nice. But what dataset did you use, and how did you define your evaluation? For example, what was the validation set size, and what did your confusion matrix show about specific classes the model struggled with?
- CandidateFor LeafScan, I used the PlantVillage dataset, which contains thousands of labeled images of different plant diseases. I split the dataset into 80% for training and 20% for validation, ensuring a diverse representation of classes. The confusion matrix revealed that the model struggled particularly with a few classes, such as bacterial blight and leaf spot, where it had higher false-negative rates. This insight led me to augment the training data for those specific classes to improve overall performance.
- SarahThat’s a good detail. When you say you augmented the data for those specific classes, what kind of augmentation did you apply? Was it rotations, scaling, or something else? And how did you confirm it actually helped, not just increased accuracy?
- CandidateI applied several augmentation techniques, including rotations, horizontal flips, and slight zooming, to increase the diversity of the training data for the underperforming classes. To confirm that the augmentation helped, I conducted a controlled experiment by training the model on both the original dataset and the augmented dataset separately. I then compared their performance on the validation set, and the augmented model showed a noticeable reduction in false negatives for the problematic classes, as well as an overall increase in accuracy, indicating that the data augmentation was beneficial.
- SarahOkay, thanks for that. Let’s pivot to your internship. In BrightApps, you mentioned cutting a slow report query from four seconds to three hundred milliseconds. What exactly did you change, and how did you measure the improvement?
- CandidateTo optimize the report query at BrightApps, I analyzed the SQL execution plan and identified several inefficiencies, including missing indexes and unnecessary joins. I added appropriate indexes and restructured the query to reduce complexity, which significantly improved performance. I measured the improvement by running the query multiple times before and after the changes, using a performance monitoring tool to track execution time, confirming the reduction from four seconds to three hundred milliseconds consistently.
- SarahOkay. That’s clear. Let’s move to your internship again. You also mentioned adding CI checks that caught regressions before release. How did you design those checks, and what kind of regressions did they catch?
- CandidateI designed the CI checks by implementing automated testing for both unit tests and integration tests within our CI pipeline using tools like Jest and Cypress. These tests covered critical functionalities, including user interactions and API responses. The checks caught several regressions, including broken UI components after updates and issues with API endpoints returning incorrect data, preventing these errors from reaching production and ensuring a smoother release process.
Unedited recordings of a full interview, start to finish. The candidate answering is a scripted test profile, not a real student, so nobody's interview is being shared here.
The report says exactly what went wrong, and what to say instead.
A verdict, seven category scores, and every question reviewed with a better answer in your own words. Communication metrics come from the recording, not from a guess.
Sample report. Scores and answers are illustrative.
The seven categories
Every interview is scored out of 100 on Technical Knowledge, Communication, English Fluency, Confidence, Resume Knowledge, Problem Solving and Behavioral.
How the score is worked out
Your overall score is a fixed weighted average of those seven, with weights set by the round you picked. A technical round leans on Technical Knowledge; an HR round leans on Communication. 70 and above is a pass, 55 to 69 is borderline. The thresholds and the weights are written into the product, not decided by the AI on the day, so the same answer scores the same way every time.
What you get after every session.
Question-by-question analysis
What the interviewer wanted, what was missing, and a score for every answer.
Better answers in your voice
Not a textbook answer. The one you could have given, with your details in it.
English rewrites
Real sentences you said, rewritten cleanly, with the pattern to watch.
Confidence from behaviour
Hedging, trailing off, hesitation before answering. Observed, not guessed.
Communication metrics
Speaking share, answer length, pace, pauses and filler words from the recording.
- Pace
- 128 words/min
- Filler words
- 37 total
Progress tracking
Score trend, pass rate and "work on next" across every session you have done.
Leaderboard and profiles
Only your best score and college are shown, never a transcript or report. Hide yourself any time in Settings.
- Rank 1Ananya S.88
- Rank 2Rohan K.84
- Rank 3Meera P.81
Searchable transcript
Every word of every session, saved and searchable afterwards.
Practice, feedback, improve, repeat.
Every session is saved. Your score trend, pass rate and “work on next” update after each one, so the next attempt is aimed at exactly what went wrong.
- Practice
- Feedback
- Improve
- Practice again
Questions students ask first.
Is it really voice?
Yes. You speak, Sarah speaks. She listens to your spoken answers in real time and replies in her own voice, with a live transcript beside the call if you want it.
Does it work with my accent?
Yes. Sarah is built for Indian English, including Hindi-English mixing. Accent is never scored. What gets scored is whether the answer was clear, specific and structured.
What do I need?
A laptop or desktop with a microphone, and Chrome or Edge. Nothing to install. A camera is optional and is only shown to you.
Is my data shared on the leaderboard?
Only your display name, college and scores. Transcripts, recordings and reports are never shown to anyone. You can hide your profile from Settings at any time.
How long is a session?
You choose: 5, 15, 25 or 30 minutes. The report is generated as soon as you end the call.
Is it free?
Your first interview is free, no card needed, and you earn one more for every friend who completes one, up to 10 friends. After that it is ₹299 per interview, or cheaper in a pack or monthly plan on the pricing page.
Your first interview takes fifteen minutes.
Upload a resume, pick a round, and find out where you stand before the real panel does.
First interview free. No card needed.