An imposter's guide to growth in engineering
summary
Defines imposter syndrome as feeling inadequate despite evident success and links it to low serotonin; maps three root feelings to a comfort/weird/growth zone; gives concrete tools: ask managers why one was chosen, find a transferable hook, timebox daily work (example blocks of 3.5 hours), open imperfect PRs, share findings, and volunteer for hard tickets. Cites learning Ruby/Rails and shipping a working feature — a flexible order routing system documented on Shopify’s engineering blog — as evidence these steps work.
AI-written summary · about
chapters (15)
- 0:00Imposter syndrome basics
- 2:29What imposter syndrome is
- 5:20Symptoms in engineers
- 11:03Imposter syndrome as growth
- 12:28Comfort vs growth zones
- 15:17Biology and serotonin
- 16:44Tools to boost serotonin
- 17:47Finding team significance
- 22:47Leveraging past knowledge
- 24:16Overcoming default behaviors
- 27:26Sharing knowledge builds confidence
- 30:33Tackling difficult tasks
- 32:17Honesty and openness with yourself and others
- 33:50Failure and burnout handling
- 35:39Measuring success via feedback
related talks
46mImposter Syndrome: Overcoming Self-Doubt in Success
38mTips to Fight Impostor Syndrome
30mTips for Fighting Impostor Syndrome
39mOvercoming imposter syndrome
30mCode, Confidence & Conquering Self-Doubt: Breaking Impostor Syndrome in Tech
55mImposter Syndrome: Overcoming Self-Doubt in Success
25mOvercoming imposter syndrome
24mImpostor syndrome, am I suffering enough to talk about it?