Project dive · MockOraa
Turning interview practice into a loop people return to
A 0→1 product where the hardest design problem was motivation, not features.
People preparing for interviews practise inconsistently and cannot tell whether they are actually improving.
- Domain
- Interview practice
- My role
- Product Designer — concept, flows, usability
- Team
- Raviteja Mokkarala, Pallavi Saple, Mounesh Pattar, Navyashree L S, Snehal Gharave, Vasini Singh, Praveen Prabhakaran
- Duration
- 3 months
- Platform
- Consumer product
- Status
- Design Complete
Overview
The project at a glance
Product Designer — concept, flows, usability
Raviteja Mokkarala, Pallavi Saple, Mounesh Pattar, Navyashree L S, Snehal Gharave, Vasini Singh, Praveen Prabhakaran
3 months
Interview practice · Consumer product
Consumer product
0→1 product · Behaviour design · Confidence metrics
The challenge
Preparation tools are good at generating questions and poor at sustaining practice. People start, feel exposed, and stop.
Business context
MockOraa blends AI + psychology to create a safe space to practice, reflect, and grow through empathy-first feedback.
User context
The problem occurs before the candidate enters a real interview, when they are preparing, practicing responses and trying to build confidence. Our target users included: Freshers Career-gap professionals Mother returnees Career switchers Design implication: The experience needed to work for people arriving with very different levels of interview experience and confidence.
Problem framing
From the requirement to the real problem
- 01 · Initial request
Preparation tools are good at generating questions and poor at sustaining practice. People start, feel exposed, and stop.
- 02 · Investigation
Interviews are a repeated-performance skill, so a product that measures a single attempt measures the wrong thing.
- 03 · Underlying user problem
People preparing for interviews practise inconsistently and cannot tell whether they are actually improving.
- 04 · Product opportunity
Design a low-friction practice loop that makes improvement visible—not just performance—so each session gives users a reason to practise again.
The design brief became: make the second session more likely than the first.
Evidence
How I understood the problem
I used a combination of user research, product analysis and usability testing to understand why job seekers struggle with interview preparation—not simply what features they might want. The research was conducted with 20 participants, focusing on the anxiety and underpreparedness candidates experience before interviews. The documented project process includes research, ideation, IA, wireframing, design system, prototyping, usability testing and iteration.
User Research — 20 participants
To understand candidates' interview-preparation challenges, anxieties and unmet needs.
Competitive / product analysis
To examine how existing interview-preparation experiences approach practice, questioning and feedback.
Ideation & Information Architecture
To translate the research findings into a guided interview-practice experience.
Usability Testing
To identify friction in the experience and validate whether the proposed flow was understandable and usable.
What has already been tried here?
Interview preparation already includes resources such as question-based preparation and evaluation. The opportunity we identified was to bring these elements together into a more interactive AI-powered practice experience rather than treating preparation as a static activity. Design implication: Move from preparing for questions to experiencing the interview.
Where does this live in the user's day?
The problem occurs before the candidate enters a real interview, when they are preparing, practicing responses and trying to build confidence. Our target users included: Freshers Career-gap professionals Mother returnees Career switchers Design implication: The experience needed to work for people arriving with very different levels of interview experience and confidence.
What forces constrain the experience?
An interview is a sequential interaction: Question → Think → Respond → Follow-up → Feedback The interface therefore couldn't behave like a conventional information dashboard. The candidate needs to concentrate on the conversation while the system manages the complexity in the background. Design implication: Keep the interview flow focused and minimize unnecessary interaction during the actual conversation.
How do the parts react together?
The product combines several sensitive elements: AI interviewer + candidate response + evaluation + feedback The challenge was not only generating a score. It was presenting feedback in a way that could help candidates understand their performance without making the experience feel purely judgmental. Design implication: Feedback became part of the experience design—not something added after the interview.
How does the behaviour actually grow?
Interview confidence is developed through practice and reflection. The product therefore connects: Practice → Feedback → Improvement → Next practice The progress experience is intended to help candidates understand their development over time rather than treating every interview as an isolated event. Design implication: Progress becomes part of the product experience through the progress dashboard and repeated practice.
What can be measured and defended?
Evidence we measured
- Research participants: 20
- Usability testing: conducted
- Task completion: tested
- User understanding: observed
- Product acceptance/readiness signals: captured
- Final product impact metrics: to be validated
User insights
Observation → insight → implication
- Observation
Abandonment clustered before the first answer, not during it.
- Insight
When candidates already feel uncertain about their interview readiness, the practice experience needs to feel approachable rather than adding another layer of complexity.
- Design implication
Reduce the path to practice and make the mock interview the primary entry point.
- Observation
Participants reacted defensively to absolute scores in early concept tests.
- Insight
For an anxious candidate, knowing how to improve is more useful than simply knowing whether they performed well or poorly.
- Design implication
Use structured feedback alongside progress tracking rather than relying on a single performance indicator.
- Observation
A practice experience becomes more useful when individual sessions contribute to an ongoing preparation journey.
- Insight
A practice session becomes more valuable when users can understand what they learned and what they should work on next.
- Design implication
Connect feedback and progress to the next practice opportunity.
- Observation
The project was fundamentally addressing interview anxiety and underpreparedness, so the experience needed to feel supportive rather than intimidating.
- Insight
The product shouldn't make candidates feel like they are being judged by another recruiter. It should create a space where they can practice, receive feedback and improve.
- Design implication
We designed MockOraa as a practice partner rather than a hiring authority, using supportive feedback and inclusive modes to create a lower-pressure preparation environment.
User journey
Where the experience breaks down
The journey is designed around a simple transformation: Unprepared → Practice → Feedback → Improvement → Confidence
- 1DiscoverUser action
The job seeker recognizes that they need to prepare for an upcoming interview and looks for a way to practice.
User thought“I know I need to prepare, but how can I practice a real interview?”
Pain pointTraditional preparation can provide questions and learning material, but it doesn't necessarily recreate the experience of interacting with an interviewer.
EmotionAnxious · Uncertain · Underprepared
OpportunityPosition MockOraa as a safe practice environment, rather than another study-resource platform.
- 2StartUser action
The candidate enters MockOraa, identifies their profile/role and prepares to start an AI mock interview.
User thought“Will this interview actually be relevant to the role I'm preparing for?”
Pain pointCandidates have different experience levels and preparation needs. A generic interview experience may not feel relevant.
EmotionCurious · Nervous · Hopeful
OpportunityPersonalize the interview using: Role + Experience + Resume/JD + Interview type so that the user understands why the questions are relevant.
- 3UseUser action
The candidate participates in an AI-powered mock interview with an avatar, answers questions and receives feedback about their performance.
User thought“How did I actually perform—and what should I improve?”
Pain pointA mock interview is only useful if the candidate can understand what happened during the interaction and how to improve.
EmotionFocused → Evaluated → Curious → Motivated
OpportunityCreate a feedback loop: Interview ↓ Performance analysis ↓ Instant / structured feedback ↓ Actionable improvement ↓ Practice again
- 4ReturnUser action
The candidate reviews their feedback and progress, identifies areas for improvement and returns for another practice session.
User thought“I know what I need to work on. Let me try again.”
Pain pointWithout visible progress or a clear connection between feedback and future practice, improvement can feel difficult to track.
EmotionMore aware · Encouraged · More confident
OpportunityTurn individual interview sessions into a continuous learning loop: Practice → Feedback → Improve → Practice again Use the progress dashboard to make development visible.
Product opportunity
Where value, viability and feasibility meet
People preparing for interviews practise inconsistently and cannot tell whether they are actually improving.
Create a repeatable practice experience that gives users a reason to return, while making MockOraa's AI interview and feedback capabilities valuable across multiple practice sessions.
An interview is a sequential interaction: Question → Think → Respond → Follow-up → Feedback The interface therefore couldn't behave like a conventional information dashboard. The candidate needs to concentrate on the conversation while the system manages the complexity in the background. Design implication: Keep the interview flow focused and minimize unnecessary interaction during the actual conversation.
Design a low-friction practice loop that makes improvement visible—not just performance—so each session gives users a reason to practise again.
Process
Directions considered, flows and early exploration
Concept A
- What it solves
- Reduces the complexity of getting from preparation to an actual practice interview.
- Strength
- Keeps the primary experience focused on the core user goal: start practising.
- Limitation
- Provides less emphasis on long-term progress if the experience is treated only as a single interview session.
- Effort / complexity
- Moderate — requires role/interview context, guided setup and AI interview interaction.
- User value
- Gives candidates a more structured and approachable way to practise.
Concept B
- What it solves
- Makes the value of an interview session clearer by connecting practice directly with structured feedback.
- Strength
- Creates a clear relationship between: Answer → Evaluation → Improvement
- Limitation
- If feedback becomes too detailed, it can overwhelm users who are already anxious about their performance.
- Effort / complexity
- Moderate–High — requires AI analysis and a structured feedback model.
- User value
- Helps candidates understand not only how they performed, but where they can improve.
Concept C
- What it solves
- Connects individual mock interviews into an ongoing preparation journey.
- Strength
- Combines the documented product directions of AI Mock Interviews + Instant Feedback + Progress Dashboard into one continuous loop.
- Limitation
- Requires more product structure than a standalone mock interview because progress needs to be represented consistently across sessions.
- Effort / complexity
- High — requires session history, progress states, feedback aggregation and repeat-practice flows.
- User value
- Makes improvement visible and gives users a reason to continue practising.
Selected directionA practice loop rather than a one-off interview
I selected the Progress-Based Practice Loop because it brings the strongest parts of the three directions together:
Guided entry → makes practice approachable
AI mock interview → creates realistic practice
Instant structured feedback → makes improvement actionable
Progress dashboard → makes development visible over time
The product direction documented in the Codex ultimately identifies AI Mock Interviews, Instant Feedback, Progress Dashboard and Inclusive Modes as the key outcome.

