Background
Agentic job search is unfamiliar UX: users wait while an agent browses career sites, then judge ranked results they did not type keyword-by-keyword. Your design must build trust, show progress, and make "save to tracker" obvious.
Your mission
Design search results and job detail views for an agentic job finder (BoardingPass-style). Cover the full journey from query to saved application.
Required views
Search flow
- Search entry — company/career-site picker, role keywords, optional location.
- In-progress — agent running state with progress, sites scanned, cancel option.
- Results list — ranked cards with match chips (skills, location, role fit), skeleton loading for slow cards.
- Filters — company, remote/hybrid, date posted, match score threshold.
- Empty/error — no results, agent timeout, one site failed (partial results).
Job detail
- Detail panel/page — title, company, location, salary if known, match breakdown, source link.
- Save to tracker — primary CTA with confirmation state.
Requirements
- Desktop (1440px) and mobile (375px) for results + detail.
- Interactive prototype — happy path: search → results → detail → save.
- Match chips — show why a job ranked (3 factors max per card).
- Skeleton loading — for results fetching; no spinner-only design.
- Accessibility — list semantics, focus management when opening detail drawer/modal.
Evaluation criteria
- Trust — agent progress feels honest; partial failure handled gracefully.
- Scannability — user can compare 10 cards in under 30 seconds.
- Action clarity — save/bookmark visible without opening detail.
- Visual polish — consistent spacing, realistic job copy, company logos placeholder pattern.
Tips
- Study BoardingPass
/jobs if you have access; differentiate or improve explicitly in notes.
- Drawer detail on desktop + full-page on mobile is a common pattern.
- Include one "low match but interesting" card to show nuance.
Submission checklist
