Help

A voice-based interview simulator. You go through a mock interview with an AI interviewer: it asks questions, listens to your answers, and asks follow-ups — just like in a real interview. Afterwards, you get a report: a score, a verdict, and a point-by-point breakdown of each answer.

Besides mock interviews, there are:

• Company tracks — the interview stages at a specific company, in order;
• By job posting — an interview built around the text of your job posting;
• Library — individual questions with breakdowns and a short voice drill;
• Problems — algorithm problems with code checking.

• A microphone and a browser (an up-to-date version of Chrome, Edge, Firefox, or Safari). Your browser will ask for microphone access — allow it.
• Headphones — highly recommended: without them, the interviewer may hear itself through your speakers and get thrown off.
• A quiet place and 15–40 minutes, depending on the interview. A single-question drill takes about 4 minutes.

• Mock for your role and level (e.g., Backend · Junior) is the best first step: a standard set of questions that come up almost everywhere.
• Company path is for when you're preparing for a specific company: the stages go in order, and at the end you get an overall verdict.
• Job-specific — paste the job description, and we'll build an interview around its stack and responsibilities.
• Library helps you brush up on weak topics one at a time: a single question, a breakdown, and a short voice drill.

The interviewer greets you, asks questions one at a time, and listens. If your answer is incomplete, they'll ask a follow-up question, just like a real interviewer would. Answer out loud, in your own words — it's fine to think out loud.

When you're done answering, just pause: the interviewer will understand that you've finished. You can also click the "I'm done" button. The interviewer will then move on to the next question.

Yes. Say "let's move on," "next question," or "let's skip this one" and the interviewer will move on to the next one. A skipped question will almost certainly get 0 points in the report, but the interview will continue.

• Put on headphones: most often the interviewer gets thrown off by hearing its own voice through your speakers.
• Check that your browser is using the right microphone (the microphone icon in the address bar).
• If the interviewer moved on while you were thinking, next time try thinking out loud: a long silence sounds like the end of your answer.
• If something went completely wrong, click "End" and start over; let our support team know what happened and we'll look into it.

In interviews with a coding stage, the interviewer asks you to solve a problem in the editor and think out loud. She sees your code and run results, and may ask questions about your solution. When you're done, say "done" or click "I'm done". After the coding part, the interviewer will ask a couple of questions about complexity and edge cases, just like in a real interview.

Each question has a rubric — a list of points that a strong answer should cover, each with its own weight. After the interview, an AI judge goes through every point and decides whether it came up in your answer, citing a quote from your answer. A point without a quote doesn't count.

The score itself is calculated by code, not by the model: it's the share of the total weight covered by the points you hit, from 0 to 100. That's why the score is consistent and easy to explain — the report shows why each point was credited and what was missing.

It's the verdict for the whole interview at your level:

• Strong Hire — a confident "yes": strong answers on almost every question;
• Hire — a "yes", but with some gaps;
• No Hire — a "no" for now: noticeable gaps in key topics.

A verdict is only given for an interview completed to the end. The OFFER stamp appears in the report for Hire and Strong Hire.

Common reasons:

• a rubric point only counts if it was actually said in your answer — "I know this" without an explanation won't count;
• your answer was correct but too brief: it lacked examples, reasoning, or trade-offs;
• the interview was cut short — questions you didn't get to are scored as 0.

Open the report: every point you didn't cover has a note explaining what was missing. If you're sure the score is wrong, flag it when rating the interview ("Unfair score") or contact support.

Only you. Your reports, scores, and profile are private. For reports, we store a text transcript of your answers; audio recordings aren't saved by default. Interviews for your own job posting are visible only to you and don't count toward public leaderboards.

The only public content is the comments you post yourself in discussions of questions and problems.

A single voice question that takes about 4 minutes: the interviewer asks a question, you answer, and a minute later you see your score and which points you covered. You can start a drill right from the question's page in the library. That's also where you'll find the breakdown: what's being assessed, how to structure your answer, and common mistakes.

The lists in the menu help you come back to questions: Favorites are the ones you've starred, and Needs work are the ones where your answer is still weak.

Python, JavaScript, Java, Go, and C++. Pick your language above the editor; your draft is saved separately for each language.

Common reasons:

• You've used up your practice for this month. Voice interviews, drills, and their reviews cost us real money, so every account has a monthly practice budget. You can see how much is left in the menu under your avatar: a percentage and roughly how many interview minutes remain. Your budget resets every month on the day you signed up. Problems, the library, and reports don't use up your budget.
• The interview ended early — if your budget runs out mid-interview, the interviewer will politely wrap things up, and you'll still get your report.
• Another interview is already in progress — for example, in another tab. Finish that one first.
• Your email isn't verified — after your first voice session, we'll ask you to confirm your address using the link in the email we send you.
• No microphone access — allow it in your browser (the lock icon in the address bar) and refresh the page.

• Run checks the first 3 tests and shows details for each one, so you can debug your solution quickly.
• Submit checks your solution on the server against all tests, including hidden ones. Only this result counts: the problem is marked "Solved" and an entry appears in "My submissions".

Each test has a limit of up to 3 seconds. A slow solution will get "Time limit exceeded" on a specific test, which means you need a faster algorithm.

Yes: Google, GitHub, GitLab, and Discord — the buttons are below the sign-in form. If you previously signed up by email with the same address, signing in through one of these services will open the same account.

On the sign-in page, click "Forgot password?" and enter your email — you'll get an email with a link. The link is valid for one hour and works only once. Didn't get the email? Check your Spam folder or request a new link.

Settings → Delete account: enter your email to confirm. All your interviews, answers, reports, task submissions, and support conversations will be deleted. This can't be undone.

In Settings — open the menu under your avatar in the top right corner. From there you can also link or unlink sign-in with Google, GitHub, GitLab, or Discord, sign out on all devices, and delete your account.

We use your role and level to pick mock interviews and the question of the day on the home page. You can only change your email through support — we need to verify that the new address belongs to you.

After you sign up, we send you an email with a link — click it and your address is verified. This way we know the account is yours, and we can help if you forget your password.

• Everything works without verification, but you can only do one voice interview or drill — after that, we'll ask you to verify.
• No email? Check your spam folder. To resend it, use the button in the yellow bar at the top of the page (up to 3 emails per hour). The link is valid for 3 days.
• If you sign in with Google, GitHub, GitLab, or Discord, there's no need to verify — the service has already confirmed your address.

When you sign up, reset your password, or enter the wrong password several times in a row, we check that a human is filling out the form. Usually the check is invisible — the button just "thinks" for a second. Sometimes a checkbox appears: just tick it.

Can't get past the check? Refresh the page, turn off your VPN or ad blocker for our site, or try a different browser. Too many login attempts in a row? Wait 15 minutes or reset your password.