Diam's Avatar

Diam Kanbier

Digital Designer

Welcome, visitor
0

Currently Open to Work

diam96@gmail.com

LinkedIn logo
Back icon Back to tiles

Employee Journey

Improving the usability of the digital job application process for Financieelsysteem B.V.

Tools used: Figma, Miro, user interviews

Problem

Financieelsysteem B.V. had no real way for candidates to apply. The careers page was confusing, there was no apply button, and applications came in by generic email; resulting in zero clarity or conversion.

Research & Insights

  • Effectiveness: No apply button means candidates can't complete their goal.
  • Efficiency: Absence of search and filters forces users to scroll every listing.
  • Aesthetics: Minimal styling gave an unprofessional first impression.
  • Error Tolerance: No validation or confirmation leaves users unsure if they applied.
  • Ease of Learning: Buzzword heavy listings confuses users.

Process Highlights

  1. Current State Audit: Stakeholder interviews and a 5 E usability walkthrough exposed a critical gap: vacancies were listed, but candidates had no way to apply online.
  2. Journey Mapping & Competitive Scan: Translated the internal employee journey into a candidate centric flow and benchmarked it against other fintech and Dutch corporate career sites to surface best practices and pain points.
  3. Iterative Prototyping: Three sprint cycles evolved low-fi wireframes into a hi-fi prototype with search & filter, a “Find your team” explorer, and a four-step application timeline.
Diagram of the candidate journey stages
Journey map showing key candidate steps and pain points.
Wireframe of the careers landing page
Landing page prototype with company values and clear call to action.
Prototype of the vacancy listing page
Vacancy page with filter bar and prominent apply button.

What I Learned & Next Steps

  • Agree on core requirements up front to avoid scope creep.
  • Protect dedicated design time so research doesn't overshadow prototyping.
  • Use more and better expert reviews to catch usability issues early.
  • Next steps: build error states, mobile responsiveness, and better interactions.

View full prototype →