Make progress legible.
Onboarding and document requirements organise the candidate’s contribution into concrete steps, with attention to what is relevant at the current stage.
A coordinated hiring experience
Profiles, evidence and people brought into a shared process. A complex product, designed around what needs to happen next.
Inside the product ↓
01 / Designing for coordination
A hiring journey involves more than a profile and a vacancy. Documents need review, information changes, requirements must be understood and responsibility moves between people.
Inquos brings job seekers, employers and recruitment partners into a coordinated network. AMUI’s work spans the public website and the product interfaces, connecting the candidate’s journey to the operational work behind it.
The guiding design question is practical: what does this person need to understand or do now?
02 / Making the work understandable
The candidate workspace connects submitted information, supporting documents and readiness. Explore three decisions behind that experience.
A submitted profile remains a record of what the candidate declared. Later changes can be understood in context, giving operators a consistent starting point for review.
Interactive case-study illustration of the product’s review logic. Example states; no personal records.
Onboarding and document requirements organise the candidate’s contribution into concrete steps, with attention to what is relevant at the current stage.
Dedicated workspace views connect the submitted profile, documents and readiness requirements so the operator can review them in context.
Readiness blockers carry an owner and an action. The product can distinguish work for the candidate from work for the operator.
03 / Engineering the experience
Useful product design depends on the meaning of the information it presents. Inquos preserves submitted profiles, associates reviews with their evidence and separates document processing from verification.
These decisions shape the interface. An operator can distinguish a declaration from a later change. A document can be shown as awaiting review without suggesting that it has already been verified.
AMUI connects this application logic to the visual experience: clear states, organised workspace views and explanations that make the available next action understandable.
“Preparation continues” becomes useful when the interface also identifies the outstanding requirement and the person responsible. This connection between state, action and ownership is central to the product’s design.
Submitted information is retained as a record, giving later reviews a consistent basis.
Processing, review and verification carry different meanings in the document experience.
Readiness requirements connect evidence and unresolved questions to the next permitted step.
04 / A clear first impression
The public website introduces the platform through distinct entry points for individuals, employers and recruitment partners. Clear typography and lightly coloured cards organise the choices before visitors enter the product.
What this work demonstrates
Inquos demonstrates AMUI’s ability to work across interface design and application development: organising complex requirements into connected experiences, with evidence, responsibility and next actions built into the product.
Explore web applications ↗