MOBILE RECRUITMENT, IOS & ANDROID NATIVE APP
EXPERIENCE DESIGNER
2020 - 2022
Robert Half's temporary workers faced a visibility problem: the app would reject timesheets without saying which category was wrong, turning every correction into guesswork. Meanwhile, worker profiles functioned as static forms rather than evolving records — skills and experience sat disconnected, making it harder to surface the right candidates for new assignments.
How can we help people get through complex insurance forms as
smoothly and as confidently as possible?
I joined the project after the MVP had shipped — brought in through Bottle Rocket as the systems and UI designer on a two-person UX team. The product strategy was set. The problems were known. My job was making the solutions feel native to iOS and buildable without constant revision. That meant designing the component library, spec'ing every interaction state, and ensuring the visual language could scale beyond these two features.
The team redesigned the mobile experience around a simple idea: status should be specific, not vague. I owned the UI layer: the color system that made status readable at a glance, the component specs that kept it consistent across screens, the interaction patterns that made it feel native. Instead of "Returned" or "Pending," we built a color-coded system that showed exactly which category of time was in which state. Worked hours could be awaiting approval while sick time was already returned, and the card on the home screen showed both at once.
I designed the status color palette and defined the states. Returned got a specific red, awaiting approval got orange, approved got green. Each color had to work on white cards, pass accessibility contrast ratios, and still feel distinct when stacked in the same view. The modals and context menus came with full interaction specs: long-press reveals quick actions, tap opens the breakdown, swipe dismisses. Spacing values, transition timing, touch target sizes, all of it went into the Sketch library so the dev team could build it once and reuse it.
