AI mock interview practice for the role you want
Practise behavioural, technical and coding interviews with your job details as context. Answer by text or voice, review specific feedback and save your setup for the next attempt.
Last updated:
Lyrra’s AI mock interviews let you rehearse a job interview around your target role and experience level. Choose the kind of questions you need, respond by text or voice, and use the session report to decide what to practise next. Coding interviews add a challenge workspace for writing and testing a solution.
Set up practice around the job you are applying for
Choose your specialisation, role type, experience level, assessment type, session language and duration. Add a job description to give the conversation a more specific focus. You can also select a saved application document as context.
A useful starting point is the next hiring round you expect. For a customer success role, you might prepare examples of handling a difficult conversation. For an engineering role, you might focus on explaining a technical decision or solving a coding problem.
You can begin without a job description or saved document. Adding relevant context helps make the rehearsal more specific, but Lyrra does not know an employer’s private questions or hiring rubric.
Choose behavioural, technical or coding practice
Interview format | When to choose it | What to expect |
|---|---|---|
Behavioural | Prepare examples of collaboration, responsibility, conflict or decisions. | Questions about experience; feedback on your contribution and STAR structure. |
Technical | Practise explaining knowledge and decisions relevant to your profession. | Role-specific questions and scenarios; explain your assumptions, approach, and trade-offs. |
Coding | Prepare for a round that includes a programming challenge. | A code editor, available sample tests, and feedback on your submitted solution and explanation. |
Behavioural interviews: explain what you did
Practise questions about collaboration, responsibility, conflict, decisions and learning from experience. Use real examples that show your own contribution. The report can help you review the STAR structure: situation, task, action and result.
A useful result does not always need a number. A decision that resolved a disagreement or a process that made a handover clearer can also show what changed, provided you explain it concretely.
Technical interviews: make your reasoning clear
Work through questions and scenarios relevant to your profession. Explain your approach, assumptions, constraints, and trade-offs, then describe how you would check that the approach works. Technical practice covers role-specific knowledge; it is not limited to software engineering.
Coding interviews: solve a challenge and explain the solution
Read the challenge, work in the code editor, run available sample tests, and submit a final solution. Use the results to investigate errors and edge cases, then explain why you chose your approach.
Code execution supports JavaScript and TypeScript, including TSX, subject to the challenge’s supported languages. The editor also lists other languages, but that does not mean those languages can run tests. Check the challenge and execution status before choosing your language.
Type your answers or practise speaking aloud
Use text when you want to concentrate on the substance of an answer. Enable Audio call to listen and respond using your microphone. Speaking aloud gives you a chance to notice answers that are easy to write but difficult to deliver clearly.
Voice input requires microphone permission and a browser that supports speech recognition. You can inspect the transcribed draft before sending it. Voice reports include pace and filler-word indicators derived from the transcript and session timing; treat these as approximate cues rather than precise speech measurements.
Sessions support English, Dutch, French, German, Romanian, Italian, Spanish, and Polish. Select the language you expect to use in the interview, then choose from the available voices if you enable audio.
Use guided coaching or add pressure with Stress test
Enable Guided coaching when you want to request a hint during the conversation. This can help you move forward when you are stuck. On a later attempt, try answering without a hint to see whether you can explain the same idea independently.
Stress test adds a more demanding interviewer style to behavioural, technical, or coding practice. Expect sharper follow-up questions that press you to explain your decisions and trade-offs. The setup uses a fixed 20-minute duration.
Choose ordinary practice to work on an answer’s structure, then use Stress test when you want to rehearse under more pressure. It is a simulation for practice, not a psychological assessment or a measure of your suitability for a job.
Use the report to understand individual answers
After a completed session, review the assessment, strengths, improvement areas, and answer-level feedback. Open an answer to revisit what you actually said alongside the feedback. Depending on the interview type and available report data, you can review:
Behavioural structure: which parts of the situation, task, action, and result you described.
Technical reasoning: how clearly you explained your approach, constraints, and validation.
Coding work: recorded test results and feedback on the submitted solution and its explanation.
Coaching suggestions: advice and example wording where provided for the answer.
Voice delivery: approximate pace and transcript-based filler-word indicators for voice sessions.
The overall assessment summarises the session. The question average summarises the scored answers; the two are not necessarily the same. Interviewer confidence, where shown, is a recorded value from the simulation, not a real employer’s level of interest.
Turn one piece of feedback into a concrete revision
Suppose feedback says your contribution was unclear. Before adding detail everywhere, ask: What decision did I personally make? What did I do next? What changed because of it?
Illustrative example: “We improved onboarding” describes a team outcome. If these are the facts of your experience, a more specific answer would be: “I reviewed the support handover, found that account details were missing, and introduced a checklist so the next owner had the information needed to continue.”
Use the structure of an example to examine your own answer. Keep your own facts and wording rather than memorising a suggested script.
Save your setup and make the next attempt easier to prepare
Save an interview setup with its settings, job details and selected document so you can reuse it later. Give it a name that identifies the role or the round. You can rename, update, or delete a saved setup, and review its settings before starting another session.
In your history and progress views, revisit completed sessions, review available score trends, and find the strengths and improvement areas from your latest report. For a useful comparison, keep the assessment type, difficulty, and context reasonably similar.
When one issue deserves focused work, explore the Practice Workspace. It uses connected feedback to support smaller exercises between full interviews.
A useful first practice session
Choose the round. Pick behavioural, technical, or coding practice to match what you expect next.
Add relevant context. Set the experience level, paste the job description, and select a current saved document if useful.
Answer as you would in the interview. Explain your reasoning and ask for clarification when you need it.
Choose one improvement. Read the feedback for a specific answer and decide what you will change on the next attempt.
Need help organising your preparation before starting? Read the job interview preparation guide. To update the document you use as context, open the resume and cover letter builder overview.
AI mock interview questions
Do I need a resume or job description to start?
No. You can start with the role and setup choices. Add a job description or select a saved document when you want the session to use more specific context.
Can I practise without using a microphone?
Yes. Use text mode to type your answers. Audio call is optional and requires microphone access and browser speech-recognition support.
Is technical interview practice only for developers?
No. Technical practice focuses on knowledge and reasoning relevant to the profession you select. Coding is a separate assessment type for working on a programming challenge.
How many credits does an interview use?
A regular interview uses one credit. Stress test uses two credits and has a fixed 20-minute setup duration. Review your balance and the current plans and credit options before starting.
Will the AI ask the same questions as my employer?
No. The conversation uses your setup and supplied context to create practice questions. It does not have access to an employer’s private interview plan.
Can the report tell me whether I will get the job?
No. It provides AI-generated feedback on this practice session. Read the explanation alongside your answers and judge whether it is useful. A score is not a hiring prediction, and employers may assess the same answer differently.
Practise the interview you need to prepare for
Choose a role, set up a session, and use one specific piece of feedback to improve your next answer.