Redesigning the Job Board

Rethinking search for Built In’s new national platform.

Remote work changed how tech professionals look for jobs. In 2021, Built In launched a national board for remote roles alongside its nine city sites for on-site and hybrid opportunities. Search now had to serve job seekers anywhere in the US, most of them not signed in, and help them find the right role faster and apply more often

PROJECT DETAILS

Role: Designer & Project Manager
Team: 2 UX Designers, VP of Product, Lead PM, Sr. Vue Engineer, Director of SEO and 2 supporting engineers
Timeline: Continuous releases & iteration over 6 months
Platform: Web, responsive

CHALLENGE

Most visitors searched without signing in, so Built In knew nothing about them: no profile, preferences or saved searches. Search had to do all the work, but it still assumed a city-first job hunt, with remote options buried and filters that didn’t match how people actually looked. Many skipped location entirely, and too few searches led to job views and applications.

GOALS

Candidates: Find the right role faster with “What” and “Where” search, autocomplete and suggestions

Business: Increase job views, applications and sign-ups for personalized job alerts

Platform: Rebuild filters around user feedback and real search behavior, with remote roles front and center

The original Job Board search & filter experience

Pain Points

  • Difficulty finding the Industry filter — users must scroll through a long, unprioritized list of industries, making it time-consuming to locate the right option.

  • Confusing Remote work filters — users interpret “Remote + In-Office” as “Hybrid,” leading to incorrect filtering and unmet expectations in results.

  • Limited results for Entry-Level roles — users report that entry-level searches return too few jobs, and experience groupings feel arbitrary and unclear.

  • Filters dominate the screen — the filter panel takes up a large portion of the viewport, especially when industries and subcategories are expanded, reducing visibility of results.

  • Keyword search is hard to discover — users often don’t notice the keyword search in the UI, but those who do find it report significantly more relevant results.

  • Lack of result count visibility — users can’t see how many jobs match their filters or understand why applying filters results in very few (or zero) listings.

  • Inability to select multiple job categories — users are forced to choose a single category, limiting flexibility and making it harder to find roles that span disciplines.

  • Confusing mobile search experience — the mobile search landing page makes it difficult for users to find keyword search and filters, leading to drop-off and ineffective searches.

Data Driven Decisions

Hypothesis

Job Search metrics are best when both the Keyword Search and Filters are used.

Ideation + Testing

Concept #1

‘What’ and ‘Where’ inputs plus all Job and Category filters present on landing.

DESKTOP PROTOTYPE
MOBILE PROTOTYPE

Concept #2

Job Type, Location and Remote options are prioritized first with all filters located in a scrollable right-hand-rail.

DESKTOP PROTOTYPE
MOBILE PROTOTYPE

Concept #3

‘Dream Job’, Location and Remote options prioritized with only the most popular filters on landing. Additional filters are hidden behind an All Filters button.

DESKTOP PROTOTYPE
MOBILE PROTOTYPE

Bootstrap Designs + Reusable Components

Job Board Mobile Screens (3)

ROLE: User Research | Competitive Analysis | Prototyping | User Testing | Ux & Ui | QA
COLLABORATORS: Anna-mi Widman, Jeff Hurd, Sam Daley, Ryan Batten, Courtney Lopez, & Trent Victor

Next
Next

BPTW