HIREQED — Arnab Roy

PROJECT / 04 · RECRUITMENT + TALENT OPERATIONS · 2024

HIREQED

A multi-role platform that carried talent from hiring into project delivery.

UX + PRODUCT DESIGN

SOURCING · INTERVIEWS · ONBOARDING · PROJECT DELIVERY

2024

RECRUITMENT + TALENT OPERATIONS

CONTEXT / WHY THE SYSTEM EXISTED

ONE TALENT ENGAGEMENT. OWNERSHIP CHANGED ACROSS ROLES.

HireQED followed the candidate beyond hiring, into project work and payment. As the engagement changed hands, each role needed different controls.

01 / ENGAGEMENT CONTINUITY

Candidate context had to survive the handoff from hiring into delivery.

SOURCING · INTERVIEW · ONBOARDING · PROJECT · REVIEW · PAYMENT

02 / ROLE-SPECIFIC OPERATIONS

What people could see and do changed, even when they were working on the same candidate and project.

CANDIDATE · CLIENT · SUPPLIER · ADMIN

DESIGN QUESTION

CANDIDATE CONTEXT NEEDED TO FOLLOW EACH HANDOFF AS OWNERSHIP AND PERMISSIONS CHANGED.

KEEP ONE CANDIDATE RECORD THROUGH THE HANDOFFS.

01 / KEEP ONE RECORD

Profile, interview state and project history stayed attached to the same candidate.

02 / CHANGE THE VIEW

Admin needed the operational history. Client views focused on evaluation and selection.

03 / CLIENT SELECTION

The same candidate context could support evaluation and selection without rebuilding the record.

DESIGN DECISION / 02 · INTERVIEW

PUT THE INTERVIEW IN ONE WORKING SPACE.

Client and candidate worked in the same coding context. The interview result still had to remain reviewable.

01 / CLIENT WORKSPACE

02 / CANDIDATE WORKSPACE

03 / INTERVIEW REPORT

The interview result still had to remain reviewable.

DESIGN DECISION / 03 · DELIVERY CONTINUITY

CARRY THE SAME ENGAGEMENT INTO PROJECT WORK.

The engagement continued after the interview. Onboarding reused the candidate and project context already established during hiring, then the same resource moved into active work.

The engagement continued after the interview.

DESIGN DECISION / 04 · FINANCIAL CONTINUITY

KEEP PAYMENT TIED TO THE SAME ENGAGEMENT.

Once project work was active, funding and payout still belonged to the same engagement. Clients added funds against the project. Candidates withdrew from the balance created by that work.

01 / FUND THE WORK

FUND THE ENGAGEMENT

Client funding stayed attached to the project relationship already used for hiring and delivery.

02 / COMPLETE THE PAYMENT

KEEP PAYMENT CONNECTED

Candidate withdrawal stayed tied to the same engagement after work was recorded.

Funding and payout still belonged to the same engagement.

OUTCOMES / REFLECTION / 04

THE SAME ENGAGEMENT CARRIED FROM HIRING INTO DELIVERY.

The engagement could move across roles without restarting at every handoff.

01 / CONTINUITY

KEEP THE ENGAGEMENT INTACT

02 / ROLE CONTEXT

CHANGE THE VIEW WITH THE JOB

03 / OPERATIONS

CONNECT HIRING TO WORK + PAYMENT

MY ROLE

UX RESEARCH INFORMATION ARCHITECTURE MULTI-ROLE WORKFLOWS INTERACTION DESIGN PRODUCT UX

REFLECTION

The product changed character after hiring. Different roles needed very different controls once work and payment entered the picture, yet the engagement still had to remain recognisable as the same piece of work.

PREVIOUS PROJECT /

TREATMENT.HOSPITAL

MEDICAL TOURISM + HEALTHCARE OPERATIONS

2024

VIEW PROJECT →

NEXT PROJECT /

MBRL DIGITAL LIBRARY

DIGITAL LIBRARY + CONTENT OPERATIONS

2025

VIEW PROJECT →