Skip to content
Vera
6 things to practise

You are grinding LeetCode. The offers are lost elsewhere.

Screens, system design, behavioral rounds, and the take-home review.

Technical candidates lose on the rounds where they have to talk.

What this actually involves

Engineering loops have a well-known trap: the coding rounds get all the preparation and the conversational rounds decide the outcome. System design is graded on narration, the behavioral round wants specifics you have never said aloud, and the take-home review asks why you made each choice days after you stopped thinking about it. This covers the talking half, which is the half most engineers skip.

The sequence

Roughly in order, though nothing here blocks anything else — start with whichever is next for you.

  1. First
    Recruiter Phone Screen PrepTwo-minute background pitch and the compensation question. Fifteen minutes of practice here is worth more than another hundred LeetCode problems.Practise this ↗
  2. Before coding rounds
    Thinking Out Loud in Coding InterviewsSolo practice actively trains you to solve silently, which is what fails the round. This unlearns it.Practise this ↗
  3. Mid loop
    System Design Interview PracticeVoice-only removes the diagram you have been hiding behind, which is the point.Practise this ↗
  4. Behavioral round
    Software Engineer Interview PrepProject stories with numbers attached, and the difference between what your team did and what you did.Practise this ↗
  5. Before applying
    Write down three project stories with numbersLatency figures, user counts, incident durations — whatever you actually measured. Engineers routinely have the numbers and have never said them aloud, so the answer comes out as "it got faster".You do this one. Vera isn’t involved.
  6. If applicable
    Take-Home Walkthrough PracticeRehearse the night before the review. It reliably surfaces the weak section while you can still fix it.Practise this ↗
  7. At offer
    Salary Negotiation PracticeEngineers under-negotiate more than almost any other role, usually by naming a number and immediately softening it.Practise this ↗

Common questions

Should I still do LeetCode?

Yes, but it does not prepare you for the rounds where you have to explain. Those need separate practice.

Which step matters most?

For most people, thinking out loud — the habit of silent solving is the single most common reason strong engineers fail interviews.

Can I skip system design if I am junior?

Often, though the narration practice transfers to every other conversational round.

Other goals

Land a Product Manager RoleRecruiter screen, hiring manager, product sense, behavioral, and the negotiation nobody prepares for.Break Into Tech From Another CareerAnswer it well once, then the rest is a normal job search.

Not practising doesn’t save you anything.

The ticket, the evening, the weeks of applying — all of it is spent before anyone says a word. The practice is the only cheap part, and the only part that changes how the rest goes.

Start with step one

15 minutes free · no card needed