Varun OS
Case study
Appearance
ResumeContact
AadivaraProduct case study

Connecting accessible candidate journeys with event-day operations.

Aadivara supports employment events for people with disabilities. The product connects candidates, administrators, employers, partners and volunteers across mobile, web and offline-capable workflows.

Role
UI/UX Designer
Contribution
UX, interaction and UI design
Platforms
Mobile + web + offline web
Team
Crecientech + ATF
MobileCandidate

Profile, jobs and interview access

WebAadivara Admin

Events, mappings, outcomes and reporting

WebEmployer

Jobs, candidates and interview queues

WebPartner

Organisation and user management

Offline webVolunteer

Check-in, assistance and slip printing

01

Candidate access

Collect the right information without making the journey feel heavy.

Candidate registration needed personal, location, disability, skill and job-preference information. The flow was divided into understandable steps so candidates could focus on one decision at a time.

The mobile experience used clear labels, large controls, visible progress and direct confirmation. Accessibility details were treated as essential profile data, not an optional afterthought.

Design decision

Break registration into short, labelled steps with reviewable profile sections.

Why

Reduce cognitive load while still collecting information required for relevant job matching.

Accessibility

Readable hierarchy, clear labels and touch-friendly actions; shipped behaviour should be verified screen by screen.

Product evidenceCandidate registration and profile
Real mobile designs from the project. Personal information is shown only as representative interface content.
02

Admin orchestration

Turn an event into a coordinated operating system.

The Admin layer connects candidate records, employers, jobs, rooms and event outcomes. Event Coordinator is treated as an Admin permission rather than a separate primary role because no separate login was confirmed.

Event setupEmployers + jobs
Operational mappingCompanies + rooms
Event dayQueue + check-in
OutcomeSelected / Rejected
Product evidenceAdmin and employer-facing records
Real project screens. The wider room-mapping and outcome logic is documented as part of the operational model, without claiming unverified production states.
03

Employer operations

Keep job setup and interview progress clear.

Employers create and manage jobs, review candidates and progress the interview queue. The interface supports the operational difference between a candidate being interviewed and the employer waiting for the next person.

Final Selected or Rejected outcomes remain Admin-owned. This avoids blurring role ownership between interview operations and the event’s official candidate record.

Product evidenceEmployer job workflow
Real web screens showing employer job management. Queue behaviour is described from the confirmed product workflow.
04

Volunteer operations

Check-in had to continue even when connectivity did not.

Volunteers support candidates through QR or manual check-in, confirm mappings and print a compact slip for event navigation. Offline updates are queued locally and sync automatically when the connection returns.

01Scan or search

QR check-in with a manual fallback.

02Confirm candidate

Verify identity and event mapping.

03Print guidance

Generate a 58 mm or 80 mm slip.

04Sync safely

Automatic retry with visible status.

Service flow + recovery states
Designing check-in for unreliable connectivitySee how the primary, fallback and recovery paths support event-day continuity.

Portfolio reconstruction based on delivered design.

Current-state flowWhere understanding breaks
  1. 1Attempt QR scan
  2. 2Lose connectivity
  3. 3Stop check-in
  4. 4Wait or use an external workaround
Improved flowWhere the interface intervenes
  1. 1Scan QR or search manually
  2. 2Confirm locally
  3. 3Print event guidance
  4. 4Queue the update
  5. 5Sync with visible recovery status
Component variantsState coverageVisible cueUser purpose
OnlineSynced

Confirms the record is available to event operations.

OfflineSaved on device

Lets the volunteer continue without losing the check-in.

PendingWaiting to sync

Makes unfinished system work visible.

ConflictReview required

Prevents a local update from silently overwriting a newer record.

RecoveredSync complete

Closes the loop when connectivity returns.

Product evidenceVolunteer offline flow
Real design board showing the offline-capable volunteer journey and printed-slip workflow.
05

System layer

Partner management supports the network behind the event.

Product evidencePartner organisation management
Real web screens showing employee and sub-organisation management.
What was delivered

A connected multi-role product model

The work established mobile and web experiences across candidate access, job management, partner administration and volunteer event operations.

What I would improve next

Validate accessibility and offline recovery in the field

I would run screen-reader, keyboard and event-day usability testing, then measure completion, check-in time, sync failures and manual recovery.

Outcome boundary

No adoption or efficiency metrics were available for this case study. The portfolio separates delivered design work from the improvements that should be measured next.