answers · portfolio · last verified May 24, 2026
frame 01 · the direct answer
what makes a good UI/UX portfolio for your first job?
three to five real case studies, written as problem-to-solution arcs and not as galleries of pretty screens. Hiring managers reviewing junior portfolios spend 90 seconds per case study. In those 90 seconds they want to see (1) what user problem you set out to solve, (2) how you thought about it, (3) the design choices you made and why, (4) what shipped, and (5) what you'd change next. Polish helps but never wins on its own — a beautiful screen with no thinking attached is the most common reason juniors get rejected.
frame 02 · the checklist
what koalia jury reviewers look for
- 01three to five case studies, no more.
- 02each case study opens with one sentence stating the user problem.
- 03no jargon in the first paragraph. write like you'd explain to your mother.
- 04show your process — sketches, research notes, rejected directions. not just final mockups.
- 05include at least one before/after comparison.
- 06every screen has a caption explaining the design choice.
- 07show one piece that you actually shipped (or could ship). working prototypes count.
- 08demonstrate one accessibility check (contrast, screen-reader pass, keyboard nav).
- 09include one piece that involves a design system or component library, not just screens.
- 10end every case study with 'what I'd change next time' — humility reads as maturity.
- 11personal site loads under 3s on 3G. it's a UX portfolio. eat your own cooking.
- 12your about page has one real photo, your location (beirut), and how to contact you.
frame 03 · why juniors get cut
the 7 most common rejection patterns
- all mockups, no thinking — looks pretty, says nothing.
- no captions explaining choices.
- five different visual styles across projects — looks like a tutorial archive.
- no working prototype anywhere.
- case studies that are just step-by-step process diagrams with no specific decisions.
- broken links to live work. (always test on a friend's laptop.)
- Dribbble shots reposted as 'case studies' with no context.
frame 04 · case-study skeleton
the structure that always works
- context. one paragraph: what product, what user, what timeframe, what was your role.
- the problem.a specific, observable user pain. bonus: a quote from a real user (or yourself if it's a self-initiated piece).
- process. 3–6 visuals showing how you thought — sketches, IA diagrams, rejected directions, interviews.
- solution. the final design with annotations explaining what changed and why.
- outcome.what shipped or what you learned. one metric if you have one — even "the redesigned flow took 3 taps instead of 5".
- what next.one short paragraph on what you'd change with hindsight. this is the maturity tell.
frame 05 · the quote
“the portfolios that get juniors hired aren't the prettiest ones. they're the ones where you can read three sentences and understand exactly what the person was thinking, and exactly why they made each call. clarity beats polish every time.”— Julien Hosri, founder of koalia, ex-lead instructor of the UI/UX bootcamp at SE Factory (250+ students)
cohort KO-1 · week 8 ships a jury-ready case study
graduate with a portfolio piece you can hand to a recruiter
week 8 is a full case study built for the demo-day jury — Julien + two surprise guests.