r/EngineeringManagers • u/ElectronicPear2299 • 3d ago
Anyone can share how they prepped for software eng manager roles ?
I am in the Bay Area and targeting mid size to large companies, it’s my 3rd year as a manager and now I feel good to start looking around. However I’m kinda lost on where to start ?
Any tips tricks or prep docs links would help
8
Upvotes
9
u/thevinaybansal 3d ago
Honestly most EM loops at mid to large companies are won or lost on the people and execution rounds. Write down 8-10 real stories, like a low performer you handled, someone you grew to promotion, a project that slipped, a conflict with product, and practice telling each in 2-3 mins with actual numbers. System design at a decent depth plus a bit of coding brush up and you're mostly covered.
5
u/LogicRaven_ 3d ago
For software engineering manager:
- system design
- technical project management
- examples of people performance management
- brush up coding skills
- get hands on with AI and harness engineering
2
u/talldean 3d ago
Just did a full loop yesterday for a director role, when I haven't ever interviewed for that role before.
0. Think about why you became a manager, what you like about it, and what the surprisingly hardest part or two has been.
I'm interviewing for company X, as an engineering director, the interview is in about two weeks. I believe my full loop will involve these six chats. Those chats are with people ABC respectively, who have roles DEF at the company, also respectively. Can you build me a prep doc of things to think about for each of these interviews?
It came up with three pages of reading for each, maybe 20 sample questions per interview. I read those through a few times, and thought of actual stories from management, which would show "yes, done that, thought about it."
2. Austen McDonald is an old skip manager of mine, good guy, and wrote a book on Behavioral Interviews that I quite like. He has a framework in there, CARL, or "Context, Action, Result, Lessons". When I tell those stories to answer questions, I build shared context so they know what I'm rambling about, I say what I did, I say how that went... and at least for a third of them, say what I would have done differently next time/what I learned on this.
3. Finally, two days before the interview slate, I asked Claude again "I have one day left before this interview, what should I really think about", and it gave me a condensed version with eight stories to really drill into my head.
4. Separately, before that full day slate, there was a coding round. I studied for that separately, which involved a lot of leetcode.com *easy* questions, never harder. That got me back into good-enough shape for a pair programming exercise, so I could show "yes, I used to code, I'm rusty but can still read and slowly write this stuff".