All Soreno features
Practice Feedback and History

Turn practice feedback into a specific next step

Soreno keeps a practice history with session status and available results. After a scored mock, review the feedback on your answers and the suggested next steps. Use a specific comment to choose what you'll practice next.

What to review after a session

A score is a starting point. The useful part is identifying a correction you can test in another answer.

  • Response feedback

    Completed mock results can include performance analysis, comments on individual responses and actionable steps. Read the explanation alongside the answer you gave.

  • Practice history

    Return to your saved mocks and drills to see their status and available results. Incomplete or unscored sessions aren't evidence of a drop in ability.

  • Presentation comments

    When enabled and successfully processed from usable session imagery, presentation analysis can comment on visible delivery, such as posture. Treat it as separate coaching input, not a precise attention or confidence measurement.

How it works

Keep a short correction log alongside your app results. Compare similar tasks before interpreting a difference in scores.

1
Read the evidence

Find a comment about a particular response. Check whether the feedback describes an error, a missing assumption or a different way to organize the answer.

2
Write one correction

Replace a broad goal like 'improve math' with an observable action: 'state the denominator before calculating a percentage change.'

3
Test it on a new example

Run a related drill or mock and check whether you made the same mistake. Use the result and your working, rather than a single score, to decide the next step.

Write a correction you can check

This fictional feedback example gives you a simple correction log. Suppose you described an increase from 100 orders to 120 as '20 percentage points.'

  1. Step 1

    Record the mistake: order count isn't a percentage, so percentage points don't describe its change.

  2. Step 2

    Write the corrected calculation: (120 − 100) ÷ 100 = 20% growth, or 20 additional orders.

  3. Step 3

    Test a new pair: 80 orders to 100 is 20 additional orders but 25% growth. State the original count before calculating.

  4. Step 4

    Review whether your next explanation used the right units. That observable correction is more useful than interpreting one overall score as progress.

How to interpret the results

Signal 1
AI feedback and scores can contain mistakes. They aren't calibrated employer assessments or predictions of an offer.
Signal 2
A harder case, different exercise or shorter answer can change a result. Compare the task and response before interpreting score changes.
Signal 3
Feedback may still be processing. No-answer and too-short sessions can be unscored; presentation analysis may be unavailable even when answer feedback is ready.

When to review your results

  • Candidates reviewing completed practice
  • Candidates planning their next drill
“Pinpoint gave our coaches instant visibility. We stopped chasing spreadsheets and focused on feedback that moved the score.”
Priya K.
Career advisor • Top-10 MBA

Soreno by the numbers

4,500+

mock interviews run last cycle

92%

of candidates improved structure scores in 2 weeks

75

schools & clubs using Soreno playbooks

FAQ's

Frequently Asked Questions

Everything you need to know about Soreno, answered in one place.

Open your practice history and select the session. Available results depend on its status and whether it produced enough material for feedback.
No. Empty or very short answers can remain unscored, and results take time to process. Check the session status before treating a missing score as a performance result.
No. It's practice feedback based on the response and evaluation used for that task. Check the comments, verify calculations and use your employer's official material to understand its assessment.
Choose a drill or mock that tests one weakness identified in the feedback. Write down the correction first, then check whether it carries over to a different example.