Anastasiya Fedarava

Open to senior product roles

Selected work / 02

Work Saudiالعمل بالسعودية

A national employment platform for people who come to Saudi Arabia to work — in English and in Arabic, from the first sign-up to a signed contract.

Role
Lead DesignerResearch to interface; leading a second designer
Team
15+ specialistsStakeholders, analysts, engineers, project management
Time
2024 — 2025About ten months, discovery to delivery
Users
Four rolesJob seekers, employers, recruitment agencies, administrators
Languages
English · ArabicLeft-to-right and right-to-left
Status
LaunchedFor users in selected markets

Eight steps, and half of them wait on someone else.

Why this matters

Job seekers don’t search for jobs here: employers and agencies find them. So most of the path is waiting — for a check, a skills test, an interview request, an offer. If the interface hides that, the system feels arbitrary.

  1. 01RegisterJob seeker
  2. 02Verify identityExternal checks
  3. 03Skills testTest centre at home · some trades
  4. 04Build the CVJob seeker
  5. 05Interview requestEmployer or agency finds you
  6. 06InterviewsOne or more rounds · video call
  7. 07OfferAccept · ask for changes · decline
  8. 08ContractApprovals, then work

In the person’s handsWaits on someone else

Simplified for illustration; the real process has more branches and actors.

Travellers with luggage crossing a sunlit terminal.

Four roles, one system.

Before designing any portal, I mapped who touches what — so a contract means the same thing to everyone who handles it.

CVInterviewOfferContract

Reading the system before redrawing it.

I led most of the discovery: the existing product, the rules behind it, and the people responsible for both.

  1. 01Review of the existing system
  2. 02Heuristic evaluation
  3. 03Accessibility analysis
  4. 04Stakeholder interviews
  5. 05Workshops & critiques
  6. 06Jobs to be done
  7. 07Legal & domain research
  8. 08Comparable platforms
  1. 1Where do people lose track of where they stand?
  2. 2Which steps depend on something outside their control?
  3. 3Where does the interface speak regulation instead of the task?
  4. 4What breaks — or turns ambiguous — in right-to-left?
  5. 5Which patterns fail accessibility?
Jobs to be done, by role

Job seeker. When I’m waiting to be found by an employer abroad, I want to know my CV is complete and visible, and what is still missing, so the right offer can reach me.

Employer. When I hire, I want to find verified candidates and see where each interview and offer stands, so I can plan without chasing updates.

Administrator. When I review a case, I want what I need in one place, so decisions are consistent and quick.

Illustrative job statements in the form we used — not quotes from research.

Access, verification and visibility are different questions.

One gateEverything waits behind “verified”. You are in, nothing works, and nobody says why.

Three layersEach question gets its own state, so the product can always say what you can do now, what is pending, and what unlocks next.

AccessCan I get in?

  1. Account created
  2. Signed in

VerificationAre my identity and skills confirmed?

  1. Submitted
  2. In review
  3. Verified

VisibilityCan employers reach me?

  1. Visible to employers
  2. Interview requests
  3. Offers

The model and its reasoning — not a claim about every detail of the production system.

Designing for the time in between.

Checks take days and happen elsewhere. The product has to stay useful, and honest, while people wait.

  1. 01Show where you stand

    A clear state for every pending check — not a spinner and a hope.

  2. 02Offer what is possible now

    Finish the CV, book the skills test, prepare documents while checks run.

  3. 03Say what happens next

    Who is acting, what they need, and how you will hear about it.

  4. 04Make problems recoverable

    If something is missing or rejected, say what and how to fix it — in your language.

06Two directions

One product, read from both sides.

  1. Mirror the flowNavigation, progress and the direction of “next” follow the reading.
  2. Keep meaning stillNumbers, IDs, media controls and logos keep their orientation.
  3. Expect mixed textNames and IDs inside Arabic sentences need careful bidirectional handling.
  4. Respect each scriptArabic gets its own sizes and line heights, not a scaled copy of the Latin.

Status as content.

Every state answers three questions: what is happening, who is acting, and what you can do now.

01 Employer · agency

Finding people, not filtering forms.

Verified identity and skills read at a glance; one action that matters — request an interview.

02 Job seeker

Interviews, round by round.

A request to answer, the next round with both time zones, and the call one tap away — on the video platform the employer uses.

03 Job seeker

An offer that explains itself.

The offer leads, with its deadline and three clear answers: accept, ask for changes, decline. Everything else is history, quietly.

04 Administrator

A case on one page.

Identity, documents, experience and contracts in the order a reviewer checks them — so decisions are consistent.

05 Administrator

Thousands of organisations, scannable.

Filters as chips, statuses that read at a glance, and the next action one click away.

06 Everyone

A calm first step.

One task per screen, both languages from the first moment.

Reconstructions made for this portfolio: own layouts and fictional data; the platform’s logo is used with the project’s branding.

  1. 01

    Map the ecosystem before designing portals.

    Why, and what it cost
    Why
    Each role came with its own requirements, and it was tempting to design each portal alone. Mapping roles, shared objects and workflows first gave design, analysis and engineering one model to argue about.
    Trade-off
    Slower first weeks, before any screen existed.
  2. 02

    Treat states as product content.

    Why, and what it cost
    Why
    Statuses were defined by the back office, not by what a person needs to know. Every state got three answers: what is happening, who is acting, what you can do now.
    Trade-off
    More states to define and maintain — for fewer dead ends.
  3. 03

    Keep compliance, lose the coldness.

    Why, and what it cost
    Why
    Regulation is not optional, but legal language and rigid gates make people feel rejected. Every required step stayed — explained in the language of the task, with progress through it.
    Trade-off
    Copy had to be negotiated line by line with the people who own the policy.

Most of the work happened in conversation.

  1. Kanban, shared with engineering

    Design moved on the same board as the build, so decisions arrived when they were needed.

  2. Demos to stakeholders, often

    The people who own the policy saw working designs regularly, which kept decisions grounded.

  3. Analysts and engineers as co-authors

    Requirements, edge cases and feasibility were worked out together, not handed over.

  4. Leading a second designer

    Dividing the work, keeping one system, running the critiques.

Construction workers on a site at sunset.

What changed — and what I can say.

Not every planned capability reached production, and the platform is not launched globally. Usage figures are not mine to share.

Next case

Eir

A family-health platform, shaped from a raw idea into a product.