Loading…
0+ curated questions with the same answer shape every time: quick recap, deep dive, pitfalls, and follow-ups. Coverage includes .
Go runtime questions come up at senior and staff-level interviews, especially at companies running Go services at scale. This module covers escape analysis (the compiler decides stack vs heap at compile time; variables that 'escape' are heap-allocated and GC'd — use go build -gcflags='-m' to see decisions), the concurrent tri-color mark-sweep garbage collector (mark phase, sweep phase, write barrier, why Go's GC pauses are sub-millisecond by design), GOGC and GOMEMLIMIT for tuning, pprof for CPU profiling (goroutine blocking, function call stacks) and memory profiling (heap allocations, allocation sites), the race detector (-race flag and what it catches), GOMAXPROCS and the Go scheduler's M:P:G model (OS threads, logical processors, goroutines), and benchmarking with testing.B. These questions separate Go developers who understand the runtime from those who just write goroutines.
Full catalog
Topics are ordered for learning. Within each topic, rows are numbered 1–0 globally so you always know where you are. Collapse topics if you want a lighter view — use Expand all when you need the full list again.
Numbers 1–0 follow the order we recommend — click any row to open the full answer, or use the sticky Next link at the bottom of each page to go Q1 → Q0.