Go developer grades, or What distinguishes a senior gopher from the rest
summary
Looks at how the profession of Go developer is evolving and critiques common interview practices like LeetCode puzzles and rote questions about threads vs goroutines or garbage collection. Proposes which concrete skills and expectations should distinguish junior, mid, and senior Go engineers and how hiring and assessment should change to match real-world Go development.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:33Talk overview
- 3:21Developer grades
- 6:13Go salaries market
- 9:22Hard skills
- 12:10Competency matrix
- 13:13Soft skills
- 26:56Interview process
- 28:00Soft skills impact
- 33:52Adaptability skills
- 36:16Creativity emotional IQ
- 37:18Career growth
- 40:28Salary responsibility
- 42:10Uncertainty management
- 44:19Effective learning
- 45:19Mental models abstractions
- 46:01Communication new tech
- 46:44Q&A
related talks
54mThe Grades of a Go Developer, or What Distinguishes a Senior Gopher
50mHow to Become a Senior Engineer
48mInterviewing Senior Developers: Testing Soft Skills with Hard-Skills Questions
01h 03mHow to Level Up from Mid to Senior
10mA great developer - how to be one, how to find one?
36mSenior Developer Development
26mHow Does a Senior Developer Evolve?
45mTo Be or Not to Be a Senior