Skip to main content
PARIS, FRANCE
CV
CASE 05
Application pipeline workspaceLIVE PRODUCT
CASE 05

Alternance
Tracker

An apprenticeship search becomes a decision space, not a collection of tabs.

Alternance Tracker gives a durable shape to a search that would otherwise scatter across job posts, messages, dates and notes. Every application gets a readable state and a clear next move.

Alternance Tracker dashboard
NATURE
DEPLOYED FRONTEND PRODUCT
ROLE
PRODUCT + FRONTEND
AUDIENCE
JOB SEEKERS
SCOPE
BROWSER-SIDE CRUD
01 / THE FRICTION

An application is not a row. It is context that keeps moving.

A job post found, an application sent, a follow-up to plan, an interview coming up: the risk is not lacking information, but no longer knowing which one deserves action now.

TABS

The job post disappears once closed.

DATES

A follow-up is easily forgotten.

NOTES

Context lives away from the application.

THE NEEDONE VIEW THAT KEEPS THE THREAD.
02 / THE STATE MODEL

A clear state makes the next move obvious.

The pipeline does not imitate a CRM. It condenses the real rhythm of a search into six states, each precise enough to describe a situation without forcing the person into a rigid process.

  1. 01

    To apply

  2. 02

    Sent

  3. 03

    Follow-up

  4. 04

    Interview

  5. 05

    Rejected

  6. 06

    Accepted

03 / THE OVERVIEW

The cockpit answers one question: where am I now?

The overview separates active work from final outcomes. The counters are not decorative: they make it possible to see at a glance what needs a decision, a follow-up or preparation.

Overview: seven counters, an active state and a readable positive rate.
ACTIVE OVERVIEW
04 / THE WORKSPACE

Details stay within reach.

Capture, instant search, status filtering and editing live in the same workspace. Finding an application does not require switching tools or rebuilding mental context.

One workspace to add, filter, find and update.
CAPTURE + PIPELINE
05 / THE LOCAL LOOP

A local first product, complete on its essential loop.

The technical choice stays deliberately simple: everything happens in the browser to validate the end-to-end flow before adding infrastructure that does not yet solve a proven need.

  1. 01FORM

    An application becomes structured data.

  2. 02DOM EVENTS

    Create, edit, delete and filter.

  3. 03LOCALSTORAGE

    The search retains its memory.

  4. 04SYNCED RENDER

    Table and statistics update together.

WHAT THIS PROJECT DEMONSTRATES

What this product proves.

I can start with daily disorder, select the states that matter and build a usable loop all the way to local persistence.

01 / MODEL

Turn a moving journey into states that stay understandable.

02 / PRIORITIZE

Surface the next action without making the view noisy.

03 / SHIP

Design the flow, CRUD, filters and responsive behavior.