Back to all articles
Candidate guides

Do You Still Need to Code by Hand for Interviews? What a Live Coding Round Listens For, and a Two-Week Plan

Yes, you will likely meet a no-AI coding round. What it actually listens for, how to ask which format you get, and a two-week plan to get fluent again.

H
The Hyrr team
•4 min read

If you have spent the last two years writing code with an assistant beside you, the idea of a blank editor and a person watching can feel like being asked to do long division without a calculator. It is a fair worry, and the honest answer is: yes, you will probably still meet a round where you write code without AI. But the round is not testing what most people fear it tests.

Two formats, and you will likely see both

Companies now run coding rounds in two broad ways:

  • The classic round. No assistant. You write a small, working piece of code and talk through it.
  • The AI-allowed round. You may use an assistant, and the interviewer watches how you prompt it, check its output and explain what you keep. We wrote about that format separately: "You can use AI in this interview": what is actually being scored.

You rarely know in advance which one you will get. Ask the recruiter. "Which format does each technical round use, and can I use an assistant in any of them?" is a normal question, and most recruiters will answer it.

What the classic round is actually listening for

Speed of typing and perfect syntax are not the point. A live coding round is mostly a conversation with code in it. A good interviewer is listening for:

  1. Do you understand the problem before you start? Restating it, asking what the inputs look like, naming an edge case or two.
  2. Do you have a plan? A sentence like "I'll do the simple version first, then fix the duplicate case" tells the interviewer you are steering, not guessing.
  3. Can you explain every line you write? This is the one AI-heavy habits weaken most. If you cannot say why a line is there, it reads as copied even when it is not.
  4. Do you test your own code in your head? Walking one small input through the code, out loud, and catching your own bug is one of the strongest signals you can give.
  5. Do you know the trade-offs? "This is fine for a few thousand items; for millions I'd use a hash map instead of the nested loop."
  6. Do you take a hint well? When the interviewer nudges, they want to see you use it, not defend the first attempt.

Notice what is missing: memorised trivia and flawless syntax. A forgotten method name, said out loud ("I don't remember if it's .sort() or sorted() here, I'll use sorted() and check"), costs you very little.

A two-week plan for getting fluent again

You do not need months. You need your hands and your mouth working together again.

Days 1–5: 30 minutes a day, assistant off. Pick small problems in the language you will interview in: reverse words in a string, merge two sorted lists, count the most common item, parse a log line. Write each one by hand, then explain it aloud as if someone were listening. Record yourself on your phone if that helps. The goal is fluency, not difficulty.

Days 6–10: add the narration under pressure. Set a 20-minute timer. Talk the whole time: restate, plan, code, walk an example through, name the trade-off. If you go quiet for more than a minute, say what you are thinking, even "I'm deciding between two approaches".

Days 11–14: a full rehearsal, twice. Do at least two complete mock rounds, ideally with a real listener who asks follow-ups. Watch them back. Look for the moments you went silent, the lines you could not explain, and the bug you did not catch until the interviewer pointed at it. Those three things are your whole revision list.

Throughout: keep one AI-allowed rep a week. Prompt, review, and say out loud why you accept or reject the output. That covers the other format.

Practising with Hyrr

Hyrr's practice interviews let you rehearse a technical round out loud with an AI interviewer that talks back and asks follow-ups:

  • Set it up for the job you want. Paste or upload the posting, or describe the role, or practise from your own background. Pick the level, a difficulty (Warm-up, Standard or Hard) and the interviewer's style: Coaching gives a tip after every answer, hints when you are stuck and the offer to retry a weak one; Realistic gives no help and saves the feedback for your report.
  • Add the coding workspace. You get one or two hands-on exercises in a live code editor and whiteboard that the interviewer watches. It supports JavaScript/TypeScript, Python, Java, C/C++, Go, Rust and SQL. The interviewer sees your code as you write it, so it can ask about the actual line you just typed. Coding quietly is fine: it does not treat that as silence. Like most live rounds, the editor does not run your code, so the walkthrough is yours to do out loud.
  • Choose the length. Fifteen minutes is a warm-up; forty-five or sixty minutes is a full round.
  • Watch it back. The session is recorded so you can review it. It never counts against you and no employer ever sees it. Your report shows your code and whiteboard as you left them.
  • Drill the weak spots. Question drills pull the questions you scored lowest on from your own practice interviews, weakest first, with instant feedback. You can answer in code.

Practice uses credits, priced by how long the session actually runs; the setup shows the cost before you start.

Practise a coding round out loud

The short version

  • Expect a no-AI round and an AI-allowed round; ask the recruiter which is which.
  • The no-AI round tests whether you understand and can explain your code, not how fast you type.
  • Two weeks of short daily hand-coding plus out-loud rehearsal is enough to get fluent again.

Do you interview engineers at work? Hyrr runs the first-round interview for your open roles, out loud, and gives your team a report on every candidate. Create an employer account

See a live AI interview

Pick a sample role and take the interview yourself, in the browser or by phone. Your scored report lands in your inbox.