Technical interview practice: the senior-expert cross-team round
This round is usually run by a senior engineer or tech lead from another team. They have no stake in your project; they only judge one thing: do you have real technical judgement?
The hard part isn't the questions, it's the follow-ups. They will challenge your design directly and follow it down to first principles. Say “that's what everyone uses” or “performance was fine” and they'll ask for an actual number.
Start a technical interview practice sessionLanguage note: the practice room's on-screen controls are currently in Chinese. Under 高级设置 (Advanced settings), set the interview language to English — the interviewer then asks, follows up and writes your report in English.
What this round decides
Your technical level — and often the level of the offer. The expert wants to confirm that you really designed the systems on your resume and hit their problems yourself, that you know when your design breaks, and that when challenged you defend with evidence instead of backing down on the spot.
The three things this interviewer checks
Depth of expertise
Where the bottleneck in your system was, how you found it, and what the real numbers were after launch.
Trade-off judgement
Why you chose this stack, what it cost, and whether you'd choose it again today.
Boundary awareness
Under what conditions the design fails, and what you'd change first if traffic grew tenfold — and why in that order.
How the session runs
- 1
Opening
You explain what you've been working on recently.
- 2
Resume drill
Verification: did you really design the systems on your resume, and did you hit their problems yourself?
- 3
Competency
Technical depth, awareness of limits, and judgement in choosing technologies.
- 4
Pressure
Your trade-offs are challenged head-on, to see whether you hold to your evidence or change your answer immediately.
- 5
Candidate questions
The floor is yours. Asking about the team's technical debt and the hard problems they're working on says more about you than asking about overtime.
How it follows up
- Challenges your design directly and follows it down to first principles.
- Won't accept “roughly” or “that's what people usually use” — asks for a concrete order of magnitude.
- Asks what every technical choice cost.
How it asks (examples, not a question bank)
Why did you choose this tech stack? What did it cost you?
You say the performance is good. Can you give me an actual order of magnitude?
The three most common ways to lose this round
- Saying what you used but not why.
- Falling apart when asked about edge cases and limits.
- Reciting textbook answers that miss the actual question.
Have these ready
- For every technology choice on your resume, at least one alternative you rejected and what rejecting it cost.
- Real numbers for your key systems — throughput, latency, data volume, cost — and how they were measured.
- The worst problem you've hit: the symptom, how you tracked it down, the root cause and the fix.
- The job description (this round also builds questions from its technical requirements).
What you get afterwards
- A three-tier hiring verdict — Hire / Borderline / No-hire risk — instead of an inflated score.
- Ratings on six dimensions: content credibility, structure, role fit, handling follow-ups, delivery and pacing, and the quality of your own questions.
- Three to six pieces of evidence, each of which must be a verbatim fragment of what you said — if a quote doesn't match the transcript, the whole report is rejected — each with the original audio to replay.
- Question-by-question notes: what you said, what was wrong with it, and a better way to say it; plus the interviewer's overall note, up to three next actions, and the questions you skipped.
- The report flags your weakest dimensions, and you can start a practice round aimed at exactly those.
Questions
Is this a coding interview?
No. MockLive is a spoken interview with no coding exercises. This round practises your judgement about systems you've actually built: why you chose them, what they cost, where they break, and the real numbers.
What if I can't give an exact number?
Say you don't know and explain how you would measure it — far safer than inventing a figure. The report quotes the places where you covered a gap with “roughly” or “usually”; those are the numbers to look up before the real thing.
When challenged, should I hold my position or concede?
Follow the evidence. In the pressure stage the interviewer deliberately pushes back on your trade-offs; it's looking for whether you have reasons, not whether you give in. If you have grounds, state them. If the other side is right, say so and explain what you'd change.
Technical interview practice: the senior-expert cross-team round
Start a technical interview practice session