Live data from Hacker News

Ask HN: How to prepare for an Engineering Manager interview?

news.ycombinator.com

21–30 of 76 posts

Re: Ask HN: How to prepare for an Engineering Manager interview?

#21
So what you need to know is that you are going to be joining a club - i.e the managers at the company.

You have to focus on fit more than anything else.

The first time you do it - its weird - very weird. All your previous ideas of work and work culture will be obfuscated. You'll realize that managers are a class onto their own.

To figure out fit, you mostly need to be able to read someone in about the first minute of meeting them. What do they value? What do they distrust? What will make them feel comfortable with you?

Older managers - probably want to know that you'll do what you're told, keep engineers in line and accept their management philosophy without question.

Newer age managers - you're very flexible and you'll take on a lot of work and you'll be part of the culture and that you worship at their altar - scrum, team velocities, standups and the rest of it.

Most important point: Do not criticize or point out large flaws in their system or process or thinking. (I've done this and have always lost out on the offer.) Focus on fit more that pointing out their errors.

At a low level like yours its probably best focus on showing that you've done a lot of thikning about the regular manager duties and to be as authentic as possible. This leaves to chance of whether they work in the same way but since its your fist time you probably don't have time to prepare anything else.

Welcome to the club!

Re: Ask HN: How to prepare for an Engineering Manager interview?

#22
In addition to what's already been discussed, you should also think about how to answer questions related to the hiring process. In today's competitive world hiring a great team consumes a huge amount of a manager's time and energy. Some questions to think about, how would you attract top talent? What's the interview process look like? How do you know an engineer will be a good hire? Things along those lines.

In the other comments people have spoken quite a bit about managing down in to the team, I'd also think about the project management and scope negotiation portion. As a partner to product management you're often called on to help shape what's possible long before ideas enter sprint planning or get turned into stories. Think about how you'd help negotiate scope when often the actual requirement has not been clarified.

Re: Ask HN: How to prepare for an Engineering Manager interview?

#23
I did the same journey as you are about to embark on a year ago. It did not end well.

The job itself was titled "scrum master", but the description read more like a team lead/product manager role. I've done a little bit of both and was interested in exploring this career path and I jumped on.

The recruiting was not what I was used to. All in all I had 8 interviews over a course of 6 weeks. They focused heavily of my personality and I did a lot of self-assessments. No coding or case studies. When I reached the end of this I was so fatigued that I forgot to do the due diligence of my part, this turned out to be a BIG mistake.

- first and foremost, i inherited a team. If this is the case with you, MAKE SURE YOU CLICK. While I get along with most of my team on a person-to-person-basis in a team setting they've been working as six one-man teams for several years and Weren't interested in changing that.

- make sure you can tolerate the product you're building. If I had joined as a developer i would have quit within a week. This has an impact when you need to defend it/the team to the outside world. How much belief in the product can you fake?

- you will be alone. Your team won't be your friends anymore and neither will the managers above you.

Long story short, after almost burning out a second time in my life I resigned and am now looking for new work.

Re: Ask HN: How to prepare for an Engineering Manager interview?

#24

Two things that I always advise new managers when I promote them or hire them. First, (for new managers) managing people is a completely different skill set from engineering, expect to suck at it when you start and let go of your hard won pride that you developed becoming an awesome software engineer. One of the "failure" modes of new managers is that they are so uncomfortable doing these new things, and so comfortab…

I've been a technical manager for about a decade. Chuck's comments would have been incredibly helpful 10 years ago...

Re: Ask HN: How to prepare for an Engineering Manager interview?

#25
I applaud your willingness to take on engineering management. Having made the move myself about 4 years ago, it's an often unappreciated form of contributing but I find it highly rewarding. It seems that most new engineering managers seem to get promoted from within since it allows them to leverage the respect they've earned inside the organization as an engineer. In no particular order, here's a few recommendations.

- Think back to the managers you've had and think about what they did well and what didn't work as well. The more you can talk about and have an opinion about what makes a good manager, the more you can show your desire and ability to become a good manager. Before becoming a manager, I spent a year going through my career and really looking in depth at my previous managers so that when I started I could try to use that to be better myself. What I found is that this made me very good at managing down and I was very popular with my team, but managing up was somewhat of a problem. So when you look back at your history and your previous managers, be sure to look at not only how your managers interacted with you and your teammates but also how your managers interacted with their managers and the rest of the org. This can be harder to see, since you're not a part of those interactions, but if you think back, you might remember at least some part of that.

- The most important part of being a manager, from my experience, is being able to deliver feedback. The more effortless and clear you are, the more easily you can provide frequent and minor course corrections as well as provide natural encouragement of desired behavior. It also makes firing/disciplining employees easy. For one, if you're giving constant feedback, those instances are much less frequent since employees can make those course corrections. But when it does become necessary, it's not a surprise. Either there was some major incident or there's been a long build-up where suggestions/warnings have been repeatedly ignored. When I've interviewed other managers, I've looked for their ability to deliver feedback and, crucially, their abilities to notice the things they should be giving feedback about. Many managers, especially new managers, just don't have the awareness to constantly be looking for small course corrections or the feel for when an employee needs a bit of emotional buoying that can come with positive feedback. Hopefully in your mentorship and lead dev experience, you've developed some of that awareness, so the more you can talk about that, the more you'll show you're ready. As far as delivering feedback, there's a lot of theory on the right way to do that, but it also requires practice. Read up on that and then find a friend who's willing to help and role play a few different feedback scenarios. You'll quickly get better with practice.

- I'm going to expand your question beyond the interview because I think it will help you with your interview. Because if you get hired, that's not the end of it. It's not a case of showing that you can do the work, getting hired and then just organically becoming good at it. Once you get hired, that's when you need to start diving into the theory behind the discipline of engineering management. If you can internalize that, then you'll be able to convey to your potential employer at the interview your willingness to work to become better. Try to show your interviewer that you have a plan for learning how to be a great manager and the concrete steps you'll take to achieve that goal. Because if you have zero experience and they know that going into the interview, that's the most they can expect from you.

- Not every engineer actually enjoys management. Many engineers really like knowing all the little details and have a hard time stepping away from that level of knowledge and only knowing the larger building blocks. If you can talk about your excitement to work at that higher level and willingness to give up that lower level, you'll at least convince them that you really want the job. Make sure that this is actually true, because it's hard to fake. But if you can show that enthusiasm, you'll subtly make a better impression.

- Lastly, try to stress areas of being a manager that you're already good at. For instance, as a lead developer, you've probably interviewed a lot of engineers. If you're great at hiring/recruiting, it makes being a manager a lot easier. If you can show that you're able to bring great engineers into their organization, that alone makes you a great hire. Another thing you've probably done is write 360 reviews for other engineers. If you can find one that you're particularly proud of, remove all identifying information from it, print it out and bring it to your interview as an example of the kind of thinking you'll bring to their organization.

Best of luck in the interview!

Re: Ask HN: How to prepare for an Engineering Manager interview?

#26
There are some great suggestions already, however, it sounds like many comments are focusing on their experiences as a tech manager and not the interview preparation, which was your question.

I interview a lot of technical managers, and beyond technical chops, I focus mostly on communication skills, charisma, and personality.

I tend to ask a lot of behavioral/situational questions to understand how the candidate would handle different situations and how his personality lines up with the team. We are usually hoping for a thoughtful and genuine answer.

Additionally, I often schedule lunch with the candidate and the key players on the team, without the participation of the recruiting team, so they can speak freely.

You can prepare for some of the situational questions but keep in mind that it is totally ok to say "I don't know" or "I have not thought of that".

Best of luck!

Re: Ask HN: How to prepare for an Engineering Manager interview?

#28

Two things that I always advise new managers when I promote them or hire them. First, (for new managers) managing people is a completely different skill set from engineering, expect to suck at it when you start and let go of your hard won pride that you developed becoming an awesome software engineer. One of the "failure" modes of new managers is that they are so uncomfortable doing these new things, and so comfortab…

Everyone that is a new engineering manager or looking to take this role in the future should read through this comment. On point!

Re: Ask HN: How to prepare for an Engineering Manager interview?

#29
post #19

I've never hired for an engineering manager before, but it just popped up on our OKR this quarter. I think what I'd be interested in knowing about someone's management background: - tell me about a time you had to let someone go. How did you deliver the news? How did the other person react? How did you communicate it to the engineering team and broader organization? Was there any fallout, and if so, how did you help…

These are all good for an experienced engineering manager, but keep in mind the OP was asking about having no management experience. I still think someone could take the questions and relate to their technical career in some form or another. If you can't you may want to question if you are ready for the new role!

Re: Ask HN: How to prepare for an Engineering Manager interview?

#30

Ten years and you have never led anybody? Think back, I am sure there were moments where you led/guided/coached peers or were a sparring partner. You should sell those experiences as first steps into being a leader. However, you should be aware that managing and coding are so different, even if it's in the same field. Managing people is tough and you learn it by doing.

The author seems to be pretty clear about having been a team lead but never having directly managed anyone. Huge difference. Having a similar background myself, I can say this is probably one of the biggest hurdles if you're looking to get into management. You can talk at length about mentorship and leading through influence and judgment and all the stuff that goes with being a "technical lead" but it doesn't make mu…

I've heard lots of names for managers, but never had someone called a "team lead" and not had direct reports.
Post reply on HN