Designing an On-Site Job Application & Safety Assessment Platform

I designed and built an internal hiring system for a venture capital firm’s portfolio companies, where frontline roles see constant foot traffic. I wanted walk-in candidates to have a simple, fast way to apply on-site, so I created a streamlined application flow and incorporated a required safety quiz.

UI/UX Product Design Tablet App
Olliboard welcome screen with bilingual toggle and primary calls to action

Project Brief

Olliboard is a bilingual kiosk application that helps staffing branches onboard walk-in candidates for warehouse, manufacturing, and general labor roles. The previous process relied on paper forms and heavy recruiter assistance, which often resulted in incomplete applications and long wait times.

My goal was to redesign the end-to-end flow so candidates could complete onboarding independently, while recruiters received complete, consistent information they could use to place people quickly.

Team & Role

I worked as the sole product designer, collaborating with branch managers, recruiters, and operations leadership. I led discovery, user interviews, personas, user flows, interaction design, and visual design for the kiosk experience.

Customers & Personas

The experience had to work for both candidates and recruiters:

  • Candidates with different levels of digital literacy and English proficiency
  • Recruiters who needed reliable, structured applications to meet hiring targets
Persona card for Ethan, tech-forward branch manager Persona card for John, mobile-first construction worker Persona card for Bill, older Spanish-speaking worker Persona card for Javier, bilingual forklift driver

These personas kept the design grounded in real constraints: bilingual copy, large touch targets, short questions, and clear progress so candidates always knew what was next.

Solution at a Glance

I restructured the intake into a linear, kiosk-friendly flow:

  1. Welcome & language selection
  2. Sign-in / account creation
  3. Branch location selection
  4. Personal information
  5. Education
  6. Availability
  7. Previous experience & skills
  8. Safety video & quiz
  9. Outcome screen: pass or retry
New candidate sign-in screen with email and password fields
Location selection screen listing available branches Location selection screen with a branch highlighted
Personal information step with name and address fields
Education step capturing school, degree, and dates
Availability step with industry, schedule, and hours questions
Previous experience step asking if the candidate has prior work history Previous experience form filled in with skills and job details

During testing, candidates often stalled on work history. To reduce anxiety, I added a clear branch for “no previous experience” and shifted emphasis from long descriptions to selecting skills and short blurbs instead.

Safety training video screen with large inline player
Scenario-based safety quiz with multiple-choice questions

The quiz checks basic safety judgment before candidates are placed on-site. Questions were written at an accessible reading level in both English and Spanish to support a broad range of applicants.

Success screen with celebratory message for passing the safety quiz Retry screen with gentle language encouraging candidates to retake the quiz

Early prototypes used more transactional language, and candidates who failed once were less likely to continue. Introducing a supportive retry state helped people feel comfortable trying again.

Impact

  • Reduced time recruiters spent walking candidates through basic forms
  • More complete and consistent applications across branches
  • Clear, standardized record of safety training completion
  • More independent, less intimidating onboarding experience for candidates

Some Ideas I had for improving Olliboard

  • Add analytics to measure drop-off by step and language.
  • Extend the flow to mobile so candidates can start before arriving on-site.
  • Design a recruiter dashboard that surfaces candidate readiness at a glance, but this wasn't in scope.