Ahmad Habbab

Home › Projects › CVT: portfolio & résumé builder

CVT: portfolio & résumé builder

Four scattered files, one link.

Job-seekers send a Word CV, a Behance link and a cover letter separately, and the three never quite agree. I designed CVT to keep all of them in one account behind one public link: about 29 screens, in 2021.

Client
Founder-led startup
Role
Sole UI/UX designer, design system
Scope
Web app and responsive public profile, ~29 screens
Status
Handoff-ready

No single link to send.

A new graduate has a CV in Word, work spread across Behance and Drive, and a cover letter written at midnight. When a recruiter asks for 'a link to your work', there isn't one.

A graduate, and the recruiter.

Job-seekers who want to look professional, and recruiters who need to judge someone in ten seconds, usually on a phone.

Enter it once, use it everywhere.

Portfolio, CV and cover letter live side by side in one account and stay in sync. The cover letter starts as a ready draft with blanks to fill, not an empty page. The public profile works on any phone.

Open on who's seeing you.

The app opens on profile views and where visitors come from, not an editor. Building a CV is a one-time chore; watching your work get seen is a reason to come back.

What the product is built around.

Three ideas that decided most of the screens.

One account for all of it

Portfolio, CV and cover letter sit side by side under one profile, entered once and always in sync.

Start the letter at sixty percent

The cover letter opens as a ready draft with labelled blanks instead of an empty page.

The public profile is for phones

Recruiters open the link on a phone. The building tools stay on desktop, where people sit down to write.

Ready for development.

4 flows: Sign-up to sent

Sign-up, the app itself, a shareable public profile and a marketing site.

~29 screens: Specced for handoff

A desktop app plus a public profile that works on phones. The build hasn't started.

What I owned

  • ~29 screens across four flows
  • Design system from scratch: 8pt grid, Inter
  • Public profile, built for phones
  • Handoff-ready specs

I designed the busy dashboard first.

A brand-new user meets that dashboard with nothing to show. The empty, first-run version should have come before everything else.

More case studies