The single highest-leverage thing you can do before a technical interview is mock practice with a real human who has interviewed at your target company. Everyone says this. It's true. But three out of four candidates we talk to don't have access to that — either they don't have a network of senior engineers, can't afford $200 for an interviewing.io mock, or are interviewing in a country where Pramp-style partner matching is thin. So they end up doing what feels like a poor substitute: solo problem-solving on LeetCode.
That's not the only option. Solo mock practice, done right, gets you 80% of the value of paired mocks — and you can fit it around a job. The trick is to simulate the pressure, not just do the problems. This guide is the seven methods we've seen work, ranked from easiest-to-start to highest-fidelity.
Method 1: The 45-minute timer + camera-on rule
Pick a LeetCode medium you haven't seen. Open your phone's camera in selfie mode, prop it next to your laptop so you can see yourself in the frame. Start a 45-minute timer with no pause. Talk out loud the entire time, explaining your approach as if to an interviewer. Don't peek at the solution — if you run out of time, write down where you got stuck and grade yourself.
Why this works
The camera turns your internal monologue into external speech. The brain treats being watched (even by yourself) as a stress event. You'll catch yourself doing things you'd never do alone: long silences, jumping to code before clarifying, abandoning a working approach because you panicked. The camera reveals these patterns; you can't fix what you can't see.
Pro tip
Watch the recording back at 1.5x speed afterwards. You don't need to watch all 45 minutes — just scrub through. The pauses, "ums," and abandoned thoughts will jump out.
Method 2: AI mock interviewer (text or voice)
An AI interviewer can ask you a question, follow up with clarifying questions, push back when you give a weak answer, and grade your response. The fidelity has improved dramatically with GPT-4o and Claude Sonnet 4 voice modes. They can interrupt politely, mirror an interviewer's pacing, and even play "skeptical senior engineer."
How to set it up (any chat LLM)
Use this prompt with Claude, ChatGPT, or Gemini's voice mode:
You are a senior engineer at <Google/Meta/Amazon> conducting a 45-minute coding interview at the <L4/E5> level. Your behavior: - Ask one coding question (LeetCode medium or medium-hard). - Wait for me to clarify before approving the approach. - Push back if my solution is suboptimal or my code is unclear. - Time-check me at 25 minutes if I haven't started coding. - At the end, give me a 5-minute follow-up question (e.g., scale, streaming, alternate approach). - Do NOT give me the answer until I explicitly ask. - Grade me at the end on: problem framing, algorithm choice, code quality, communication, time management.
What this is good for
- Volume practice (do 5 mocks in a weekend at zero cost)
- Drilling specific weak spots ("ask me only graph problems")
- Practicing the meta-skill of communicating under questioning
- Getting instant, structured feedback without scheduling
What this is NOT good for
- True interpersonal stress (AI is patient; real interviewers aren't always)
- Detecting subtle communication issues like over-confidence
- Cultural fit / behavioral rounds (AI praises everything by default)
Our CoPilot Interview app includes a structured "Interviewer Mode" that's designed for this use case — it generates questions, evaluates your answers, and produces a scored report at the end.
Method 3: Record yourself solving in front of an empty Zoom
Open Zoom. Start a meeting with yourself. Hit record. Solve a problem out loud, pretending the interviewer is in the corner of the screen. After 45 minutes, watch the recording.
Why it's more stressful than camera-only
Something about Zoom specifically triggers the "interview brain" — the green camera light, the floating self-view, the awareness that this is being recorded. Many candidates report this is the closest thing they've found to real virtual interview pressure.
Bonus: do it with screen-share on
Most virtual interviews are conducted with screen-share. Practice with your editor or whiteboarding tool open while screen-sharing in Zoom. You'll catch the small annoyances (window switching, your face blocking the editor, audio echo) that always seem to happen for the first time during the real interview.
Method 4: Reverse mocks — interview yourself as the interviewer
Pick a problem you've already solved. Pretend you're the interviewer giving it to a candidate. Write down: what clarifying questions would you ask the candidate to draw out? What's the optimal solution? What follow-ups would you give? What does a Strong Hire look like vs Lean Hire?
Why this works
Becoming the interviewer in your head is the fastest way to internalize what interviewers grade on. Once you've "scored" a few candidates (yourself in past mocks, or hypothetical candidates), you stop solving for "the right answer" and start solving for "the signal." That shift is worth dozens of LeetCode problems.
Try this
Spend an hour mocking yourself as the interviewer for one canonical problem (say, "design a URL shortener"). Write down: what would I want to hear? At the end, take that rubric and grade your own most recent attempt at the same problem.
Method 5: Timed problem chains
Pick 3 LeetCode mediums on related patterns (e.g., all binary tree problems). Set a 2-hour total timer. Solve them back to back with no breaks longer than 90 seconds.
Why it works
Real on-site loops are 4-5 rounds in a single day, and the cognitive fatigue is significant. Most candidates' last two rounds are noticeably worse than their first two, purely from exhaustion. Building chain endurance in practice makes you durable for the real thing.
How to use the data
Track your solve time and confidence (1-5 scale) for each problem in the chain. After several chain sessions, you'll see a pattern: problem 3 is often where you're sloppiest. That's where your bottleneck is — not at the problem-difficulty level but at the endurance level.
Method 6: Auto-graded coding platforms with hard timers
HackerRank and CodeSignal both have "real interview" simulation modes that put you in front of a problem with an enforced timer, no IDE auto-complete, and webcam recording. CodeSignal's General Coding Assessment (GCA) is used by 40+ companies as an actual screening test, so practicing on it has dual value.
Recommended sequence
- Do 2-3 CodeSignal GCAs to baseline your speed under stress
- Do HackerRank's mock interviews for company-tagged sets (especially Amazon, Goldman Sachs, Bloomberg if those are targets)
- Track your scores over time — if you plateau, the issue isn't more problems, it's pattern recognition
Method 7: Pramp peer mocks (one human, no commitment)
This is the "one human" hack. Pramp matches you with a random peer. You give them a coding problem for 30 minutes; they give you one for 30 minutes. Both of you are practicing. It's free, no scheduling friction, and you get the interpersonal stress that solo work can't replicate.
Caveats
Match quality is uneven — you might get a senior engineer or someone who's clearly less prepared than you. We recommend at least 3-5 sessions to get the average effect. Use it for coding rounds; behavioral mock partners on Pramp are rarely well-calibrated.
Pro tip
Even if you don't have an interview partner in your network, do ONE Pramp mock per week throughout your prep. It's the lowest-friction way to get human interview reps.
The combination that beats human-only mocks
Here's the schedule we recommend for someone with no interview partner:
| Week of prep | Solo / AI mocks | Pramp / paid mocks |
|---|---|---|
| Weeks 1-2 | 3-4 per week (method 1, 2) | 0 |
| Weeks 3-4 | 3 per week (method 2, 3, 5) | 1 Pramp per week |
| Weeks 5-6 | 2 per week | 2 Pramp + 1 paid mock |
| Week 7 | 1 per week | 2 paid mocks (different disciplines) |
| Week 8 (taper) | 1 | 1 final calibration mock |
This combination consistently outperforms "5 paid mocks and nothing else" because the solo work builds fluency that the paid mocks just calibrate.
The 5 things solo mocks can't teach you (and what to do about them)
Be honest with yourself about the gaps. Solo work can't replicate:
- The interruption rhythm. Real interviewers ask "what do you mean by that?" at unexpected moments. Fix: at least 2-3 Pramp / paid mocks before the real loop.
- The follow-up unpredictability. A live human might pivot the question mid-flow. Fix: AI mocks with explicit "throw a curveball" instruction in the prompt.
- Body language self-detection. You don't know your tells. Fix: Video recordings + watching them back.
- The vibes test. Behavioral rounds reward warmth and presence. Fix: One behavioral mock with a human friend, ideally someone who doesn't work in tech — they'll give you blunt "did you sound likable?" feedback.
- Real-stakes adrenaline. Nothing simulates wanting the job. Fix: Treat the early rounds of your real loop (e.g., the first 1-2 phone screens) as paid mocks for the loops you actually want. The first one or two real-stakes interviews are themselves the best training.
Counter-intuitive tip: apply to companies you don't really want first. Use those early loops as paid mocks. By the time you reach your target company's loop, you'll have done 2-3 real-stakes interviews with cumulative learnings.
AI-powered mock interviews, on demand
CoPilot Interview's Interviewer Mode generates questions, scores your answers in real time, and produces structured reports. Use it for unlimited solo mocks.
Download freeFAQ
Are AI mock interviews as good as human ones?
AI mocks are excellent for volume practice, instant feedback, and stress-free repetition. Human mocks are essential for behavioral nuance, follow-up unpredictability, and real interpersonal stress. Use AI for the first 70% of your mock work; human partners for the final 30% before your loop.
How do I simulate interview pressure when alone?
Three reliable techniques: (1) record yourself on video and rewatch — the camera is the pressure, (2) set a strict 45-minute timer with no pause button, (3) Zoom-call yourself and pretend the interviewer is real. Best results when you stack all three.
Is solo mocking enough or do I need at least one human?
Plan for at least 2-3 human mocks before your real loop. Solo work develops fluency; human mocks calibrate your stress response and reveal communication gaps you can't self-detect. The combination is much stronger than either alone.
What about behavioral rounds?
Behavioral is harder to mock solo because the feedback signal is largely about delivery, warmth, and likability. Record yourself answering 3-5 STAR questions on video. Watch the recordings. You'll catch the "trailed off" or "talked for 6 minutes" issues that you can't feel from inside the answer. Pair with one human mock if possible.
I don't have a Pramp partner that matches my level. Now what?
Use interviewing.io's free first-mock offer (they often run promos), or post in r/cscareerquestions or your school's CS Slack/Discord. Many candidates underestimate how willing peers are to swap mocks when asked directly.