Back to Work Growth

Workhuman Careers Refresh

97% of candidates left the careers site without exploring a single job. A three-layer information architecture rebuilt the funnel from the ground up.

Role Lead Product Designer
Timeline 2024 – 2025
Platform Web (Desktop + Mobile Responsive)
Team Marketing · HR/Recruiting · Engineering · Content Strategy
Methods Competitive Analysis · Stakeholder Interviews · Analytics Review · Content Strategy · IA · User Journey Mapping · A/B Testing

Nearly 2 in 3 candidates now explore job listings

Measured post-launch via HEAP Analytics. The funnel that was losing 97% of visitors now converts the majority of them.

64.6%
Homepage → Job Listing CVR
Up from 2.7% · sustained over 3 months
Validated via HEAP Analytics across US, Canada, Ireland, and UK regions.
↓59%
Exit Rate
69.5% → 28.7%
↓41%
Bounce Rate
32.9% → 19.4%
↑28%
Time on Page
50s → 64s
13.1%
Job Browse Bounce Rate
Candidates self-selecting effectively
Original careers homepage — generic team grid with no narrative
Redesigned careers homepage — culture-first storytelling with clear path to roles

The Business Challenge

Workhuman's careers experience was a thin layer over Workday (ATS). Candidates landed, clicked a job, and immediately left for Workday — giving Marketing zero tracking data.

Conversion Blockage

2.7% CVR = Massive Leakage

Only 3 out of 100 candidates viewing the careers homepage clicked through to browse job listings.

  • No culture context provided
  • Competing on job titles alone
  • Lost storytelling opportunity
  • Marketing couldn't track journeys
Poor Engagement

33.8% Bounce Rate

Candidates weren't finding value in the content and left immediately.

  • Insufficient candidate context
  • Lower-quality applications
  • Poor cultural fit matches
  • More recruiter time screening
Attribution Gap

No Attribution Data

Marketing couldn't prove ROI on recruiting campaigns.

  • Can't attribute applications to campaigns
  • Can't measure content effectiveness
  • Can't justify recruiting budget

The analytics told a pretty clear story: average session was 2 minutes, candidates viewed 1 job, and 85% clicked Apply and immediately left for Workday. They were using the site like a job board, not an employer brand experience. All the culture content that existed — team pages, benefits, values, awards — was completely invisible to someone who landed and just wanted to see what was open.

Understanding the Opportunity

Four research activities — and the one that surprised me most was the content audit.

1. Competitive Analysis

10+ Leading Tech Companies

Evaluated Canva, Salesforce, Figma, Lattice, Notion, Shopify, Stripe, Intercom, HubSpot, Atlassian across 3 dimensions: careers overview pages, job search/browse experiences, and job detail pages.

Key patterns identified:

  • Rich media for culture storytelling
  • Clear navigation to sub-categories
  • Filtering by location/department as baseline
  • Best experiences keep candidates on-site longer
2. Stakeholder Interviews

7 Stakeholders Across Functions

Marketing (3): Need attribution data. Recruiting (2): Want qualified candidates. HR (2): Benefits/culture accuracy.

Key insights:

  • "We have no idea what content drives applications."
  • "Candidates ask the same questions in the first interview."
  • "Benefits differ by region — we need flexibility."
3. Analytics Review

Existing Traffic Data

  • Avg time-on-site: 2 minutes
  • Bounce rate: 32.9%
  • Jobs viewed per session: 1.0
  • Apply click-rate: 85% (then immediate exit)

Translation: Candidates treat us like a job board, not an employer brand experience.

4. Content Audit

Hidden Assets Identified

  • 10 distinct teams with unique cultures
  • 4 regional benefit structures
  • 2 office locations
  • 5 cultural programs
  • Company values and awards

All this content existed but wasn't accessible to candidates during job search.

What I actually came away with

01

The homepage wasn't doing its job

A 2.7% CVR means candidates landed and left immediately — they had no reason to stay. The site was asking people to browse jobs before giving them any reason to want to work there. The homepage needed to answer "why Workhuman?" before it asked anyone to look at listings.

02

Candidates need different things at different moments

Someone who just heard of Workhuman has different questions than someone evaluating a specific role. Trying to serve both on the same page was part of why the original site failed. Three layers ended up feeling right: one to build interest, one to browse, one to evaluate.

03

Tabs work because candidates care about different things

The competitive audit showed Canva and Figma both using tabs on job detail pages. It clicked — candidates don't read a job posting top to bottom. Some care about the team, some about benefits, some about where they'd be working. Tabs let them go straight to what matters to them.

04

People find better jobs by wandering

