Loading…
0+ curated questions with the same answer shape every time: quick recap, deep dive, pitfalls, and follow-ups. Coverage includes .
Production operations and SRE interview questions for Go test whether you've run Go services under real traffic and real incidents. This module covers SLI/SLO/SLA applied to a Go HTTP service (defining the error budget from the SLO, how it drives deployment decisions), graceful shutdown in Go (signal.NotifyContext, http.Server.Shutdown with a deadline, draining in-flight requests and closing the database pool in the correct order), goroutine leak detection (the runtime.NumGoroutine metric, pprof goroutine profile, the patterns that cause leaks — goroutine blocked forever on a channel, goroutine waiting on a context that was never cancelled), memory leaks in Go (the difference between a GC pause and a genuine leak, how to detect a growing heap with pprof, the common causes: global maps that grow without bound, closures capturing large objects), Go-specific performance profiling (CPU flame graph with go tool pprof, allocation profiling with -memprofile, escape analysis with gcflags), and the incident response playbook for a Go service going down. These questions are asked at companies where Go is the primary service language.
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.