placd.in

Goroutines & Concurrency interview questions

15 real Goroutines & Concurrency questions from the Go bank, as asked in Indian campus drives and tech interviews. Every question has a verified answer and an AI-tutor explanation on placd — free to start.

1. What is Goroutine?

Junior
  1. A.a lightweight function execution started with the go keyword and multiplexed onto OS threads by the runtime
  2. B.the setting that limits how many operating-system threads may execute user code simultaneously
  3. C.the runtime component that maps goroutines onto threads using per-processor run queues that steal tasks when idle
  4. D.the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added
Reveal the answer + AI explanation — free account

3. Which statement is correct?

Junior
  1. A.Goroutine — a lightweight function execution started with the go keyword and multiplexed onto OS threads by the runtime
  2. B.Goroutine — the runtime component that maps goroutines onto threads using per-processor run queues that steal tasks when idle
  3. C.Goroutine — a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished
  4. D.Goroutine — the setting that limits how many operating-system threads may execute user code simultaneously
Reveal the answer + AI explanation — free account

4. What is GOMAXPROCS?

Mid
  1. A.the runtime component that maps goroutines onto threads using per-processor run queues that steal tasks when idle
  2. B.the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added
  3. C.a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished
  4. D.the setting that limits how many operating-system threads may execute user code simultaneously
Reveal the answer + AI explanation — free account

6. Which statement is correct?

Mid
  1. A.GOMAXPROCS — a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished
  2. B.GOMAXPROCS — a lightweight function execution started with the go keyword and multiplexed onto OS threads by the runtime
  3. C.GOMAXPROCS — the setting that limits how many operating-system threads may execute user code simultaneously
  4. D.GOMAXPROCS — the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added
Reveal the answer + AI explanation — free account

7. What is Work-stealing scheduler?

Senior
  1. A.the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added
  2. B.the runtime component that maps goroutines onto threads using per-processor run queues that steal tasks when idle
  3. C.the setting that limits how many operating-system threads may execute user code simultaneously
  4. D.a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished
Reveal the answer + AI explanation — free account

9. Which statement is correct?

Senior
  1. A.Work-stealing scheduler — the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added
  2. B.Work-stealing scheduler — the runtime component that maps goroutines onto threads using per-processor run queues that steal tasks when idle
  3. C.Work-stealing scheduler — the setting that limits how many operating-system threads may execute user code simultaneously
  4. D.Work-stealing scheduler — a lightweight function execution started with the go keyword and multiplexed onto OS threads by the runtime
Reveal the answer + AI explanation — free account

10. What is WaitGroup?

Mid
  1. A.the setting that limits how many operating-system threads may execute user code simultaneously
  2. B.the runtime component that maps goroutines onto threads using per-processor run queues that steal tasks when idle
  3. C.a lightweight function execution started with the go keyword and multiplexed onto OS threads by the runtime
  4. D.a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished
Reveal the answer + AI explanation — free account

12. Which statement is correct?

Mid
  1. A.WaitGroup — a lightweight function execution started with the go keyword and multiplexed onto OS threads by the runtime
  2. B.WaitGroup — a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished
  3. C.WaitGroup — the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added
  4. D.WaitGroup — the setting that limits how many operating-system threads may execute user code simultaneously
Reveal the answer + AI explanation — free account

13. What is Loop variable capture (pre-1.22)?

Senior
  1. A.the setting that limits how many operating-system threads may execute user code simultaneously
  2. B.the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added
  3. C.the runtime component that maps goroutines onto threads using per-processor run queues that steal tasks when idle
  4. D.a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished
Reveal the answer + AI explanation — free account

14. Which term means: "the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added"?

Senior
  1. A.Goroutine
  2. B.Loop variable capture (pre-1.22)
  3. C.GOMAXPROCS
  4. D.WaitGroup
Reveal the answer + AI explanation — free account

15. Which statement is correct?

Senior
  1. A.Loop variable capture (pre-1.22) — a lightweight function execution started with the go keyword and multiplexed onto OS threads by the runtime
  2. B.Loop variable capture (pre-1.22) — the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added
  3. C.Loop variable capture (pre-1.22) — a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished
  4. D.Loop variable capture (pre-1.22) — the setting that limits how many operating-system threads may execute user code simultaneously
Reveal the answer + AI explanation — free account

Free to start

Answers, AI explanations, and a scored voice mock interview

Sign up free to check your answers with explanations, ask the AI tutor anything on any question, and take one full AI mock interview — scored like a real panel.

Practice Goroutines & Concurrency free

More Go topics

Core Language (15)Types & Structs (15)Interfaces (15)Channels (15)Error Handling (15)Memory & Performance (15)Generics (15)Standard Library & Idioms (15)Packages & Tooling (15)