RUBRIK | 2025 INTERNSHIP

Cross-region recovery for Azure VMs

Giving enterprise customers the flexibility to recover their data anywhere.

ROLE

Product Design Intern

TEAM

1 PM · 3 Engineers · 1 UX Writer

DURATION

4 weeks · Shipped

TOOLS

Figma, FigJam, Dovetail

OVERVIEW

My summer @ Rubrik

Over the summer I interned at Rubrik as the sole designer on the Orchestrated Application Recovery (OAR) team.

Four weeks, end-to-end ownership, shipped to production.

CONTEXT + BACKGROUND

OAR: Your Data's Evacuation Plan

Rubrik protects 5,000+ organizations from cyberattacks and data loss.

OAR, their Orchestrated Application Recovery product, automates the entire process of moving and restarting applications to a backup site. It coordinates recovery end to end, so when a cyberattack hits or a disaster strikes, businesses can get back up and running without downtime.

PROBLEM

Expanding Cross Region Recovery

Rubrik's recovery workflow let customers back up data to the cloud, but only within the same geographic region as the source.

So, for example a subscription in Region 1 (like US West) could only recover to the same region and not an alternate or cross region. For enterprise customers operating across regions or bound by compliance requirements, this made full adoption impossible.

OUTCOME

Shipped Experience

Over four weeks, I took this feature from exploration to production as the sole designer.

The process involved unlocking the target region field, solving a complex VM size availability problem across 100+ objects, and introducing a new aggregated display pattern to Rubrik's design system across four iterations of design and validation.

IMPACT

A Highly Requested Feature: Delivered!

336 enterprise customers with immediate access

1,300+ upsell opportunities unlocked across Azure and EC2

Removed the last barrier to full Rubrik adoption for compliance-driven enterprise customers. Closed the competitive gap that had kept customers running parallel tools alongside Rubrik.

REFLECTION

My Key Takeaways

  • Asking the right questions — moves faster than having all the answers. Working on a deeply technical product with a short timeline, I learned to build just enough understanding to make informed decisions and keep moving.

  • Better, not just new. Design crits pushed me to consistently evaluate whether a proposed solution was genuinely improving the experience or just adding complexity.

  • Understand the system before you push past it. Taking time to internalize Rubrik's design system early meant that when I needed to introduce a new pattern, I could make a clear case for why existing primitives weren't enough.

Get in Touch! ✉️👋
This is an overview of my work on this project. If you're interested in learning more, reach out and I'd be happy to walk you through the full case study!

Thanks for stopping by! 🪴

Would love to talk projects, collaborations, or anything design!

Built with love © 2026 Vanshika Gaur