GO THE BACKEND INTERVIEW SERIES / 2026

Know the answer.
Explain the why.

The Go Backend Interview Playbook

From goroutines to garbage collection. Build a clear mental model of Go’s internals—and give answers that hold up to the next question.

English PDF One-time purchaseNo subscription
goroutines.goINTERVIEW NOTES
01package main
02
03func main() {
04 go work()
05}
06
07// Who runs this goroutine?
Q.02 / THE SCHEDULER30-second answer

What do G, M, and P represent?

G is a goroutine. M is an operating-system thread. P is the scheduler resource required to execute Go code. An M normally needs a P to run a G.

G GoroutineM OS threadP Execution context
15core topics
31focused pages
14free quick answers
01complete playbook

01 / THE SYLLABUS

One guide. The important internals.

Follow the full syllabus or jump straight to the topic you need to brush up on.

GROUP 01

Runtime & memory

Understand what happens beneath your code.

  • 01Garbage collection & write barriers
  • 02The GMP scheduler
  • 03Memory allocation
  • 04Preemption
  • 05Escape analysis
GROUP 02

Concurrency & coordination

Reason about the goroutines working together.

  • 06Channels
  • 07Maps & sync.Map
  • 08Context & timeouts
  • 09Synchronization primitives
  • 10Concurrency exercises
GROUP 03

Language essentials

Get the details right when follow-ups get specific.

  • 11Strings & select
  • 12defer, panic & recover
  • 13Interfaces
  • 14Arrays & slices
  • 15Interview checklist

02 / THE APPROACH

Go beyond
memorized answers.

Knowing an API is one thing. Explaining what happens underneath is what makes an interview answer convincing.

01

Start with the short answer.

Get the essential idea across in 30 seconds. Then follow the reasoning into the details.

02

Know what changes between releases.

Separate language guarantees from scheduler, collector, and map implementation details.

03

Think through the failure cases.

Build intuition for contention, goroutine leaks, deadlocks, and shutdown behavior.

03 / START HERE · FREE

Your next interview.
Your first 14 answers.

Every 30-second answer from Part I, in one handy PDF. Read it before you buy, or keep it for a quick refresh.

Download the free edition5 pages · English PDF · No email required
quick-answers.pdfFREE
01

How does Go garbage collection work?

02

What do G, M, and P represent?

03

How does Go allocate objects?

04

What does a channel maintain?

BUILT FOR YOUR NEXT TECHNICAL ROUND

You write Go.
Now talk Go.

A good fit

Mid-level and senior backend engineers, developers moving into Go, and interviewers refreshing their technical questions.

A different starting point?

If you’re learning your first language or looking only for algorithm drills, this guide isn’t designed for that stage.

04 / THE COMPLETE EDITION

A stronger answer
starts here.

Go Runtime & Concurrency Interview Playbook

  • All 15 core topics in a 31-page English PDF
  • Quick answers and deeper explanations
  • Code examples and concurrency exercises
  • Version notes and an extended question bank
  • Personal-use license
THE COMPLETE PLAYBOOK
$19USD

One payment. Yours to keep.

Checkout coming soonPayments aren’t open yet. You can download the free edition now.
PDF download + delivery link by email when checkout opens.
Want a taste first? Get the free edition.

05 / A FEW MORE ANSWERS

Before you dive in.

What exactly am I buying?

A 31-page English PDF with 15 core topics, concise answers, deeper explanations, code examples, and an extended question bank. It is a one-time purchase for personal use.

What is included in the free edition?

All 14 answers explicitly labeled “30-second answer” in Part I, collected into a 5-page PDF. The complete edition adds deeper reasoning, implementation details, code, and the extended question bank.

How will I get my PDF?

When checkout is available, confirmed PayPal payments unlock a download on the success page. An order download link is also sent to your PayPal email. The order link lasts 7 days and allows up to 5 download-link requests.

Do I need to know Go already?

Yes. This guide is for engineers who already write Go and are preparing for mid-level or senior backend interviews. It is not a first programming course or a collection of algorithm drills.

Which Go version does it cover?

The guide separates language guarantees from implementation details and includes version-sensitive notes. Runtime internals should always be checked against the Go release you are discussing.