Moving from principal or director to VP of Platform/Infrastructure is a step change in scope and focus. Your leverage shifts from writing and reviewing code to org design, strategy, and cross-company alignment. The skills that got you here-technical depth, judgment, and the ability to ship-remain important, but they're applied differently: through the people and systems you build, not through your own keyboard.
Scope of the role
You own the foundation: compute, data, reliability, developer experience, and often security and AI platform. Success is measured by uptime, productivity of other teams, and strategic bets (e.g., cloud, platform consolidation). Your customers are internal: product engineering, data science, and sometimes security and compliance. Their success is your success; if they can ship faster and more reliably because of your platform, you're winning.
Get clear on the boundaries. Platform often overlaps with product (e.g., who owns the developer portal?), security (who owns secrets, IAM, and vulnerability management?), and data (who owns the data platform vs. analytics?). Document RACI and interfaces so there's no ambiguity. Revisit these boundaries as the company and strategy evolve.
Mindset shifts
You delegate technical depth and absorb organizational and political complexity. Your job is to create clarity, remove blockers, and represent platform in exec and product discussions. Stay technical enough to make good bets; don't try to stay in the code daily. That means reading design docs, attending key architecture reviews, and keeping a finger on the pulse of your stack, but not being the one writing the code or debugging at 2 a.m.
Learn to say no (or not yet) with clarity and data. You'll be pulled in many directions; prioritization is one of your main levers. Explain the tradeoffs, share the roadmap, and invite input, but own the final call. Build trust by delivering on what you promise and by being transparent when you have to deprioritize or delay.
Where to spend time
Prioritize: org health and hiring, roadmap and prioritization, cross-functional relationships, and board/exec storytelling. Protect time for strategic thinking; guard against becoming the escalation bottleneck for every incident. Block calendar for deep work and for 1:1s with your directs; if you're in back-to-back meetings, you're not leading, you're reacting.
Invest in your exec and peer relationships. Platform depends on product, sales, and finance for funding and alignment; invest in those relationships so that when you need to make a case for a big bet or a headcount increase, you have credibility. Tell the story of platform in business terms: productivity, risk reduction, and enablement, not just uptime and features.
The best platform VPs make their teams and systems so good that the rest of the company can move fast without thinking about the foundation.