In a large company or global capability centre, promotions follow a written process: a ladder, a review cycle and a committee or calibration. Learn that process, work on problems your leadership cares about, make your impact visible beyond your own team, and give your manager a clear case to argue for you.
What people tell me
I work at a large company with many engineering teams, part of a global organisation with headquarters abroad. I deliver my work on time and my manager says I am doing well, but promotions seem slow and unpredictable. Some people move up quickly and I cannot see what they are doing differently. The decisions seem to happen in meetings I am not part of.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- Large companies promote through a process; learn the ladder, the cycle dates and who decides.
- Doing your tickets well is expected at your level; promotion needs evidence at the next level.
- Pick work tied to what leadership, often abroad, is measured on.
- Your manager argues your case in rooms you are not in; give them a written case.
- Visibility across teams and with headquarters matters more than in a small company.
Promotions in large companies are a process
In a small company, a founder can decide to promote you over lunch. In a large company, including the global capability centres (GCCs) that many multinationals run in India and elsewhere, promotions follow a system. There is usually a written career ladder, a fixed review cycle, and a calibration or committee meeting where managers compare people across teams.
Once you understand that system, promotions stop feeling random. The people who move quickly are rarely more talented. They understand the process and give it what it needs.
Step 1: learn the rules of your company
Find out, from your manager or internal documents:
- The ladder. What does the next level expect? Read it line by line.
- The cycle. When are promotion cases written and decided? Often once or twice a year. Missing the window means waiting months.
- Who decides. Your manager, a skip-level manager, a committee, or leadership at headquarters?
- What evidence counts. Some companies want a written case, some rely on peer feedback, some on project outcomes.
If you do not know these answers, that is your first task.
Step 2: work at the next level, visibly
Delivering your tickets on time is what your current level expects. Promotion needs evidence that you already operate at the next level. That usually means some mix of:
| Next-level signal | Example |
|---|---|
| Larger scope | Owning a service or feature area rather than tasks |
| Ambiguity handled | Turning a vague request from headquarters into a clear plan |
| Influence | A design or practice other teams adopted |
| Reliability | Reducing incidents or on-call load measurably |
| Growing others | Onboarding new joiners, useful code reviews |
The career growth roadmap breaks these signals down in order.
Step 3: choose work leadership cares about
In a GCC, the most important stakeholders often sit in another country. Find out what they are measured on this year: cost, reliability, a product launch, moving work from headquarters to your centre. Work that directly helps those goals gets noticed. Work that nobody above your manager knows about does not.
Ask your manager: "What are the two or three things our leadership cares most about this year, and how can my work connect to them?"
Step 4: make your manager's job easy
Your manager defends your promotion in rooms you are not in. Give them material.
- Keep a running document of your work: problem, what you did, measurable result, who noticed. The brag document guide explains the format.
- Map each item to a line in the ladder.
- Share it with your manager a few weeks before the cycle, and ask directly: "Is this enough for a promotion case? What is missing?"
- Collect feedback from people in other teams or at headquarters who saw your work.
Step 5: be visible beyond your team
Large companies reward people known outside their own team. Present a short demo at a wider team meeting. Write a design note that another team reuses. Volunteer for cross-team incident reviews. If you work with colleagues abroad, overlap some hours with them and communicate in writing clearly. The personal branding roadmap covers internal visibility, not just LinkedIn.
What slows people down
- Waiting for your manager to notice. They are busy; tell them.
- Staying on the same comfortable work for years.
- Being excellent but invisible to decision-makers.
- Asking about promotion only when the cycle has already closed.
If you are still stuck
If you are earlier in your career, How do I get promoted from junior to mid-level developer? covers the first step, and How do I go from mid-level to senior software engineer? the next one. If you want help writing your case, join Sefism and, as a member, book a 1:1 session.
Was this answer helpful?
Read next
- Twelve Moves That Take You From Mid Level to SeniorGoing from mid level to senior software engineer is about scope, not years. Twelve moves that actually get you there: leverage over volume, a written promotion bar, design docs, multiplying through others and choosing a direction.
- The Habits That Make an Engineer Worth Routing Work ThroughThe habits of great software engineers are mostly about reliability, not brilliance. Fifteen learnable habits, from estimating in ranges to labelled review comments and weekly notes, that make you the person work gets routed through.
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open: sign up and your account is active shortly after. Prefer to talk? A free call works too.