Loading…
0+ curated questions with the same answer shape every time: quick recap, deep dive, pitfalls, and follow-ups. Coverage includes .
Engineering practices interview questions filter for senior and staff Go engineers. This module covers code review for Go (what to flag first: exported types without comments, missing error checks, goroutine leaks, interface pollution — and how to give feedback that lands without the 'just use Java' subtext), technical debt strategy in Go (how to make the case for refactoring a 50k-line Go service, how to introduce golangci-lint incrementally without breaking the whole team), Architecture Decision Records for Go teams (when to write one — choosing between Gin and Echo, switching from database/sql to GORM, introducing generics into a pre-1.18 codebase), Go idiomatic code standards (gofmt is non-negotiable, effective Go naming conventions, the package-level documentation comment), and mentoring Go engineers (how to explain goroutine scheduling to someone who thinks in threads, how to introduce the context package to someone who's never used structured cancellation). Every answer uses the reflection beat — not 'here's what I did', but 'here's what I learned.'
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.