In this episode, Dave and Jamison answer these questions:

1. I have around 14 years of experience and was recently promoted to a Head of Engineering role. I am now leading an engineering department of around 75 people. I’ve become increasingly ‘hands off’ with coding, and it’s been at least 2-3 years since I wrote code regularly. My role is completely hands off technically.

   I’m questioning whether this is the right role for me. I want be more hands on, but I worry my skills are now so rusty that I’d have to start over and spend all my spare time learning to code again.

   Do you think it’s realistic to get back to a hands on engineer role at this point? Have you seen it done successfully before? Does walking away from this leadership role make it harder to potentially take on other leadership roles like CTO in the future?

2. Hypothetically speaking, let’s say that you were pretty sure layoffs were coming to your company even though they say they are cutting costs everywhere else that they can in order to avoid layoffs. Now let’s say that, hypothetically, in anticipation of this you took some interviews and received an offer from a company that you believe will ride out the upcoming economic downturn fairly well, and, hypothetically, you accepted the offer. Would you go to your manager and offer to take a voluntary severance, and in doing so, would you let them know you had something else lined up or would you leave that out and present it as just taking your chances while your severance checks were coming in?

   Thanks for doing what you do.

Show Notes

• https://charity.wtf/2019/01/04/engineering-management-the-pendulum-or-the-ladder/

In this episode, Dave and Jamison answer these questions:

1. I’m a senior front end engineer at a medium sized tech company.

   During the good times of limitless tech growth, a common way for engineers to grow our “impact” (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.

   Now, with many companies doing layoffs and hiring freezes (mine included), teams simply aren’t growing and there just aren’t as many people to “impact”. What are some other ways to have more “impact” 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.

2. 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’t 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’s clear that they don’t really have a full picture of what’s going on. To make matters worse… 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.

Show Notes

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

In this episode, Dave and Jamison answer these questions:

1. A listener named Mike asks,

   I’ve been offered an Engineering Management position at a company I previously worked for. The team is very small and composed of juniors and mid-level developers. The role is also completely new and because of the size and experience of the team there is some expectation that the manager will also have a fair amount of involvement in PR reviews and likely also writing some code. Is this common? Do you feel like a manager can also be a team lead from a technical perspective on a day to day basis? What should I be thinking about when considering this role?

2. ‌

   How do I keep up juniors’ morale regardless of bad code/ideas? I work in a team of 4-5 developers. We have one junior, one mid (me), one senior and our team lead. I think we mostly work well. However, sometimes the senior and team lead sort of talk down at the junior. For example, in a meeting talking about how to solve a problem the junior will propose an idea, but the senior and/or both team lead would respond by saying that no its not a good idea which is fine. However the tone of the voice often hints ‘oh you should know this it’s obvious you jamoke’.

   The junior has started to stay quiet and has told me he doesn’t feel comfortable asking the seniors for help. I’ve interjected in meetings to say I understand why the junior might have this idea but I don’t think it’s the best solution. What should I do? Should I talk to the senior/team lead? Do I just let it play out?