How to do Prioritization as a Software Engineer (From L8 SWE at Microsoft)

You can find a copy of the prioritization worksheet here: https://docs.google.com/spreadsheets/d/11NXbPJmhVxikhJWIG5CSjubBSCoZJV_LPGSiU9R2oIM/edit?usp=sharing. Feel free to clone and tweak it for your use!

Amazing empirical formula for making prioritization easier! Although I have a slightly different perspective. While prioritization becomes increasingly difficult as one grows, for me becoming tech lead was about developing leadership skills. It was about creating an inclusive environment for each team member to bring their best and seeking diverse perspectives to solve challenging problems. It was about being seen as a leader/role model in the team. I had go from being a "rockstar" to a team player. This is what my journey was from L63-L64 to L65 to EM.

Hey Kun! Thanks a ton, I'm excited to see how I can use the prioritization frameworks even as an L3. Also - I like that shirt a lot!

I like the equation, works well for certain mathematically inclined individuals. It would have been great to have that on the screen initially.

Hey Kun, how would you incorporate into the framework tech debt that enhances engineering velocity but does not provide a direct impact to customers?

Hi Kun!! Thank you for your video. Can you do one video to talk about engineer collaboration? For example, recently i need to redo my design (junior eng) because the senior eng missed a key criteria, after he approved my design all the way to final stage. The problem is, I don’t know how to justify my time “wasted” during the previous design, and whether it will result me looking underperformed during performance review (because not as much output, even though I have tried my best). These nuances sometimes can throw one off, because one has to take the responsibility of redoing the project design. Would the junior eng to take this responsibility, because he is the one that builds the software?