Most IT professionals do not get promoted because they are the most talented person on the team. They get promoted because they built a documented case that made the decision obvious for their manager. Talent without documentation is invisible to the people who control promotion decisions, and in large organizations, the person deciding your promotion may not interact with your daily work at all.
A 2024 Robert Half Technology survey found that 61 percent of IT professionals felt they were overdue for a promotion, but only 23 percent had formally discussed advancement with their manager in the past year. The gap between deserving a promotion and getting one is almost always a communication and documentation gap.
This article covers how to build, document, and present a promotion case in IT, including the specific evidence that decision-makers weigh, the timing that matters, and the mistakes that derail otherwise strong candidates.
Understanding How Promotion Decisions Are Made
Before building your case, understand the mechanics of the decision process. Promotion decisions in IT are rarely made by a single person in a single meeting.
Promotion committee -- a group of senior leaders, typically including your manager, your skip-level manager, and HR business partners, who review and approve promotion nominations against a set of criteria and a limited budget -- is the standard mechanism at companies with more than 200 employees. At smaller companies, the decision may rest with your direct manager and one level above.
What Promotion Committees Evaluate
Committees typically assess candidates across four dimensions:
| Dimension | What They Look For | Weight |
|---|---|---|
| Performance at current level | Consistently meets or exceeds expectations | 25-30% |
| Performance at next level | Already doing work at the level above | 30-40% |
| Business impact | Measurable contribution to revenue, cost, or risk | 20-25% |
| Organizational influence | Mentoring, cross-team collaboration, leadership | 10-15% |
The critical insight is that doing your current job well is necessary but not sufficient. Promotion committees are looking for evidence that you are already operating at the next level, not that you are ready to start learning it.
"The biggest mistake I see from engineers seeking promotion is waiting to be told they're ready. In every company I've worked at -- Google, Amazon, Facebook -- the people who get promoted are the ones who start doing the next-level work before the title change. The promotion is a recognition of what you've already been doing, not permission to start." -- Will Larson, CTO of Calm and author of An Elegant Puzzle: Systems of Engineering Management (Stripe Press)
Step 1: Define Your Target Role Clearly
Vague promotion requests fail. "I want to be promoted" is not actionable. "I want to be promoted from Systems Engineer II to Senior Systems Engineer, and here is the evidence that I am already performing at that level" is actionable.
- Obtain the official job level framework or career ladder for your role -- most companies with 500+ employees have one, and if yours does not, ask HR if one exists
- Read the requirements for the level above your current position carefully, noting every specific competency, scope expectation, and skill requirement
- Map your current work against those requirements, identifying where you already meet them and where gaps exist
- Discuss the level requirements with your manager to confirm your understanding is accurate
Career ladder -- a formal document that defines the expectations, competencies, scope, and impact requirements for each level within a role family (e.g., Engineer I through Principal Engineer) -- is your roadmap. Without it, you are guessing at what the promotion committee wants to see.
At companies without formal career ladders, frameworks from companies that publish theirs can serve as references. GitLab publishes its entire engineering career framework publicly, and Rent the Runway, Patreon, and Buffer have all published engineering leveling guides. Use these as templates to create your own gap analysis.
Step 2: Document Your Impact With Numbers
Promotion cases are won with evidence, and the strongest evidence is quantified. Subjective statements like "I improved system reliability" carry far less weight than "I reduced production incidents from 12 per month to 3 per month over six months by implementing automated canary deployments."
Categories of Quantifiable IT Impact
- Cost reduction: "Reduced AWS infrastructure spend by $180,000 annually by rightsizing EC2 instances and implementing Reserved Instance coverage from 20% to 78%"
- Reliability improvement: "Increased uptime from 99.5% to 99.95% SLA compliance, reducing P1 incidents by 60% through improved monitoring with
Datadogand automated rollback procedures" - Speed and efficiency: "Reduced deployment frequency from biweekly to daily by building a
JenkinsCI/CD pipeline, cutting release cycle time from 14 days to 1 day" - Security posture: "Led remediation of 340 critical vulnerabilities across 1,200 servers in 90 days, achieving SOC 2 Type II compliance ahead of the audit deadline"
- Team productivity: "Automated onboarding environment provisioning with
Terraform, reducing new developer setup time from 3 days to 2 hours"
The Impact Log
Start an impact log today, even if your promotion conversation is months away. Every week, spend 15 minutes documenting:
- What you accomplished
- What the measurable result was
- Who benefited (team, department, company, customers)
- What would have happened if you had not done it
Brag document -- a running personal record of professional accomplishments, metrics, and impact maintained by the individual rather than by management -- is a term popularized by Julia Evans, a software engineer and author of technical zines, who has written extensively about why self-documentation is essential for promotion and compensation conversations. Her advice: if you do not write it down, it did not happen as far as promotion committees are concerned.
Step 3: Demonstrate Next-Level Behavior
Performing at your current level gets you a good performance review. Performing at the next level gets you promoted. The distinction is critical.
What Next-Level Looks Like in IT Roles
| Current Level | Current Expectation | Next-Level Behavior |
|---|---|---|
| Junior Engineer | Complete assigned tasks | Identify tasks that need doing without being assigned |
| Mid-Level Engineer | Own features end-to-end | Own subsystems, make architectural decisions |
| Senior Engineer | Design and lead technical projects | Influence technical direction across teams |
| Staff Engineer | Set technical strategy for a domain | Drive company-wide technical initiatives |
| IT Manager | Manage a team's delivery | Manage multiple teams or a department strategy |
The pattern is consistent: each level increase requires expanding your scope of influence beyond your immediate responsibilities. Moving from mid-level to senior means your decisions affect not just your own code but the team's architecture. Moving from senior to staff means your decisions affect other teams.
Practical Ways to Demonstrate Expanded Scope
- Volunteer for cross-team projects that expose you to stakeholders outside your immediate team
- Write technical proposals or design documents that address problems larger than your individual assignment
- Mentor junior team members formally through your company's mentorship program or informally through code reviews and pairing sessions
- Present at team meetings, department all-hands, or internal tech talks to build visibility with leadership
- Take on incident commander or on-call lead responsibilities that demonstrate operational judgment under pressure
Kim Scott, former VP at Google and author of Radical Candor (St. Martin's Press), has emphasized that promotion decisions are heavily influenced by visibility to leadership. Doing excellent work that nobody above your manager sees is a common failure mode, particularly for introverted IT professionals.
Step 4: Build Allies and Sponsors
Promotions are not decided in isolation. They require advocates.
Sponsor -- a senior leader who actively advocates for your career advancement in rooms you are not in, as distinct from a mentor who offers advice but may not have the organizational power to influence promotion decisions -- is the most powerful asset in a promotion campaign.
How to Build Sponsorship
- Deliver exceptional work on projects led by senior leaders, so they have firsthand experience of your capabilities
- Seek feedback proactively from your skip-level manager and other senior leaders, creating touchpoints that build familiarity
- Volunteer for high-visibility initiatives that matter to leadership, even if they are outside your normal scope
- Ask your manager directly: "Who else should be aware of the work I'm doing?" -- this is not self-promotion; it is career management
A 2023 study by the Center for Talent Innovation (now Coqual) found that professionals with sponsors are 23 percent more likely to be promoted than those without, controlling for performance ratings. In IT specifically, where technical work can be invisible to non-technical leadership, sponsorship bridges the visibility gap.
Step 5: Time Your Request Strategically
When you ask matters almost as much as what you ask for.
Best Timing
- After completing a major project: your impact is fresh and visible, and leadership can easily connect your contribution to business outcomes
- During performance review season: this is when promotion budgets are allocated, and your manager is already thinking about team development
- After receiving strong peer or customer feedback: external validation reinforces your case
- When your team is growing or restructuring: organizational change creates new roles and responsibilities that may align with your promotion request
Worst Timing
- Immediately after a production incident you were responsible for
- During company-wide budget cuts or layoffs
- When your manager is under stress from their own deadlines or conflicts
- Without having discussed your career trajectory at least once in the previous six months -- a promotion request should never be a surprise
Step 6: Present the Case
The promotion conversation with your manager should feel like a business proposal, not an emotional appeal.
Structure of the Conversation
- Open with your goal: "I would like to discuss my promotion to [specific title]. I have been preparing for this and want to share the evidence I have documented."
- Present your impact evidence: share the quantified accomplishments from your impact log, organized by the promotion committee's evaluation dimensions
- Show next-level performance: demonstrate specific examples where you have already operated at the level above your current title
- Acknowledge gaps: if there are areas where you do not yet meet the next-level requirements, address them proactively with a plan to close the gap
- Ask for feedback: "What additional evidence would make this case stronger?" -- this turns the conversation from a request into a collaboration
What Not to Say
- "I deserve this because I have been here for X years" -- tenure is not a promotion criterion
- "Other people at my level make more" -- compensation and promotion are separate conversations
- "I will leave if I do not get promoted" -- threats destroy trust and guarantee a negative outcome even if the promotion is granted
- "I work longer hours than anyone" -- hours worked is not a measure of impact; outcomes are
Handling a Promotion Denial
Not every promotion request succeeds on the first attempt. How you handle the denial determines whether you get promoted next cycle.
Ask for specific, actionable feedback:
- "What specific evidence was missing from my case?"
- "What would I need to demonstrate in the next six months to make the case stronger?"
- "Are there specific projects or responsibilities you would recommend I take on?"
Document the feedback, create a plan with your manager to address the gaps, and set a follow-up date to revisit the conversation. Most promotions that fail in the first attempt succeed in the second when the candidate addresses the specific gaps identified.
Performance improvement plan (PIP) -- a formal document outlining specific performance deficiencies and required improvements within a defined timeline, typically associated with the risk of termination -- is entirely different from promotion feedback. Promotion denial means you are performing well but have not yet demonstrated next-level readiness. A PIP means your current performance is inadequate. Do not conflate the two.
If you are denied promotion twice after addressing the feedback from the first denial, the issue may be structural rather than performance-based. Some organizations have implicit caps on the number of people at each level, limited promotion budgets, or managerial reluctance to advocate. In these cases, an external move to a new employer at the higher level may be the faster path. A 2023 ADP Research Institute study found that IT professionals who changed employers received an average salary increase of 14.8 percent, compared to 5.6 percent for those promoted internally. External moves carry risks -- loss of institutional knowledge, culture adjustment, and network rebuilding -- but when internal advancement is genuinely blocked, they are often the rational choice.
The Role of Technical Visibility
Promotion committees cannot evaluate work they have never seen. For IT professionals, particularly those in individual contributor roles, creating technical visibility requires deliberate effort.
Practical Visibility Tactics
- Internal tech talks: present your project's architecture, a postmortem analysis, or a new tool evaluation to your department; even a 15-minute presentation establishes you as a subject matter authority
- Written technical proposals: when you identify a problem or improvement opportunity, document it formally with an RFC (request for comments) or design document; written artifacts persist in organizational memory long after conversations are forgotten
- Cross-functional collaboration: volunteer for projects that span engineering, product, and business teams; these expose you to decision-makers who would otherwise never interact with your work
- Mentoring documentation: when you mentor junior engineers, track the outcomes; a record showing that two engineers you mentored were promoted or achieved certifications like
CompTIA Security+ (SY0-701)orAWS SAA-C03under your guidance is powerful promotion evidence
Tanya Reilly, a staff engineer at Squarespace and author of The Staff Engineer's Path (O'Reilly Media), has written that the transition from senior to staff engineer requires a fundamental shift from "doing technical work" to "making technical work visible and influential across the organization." The same principle applies at every promotion boundary in IT: the scope of your visibility must expand along with the scope of your impact.
The Certification Factor in IT Promotions
Certifications alone do not drive promotions, but they remove objections. A manager who wants to promote you to a senior cloud engineer role has a stronger case with the promotion committee if you hold AWS Solutions Architect Professional (SAP-C02) or Azure Solutions Architect Expert (AZ-305).
Gartner's 2024 research on IT workforce management found that 47 percent of IT organizations use certifications as a factor in promotion decisions, and 34 percent require specific certifications for certain role levels. In government and defense contracting, certifications like CISSP or CompTIA Security+ (SY0-701) are often mandatory for promotion to roles involving sensitive systems.
The strategic approach is to earn certifications that align with your target promotion role before requesting the promotion, so the certification becomes supporting evidence rather than a prerequisite that delays the decision.
See also: IT certifications with the highest salary premium, LinkedIn headline optimization for IT professionals, starting an IT freelance practice
References
- Robert Half Technology. "2024 IT Professional Satisfaction and Career Development Survey." Robert Half International, 2024.
- Larson, Will. An Elegant Puzzle: Systems of Engineering Management. Stripe Press, 2019.
- Scott, Kim. Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity. St. Martin's Press, 2017.
- Coqual (formerly Center for Talent Innovation). "Sponsorship and Career Advancement Study 2023." Coqual, 2023.
- Gartner. "IT Workforce Management: Certification and Promotion Practices 2024." Gartner, 2024.
- Evans, Julia. "Get Your Work Recognized: Write a Brag Document." jvns.ca, 2019.
Frequently Asked Questions
How do I ask for a promotion in an IT role?
Treat the promotion conversation like a business proposal. Present documented evidence of your quantified impact, specific examples of work you have done at the next level, and acknowledgment of any remaining gaps with a plan to close them. Ask your manager what additional evidence would strengthen the case. Never frame it as a demand or threaten to leave.
What evidence do promotion committees look for in IT?
Promotion committees typically evaluate four dimensions: performance at your current level (25-30% weight), evidence that you are already performing at the next level (30-40%), measurable business impact such as cost reduction or reliability improvement (20-25%), and organizational influence including mentoring and cross-team collaboration (10-15%). Quantified accomplishments with specific numbers carry the most weight.
How long should I wait before asking for a promotion in IT?
There is no fixed timeline. The readiness indicator is whether you have documented evidence of performing at the next level, not how many months you have been in your current role. That said, most promotion cycles run annually, so align your request with performance review season when promotion budgets are allocated. Have at least one career development conversation with your manager before making a formal request.