After the Offer: Succeeding as a New SWE
summary
A clear playbook for the first year: prioritize engineering excellence by learning Kotlin after a Java to Kotlin migration (one mistake here once broke Instagram), spend 30 minutes before work reading teammates’ code, and push for regular clean-up hackathons to remove dead code. Measure everything with numbers (a recruiting panel example: 300 attendees → ~20 leads → hires). Manage your manager for project priority, scope with buffers, ask quick questions early, and take on a mentee after six months to grow influence.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 4:05Performance metrics
- 5:47Engineering excellence
- 10:40Measuring project impact
- 13:56Self-sufficiency and growth
- 16:52Direction and management
- 20:26People, culture, and power
related talks
42mHow to Hit the Ground Running as a Staff + Software Engineer at a New Company
37mWhat I wish I knew when I was a junior developer that I would tell as a staff software engineer
24mElevating Young Developers: Best practices for seasoned developers on onboardings
17mHow to Do Great Work
36mHow To Onboard New Hires Into Happy and Productive Employees
17mThe Junior Jump: from Student to Team Member
40mCorporate Success: The Unwritten Curriculum
26mAll the things I learnt as a junior developer (so you don't have to)