← System design · Lesson 2 of 5

Thinking out loud and signposting

Give the interviewer a map, so they can follow your thinking without guessing.

What they’re listening for

  • • Can I follow how you're thinking?
  • • Do you start simple and improve step by step?
  • • Do you check in with me, or just talk at me?

The interviewer can't see inside your head. Signposts are short phrases that say where you are and where you're going next. They also give you a few seconds to think.

Stiff vs. natural

Interviewer: “Okay, your assumptions sound good. Where do you want to start?”

Sounds stiff

“(draws for two minutes in silence) …So this is the architecture. There is a load balancer, three services, a cache, a queue and two databases.”

Sounds natural

“So my plan is to start with the simplest version that works, then look at where it breaks when we add traffic. Simplest version: one service, one database. A request comes in with a long URL, we generate a short code, save the pair and send back the short link. A redirect is just a lookup by code. That obviously won't survive millions of clicks, but it gives us something to break. Does that sound like a good place to start?”

  • “My plan is…” gives a roadmap in one sentence.
  • Starting simple is easy to explain and shows good judgment.
  • “Something to break” is a relaxed way to say you'll improve it next.
  • Ending with a question turns it into a conversation.

Parking a question and coming back to it

  1. You

    “Okay, so for the short code, I'm thinking we generate a random seven-character string and save it.”

  2. Interviewer

    “What happens if two links get the same code?”

  3. You

    “Ooh, good point, collisions. Can I park that for one minute? I want to finish the basic flow first, and then I'll come right back to it.”

    Park it, but say when you'll come back.

  4. Interviewer

    “Sure.”

  5. You

    “So a redirect goes: browser, our service, look up the code, send the redirect. Okay, back to collisions, like I promised. Seven characters of letters and numbers gives us trillions of codes, so collisions are rare, but rare isn't never. Simplest fix: make the code column unique. If the insert fails, we generate a new code and try again.”

    Coming back on your own builds trust.

  6. Interviewer

    “Makes sense.”

Signposts

  • “My plan is to start simple, then see where it breaks.”A roadmap at the start.
  • “Let me park that and come back to it.”Saving a good question for later.
  • “Okay, back to …, like I promised.”Returning to something you parked.
  • “So where we are now is…”A quick recap in the middle.
  • “I'm going to zoom in on …, since that's the interesting part.”Choosing where to go deep.
  • “Does that make sense so far, or should I go deeper anywhere?”Checking in.

Now say it out loud

Rehearse with the AI interviewer and get feedback on your answers.