Building Services in Go interview questions

Standard-library HTTP, project structure, dependency management, and testing patterns.

3 questions in Go.

Go for infrastructure and servicesA 20-minute read on how the topic fits together, before the questions.Go fundamentals60 short answers on one page, for revising rather than studying.

medium3

mediumConceptCoding

A client hangs up halfway through a request. How do you structure a Go HTTP service so it stops doing the work?

Go context cancellation stops wasted request work when the client disconnects or a timeout expires. Pass the request context into database, HTTP and worker calls, and make goroutines return when ctx.Done closes.

7 minmid, senior, staff

mediumDesignCoding

Go gives you no project layout and no dependency-injection container. How do you structure a service so it stays testable as it grows?

Wire dependencies explicitly through constructors from one place in main, define narrow interfaces where they are consumed rather than implemented, and keep handlers thin enough that the logic beneath is testable without a server. With no framework, these are decisions rather than defaults.

5 minmid, senior, staff

mediumConceptDesign

What are the subtle trade-offs and failure modes when scaling Building Services in Go in production?

Evaluate architectural trade-offs in Building Services in Go between consistency, throughput, operational complexity, and data durability at scale. Use this GOLANG answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects go services to the point an interviewer is testing.

1 minmid, senior