Feedback with a follow-through.
Review strengths, gaps and suggested actions after an interview. Use scores as a reflection tool, not a prediction of an employer's decision.
How feedback works ↗︎The product
Practise mock interviews, build a behavioural Story Bank and work through coding and system-design questions. Review AI feedback alongside your own judgement.
A connected space to prepare your stories, think through difficult problems and practise answering out loud.
A generic question list can only take you so far. Add the role requirements and practise with context that reflects your next move.
You have solved problems, made decisions and worked through setbacks. Use STAR — situation, task, action and result — to give those experiences a structure you can return to.
Good technical interviews involve more than a solution. Practise framing the problem, explaining trade-offs and testing your reasoning.
A session is a starting point. Your stories, feedback and practice history help you decide where to spend your next bit of effort.
Review strengths, gaps and suggested actions after an interview. Use scores as a reflection tool, not a prediction of an employer's decision.
How feedback works ↗︎Organise assumptions, approaches, trade-offs and tests in coding and system-design workspaces. Explain how you reached the answer.
Keep your practice history and plan upcoming sessions. Come back to the same skills as your next opportunity gets closer.
Each tool supports a different part of preparation. Start with the one that addresses the gap in your last attempt.
Choose your role, experience level and text or voice mode. Add an optional job description or PDF CV to focus practice on your next opportunity.
Review the questions against your expected interview format. Added context does not give MockReps access to an employer's questions or hiring rubric.
See how a session worksRecord the situation, your task, your action and the result in Story Bank. Start with a real experience and make your own contribution clear.
For a technical disagreement, explain the evidence that changed the decision. Keep the facts intact as you shorten or improve the answer.
Work through a STAR exampleBring assumptions, an approach, edge cases and proposed tests to a guided workspace. Use feedback to choose an explanation to strengthen.
Check the technical advice yourself. These workspaces do not execute your code or validate a running cloud environment.
Try the engineering rehearsalPublic guides are free to read without an account. Personalised interviews, reports and technical feedback reviews use credits, with a separate cost for each step. Every new account starts with 15 free credits.
Original uploads are temporary. A minimised career profile provides context for practice, with cleanup built into processing.
Bring your experience. Find your words. Take the next step.
Start practising Prepare for your next role. Pay once.Google Analytics helps us measure visits, signups and purchases across our website and app. Optional TikTok advertising cookies help measure our campaigns on this public site. Your interview content stays out of analytics. You can keep browsing without choosing.
Read our cookie notice