Exploring Product Directions at Google
As a UX Engineer on Google Travel, I built dozens of React prototypes to help teams explore new product directions, validate assumptions and make decisions faster. Not every prototype shipped, but every prototype answered a question.
- UX Engineer
- UX Leads
Researchers
Product Managers - Prototyping
Interaction Design - React
Google Maps API
Travel Discovery in Search
How can Search support travel discovery, not just information retrieval?
I prototyped a visual travel module that appeared for high-intent travel queries, surfacing destinations, imagery, maps, and travel content directly within Search results.
This exploration contributed to a broader shift toward more visual, widget-based travel experiences in Search.
Built as a React prototype against live Search components so PMs and designers could click through real queries before any backend work.
Testing Map Density Through Pin Clustering
How much information can we show on a map before it becomes overwhelming?
I explored clustering strategies across zoom levels, balancing geographic accuracy with visual clarity.
The work informed discussions around map density and information hierarchy.
Tested several clustering thresholds with real map data to find the point where density stopped helping and started hurting scanability.
Geopolitical Information Bottom Sheet
How can Maps communicate complex geopolitical information without overwhelming the map itself?
I designed a multi-page bottom sheet that progressively revealed context while keeping the map as the primary focus.
The interaction model was adopted and shipped in production.
The multi-page sheet pattern shipped and became a reusable way to layer dense context without covering the map.
Progressive Disclosure Through Zoom
How should information density evolve as users zoom in and out?
I explored adaptive map behavior where labels, places, and contextual information appeared progressively based on zoom level.
The concept was ultimately not shipped, but it helped the team evaluate information-density tradeoffs and informed later design discussions.
Not shipped — the zoom-driven density felt unpredictable in testing, but the exploration shaped how the team reasoned about map detail later.