The Secret to Rapid Promotions
When you start your career as a Junior Developer, you naturally assume the relationship is a one-way street: the Engineering Manager tells you what to do, you do it, and if you do it well, they reward you with a promotion.
This passive mindset is why many developers stay stuck at the Mid-Level tier for years. Your manager is likely overwhelmed, managing 10 other engineers, dealing with product deadlines, and fighting political battles. They are not thinking about your career trajectory every day. You have to.
This is the art of Managing Up—taking proactive control of your relationship with your manager to make their life easier, which in turn accelerates your career.
1. The "No Surprises" Rule
Managers hate surprises, especially bad ones.
- The Mistake: You are assigned a Jira ticket due on Friday. By Wednesday, you realize a complex database migration is blocking you, but you stay quiet, hoping you can fix it. On Friday, you miss the deadline.
- Managing Up: The moment you identify a critical blocker that threatens the timeline, you inform your manager. "Hey, I've hit a wall with the DB migration. I'm going to spend 2 more hours on it, but if I can't resolve it, this Friday's deadline is at risk. Should I pull in a Senior dev to pair program?" You delivered bad news early and offered a solution.
2. Own Your 1-on-1 Meetings
The weekly or bi-weekly 1-on-1 is your meeting, not your manager's.
- The Mistake: Showing up empty-handed and saying, "I'm working on the login bug. Everything is fine."
- Managing Up: Create a shared Google Doc agenda. Add items throughout the week. Bring specific topics:
- Blockers: "I need you to approve this AWS access request so I can deploy."
- Feedback: "How did you feel about the architecture doc I wrote last week?"
- Career: "I want to take on more backend tasks next sprint to build my skills there."
3. Bring Solutions, Not Just Problems
If you only bring problems to your manager, you become a burden.
- The Mistake: "The current CI/CD pipeline takes 20 minutes to build and it's really annoying."
- Managing Up: "The CI/CD pipeline is taking 20 minutes. I looked into it, and we aren't caching our Node modules. I can write a quick GitHub Action to implement caching, which should cut the time to 5 minutes. Do I have your approval to spend 3 hours on this tomorrow?"
4. Understand Your Manager's KPIs
Your manager has a boss too (the Director or VP of Engineering). Your manager is judged on specific metrics (e.g., shipping a feature on time, reducing cloud costs, lowering bug counts).
- The Strategy: Figure out what keeps your manager awake at night. If they are stressed about the upcoming Q3 release, volunteer to take the most tedious, annoying task off their plate. If you make your manager look good to their boss, they will ensure you get promoted.
5. Document Your Own Value (The Brag Document)
Do not expect your manager to remember the brilliant bug fix you deployed in February when your performance review happens in December.
- Managing Up: Keep a running document of all your major PRs, metrics improved, and times you helped a teammate. A month before review cycle, hand this summarized document to your manager. You have literally done their job for them—giving them the ammunition they need to fight for your raise in the leadership meetings.
