BROADCASTS.com

In this episode, Dave and Jamison answer these questions:

\n
1. \n

   I\u2019m a senior front end engineer at a medium sized tech company.

   \n\n

   During the good times of limitless tech growth, a common way for engineers to grow our \u201cimpact\u201d (an important criteria at many companies for promotion) was to find ways to lead/manage more people, whether this was becoming a manager and having more direct reports, or becoming a tech lead and mentoring more people, especially interns and junior engineers.

   \n\n

   Now, with many companies doing layoffs and hiring freezes (mine included), teams simply aren\u2019t growing and there just aren\u2019t as many people to \u201cimpact\u201d. What are some other ways to have more \u201cimpact\u201d and grow my leadership skills? Both for hitting promotion criteria, but also for my own growth as an engineer that would like to be a manager or staff engineer someday.

   \n
\n
2. \n

   I am a very senior engineer at my company. There is an engineer on the team less senior than me, but not under me on the management tree. This person is well regarded in the organization, but has a strong tendency to over-engineer things. Normally I don\u2019t mind a little over-complexity if it means that the person leading the project is taking ownership/accountability of the feature. But with this individual, they tend to be put in a place to make sweeping decisions that broadly impact systems when it\u2019s clear that they don\u2019t really have a full picture of what\u2019s going on. To make matters worse\u2026 when I raise these points directly, the person will usually offer to accommodate my concerns by further over-complicating their solution/architecture rather than stepping back and picking an approach more appropriate for the problem.

   \n
\n

This episode is sponsored by the original podcast from Red Hat, Compiler. Listen to Compiler: https://link.chtbl.com/compiler?sid=podcast.softskillsengineering