Google Careers - Location page Redesign

Google Careers - Location page Redesign

Google Careers - Location page Redesign

Research-Led Redesign for High-Intent Candidates

Google Careers pulls in 3M+ applications anually, but candidates were dropping off before finishing a profile. I led research on Google's project with Codelab, UC Davis's student design agency: 180+ survey responses, user interviews, and two rounds of A/B testing. The findings reshaped the page's information architecture, and I went beyond my research scope to build mid-fi components within Brightspot CMS constraints that made it into the final proof of concept.

Google partnered with Codelab, a design and software agency at UC Davis, to optimize its locations ecosystem and convert high-intent leads to apply.

Update, August 2026: Google is implementing the majority of our designs for launch later this year.

Proof of Concept

UX Research

UX Design

YEAR

2026

TEAM

Research

Design

Product
Engineering

ROLE

UX Researcher

TOOLS

Figma
Google Forms

Brightspot CMS

SKILLS

Survey • Design • A/B Testing • Data Synthesis • Mid-Fi Wireframing

ROLE

UX Researcher

YEAR

2026

TOOLS

Figma
Google Forms

Brightspot CMS

TEAM

Content

SKILLS

Survey • Design • A/B Testing • Data Synthesis • Mid-Fi Wireframing

THE problem

Google Careers’ location page was losing candidates before they ever hit apply.

The page was clean and well organized, but it was built to inform rather than to make someone get a feel for what it was like to work and live there. It told candidates what jobs existed without telling them what life at that location actually looked like: no sense of commute, neighborhood, or daily routine. Candidates got a row of job listings and a small photo carousel instead.

The Investigation

