Ritvika Nagula walked into Microsoft as a new college grad in April 2019 thinking that quality work would speak for itself. Five years and four promotions later, she is a senior software engineer at Azure with a radically different approach — one that marries relentless visibility, biweekly manager check-ins, and a conscious drive to own end-to-end projects. Her story, published as an as-told-to essay in Business Insider, has become a template for engineers trying to decode what “ready for the next level” actually means. At a moment when artificial intelligence is redrawing the lines between task execution and outcome ownership, that template matters more than ever.

Nagula’s first year taught her a lesson she now repeats to anyone who will listen. Delivering solid code on time isn’t enough. “I did not know that I should be proactive about communicating my career aspirations with my manager,” she said. “It can lead to a disconnect where your manager or the leadership thinks that you are not necessarily career ambitious.” Her corrective was methodical: biweekly one-on-ones, a monthly pulse-check specifically about promotion readiness, and a written 18–24 month target for moving to the next level.

The raw mechanics are straightforward, but their power lies in the compounding signal they send. “What do you think is going good? Do you think I could do something better? Is there anything that I might be overlooking?” she asks every month. That cadence converts a vague hope for advancement into a project plan with milestones, deadlines, and a documented trail of evidence that promotion committees can evaluate.

The Playbook, Step by Step

1. Biweekly 1:1s and Monthly Career Check-ins

Semi-annual reviews are too slow. By the time you learn you’ve missed a mark, the window to close the gap may have passed. Nagula insists on bringing career goals into the conversation at least once a month. A shared document tracks the promises made and the proof gathered. The key question: “What would you need to see from me to make a promotion an obvious next step?”

2. Map the Leveling Rubric

At Microsoft, an internal “role library” spells out exactly what is expected at each engineering level. Nagula cross-references that written standard against her own performance monthly. If a senior promotion demands end-to-end delivery, she asks her manager to match her with projects that provide that scope. The tactic removes guesswork and makes readiness verifiable.

3. Own End-to-End Outcomes

“Getting promoted is not just doing the work that you’ve been asked to do; it’s also taking ownership, taking control, and trying to find these opportunities for yourself.” Nagula explicitly flagged her interest in driving a project from design through rollout. That overt signaling meant her manager thought of her when new features or critical cross-team work appeared. Demonstratable ownership, she says, is the litmus test for senior promotions.

Why AI Makes This Playbook More Urgent

Microsoft’s deep embedding of Copilot across Office, Azure, and GitHub is shifting how employee impact is measured. Routine coding tasks are increasingly absorbed by generative tools, shifting the value proposition toward those who can orchestrate complex systems, supervise AI outputs, and tie technical work to business outcomes. The sponsorship economy that emerges from this shift favors employees who explicitly show they can lead in an AI-augmented environment.

Consider the dynamics:

  • AI-generated code and synthesized meeting notes can obscure who actually drove a result. An engineer who quietly finishes tickets may disappear into the noise, while one who documents her intent, coordinates across teams, and frames results in terms of business impact stays visible.
  • End-to-end ownership is exactly what AI cannot automate. Designing a feature, understanding why it matters to customers, monitoring its rollout, and correcting course — these demand human judgment that committees reward with promotion.
  • Manager sponsorship becomes even more critical when headcount resourcing tilts toward AI initiatives. By making her ambitions known early and often, Nagula positioned herself for high-impact projects that aligned with Azure’s strategic bets.

In short, the automation wave amplifies the behaviors Nagula recommends. The same playbook that worked before Copilot works even better now.

The Evidence: Fact, Pattern, and Caveat

Business Insider confirmed Nagula’s employment and promotion history. Her account joins a chorus of practitioner advice across the tech industry — popular posts by engineers who accelerated their careers all echo the same themes: signal intent, gather measurable outcomes, secure sponsorship beyond your direct manager. This is not a one-off anomaly but a pattern visible in large tech companies where promotion packets are judged by committees.

However, retellings flatten nuance. Nagula’s story is one route, not a universal formula. Promotion mechanics differ by team, geography, and budget cycle. In the AI era, some internal paths are accelerating faster than others. Microsoft employees working on Copilot-adjacent features may find promotions come quicker than those in legacy infrastructure. The playbook works best when the projects you lead map to the company’s strategic direction.

Strengths, Risks, and Structural Inequities

The approach is actionable, repeatable, and aligns with managerial incentives — managers want reliable owners for high-impact work. It reduces ambiguity and future-proofs careers by emphasizing supervisory skills over rote execution.

Yet blind spots remain:

  • Visibility vs. optics: Repeatedly asking for promotion without demonstrable growth can backfire as entitlement. The signal must be backed by evidence.
  • Burnout: Targeting frequent promotions can encourage unsustainable workloads. Rapid advancement without support risks personal cost.
  • Two-tier tracks: As companies tilt resources toward AI, employees in non-AI domains may find fewer high-visibility projects, creating equity challenges that organizations need to address.
  • Manager dependency: Overreliance on a single manager’s advocacy is fragile. Building cross-team sponsors and a broader network reduces that risk.

Translating the Playbook into a 12-Month Plan

For engineers who want to operationalize Nagula’s advice, a concrete sequence helps convert ambition into deliverables:

  1. Document your baseline: Map the internal leveling rubric against your current role and identify 3–5 gaps.
  2. Set a target date: 12–18 months for the next level, broken into quarterly milestones.
  3. Create a shared tracker: Commit to monthly promotion check-ins with your manager, using a living document that logs accomplishments and emerging evidence.
  4. Volunteer for one end-to-end project: Choose work that requires cross-functional coordination and ties directly to team priorities.
  5. Secure two cross-team endorsements: Senior peers or product partners who can attest to your impact widen your advocate circle.
  6. Draft a promotion packet early: A one-page summary of goals, outcomes, and stakeholder quotes serves as a north star and a rehearsal for the formal review.

This sequence makes invisible ambition visible and builds the hard evidence that committees weigh.

The Larger Trend: Sponsorship in the Age of Intelligent Automation

Organizational research increasingly validates the link between proactive career conversations and advancement. In an AI-saturated workplace, the premium on human oversight — defining problems, interpreting ambiguous outputs, maintaining accountability — means the people who consistently demonstrate those skills will move up. Nagula’s story isn’t just a career hack; it’s a response to a structural shift in what companies value.

At the same time, the shift is not neutral. Microsoft’s aggressive AI integration creates new roles and accelerates some career tracks while others risk stagnation. The playbook’s emphasis on finding high-impact projects thus becomes a call to align personal ambition with corporate strategy — a dynamic that can be both empowering and exclusionary.

Closing Analysis

Nagula’s account is vibrant because it is specific, honest about early mistakes, and granular on the mechanics. In an era where AI both multiplies output and blurs contribution, the behaviors she models — explicit goal-setting, frequent feedback loops, and demonstrable ownership — are increasingly the currency of promotion decisions. Those who adopt them give themselves the best chance to advance. But they must also guard against burnout, assess whether their path aligns with fair organizational practices, and remember that the playbook is a tool, not a guarantee.

The engineer who thought quiet competence would be enough left that version of herself behind in 2019. The lesson she offers now is that in the AI-era workplace, being seen — backed by real results — is the strategy that opens doors.