Career Advice I'd Give Every Software Engineer Right Now
Show notes
Engineering hasn't become easier, writing code has just become faster. Time to stop fighting symptoms and start thinking in systems. In this Q&A, I break down the career advice I'd give to any engineer, from mastering architecture to knowing when to quit a high-paying job.
In this episode, we cover:
- How "Systems Thinking" can be applied in practice
- The "Golden Handcuffs": Why high salaries keep engineers in toxic jobs
- How to transition into leadership without waiting for a title
Timestamps
00:00:00 - Intro
00:00:58 - How to innovate in stubborn legacy companies
00:04:49 - The "Golden Handcuffs": Money vs. Mental Health
00:07:27 - Stop solving symptoms: Systems Thinking explained
00:13:10 - Transitioning from Senior Engineer to Solutions Architect
00:15:08 - Communicating technical risks to non-technical bosses
00:17:48 - Proving leadership before you have the title
00:22:25 - My strategy for dealing with Imposter Syndrome
00:26:12 - Creating a "Zettelkasten" to retain technical knowledge
00:29:12 - The mindset that makes me stress-proof at work
00:33:10 - Learning to code with a product/design background
00:38:40 - Working with international remote teams
00:40:35 - Career Pivot: Software Engineering to Cyber Security
00:43:20 - Solopreneur opportunities in the "Education Gold Rush"
00:51:50 - Future Predictions: Vibe Coding vs. Vibe Engineering
#SoftwareEngineering #CareerAdvice #SystemsThinking