Wonderful video for engineering managers.

You are spot on with the point about new managers falling back to coding because that's what is familiar. I myself am currently going through it.

Thank you so much. It really helps for engineering manager role thought process.

I think your channel is really underrated. Hope you more subscribers and watches! Your work does matter

@NotOnlyCode

2 жыл бұрын

Thank you so much, Nikolay, it means a lot to me!

Thank you for sharing the video and making people understand about engineering manager role ✌️

@NotOnlyCode

2 жыл бұрын

Glad it was helpful!

thank you very much Gregory! it's a good video and very useful!, I didn't need to change the speed of video ;)

@NotOnlyCode

2 жыл бұрын

Thanks, good to know the pace is now better! :)

Thanks for the video Gregory. I could so much relate to the fear part in why do you want to code section. How would you suggest Engineering Managers keep them updated with Technologies so that they can clear out subsequent tech management interviews in coming years?

@NotOnlyCode

2 жыл бұрын

Hi Jayant! The answer's below a bit long, but I hope it's helpful. So there are usually 2 types of technical interviews: system design (or technical discussion) and coding. As a manager you work closely with your team - you talk to them on daily basis, so you know what kind of decisions the team makes, what works well and what doesn't. You also participate in higher level discussions that are happening across multiple teams. Even if you don't make decisions yourself and you don't implement the solutions, you should be close to that. That knowledge and experience, supported by some book or a course should be enough to pass the system design part. I also spend some part of my time at work studying the domain I work with. For example, currently I work a lot with SREs and building internal tools to manage high availability of our services. I'm not an expert in this domain, but whenever I have some time at work, I follow news about the latest developments, and I catch up with coworkers that are specialists in this area. It might not contribute directly to the future success of my interviews, but it has a lot of value. When it comes to coding interview, it's a bit (but just a bit) more complicated. There are various types of coding interviews - most common are leetcode-style tasks (data structures and algorithms) and writing a simple app. Leetcode type interviews require similar preparation no matter whether you're EM or developer, because they're so different from daily programmer's work. As an EM you should still know the syntax of some programming language and be able to write loops and conditionals - and that's what's needed for leetcode-style interviews. The rest is practicing the algorithms. Writing an app is the only type where I feel EMs are at a disadvantage, but to be fair I haven't had such interview as an EM yet, and I think most companies are aware that managers don't write code on daily basis therefore it makes little sense to ask them to write an app from scratch. If you want to make sure that you pass such interview, I suggest asking the recruiters before what kind of technology you can use, so that you can prepare for that. But again, at EM level the interviews should be more agnostic and rely more on your experience than on knowing some particular framework or library. So overall I think that as long as you perform "technical work" in your role, that is not necessarily coding, but might be code reviews or participating in technical discussions and decisions, you should be well equipped to pass the interviews.

Thank you Gregory, great video. Can you please do a video regarding the software operation manager or software SRE manager responsibilities and interview process? Do they need coding etc. ?

@NotOnlyCode

2 жыл бұрын

Hey! That's a great question. I haven't worked on either of these positions myself, so I'd need some time to prepare such video, but I can share a bit here. A lot depends on the company, for example I used to work with a release manager (a position that oversaw devops/system engineering team) who did not code at all and had a background in product management. On the other hand all SRE managers I've worked with have coding skills - some of them write code, some of them haven't touched it in a long time (especially when they manage 10+ people), but all of them can do that. SRE is generally meant to be at least 50/50 development/operations work, so coding skills are helpful there, and SRE managers from my experience need to know how to code, too.

@familyjw1590

2 жыл бұрын

@@NotOnlyCode thanks for the reply. Looking forward to seeing your video regarding this.

imho anyone working in the software space can only benefit from keeping a daily or weekly coding practice in their routine, even if only to chip away at an idea. it's too easy to lose a practical approach to software products if you're entirely relying on what others say and abstract ideas presented on slides etc.