Cindy Ly’s portfolio feels playful without losing focus.

She is currently studying HCI and Design at the University of Washington and has already completed a product design internship at Zendesk. The work fits comfortably alongside some of the strongest student portfolios I have seen from that program.

The overall concept leans into an operating-system aesthetic. That direction has become more common over the last few years, but Cindy gives it enough of her own treatment to keep it from feeling copied.

The taskbar, navigation patterns, subtle control surfaces, and small interface details create a recognizable system without overwhelming the work. That balance matters.

A portfolio should feel personal, but it still needs to work for the people reviewing it. Cindy manages to do both.

The first thing I really like is how Cindy presents herself and the work.

Her intro is short, but the phrase “emotional resonance” gives it a distinct angle. It is not language you see in every product design portfolio, and more importantly, the work supports it.

That is essential.

If you make a claim like that in the hero and then only show dry enterprise tooling with no emotional dimension, the positioning starts to feel empty. Cindy has worked at Zendesk, but her broader portfolio includes projects where emotion, community, identity, and human behavior are much more visible.

The words and the work align.

There are also small details throughout the portfolio that make the experience feel alive. One navigation element opens, closes, and changes state as you scroll. It is subtle enough that you may discover it accidentally.

Those moments matter.

They are not the main argument for hiring Cindy. They are the layer that makes the rest of the experience feel more intentional. A single interaction like that may take an hour to figure out, but it can change how the whole portfolio is perceived.

The operating-system concept works for the same reason.

Cindy does not plaster every screen with references to desktop software. She borrows a few familiar elements, then lets the portfolio remain usable and calm. The concept gives the site character without turning navigation into a puzzle.

You do not always need a completely new idea.

Sometimes you can take a familiar direction, understand why it works, and give it enough of your own judgment to make it feel fresh.

Cindy’s case studies are consistently strong.

That alone is worth pointing out. Many portfolios have one excellent case study and one or two that feel considerably weaker. Cindy maintains a high bar across the set.

Her civic accountability project could easily have become dry. It deals with statistics, public data, and information that can be difficult to explain quickly.

But the case study never feels like a report.

The balance between text and visuals is excellent. In many sections, the visuals carry more weight than the copy. Headings are informative and usually take up a large enough portion of the page to be absorbed while scrolling. Body text stays short, often with highlighting where it matters.

That makes the case study easy to scan.

If you move through it slowly without stopping, you still understand most of the story. That is how hiring managers often consume portfolios.

Cindy also uses video where a static screen would be insufficient. Instead of placing several interface states side by side, she shows the product moving through them.

That is more engaging, but it is also more accurate.

Digital products are experienced through change. Screens update. Data reacts. Interfaces reveal and hide information. A static image can only show one moment of that experience.

One visualization even reacts to the cursor, which turns a potentially complicated data view into something you can understand through interaction.

Her use of before and after is also smart. She leads with the improved version, then reveals what existed before. That reduces the risk of someone mistaking the old interface for her work and gives the reader a reason to care about the comparison.

Impact is clearly surfaced as well. Large numbers and usage information are difficult to miss, which is exactly how it should be.

There are small sections I would trim. The design system snapshot, for example, does not add much and risks overstating what is being shown. But the overall storytelling is excellent.

Cindy’s side-quest section is already good.

It includes 3D modeling and printing, a lamp, a handbag, data visualization, applications, and other work that helps expand the picture of what she can do.

The issue is less about what is there and more about what is missing.

Cindy says she enjoys motion design. Some of that ability appears inside the case studies, but very little of it is visible in the side-project section.

That feels like a missed opportunity.

A playground does not need to become an infinite archive of everything you have ever made. But it is the right place for smaller interactions, motion experiments, prototypes, and fragments that do not have enough depth for a full case study.

Those pieces can still be highly valuable.

Sometimes one small interaction is enough to make someone smile or remember the portfolio later. Cindy already has moments like that in the site itself. I would bring more of that work into this section.

And I would keep adding to it.

If she makes a small interaction for a future case study and loves how it turned out, she does not need to wait until the full project is published. It can live here in the meantime.

The side-quest section should reinforce the range she already talks about. Right now, it does that for 3D work particularly well. Motion and interaction deserve the same treatment.

The second opportunity is inside the Zendesk case study.

The overall structure is still strong. The writing is concise, the headings work, and the project has clear substance.

But some of the product screens are shown too broadly.

One large screenshot may contain only two or three elements Cindy actually designed, surrounded by the full Zendesk interface. That gives context, but it also makes the reader search for the relevant work.

The problem becomes more noticeable when several similar full screens appear with relatively small changes between them.

The impact of the work may be substantial, but visually the changes become easy to miss.

I would isolate the relevant interface pieces.

Keep some of the original product visible in the background so the reader understands where the feature lives. Then pull Cindy’s contribution forward, enlarge it, and let it break out of the screen slightly.

That would give the viewer both things they need:

The side navigation, unrelated charts, and surrounding controls do not need equal visual weight if they were not part of her contribution.

This is especially useful for internship work inside an existing product. You rarely own the whole screen. A good case study should make the boundary of your work clear without pretending the rest of the interface is yours.

Cindy already has the material. The presentation needs to direct attention more precisely.

Cindy Ly’s portfolio is a very strong student portfolio.

It has a distinct visual concept, but the concept does not get in the way. The case studies are easy to scan, visually rich, and consistently well executed. She uses motion well, shows impact clearly, and brings difficult subject matter to life through thoughtful presentation.

The Fig Build project is especially impressive.

Her team won out of 690 teams, and the work is a strong example of what designing for impact can look like even when the product has not shipped. The project begins with a serious real-world problem, explores a plausible intervention, and gets close enough to a viable direction that someone with deeper domain and technical knowledge could take it further.

That kind of thinking matters.

It shows that Cindy can look beyond interface polish and shape a product around an unresolved problem. For early-stage teams and founding design roles later in her career, that is an extremely valuable signal.

The remaining opportunities are focused.

Her side-project section could show more motion and interaction work, especially because she already names that as an interest. And the Zendesk case study would benefit from isolating her contributions instead of relying on repeated full-product screenshots.

But the foundation is excellent.

Cindy’s portfolio already communicates a designer with strong visual judgment, product instincts, and the ability to make work feel both useful and memorable.

Still struggling to get your portfolio off the ground?

Don’t want to spend weeks learning yet another tool? Framer is my top recommendation for building your portfolio — fast, clean, and without the usual headaches.

If you’re just starting out (or even if you’re not), I think Framer is a perfect fit. Here’s why:

And that’s just scratching the surface. I wrote more about why I recommend Framer here—but honestly, the best way is to try it for yourself.

Affiliate disclaimer: I only recommend tools I personally believe in. Some links in this post are affiliate links, which means I may earn a small commission if you choose to purchase — at no extra cost to you.

Do you want your own portfolio reviewed in-depth with a 30-minute advice-packed video review? Or do you require mentoring to figure out a proper strategy for your job search?

I got you!