mudit.
OccuSearch
/22-23
Forms speak in codes
Australian visa forms expect ANZSCO (official job code) and CRICOS (official course ID)-not everyday titles.
Even with the right code, applicants still have to research-across many sites-which Australian states/territories have employment opportunities for their occupation and how the job market is trending (rising, steady, or slowing), plus what it will cost to get started (fees and required funds).
Small mismatches or out‑of‑date info waste weeks and drain confidence.
Here’s what the old process looked like before OccuSearch.
What OccuSearch lets you do
OccuSearch is a mobile companion for planning an Australian move. Search in everyday words, then see the exact IDs forms accept - ANZSCO for jobs, CRICOS for courses - alongside the context people actually need: where employment opportunities are stronger, how the job market is trending, your score, fees & required funds, and tools to save, compare, and actANZSCO = official job code · CRICOS = official course ID.
How we turn codes into decisions
One path. From a plain title to a confident next step.
How I shipped it
I led research → IA → flows → UI kit → prototype → QA with PM/Eng/QA.
Mapped the mess: I reviewed internal feedback, interviewed applicants, and walked real migration scenarios to find confidence drop‑offs and abandon points.
Shaped the IA (with PM/Eng/QA): I reduced steps and used progressive disclosure so the right information appears at the right time; IA choices were co‑designed with PM, engineers, and QA to match data and rules constraints.
Embedded tools (stakeholder ask → product pattern): Stakeholders wanted these calculators in‑app; I shaped that into a first‑mile Tools hub—above‑the‑fold placement, grouping, verb‑first labels, and consistent interactions across Points, Visa fees, Funds/Living costs, VEVO.
Microcopy & trust: I wrote verb‑first labels and added Source / Last updated where decisions happen.
Partnered to ship: I worked with engineering, content, and QA to align on source cadence and harden empty/offline/error states.
Design Decisions
1) Home as a self‑serve tools hub (first‑mile design)
Problem: People bounced to agents or websites for routine checks. Time to first action was high.
What I shaped (from a stakeholder ask): Stakeholders wanted calculators. I turned that into an above-the-fold Tools hub with equal cards, verb-first labels, and Search + Recents/Bookmarks in view so returners resume instantly.
Trade-off: Denser home. Solved with grouping and short, consistent labels.
Risk and mitigation: Home density risk. Grouped Tools block, concise verbs, promos moved below the fold.
2) Occupation detail IA for focus, built for ANZSCO ⇄ CRICOS parity
Problem: Official sources dump everything; many users don’t know ANZSCO codes.
What we designed together (PM/Eng/QA + me): Search uses titles first and shows ANZSCO for confidence. The detail page uses scrollable tabs (Eligibility, EOI statistics, Labour insight, Unit group, General). In State eligibility, users see state tiles/chips first; tapping expands rules. The same skeleton scales to CRICOS courses so course↔occupation feels native.
Trade‑off: One extra tap for depth; paid back by clarity and reusable IA (co‑validated with PM/Eng/QA).
Risk & mitigation: Extra taps → Tabs + expand keep focus; parity with CRICOS reduces relearn cost and speeds delivery.
3) Funds = two calculators, one plan (coachmark → living costs → merged view)
Problem: People mixed what I must show (visa requirement) with what life will cost (lifestyle), causing confusion and rework.
What I changed: After the visa funds estimate, a non‑blocking coachmark invites Living costs. Living costs is a 6‑step path (City → Area → Accommodation → Transport → Food → Utilities) with realistic ranges and a running monthly total. A merged view then compares Funds to show (visa) vs 12‑month living and totals a First‑year outlay (est.) with small badges like Meets guidance / Below by A$ ….
Trade‑off: More states to maintain; capped coachmark frequency and prefetched assets to keep it fast.
Risk & mitigation: More states → Frequency cap + asset prefetch; unified comparison card to avoid conflating numbers.
One app, every answer.
OccuSearch delivers a guided, all-in-one experience that replaces multiple disconnected tools. Users can search occupations in plain language, see visa requirements and state demand in context, and use built-in tools like the Visa Fee Estimator, Fund Calculator, Points Test Calculator, and VEVO Check, without leaving the app.
Real-time updates ensure accuracy, while the design focuses on clarity, speed, and trust, helping users make decisions without cognitive overload.
Outcome
Post‑launch (2022–2023): 4.5★+ rating, 88% task completion on guided flows, and fewer drop‑offs. Feedback called out simplicity, accuracy, and speed vs the old process.
Definition: Task completion = a user finished a guided flow (e.g., Points, Fees, Funds, VEVO) from first step to result screen.
Credits & attribution
Design: Solo Product Designer (me).
Stakeholder input: Calculators were a business requirement; I shaped them into the first‑mile Tools hub (placement, grouping, labels, interaction patterns).
Information architecture: Co‑designed with PM/Engineering/QA to reflect data, policy rules, and technical constraints; I led the interaction model, flows, and on‑screen copy.
Data freshness & content ops: Engineering/content teams managed update cadence and validations.
This work was created at a previous employer. Content is adapted for portfolio use; sensitive details are modified to respect confidentiality.