How to use InterviewPilot
Everything you need for your first interview: the set-up, how to talk to your interviewer, what each page is for, and the rules everyone is expected to follow.
Running your first interview
01Create an account and confirm your email
Sign up with Google or an email and password. Confirming your address is required before an interview can be graded. It keeps throwaway accounts from burning the grading budget.
02Set up the interview
On the Practice page, pick your domain, role, experience level, and language. Add a job description if you have one and the questions will be tailored to it. Technical and mixed interviews also generate a live coding problem.
03Allow the microphone (and camera, if you want)
The interview is spoken, so the microphone is required. The camera is optional: it powers the live confidence and eye-contact read, and the video never leaves your browser. Headphones are strongly recommended so your speakers don't echo into the mic.
04Press Start and just talk
Your interviewer greets you and asks the first question. Answer out loud in full sentences. You can interrupt her mid-sentence. She stops instantly, the way a real person would.
05Solve the coding round out loud
In technical and mixed interviews, a problem sits in the editor beside the conversation. Think aloud while you work, then press Share to send your code to the interviewer. She'll react to it and ask a follow-up.
06End the interview and choose your report
You decide when the interview is over. The interviewer never hangs up on you. When you end it, you're asked whether to generate the report and can rate the session. Ended by mistake? Discard it and nothing is graded.
How to talk to your interviewer
She listens the way a person does, so the habits that work in a real interview work here.
Speak in full sentences, not keywords
The interviewer grades what you actually say. "Redis, caching, fast" scores far worse than explaining why you reached for a cache and what it cost you.
Pause when you finish a thought
A brief pause tells the interviewer your turn is over. If you trail off mid-sentence she may wait, thinking you're still going.
Interrupt whenever you need to
Talk over her to redirect, correct yourself, or ask her to repeat the question. She stops immediately — it isn't rude here.
Think out loud during coding
Silence while you type reads as a blank. Narrate your approach, the edge cases you're considering, and the trade-offs you're weighing.
Use structure for behavioural answers
Situation, task, action, result. Name a real project, say what you personally did, and finish with the outcome.
It's fine to say you don't know
Admitting a gap and reasoning towards an answer scores better than a confident invention. The graders can tell the difference.
What each page is for
Practice
Where every interview begins. Choose the domain, role, level, tech stack, language, and optionally paste a job description. The set-up decides the questions you'll be asked.
Your feedback report
Generated after every interview by a panel of five AI reviewers. It gives category scores, strengths, growth areas, and a learning path. The Practice weak areas button turns that report straight into your next interview.
History
Every report you've generated, searchable by role or technology, filterable by interview type, and sortable by date or score. Use it to watch your scores move over time.
Leaderboard
How your best scores compare with other candidates, ranked by performance within your domain — a nudge, not a judgement. Visible to signed-in members only.
Community
Questions other candidates have faced in real interviews, shared by the people who faced them. Open one to read answers, like the ones that helped, and add comments. Post your own question after an interview while it's fresh.
Profile
Your verification status, overall statistics, and standing among other candidates. Percentiles only appear once enough people have taken interviews for the number to mean something.
That's the whole thing. Go take one.
The first interview is the hardest to start and the most useful one you'll take.
Start an interviewRules of conduct
Warning: this will get your account banned
- Abusive, obscene, or foul language directed at the interviewer or used during a session.
- Hate speech, harassment, threats, or sexual content of any kind.
- Posting abusive or offensive content to the Community pages.
- Deliberately attempting to make the interviewer produce harmful or offensive output.
Use of bad or foul language will result in the banning of the candidate. Sessions and community posts are subject to review, and a ban removes access to interviews, reports, and the leaderboard. Automated detection is being built; until it ships, reports are handled manually, and a ban applies either way.
Also worth knowing
Don't share passwords, OTPs, or anyone else's personal data during an interview. The transcript is stored with your report. Practise as yourself: the point is to get better, and a report based on someone else's answers tells you nothing.