Design Process /Style Guide
Final experience
The solution
Design decisions
Decisions, not just screens
Optimise the start, not the score
- ProblemAbandonment clustered before the first answer, not during it.
- Options considered
- Multi-step interview preparation flow
- Role/context selection before starting
- Guided entry into a mock interview
- Direct entry into the practice experience
- Trade-offMore preparation can provide greater personalization, but additional steps can increase cognitive load before the user reaches the core value.
- DecisionReduce the path to practice and make the mock interview the primary entry point.
- WhyThe product's core value is practice. I therefore prioritized getting users into a realistic interview experience quickly while retaining only the context necessary to make the session relevant.
- Expected outcomeTo be validated: reduced friction before starting a mock interview and improved completion of the initial practice flow.
Show change, not judgement
- ProblemParticipants reacted defensively to absolute scores in early concept tests.
- Options considered
- Single overall performance score
- Category-based feedback
- Detailed qualitative feedback
- Feedback combined with progress across sessions
- Trade-offA single score is easy to understand, but can oversimplify performance. More detailed feedback is more actionable, but can increase cognitive load.
- DecisionUse structured feedback alongside progress tracking rather than relying on a single performance indicator.
- WhyThe documented product direction combines Instant Feedback with a Progress Dashboard. This supports a shift from simply evaluating one interview to helping the user understand their development over time.
- Expected outcomeTo be validated: users should be able to identify improvement areas and understand their progress across practice sessions.
Make the second session obvious
- ProblemA practice experience becomes more useful when individual sessions contribute to an ongoing preparation journey.
- Options considered
- End the experience after displaying feedback
- Return users to the dashboard
- Recommend an improvement area
- Connect feedback directly to another practice session
- Trade-offShowing everything users could do next creates choice, but can also create decision fatigue. A focused recommendation provides direction but reduces user choice.
- DecisionConnect feedback and progress to the next practice opportunity.
- WhyThe Progress Dashboard was identified as a core product outcome. I used it to frame practice as a continuous loop rather than isolated interview sessions.
- Expected outcomeTo be validated: users should understand what to work on next and be able to continue practising without having to reconstruct their preparation journey.
Private by default
- ProblemThe project was fundamentally addressing interview anxiety and underpreparedness, so the experience needed to feel supportive rather than intimidating.
- Options considered
- Standard interview experience
- Highly evaluative experience
- Supportive AI practice experience
- Inclusive modes accommodating different user needs
- Trade-offA highly realistic interview can increase authenticity, but an overly evaluative experience may conflict with the goal of creating a safe environment for practice.
- DecisionWe designed MockOraa as a practice partner rather than a hiring authority, using supportive feedback and inclusive modes to create a lower-pressure preparation environment.
- WhyThe documented product outcome explicitly includes Inclusive Modes, alongside AI Mock Interviews, Instant Feedback and the Progress Dashboard. This allows the product to address both performance and the human experience surrounding interview preparation.
- Expected outcomeTo be validated: users should feel more comfortable practising, understand the feedback they receive, and be able to use the experience across different accessibility needs.
Testing & validation
What was tested, and what changed
- Prototype
- Test
- Observe
- Learn
- Iterate
We tested the core MockOraa experience to evaluate whether the proposed AI mock-interview flow, feedback experience and overall product structure were understandable and usable.
Research: 20 people were involved in understanding the problem of interview anxiety and underpreparedness.
Usability testing was incorporated into the design process to evaluate the prototype and identify areas for iteration. The documented process confirms: Research → Ideation → IA → Wireframes → Design System → Prototype → Usability Testing → Iteration.
The final product direction therefore brought together: AI Mock Interviews Instant Feedback Progress Dashboard Inclusive Modes
Testing and iteration informed the evolution of the prototype toward a more structured product experience, with: AI Mock Interview ↓ Instant Feedback ↓ Progress Tracking ↓ Inclusive Practice
Quantitative impact was not measured.
Before → after
- Multi-step setup before the first question
- A single absolute score per attempt
- No defined next action after a session
- Practice framed as performance
- One-tap session start
- Progress delta across sessions
- Each session ends by proposing the next one
- Practice framed as private rehearsal
Outcome & impact
What changed — reported honestly
Design a low-friction practice loop that makes improvement visible—not just performance—so each session gives users a reason to practise again.
Qualitative — intended outcome.
The concept evolved from an AI interview experience into a more complete preparation product combining: AI Mock Interviews Instant Feedback Progress Dashboard Inclusive Modes
The project progressed through a structured design cycle: Research → Ideation → IA → Wireframes → Design System → Prototype → Usability Testing → Iteration.
Reflection
What I learned
The structured design process helped evolve MockOraa beyond a basic mock-interview concept into a broader preparation experience combining AI Mock Interviews, Instant Feedback, Progress Dashboard and Inclusive Modes.
I would strengthen the validation phase with a more clearly documented usability study. Specifically, I would define: the usability-test sample size the key tasks being evaluated task-completion criteria confidence measurement method repeat-practice behaviour follow-up measurement after the initial session This would make it possible to move from “the experience appears useful” to evidence about whether it actually improves preparation behaviour.
For skill products, the design target is the return visit. Anything that makes the first session impressive but the second session unlikely is a net loss.
If I had more time — next I would explore…
- — Measure session completion and 7-day repeat rate
- — Run a documented usability study with a stated sample size
- — Validate the confidence instrument against a standard scale
Team & collaboration
- My contribution
- Product Designer — concept, flows, usability
- Team contribution
- [DETAIL TO VERIFY]
In short
The case study in four lines
- The problem
- People preparing for interviews practise inconsistently and cannot tell whether they are actually improving.
- The decision
- Optimise the start, not the score
- The outcome
- Design a low-friction practice loop that makes improvement visible—not just performance—so each session gives users a reason to practise again.
- The learning
- For skill products, the design target is the return visit. Anything that makes the first session impressive but the second session unlikely is a net loss.