Know exactly why you didn't get the offer — and fix it before the next interview.
Debrief every interview in 5 minutes. Get honest feedback, a CV you can defend line by line, and prep that targets your real weak spots.
Step 1
Tell us how it went
Five minutes of notes after the interview: what they asked, what you said, where you froze.
Step 2
Get the honest read
Likely reasons for the outcome, your weak spots, and stronger answers — grounded in your own words.
Step 3
Fix it before the next one
Concrete drills, plus the questions your CV invites. Your recurring weak spots build up across every interview.
Sample debrief
This is what you get back
From notes on a senior backend interview that ended in a rejection after the system design round.
The honest read
You were solid on the coding exercise but lost the system design round: you jumped into components before pinning down requirements, and when asked about consistency you had no trade-off to offer. That is a very common reason for a senior-level rejection.
Most likely reasons
No clear reasoning on consistency vs. availability when challenged
high confidenceBased on: You said you “just said we'd use Postgres” when asked what happens during a partition.
Skipped requirements and scale estimates at the start
medium confidenceBased on: You described drawing the architecture in the first two minutes.
Weak spots
System design: trade-offs
highNamed technologies without justifying the choice.
At senior level the interviewer is grading your reasoning, not your component list.
Structuring a design interview
mediumStarted drawing boxes before agreeing on requirements.
It signals you design for a problem you haven't defined yet.
What went well
Clean, working solution to the coding problem
You finished it with ten minutes to spare and tested edge cases.
Stronger answers
What happens to your service during a network partition?
We'd use Postgres so it would be consistent.
For the booking path I'd choose consistency over availability: a failed request is better than a double booking, so writes go to a single primary and the API returns a retryable error if it's unreachable. Read-only browse pages can serve slightly stale data from replicas.
Practise next
Do five timed system-design problems, 45 minutes each
Spend the first 5 minutes on requirements and numbers out loud; record yourself and check you named at least one trade-off per component.
Three tools, one loop
Interview debrief
What worked, where you lost points, and what to practise next. Not ten generic tips — feedback tied to what actually happened.
CV check with an honesty check
Paste your CV and a job. Get the fit, the gaps, and the claims you couldn't defend once an interviewer starts digging.
Questions from your own CV
“You wrote you cut latency by 40%. How did you measure it?” Prepare for the questions your bullets actually invite.
Pay as you go. No subscription.
Every new account starts with free energy — enough for your first analysis. Top up only when you need more.
A debrief costs 50 energy, a CV check 75, and CV-based interview questions 50. Energy doesn't expire. If an analysis fails, your energy is refunded.
Questions
- Is this a live-interview copilot?
- No, and it never will be. We don't listen to your calls or feed you answers while you interview. preps.work is for the work before and after: understanding what went wrong and getting better.
- How is this different from pasting my notes into ChatGPT?
- ChatGPT answers what you ask, once. Here every debrief feeds your dashboard, so recurring weak spots show up across your whole search, and the CV check is built to challenge your claims, not flatter them.
- What happens to my CV and notes?
- They're stored to build your history and sent to our AI provider (Anthropic) only to produce your analysis. They're never shown to anyone else and never used to rate people or companies. Want them gone? Email us and we'll delete your account and data.
- Who is it for?
- Built for software engineers from Ukraine and Eastern Europe applying to EU and US companies — but it works for any engineer who wants straight feedback.
- How does energy work? Does it expire?
- You prepay for energy and each analysis uses a fixed amount, shown before you start. Energy doesn't expire, and if an analysis fails the energy is refunded automatically. There's no subscription to cancel.
More questions? hello@preps.work