How to Get Promoted in Cloud Engineering: What Actually Drives Decisions

How promotion decisions actually get made

In most companies, promotion decisions happen in one of two ways:

• Calibration cycles: Once or twice a year, managers meet to discuss their team members’ performance and agree on promotion recommendations. Your manager advocates for you, compares you to peers at your current and target levels, and presents evidence to support the case.
• Spot promotions: Less common, but happen when someone has clearly outgrown their level and waiting for a calibration cycle would be obviously wrong. Usually require manager initiative.

In both cases, your manager is the primary advocate. If your manager does not have clear, concrete examples of your work at the next level, they cannot make the case — even if they believe you deserve promotion. Your job is to make their job easy by creating that evidence continuously.

Scope matters more than quality

This is the insight that surprises most people: doing your current job very well does not usually lead to promotion. It demonstrates you are good at your current level. Promotion requires demonstrating that you are already operating at the next level.

The distinction is scope:

• A junior engineer who writes excellent Terraform for tasks they are assigned is doing their job well
• A junior engineer who notices a gap in the team’s infrastructure strategy, proposes a solution, gets alignment from the team, and implements it is operating at mid-level

The second person is doing work with broader scope — it affects more people, requires more judgment, and involves more coordination. That is what promotion decisions are based on.

Practically, this means:

• Do not wait to be assigned stretch work. Identify problems at the next scope level and ask if you can own them.
• When you complete a piece of work, ask: “could I have made this decision myself, or did I need approval? If I needed approval, why — was it because of my level or because the decision genuinely needed escalation?”
• Track the scope of your work, not just the volume. Ten tickets closed at current scope is not equivalent to one initiative completed at the next scope.

Visibility without self-promotion

Good work that nobody knows about does not help your promotion case. This is especially true in cloud engineering, where infrastructure work is often invisible when it is working correctly.

Making your work visible is not the same as bragging. It looks like:

• Writing a short postmortem or technical summary after completing a significant piece of work — “we migrated the logging stack to the new configuration; here is what we did and why”
• Giving a five-minute lightning talk at the engineering all-hands about something you built or learned
• Writing a well-structured PR description that explains what changed, why, and what the impact is — rather than just the diff
• Raising design questions in public channels rather than in direct messages, so your thinking is visible to a broader audience
• Mentioning completed work in weekly standups or manager 1-to-1s with enough specificity that your manager can relay it

The goal is that when your manager sits in a promotion calibration meeting, the people in the room have heard your name associated with good outcomes — not just your manager telling them about you.

Mentorship versus sponsorship

A mentor gives you advice and guidance. A sponsor advocates for you in rooms you are not in. Promotions happen in rooms you are not in.

Mentors are valuable for growth. Sponsors are what move promotion timelines. The difference:

• A mentor says: “here is how I would approach that technical problem”
• A sponsor says: “Alex should be the one to lead that initiative — this is the right opportunity for them, and they are ready”

Sponsors are usually managers or senior engineers who have visibility into decision-making above your level. They need to have seen your work well enough to vouch for it credibly.

You build sponsorship by doing good visible work and developing a genuine relationship with people who have influence — not through flattery, but through producing results they can point to. Ask for feedback from these people on your work. Make it easy for them to know what you are doing and how it is going.

The promotion gap analysis

Most companies have a levelling framework that describes what each level looks like. If yours does not, ask your manager to describe the difference between your current level and the next one specifically — not generically.

Once you have that description, compare it honestly to your current work:

• Which criteria do you already meet consistently?
• Which criteria do you meet sometimes but not consistently?
• Which criteria do you not yet meet?

The “not yet meet” list is your promotion gap. Focus there. Be specific: “I do not yet consistently own projects that span multiple teams” is more useful than “I need to improve my seniority.”

Then: what would it look like to close each gap in the next six months? What specific work would demonstrate it? Discuss this with your manager. If they agree your gap analysis is accurate, they become an ally in helping you close it — because a clear promotion case makes their job easier too.

When promotion is not happening

If you have been operating at the next level consistently for twelve months or more, have had explicit conversations about readiness, and promotion is still not happening, consider:

• Is there a structural constraint? Small teams sometimes have no headcount at the next level. Promotion in this case requires the team to grow or someone to leave — not more evidence of your capability.
• Is your manager actually advocating? Ask directly: “what would you need to see from me to make a strong promotion case?” If the answer is vague, you may not have effective sponsorship from your manager.
• Is the timeline realistic? Promotion cycles are typically annual or biannual. “Not yet” after six months of performing at the next level is often just a timing issue.
• Is this the right company? Sometimes the most effective path to a promotion title is accepting it at a new company. If you are consistently performing above your level and the organisation cannot recognise it, that is information about the organisation, not about your capability.