i used to dread mocks because everything felt rehearsed — the candidate would rattle off frameworks and the debrief would be polite fluff. over time i started requesting unfiltered debriefs from community veterans and noticed two things: they call out the tiny human moments (hesitations, unclear assumptions) and they recreate interviewer pushback to show realistic pivots. in my experience, that combination exposes the real interview flow and gives you fixable, tactical next steps rather than another ‘good job’ pat. how have you asked for that level of blunt feedback without coming off defensive?
honestly, most people treat mocks like theater practice — expect applause after a monologue. if you want realism, tell your mock interviewer to play devil’s advocate and actually interrupt you. say ‘don’t sugarcoat it’ and mean it. you’ll hear the parts where you lean on jargon or panic. don’t expect compliments; expect specific cuts. change is painful, but that’s how you stop sounding like every other rehearsed candidate.
look, frameworks are fine as props, but give me clarity on the assumption you’re making and i’ll shred it. i’ve seen people fall back to buzzwords the moment pressure hits. the trick? force a 60-second interruption rule: interviewer asks a blunt follow-up mid-solution. if you freeze, that’s the exact feedback you need. it sounds harsh, because it is — interviews are harsh. learn to take it.
thanks — this resonates! i tried asking for blunt feedback once and the veteran actually paused my case when i rambled. it stung but i learned to make cleaner assumptions. anyone got a short script to ask for a “no-fluff” debrief next time? i get shy asking directly 
I’ve run and coordinated numerous mock interviews with junior candidates across consulting and product roles. When candidates explicitly request candid critiques, I frame the debrief around three pillars: observable behavior, immediate impact, and a single actionable change. For example, instead of saying “your structure was weak,” I point to the exact moment the structure broke, explain why it matters to a scorecard, and suggest one drill (timed issue trees or 60-second summaries). Invite the veteran to annotate timestamps if possible; that turns vague comments into step-by-step practice tasks and preserves psychological safety in the session.
one time i requested a mock where the interviewer purposely cut me off with a surprise constraint. at first i floundered, but then i realized how often i leaned on slides of frameworks instead of asking clarifying q’s. after that drill i practiced 3-minute reset routines and they helped a ton.
Across 40+ mock sessions i’ve tracked outcomes where candidates requested explicit, timestamped critiques versus general feedback. The timestamped group reduced repetition and filler usage by ~35% over 4 weeks, according to self-coded transcripts. The practical takeaway: ask your veteran to note 2–3 timestamps during the mock and give one prioritized fix per timestamp. That converts subjective ‘it felt scripted’ into measurable behaviors you can train against.