Ritvika Nagula joined Microsoft’s Azure division in April 2019 as a fresh graduate. By 2024, she had earned four promotions—a pace that eludes most engineers in big tech. Her secret? Not a mysterious formula, but a systematic, evidence-based approach to career management that she recently shared in an as-told-to piece republished by multiple outlets, including The Economic Times. The tactics are deceptively simple: explicit goals, frequent manager check-ins, mapping to internal role rubrics, and volunteering for end-to-end projects. Together, they form a repeatable playbook that turns good work into unignorable evidence—precisely what promotion committees need to see.
From Passive Performer to Strategic Career Architect
Nagula’s first year at Microsoft was driven by a common assumption: that doing great work would naturally lead to advancement. It didn’t. “I realized that promotions aren’t just about performance—they’re about demonstrated readiness for the next level,” she told Business Insider. That realization sparked a pivot. She began treating her career like a product roadmap, with clear milestones, measurable outcomes, and frequent stakeholder review. This shift from passive output to proactive career management became the engine of her rapid ascent.
Her story lands at a moment when the definition of “impact” in tech is shifting. With AI automating more routine tasks, the human skills that remain—problem framing, cross-team orchestration, and strategic ownership—are commanding premiums. Compensation data from Levels.fyi shows AI-specialized engineers earning progressively larger pay differentials at senior and staff levels compared to non-AI peers. Inside Microsoft, Business Insider’s analysis of internal pay data reveals that employees in AI organizations earn substantially above the company average. In this environment, Nagula’s playbook isn’t just a career hack; it’s a survival guide for the AI era.
The Four-Promotions-in-Five-Years Playbook
Nagula distilled her approach into a handful of repeatable actions. Each one deliberately converts tacit effort into documented, sponsorable proof—the currency of promotion committees in large organizations.
- Schedule frequent 1:1s with your manager, and reserve a monthly check-in solely for career progression. Biweekly syncs keep alignment tight, but the dedicated monthly meeting ensures promotion readiness stays a standing agenda item, not an afterthought.
- Set a concrete promotion timeline and translate it into measurable milestones. Nagula targeted the next level in 18–24 months, then backward-planned specific deliverables that would close competency gaps. This turns “I want a promotion” into “By Q3, I will have owned a full feature rollout, reduced latency by 20%, and mentored two junior engineers.”
- Use an internal role library or leveling rubric to identify and close gaps. Most big-tech firms maintain detailed rubrics listing responsibilities and competencies for each level. Nagula mapped her work against Microsoft’s internal role library, turning ambiguous “ready or not” conversations into objective, verifiable checklists.
- Ask to lead end-to-end projects that demonstrate cross-functional ownership. Promotion committees look for evidence that you’re already operating at the next level. Owning a project from design to rollout—coordinating with product managers, partner teams, and stakeholders—provides that signal. Nagula volunteered for these opportunities rather than waiting to be assigned them.
- Build a broad network of feedback providers and sponsors. She actively collected endorsements from peers, product partners, and mentors, creating a 360-degree view of her impact. This sponsorship network became a force multiplier during calibration meetings.
These steps are straightforward but powerful because they systematically eliminate the gap between what you do and what the organization sees.
Why the Playbook Works (and When It Won’t)
The logic behind each element is rooted in how large engineering organizations evaluate talent.
Visibility beats good work alone. Consistent delivery is table stakes. Advancement requires a shift from individual output to reliable ownership and influence. Frequent, documented conversations make progress visible, create a paper trail for promotion packets, and compress feedback cycles so gaps can be closed before formal reviews.
Rubrics remove subjectivity. Leveling rubrics turn subjective “I think she’s ready” into objective evidence. When you and your manager track specific rubric items, the promotion discussion moves from opinion to audit-ready checklist.
End-to-end ownership is the strongest signal. Leading a cross-functional project demonstrates technical judgment, coordination, and accountability—all markers of senior roles. Nagula’s proactive requests ensured her experience matched the rubric’s stretch requirements.
The AI era redefines impact. As AI absorbs routine coding and operations, the value shifts to skills like AI orchestration, system integration, and governance. Companies are paying premiums for people who can safely integrate AI into production systems. The projects that “move the needle” increasingly involve AI-adjacent work, amplifying the returns from Nagula’s emphasis on measurable, high-visibility ownership.
Yet the playbook isn’t a universal guarantee. Promotions depend on team priorities, budget cycles, and available headcount. The approach increases probability but can’t create openings. Moreover, access to promotionable projects is uneven—often concentrated in AI-focused teams, risking a bifurcated workforce. The playbook also requires cautious management to avoid burnout. Chasing rapid promotions can tempt people to take on unsustainable scope without adequate resources. And repeated promotion discussions without measurable progress can backfire, turning ambition into perceived entitlement. The signal must always be backed by data.
The AI Premium: Why This Strategy Matters More Than Ever
Independent compensation analyses corroborate the macro trend. Levels.fyi’s Q3 2025 AI Engineer Compensation Trends report reveals widening pay gaps between AI and non-AI engineers, especially at Staff and Principal levels. For instance, at the Staff level, AI engineers command roughly 20–30% more total compensation than their non-AI counterparts. Inside Microsoft, Business Insider’s review of internal pay data shows that median compensation in AI organizations is tens of thousands of dollars higher than the company average, with senior individual contributors reaching total packages exceeding $500,000.
These numbers underscore a structural shift: organizations are willing to pay a steep premium for people who can lead AI-augmented work. Nagula’s tactics—visibility, measurable impact, and cross-functional leadership—align directly with the competencies that attract those premiums. In the AI era, the ability to frame problems, orchestrate AI tools, and govern integrated systems is the new currency of career acceleration.
A Practical 12-Month Plan to Adopt the Playbook
Implementing Nagula’s approach doesn’t require privileged access or extraordinary talent—just discipline. Here’s a quarter-by-quarter roadmap.
Weeks 1–2: Document your baseline. Download or copy your company’s leveling rubric. Map your current responsibilities against it and identify 3–5 verifiable gaps. Create a one-page “promotion packet” draft listing current evidence and target criteria.
Month 1: Set the target and timeline. Choose a target level and date (e.g., “Level X by Q2 2026”). Put it in writing and share it with your manager during a career-focused 1:1. Ensure the timeline aligns with your company’s review cycles.
Month 1 onward: Establish a cadence. Keep biweekly 1:1s; once per month, dedicate a session to promotion readiness. Use a shared document to track feedback, agreed milestones, and deliverables. The one-page promotion packet becomes the living artifact that evolves with progress.
Months 1–6: Secure one end-to-end project. Volunteer for or negotiate ownership of a cross-functional initiative that directly maps to your open rubric items. Frame the project in business-impact terms and define clear success metrics (e.g., “reduce latency by 10%,” “onboard five new enterprise customers”).
Months 3–9: Broaden sponsorship. Solicit endorsements from 2–3 cross-team partners (product managers, partner engineers). Add short, specific testimonials to your promotion doc. These help committees see cross-functional impact.
Months 6–12: Iterate and document impact. Deliver milestones, collect quantitative evidence, and refine your promotion packet as formal evaluation windows approach. If the promotion is deferred, request explicit, written next steps and a revised timeline.
Templates and Scripts for Immediate Action
Language matters. Here are artifacts that convert informal conversation into committee-ready evidence.
Monthly career 1:1 agenda (30 minutes)
- 5 minutes: Quick wins since last meeting (attach evidence links)
- 10 minutes: Progress against rubric items (what’s closed, what’s open)
- 10 minutes: Concrete asks (projects, stretch responsibilities, endorsements)
- 5 minutes: Immediate next steps and deadlines
Sample script to ask for end-to-end ownership
“I’ve mapped the role rubric and identified leading a full feature rollout as a gap for the next level. If you agree, I’d like to own [project X] and can prepare a success metric plan and stakeholder list to show impact.”
Promotion packet one-page must include
- Target level and timeline
- Three measurable outcomes with metrics
- Project ownership summary and cross-functional endorsements
- List of rubric items satisfied (with evidence links)
- Outstanding gaps with proposed closure steps
What Managers and Organizations Should Do
Nagula’s playbook places responsibility on the individual, but companies must sustain fair systems. Recommended actions:
- Publish leveling rubrics and exemplar promotion packets so transparency is the default, not an exception.
- Rotate or distribute “promotionable” projects across teams to avoid concentrating opportunities in AI tracks.
- Reward and measure sponsorship by including manager development/advocacy in performance reviews.
- Monitor promotion and compensation rates across functions to detect and correct emerging two-tier systems.
Ethical Considerations: The Two-Tier Risk
The market’s AI premium is real and growing. But if high-impact, high-visibility projects are channeled primarily to AI teams, organizations risk creating a workforce with predictable career ceilings based on assignment, not ability. People in operations, security, or foundational infrastructure may find their paths stagnating even as they deliver essential work. Companies must intentionally design career ladders that reward diverse expertise and ensure all tracks offer visible, measurable promotion pathways. Otherwise, the AI premium could exacerbate inequity under the guise of market logic.
Conclusion: Turn Good Work into Unignorable Impact
Ritvika Nagula’s story resonates because it demystifies a common frustration: “I do great work but don’t get promoted.” Her playbook is a disciplined antidote. Make goals explicit. Measure against a rubric. Ask for ownership. Document outcomes. In a tech landscape where AI is redefining value, these behaviors are not optional—they are foundational. But the playbook is conditional. It requires managerial sponsorship, access to the right projects, and organizational policies that reward evidence over impression. For engineers and operators ready to accelerate their careers, the path is clear: plan deliberately, act consistently, and make your contributions impossible to overlook. The next year of your career doesn’t have to be a gamble; it can be a roadmap.