Google Cloud UX Internship

Can understanding enterprise complexity help us design simpler, smarter experiences?

Story

During my internship at Google Cloud, I worked on two vastly different projects—one rooted in internal product operations, the other in cloud infrastructure design.

But both revealed the same insight:

The more deeply we understand complexity, the better we can simplify it for others.

🧩 How it all began...

Let’s break down how design helped tackle scale and complexity at Google Cloud.

What is Google Cloud—and where did I fit in?

A platform powering digital transformation

Google Cloud offers infrastructure, tools, and services that help developers and enterprises build, deploy, and scale faster. From AI to analytics to virtual machines—GCP supports some of the most complex workloads in the world.

Now where do I fit in this equation…

GCBP builds and maintains the core internal platforms that power both Google Cloud's internal operations and partner ecosystems. It’s the behind-the-scenes engine that ensures the cloud runs smoothly—for everyone.

As a UX Design Intern, I am working on 2 key initiatives within Google Cloud:

Ohara

An internal platform that manages all Google Cloud products

VMWare

A conceptual design sprint to simplify VM creation through user intent

In both cases, I wasn’t just designing screens—I was designing clarity inside complexity.

Project 1: Ohara – UX for Product Management at Scale

How do you design clarity into a platform that already does everything?

What is Ohara?

Ohara is an internal platform which is one of the products of GCBP. It is critical for managing product information within a large organization. It acts as a central source of truth for product data.

Think of it as the central nervous system of product operations.

But as Google Cloud scaled, Ohara became increasingly complex. The workflows were robust—but not intuitive. Teams spent time deciphering the system instead of managing products.

💢 The Problem

Ohara was built as a MVP for product data management across Google Cloud—handling everything from catalog entries to metadata changes. But as the number of products and teams grew, the system’s usability began to buckle.

What started as a powerful backend tool turned into a daily bottleneck for its users.

These weren’t isolated issues—they were system-wide patterns making daily work slower, harder, and riskier.

🧭 How I Approached It

Instead of rushing into solutions, I focused on understanding the system, the users, and the patterns behind their frustrations.

Since Ohara is an internal platform

I took a lean research approach—leveraging real, ongoing user feedback from within the organization to guide our design direction.

🔍 What we uncovered

Based on internal feedback, support tickets, issue logs, and stakeholder interviews, we defined four key challenges:

  • 01

    Unclear & Overwhelming Error Messaging

    Errors lacked clarity or guidance—users didn’t know what went wrong, why, or how to fix it.

  • Difficulties in the Review & Approval Process

    Bulk modifications were hard to parse, leading to blind approvals and missed critical changes.

    02

  • Navigation Challenges

    The deep, hierarchical structure made it difficult to locate or understand where users were in the system.


    03

  • Cumbersome & Unintuitive Workflows

    Even simple tasks required multiple clicks, constant context switching, and high cognitive effort.

    04

  • Poor Search & Filtering

    Finding the right product data was time-consuming due to limited and unintuitive search options.

    05

✏️ Ideation

Turning messy insights into structured design opportunities

Once we had a clear understanding of the core issues across navigation, reviews, and error handling, I shifted focus to exploring possibilities—without rushing to solutions.

Ideation wasn’t just about creativity—it was about creating the right structure for ideas to emerge, evolve, and eventually land in a context as complex as Google Cloud.

✨ Reflections & Learnings

Working on Ohara wasn’t just a UI challenge—it was a deep dive into the invisible systems that power one of the world’s largest cloud ecosystems.

⚙️ Project 2 – VMware Engine Design Sprint

What if configuring a virtual machine felt more like building your perfect setup—customized, goal-driven, and smart?

🧭 Context

What is GCVE?

Google Cloud VMware Engine allows enterprises to seamlessly run their VMware workloads on Google Cloud’s infrastructure—without refactoring.

Think of it as a fast lane for IT teams to move and scale their existing systems into the cloud—without losing control.

🔍 Discover & Analyze

We started with a competitive analysis—not just within cloud providers, but also tools that help users configure complex systems (like PC part pickers and server builders).

  1. What makes a setup experience feel approachable—even when it’s technical?

  2. Where do these tools help users make confident decisions?

  3. What kind of trade-off information (cost vs performance) do they surface well?

and more….

✏️ Define & Reframe

From our research, we crafted focused How Might We prompts and conducted Crazy 8's

🧩 My Role: Intent-Led Design

My focus was on designing the intent-capturing framework—making sure the system could understand a user’s goal, and let that guide the entire setup journey.

I explored how user intent could:

1

Shape recommended specs dynamically

2

Trigger smarter defaults (based on context)

1

Adapt based on performance, cost, or compliance needs

4

Provide transparency behind every recommendation

VMware Engine is used by cloud architects and infrastructure engineers. So it wasn’t about simplification—it was about giving control, with clarity.

🔐 The Outcome

Final Takeaway!

Two projects. Two worlds. One common thread: designing clarity into complexity.

🔁 Insights That Crossed Over

From Ohara → VMware:
Ohara gave me a front-row seat to how large-scale internal systems function—where even the smallest design shift can ripple into meaningful operational change.
It trained me to think beyond interfaces, focusing instead on how users make decisions under pressure, across roles and workflows.

So when I entered the VMware sprint, I brought that lens with me. I was already thinking in systems. So when the question became “What’s the user trying to achieve?”, my response was instinctive:

Design flows that align with intent, reduce friction, and respect expertise—without ever dumbing it down.

From VMware → Ohara:
In the sprint, we flipped the traditional setup flow on its head: starting with user intent instead of configurations. That shift reframed how I thought about Ohara.

Why overwhelm every user with every change, when their role only requires focus on a few?
That question led directly to my AI-generated summary feature—surfacing only what matters, to the people it matters to.

Two different products. Two different problems.
But together, they taught me how to design for clarity, confidence, and context—no matter how complex the system.

Wrapping up, thank you!

If you’re still here, then I know you have found something interesting, or everything interesting maybe✨

  • Let’s Create Something Great

I'm all about transforming ideas into designs that resonate. Whether you're looking to collaborate or need a fresh perspective, I'm eager to bring innovative solutions to the table.

Here’s how I can help—no coffee required:

P.S. I'm looking for a Full time role. Got something in mind? Let’s chat!

Create a free website with Framer, the website builder loved by startups, designers and agencies.