What 180+ people told us
(and what they didn't)

We ran a survey across five universities—UC Davis, UCLA, UCI, Georgia Tech, Boston University. Tabling, Slack, Discord, campus flyers. We conducted 12 moderated interviews. We tested nine different page variations to see what actually moved the needle.


Image gallery of the UXR team outreaching for survey applicants around UC Davis campus

"It doesn't scream 'Google' like other sites do."

The survey told us the page felt sterile, overwhelming, off-brand.

PERCEPTION

48%

negative word associations: sterile, bland, lifeless

OVERWHELMING

OVERWHELM

53%

drop-off among highest-intent candidates after viewing

OFF-BRAND

50%

left with low to moderate confidence in understanding the location

To synthesize 180+ open-ended responses, I used Gemini to surface clusters and patterns. The question remained, “What do candidates want? And why?

"There's a lack of information and images. It makes it hard to actually picture yourself working there."

— High-intent candidate

The Discovery

Two cohorts. Two completely different mental models.

Entry-level candidates wanted a lifestyle. Experienced hires wanted logistics.

Entry-level candidates:

We surveyed.

  • Entry-level candidates cared about lifestyle, city culture, and social scene. What does daily life actually feel like?

Experienced hires:

We interviewed.

  • Experienced professionals cared about logistics, commute times, and family relocation.

We interviewed.

  • Experienced professionals cared about logistics, commute times, and family relocation.


Google wanted one page for both but they weren't reading it the same way. This split surfaced in how people talked about weighing relocation through a both the interviews and surveys. To get experienced hires into the study at all, we reached into our own networks instead of waiting on a formal recruiting pipeline, which gave us more candid responses than a screened panel would have.

One finding surprised Google the most

We had to lead with place, not just workplace.

Across both cohorts, candidates ranked city culture and proximity to loved ones above office amenities.

The patterns that emerged

Three key friction points: Navigation, Authenticity, Decision making

01

The map wasn't helping anyone navigate.

We tested it. Users got confused, the map wasn’t functional or intuitive and it was hard to find specific locations. Clients told us: interactive maps are a consistent pain point across their entire product suite but implementing search bars were not feasible here. We had to get creative.

02

The content informed but didn't inspire.

None of that “Google innovation” was being conveyed. One candidate wrote: "Putting pictures at the top doesn't give me any idea of what it would be like to work there." Images alone weren't enough. They needed real voices. Real context.

03

Candidates left without enough to decide.

The top three things they needed, daily logistics, lifestyle fit, living conditions, weren't on the page.

Screen recording of me conducting an usability audit of the original Google Career's location page

From insight to direction

I built a handoff document that became the design brief

We used the iceberg model and five whys across FigJam boards to move from raw data to direction. I took those findings and translated them into a strategic framework. A handoff document mapping candidate pain points directly to UI strategy within Brightspot's CMS constraints.


I presented this directly to Google. It became the design team's foundation for the sprints that followed.


A peak into the document:

Insight

Insight TO DIRECTION

direction

"Visuals feel lifeless"

Segment-specific cultural imagery: city life and social scene for entry-level candidates, localized logistics and commute context for experienced hires. Add interaction.

"It's overwhelming"

Progressive disclosure, designed to work within Brightspot's grid rather than fight it

"I want real experiences"

Day-in-the-life modules and employee voice,

"It feels intimidating"

Encouraging microcopy and qualification transparency woven into the application flow itself

Where i stepped in

Research showed candidates couldn't picture themselves at this location, so I translated that into a mid-fi exploration the design team built from.

The original page led with nine job tiles and a thin paragraph of copy. That's a directory, not a living, breathing workplace. Candidates couldn't picture themselves there.


I used Gemini and Figma Make early to explore concepts that lived outside Brightspot: campus tours, interactive commute maps, salary transparency hubs. This was a great starting point to make abstract concepts tangible enough to convey and pitch early ideas.

The Constraint

Brightspot's constraints became our creative ally.

80% had to work within Brightspot's module system. 20% could be custom-engineered. The 80/20 budget meant I had to design mid-fidelity components that worked within its module system while identifying where a custom 20% would create the most impact.


Working with Brightspot forced us to solve the problem through content, information hierarchy, and editorial choices, this made us think smarter. Working within the constraint made us more disciplined, more creative and create components that were intentional.


The custom component built directly from research.

I designed 'One Workplace. Countless Stories.' specifically to put employee voice front and center in an interactive way. Standard testimonial blocks are large, heavy, and slow to read through. Candidates scroll past them. But we needed candidates to engage with real stories, not just read about them. So this component lets users click through, interact with media, build a felt sense of what working there actually feels like.

so…Did it work?

Confidence shifted from low-to-medium to medium-to-high.

We ran 12 user acceptance testing sessions tracking three metrics:

KPI

45% increase in confidence

jumped from low-to-medium to medium-to-high—a 45% increase. Candidates left understanding the location.

23% increase for time on new page

in comparison the original. Users lingered in the "One Workplace" section longer than anywhere else.

31% rise in intent to apply

Intent to apply rose to 31% versus 12% on the original.



Intent to apply rose to 31% versus 12% on the original.

The barriers that remained—imposter syndrome, hiring anxiety—those live outside what design can solve. Knowing that boundary is part of doing honest research. We fixed what we could. We were honest about what we couldn't.

looking back

Reflection

  • Looking back, the biggest lesson was about listening. Not just to what people said, but how they were thinking underneath what they said. Candidates said "I want information." What they meant was "I want to feel like I belong here." That's two different problems.

  • Gemini got great at clustering 180 responses into patterns. But it would have missed that shift from what to why. The tool is excellent at processing volume. It's terrible at noticing the thing nobody thought to ask yet. That's still the human job.

  • Getting better at asking those questions—before diving into analysis—that's what I want to keep sharpening.

"The Employment Brand team at Google has been incredibly impressed with the thoughtfulness, expertise, and design-forward approach shown in the work for our Careers location pages. The team came to every meeting prepared and concise, asked insightful questions, and delivered exactly what we expected."

— Amy Lynam, Integrated Marketing Manager, Google