How I Find Problems to Solve as a Staff Engineer - Lalit Maganti
lalitm.com · 1,934 words · saved by 2 readers
How listening broadly turns everyday problems into useful project ideas.
Note: this post was revised after publishing for increased clarity, based on reader feedback. “How do you find problems worth working on?” a senior engineer I mentor asked me recently. He’s trying to make the jump to staff engineer and realized that the role isn’t just about doing the work he’s assigned. He also needs to get involved in figuring out what his team and org should be building. Someone else had suggested blocking out time in his calendar to think about the bigger picture. He’d tried that, but hadn’t found it productive, so he asked if I had any alternatives. I told him I…
saved by
related reading
- How to pick – and solve – the next great problemengineering.stanford.edu
- What Actually Makes You Seniorterriblesoftware.org
- Most Technical Problems Are Really People Problemsblog.joeschrag.com
- Why I Ignore The Spotlight as a Staff Engineer - Lalit Magantilalitm.com
- AddyOsmani.com - 21 Lessons From 14 Years at Googleaddyosmani.com
- How to Do Great Workpaulgraham.com
- Finding Person-Problem Fit - Compound Manualmanual.withcompound.com
- Finding Person-Problem Fit - Compound Manualmanual.compoundplanning.com
- How to Do Great Workpaulgraham.com
- How to Get Startup Ideaspaulgraham.com
- How to Solve Technical Problemsjquiambao.com
- How to Solve Your Big Problems, by Solving Your *Real* Problemjasonfeifer.beehiiv.com