The analytics showed candidates only viewed 1 job per session on average. But from the stakeholder interviews, recruiting knew that their best hires often came in for one role and ended up in a different one. The site wasn't giving people a way to wander — so they didn't.

Three-Layer Progressive Engagement System

Three pages, each with a specific job to do.

Layer 1
Careers Homepage
"Why Workhuman?"
Culture · Teams · Benefits · Values · Awards · Locations

Goal: Drive CVR from 2.7% to 40%+. Build interest before job browse.
→ 64.6% CVR achieved
Layer 2
Open Positions
"What roles are available?"
Browse · Filter · Search · Color-coded department tags

Smart filters by location, department, and role type. Stay on Workhuman.com.
→ 13.1% bounce rate (exceptional)
Layer 3
Job Detail Page
"Is this specific role for me?"
5-Tab System: Role · Team · Culture · Benefits · Location
Right Rail: "Recommended Jobs" (persistent across all tabs)

Full context before the Apply click.
→ 3–4 jobs explored per session

Layer 1 — Careers Homepage

Culture storytelling before the job browse. Before: a generic team grid with no narrative. After: compelling headline, employee video, and a clear path to explore roles.

Before — generic team grid with no narrative or culture context
After — culture-first storytelling with compelling headline and clear path to roles

Layer 2 — Browse & Filter

Color-coded departments, optional filters, and persistent breadcrumb navigation. Designed for both explorers ("just looking") and targeted searchers ("I want Product roles in Dublin").

Job browse page — filter by location, department, and role type with color-coded tags
Job browse detail — expanded job card with preview and department context

Layer 3 — Job Detail + Recommendations

The 5-tab system gives candidates exactly the information they need — when they need it. The right rail keeps additional roles visible without interrupting the current read.

Job detail page — 5-tab system: Role, Team, Culture, Benefits, Location
Recommendations rail — Candidates Also Viewed, driving 3-4 jobs explored per session

The 13.1% bounce rate on the job browse page was the number I was most glad to see. Low bounce there meant candidates were actually engaged — not just landing and leaving. The homepage wasn't pushing unqualified people into the funnel. It was giving interested people a reason to go deeper.

Benefits Tab — Localized at Scale

4 regional variants (US, Canada, Ireland, UK) built from one flexible component system. Adding a new region requires updating content only — no design or engineering work.

Benefits tab — localized content with regional variants for US, Canada, Ireland, UK
Benefits cards — flexible component system for regional benefit structures

Reusable Patterns

Every component built for this project was designed to be reused. Several have since been adopted across other parts of the site.

Job listing card component — reusable pattern with department color-coding and role metadata
Tab-Group Pattern

Used across 3 product areas

Job details, team pages, office location pages. Horizontal on desktop, dropdown on mobile. Now part of the main design system.

Recommendation Module

"Candidates Also Viewed"

3-item persistent rail, same-department logic, opens in new tab to preserve context. Pattern adopted site-wide after launch.

Department Tag System

10 teams, color-coded

Used across job cards, team pages, and navigation. Instant visual scanning reduces cognitive load during browsing.

Measuring Success — Real Data

HEAP Analytics data, October–December 2025. Not a spike — November outperformed October.

Candidates
  • Context to self-select before applying — cultural fit, team, benefits, location all visible before the Apply click
  • Browsing multiple roles increased naturally via Recommended Jobs rail
  • 13.1% bounce on job browse = candidates are engaged, not lost
Recruiting
  • Better-informed applicants arriving with realistic expectations
  • Candidates self-selecting on culture before the first screen call
  • Regional content (US/Canada/Ireland/UK benefits) accurate per location
Marketing
  • Full candidate journey now trackable for the first time
  • Campaign attribution now measurable (previously zero visibility)
  • Tab system allows A/B testing individual content sections

What worked, what I'd do differently

What Worked
  • Three-layer architecture mapped cleanly to the candidate journey — each layer had one job
  • The "Candidates Also Viewed" rail drove 3–4x more jobs explored per session and got adopted site-wide
  • Cross-functional buy-in held because every stakeholder got something: Marketing got attribution, Recruiting got quality, Engineering got a clean integration pattern
What I'd Do Differently
  • Involve the content team earlier — content creation was the longest part of delivery, and I could have unblocked it faster
  • Test the tab order rather than assuming Role Description should be first — that was an assumption I'd want data on
  • Mobile tab navigation was less discoverable than desktop; I'd invest more in the mobile-specific pattern

Next Case Study

Aegis Group

Strategic pivot from consumer meditation to healthcare workforce wellness

View Case Study All Work