How to Get Promoted: The 6 Steps to Take Control of Your Career
Stop waiting for someone to notice your work. Take ownership of your career and build a clear path to your next promotion.
Welcome to my newsletter! I'm Dave Anderson, an ex-Amazon Tech Director and GM. I write this newsletter I've called Scarlet Ink, which is a weekly newsletter on tech industry careers and tactical leadership advice.
Free members can read some amount of each article, while paid members can read the full article. For some, part of the article is plenty! But if you'd like to read more, I'd love you to consider becoming a paid member. 99% of my articles are intended to be evergreen (readable and valid forever). Some weeks I have fresh content; other weeks I'll update/rewrite something from 4+ years ago because I want to keep the quality of all articles high.
My first six months at Amazon were rough. There were so many acronyms, project names, people to know, and processes to follow; I felt overwhelmed. It took me a bit to decide that I was actually going to make it through that ramp-up period.
However, once that six-month period ended and I decided that I wasn't going to be fired, I started to consider what was next in my future.
I was a Level 5 SDM (software development manager), which is an entry-level management position. Most managers at Amazon are Level 6, which is considered the standard team manager level.
That Level 5 role isn't used too frequently in the Amazon corporate world. The definition of a Level 5 manager is that they require extra assistance to do their job, while a Level 6 manager can work independently. It's relatively rare to hire Level 5 development managers. This is because plenty of senior leaders refuse to hire managers who aren't experienced enough to work independently. They're hiring managers to scale themselves, and a leader who requires extra assistance isn't what they're looking for.
In other words, they don't have time to babysit their managers.
Considering the above, almost all of my peers were Level 6 SDMs. As I compared my performance with theirs, I began to believe that I should start on my promotion process. In other words, I was cocky and was pretty sure that I was better than most of my peers who were higher level.
When I asked about the process for getting promoted, I was told a line of utter absurdity.
You shouldn't ask for a promotion. Do a great job, and you'll get promoted at the right time.
Complete garbage. Made me furious. Of course you should ask for a promotion, a raise, or anything else you want out of your career. You are the person who is impacted the most by your career, and you need to own it!
Amazon's corporate policy at this time told people that the best employees didn't ask for a promotion. They just focused on their work and would be rewarded at the right time. In my experience, all the best managers agreed that this was a load of bull.
One quick point. You should not wait to do this exercise until you're ready for promotion. At all times in your career, you should clearly understand where you are in your career and what your next steps are. You may be years from promotion; that's fine. That distance shouldn't stop you from thinking about your future.
Step 1: Understand the Promotion Bar.
Before having a conversation with your manager, you need to understand the promotion bar.
At Amazon, there's a set of wonderful Role Description documents, which clearly explains each level and the differences between them. If your company has those, this is where you start.
If your company doesn't have clearly detailed role descriptions, you need to research what the expectations are for your next role. Talk to HR (it's one of their primary jobs), and see if they have resources you could use. Talk to your manager. Not to ask for a promotion (that comes later). This is simply about understanding what the next level is.
"I love working on myself and my skills. I'd like to understand what the expectations are for the next level in my career. Do you know of any resources where I could read about those?"
If there isn't a role description document, I think it's wise to collect any information you find into a new role description document. This allows you to properly begin an assessment. This document needs to summarize what moving to the next level would entail. These may be concrete things ("the next level manages at least 10 people") or often more abstract things ("the next level runs large department-wide projects").
In all situations, you should just assume that the role description will be necessarily vague. All jobs have an aspect of, "If you're doing a 'big' project, we'll just know if it's 'big' by looking at it." Try not to get discouraged. Your goal is to get from "I have no idea what my next role looks like" to "I have some abstract descriptions of what it means."
You'll hopefully have a lot of text now. You'll want to break down all that text into a list 5-10 items long. Things like "A senior manager manages complex projects across multiple organizations." or "A principal software engineer mentors junior engineers and makes them more successful."
Get that list into a spreadsheet for the next step.