Ask The Instructor: [Course] Nail Your Promotion As A Software Engineer
Promotion is one of the most difficult and nuanced topics, so there's no way any course can absolutely cover 100% of all possible scenarios. If you have any questions about the course, please ask them here! I'm happy to talk about:
- What gaps you may have to get to the next level
- How to create additional scope in your team
- Whether a prospective team you're considering looks good for promotion
- Why you're getting stuck at your current level
- Maintaining that dialog with your manager about promotion
![Senior Software Engineer [E5] at Meta company logo](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fcompany_logos%252Fmeta.jpeg%3Falt%3Dmedia%26token%3Da7a5bcc0-e178-4b5b-b71e-09bf6c6aefae&w=48&q=75){kind=small}
![Entry-Level Software Engineer [L3] at Google company logo](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fcompany_logos%252Fgoogle.jpeg%3Falt%3Dmedia%26token%3D780356ef-3efc-4728-9eb4-d909b75bb4a6&w=48&q=75){kind=small}
Discussion
(2 comments)- 0
7 months agoSupportive TarodactylTaro CommunityThanks for the amazing course! The project credit section was especially enlightening for me.
What's your advice on aligning a team that doesn't see eye-to-eye with yours? For example, I was working with 2 platform teams that over-promised and under-delivered. They delivered poorly documented and very buggy implementations that my team had to build on top of, resulting in significant delays. They refused to test their code before marking it as done, so their mobile & BE implementations were often incompatible even within their own teams.
My project's overall DRI (E6 BE) ended up switching teams halfway through the project, so the project became a total mess. Our other BE engineer resigned a month before the E6 switched teams, so we had no BE engineers on this project at one point. I was the project's mobile DRI (E5), but also jumped in to do BE to try to save the project before we were able to eventually onboard another BE engineer. We finally delivered the 3-month project 3 months behind schedule, but I was so burnt out by the death march over the last 6 months that I asked to be taken off the project as soon as we had hit our 1st milestone.
- 17 months agoAlex Chiou [OP]Tech Lead @ Robinhood, Meta, Course Hero
Ugh, this sounds so messy. In this case, you definitely need to escalate, especially as you aren't E6 (or better yet, E7). In other words, you need to rope in your manager (and probably your skip too) and have them apply pressure. Make sure to compile as much proof as possible though to show them that you aren't just complaining for no reason. Showing empathy for the other side (even if you don't have any) is important as well (e.g. "I know this XFN team is stretched, but...").
If the manager is not helpful (especially if they're giving you a response like "Well, it's up to you to figure this out"), then it's probably time to switch teams 😥
