Sydney Nguyen is still studying Experience Design at San José State University, with some time left before she graduates.

That matters because her portfolio often feels further along than you would expect at this stage.

She has spent a few years exploring design, but she has not yet built the kind of conventional professional track record many students rely on. There is no major product design internship sitting at the center of the portfolio.

Yet the work feels credible.

Part of that comes from the portfolio itself. Sydney leans fully into a whimsical, hand-drawn direction. There are illustrations, sparkles following the cursor, playful borders, travel photos, hackathon memories, and a cat making an early appearance.

Some designers worry this kind of presentation will feel unprofessional. I don’t think that concern should stop you when the direction fits you and the roles you are pursuing.

Design sits close enough to art and visual expression that stripping all personality from a portfolio often does more harm than leaving some in. Sydney’s direction will not suit every enterprise team or corporate consultancy, but it can resonate strongly with startups, consumer products, expressive brands, and teams that value personality.

More importantly, the playfulness does not hide weak work.

Sydney has multiple functional products behind the projects she presents. Some came from hackathons. Others she built herself using current coding tools. You can open them, use them, and see that they extend beyond a Figma prototype.

That alone makes this portfolio a useful picture of how the expectations around early-career work are changing.

Sydney’s strongest skill in this portfolio is storytelling.

Hiring managers do not enter a portfolio with unlimited attention. A junior role can attract hundreds of applications within its first day. Even after basic filtering, that can leave someone with an intimidating number of portfolios to review.

They make decisions fast.

First, they look for a broad fit. Does the portfolio feel appropriate for the role, product, and company? Then they choose a project, often based on whichever one appears closest to what their team is building.

Sydney supports that decision well.

Her project cards include small tags that clarify the surface and nature of the work. A hiring manager looking for mobile experience can spot it. Someone working on a music product can identify the relevant project. Someone hiring for a web platform can choose accordingly.

The tags could be refined in places. “UX research,” for example, is expected within many product design projects and may be less useful than an industry or product-type label. But the mechanism works.

Hovering over most project cards also reveals a short video preview.

Some recordings could be cut more carefully, and one project does not appear to have a preview yet. Still, the principle is strong. Before opening the case study, you get a taste of the product and its interaction model.

Once inside, the case studies are built around scanning.

The openings can be tightened. Sections labeled “Background” and “Concept” currently ask for too much reading before the visual story begins. Sydney could compress each into one information-heavy heading and a much shorter supporting sentence.

After that early bump, however, the structure settles into something much more effective.

Large headings carry most of the information. Visuals explain the product. Body copy fills in details for anyone who decides to stop. Sections such as audience, opportunity, use cases, and features can be understood while moving through the page.

You do not have to read every paragraph to understand what Sydney designed or how she approached it.

That is the job of a portfolio case study.

Some headings are still descriptive. “Key Features,” for example, tells me what category I have reached but contributes little to the project narrative. Even so, Sydney is far ahead of many portfolios in how consistently she front-loads meaning.

Her use of video is similarly measured.

She does not animate every screen for decoration. Static visuals remain static where the layout is the main point. Video appears when interaction needs to be understood, making those moments more valuable and more likely to stop the scroll.

By the end of the case study, you understand the product, its audience, its core flows, and Sydney’s ability to take an idea from concept to something usable.

And you can try the product yourself.

I would move that link much closer to the top. A hiring manager may prefer to test the app before reading the case study, especially when there is no account creation or complex setup involved. Letting them do that immediately could make them more invested in the story that follows.

Sydney’s project selection also demonstrates something students need to hear more often.

You do not need to wait for an internship before you can create credible work.

Internships remain valuable. They introduce company constraints, established products, collaboration, stakeholders, and the less glamorous parts of getting work shipped. But a lack of internship experience no longer means your portfolio has to be filled with speculative school exercises.

Sydney’s work comes from two strong sources.

The first is building independently.

She takes an idea, applies product thinking, designs it, and then builds a functional version. The finished result may remain a demo rather than a full commercial product, but it is far more persuasive than a clickable prototype.

It shows that she can think through an end-to-end experience and carry it across the distance between an interface concept and something people can use.

One of these products was built in two days.

Speed is not always the important part, but in this context it shows decisiveness. She could define a manageable scope, choose what mattered, and get the product into a working state.

The second source is hackathons.

Hackathons and similar build events solve several problems that junior portfolios often have.

They demonstrate teamwork. They force decisions under time pressure. They require communication across roles. They tend to produce more ambitious outcomes than one person might build alone. And in many cases, they end with a shipped product rather than a presentation deck.

Sydney’s team projects show all of that.

One case study explains how a four-person team divided responsibilities and brought a product together. The tool is available. The code exists on GitHub. You can see evidence that the team made the thing, rather than stopping at a concept.

That carries weight.

A self-initiated project can show personal initiative and end-to-end ownership. A hackathon project adds collaboration and shared delivery, removing some of the uncertainty hiring managers may have about someone who has not worked on a professional product team yet.

You do not need to win.

A prize is nice, and placing well provides another signal. But the value lies in the process, the team, and the finished work.

There are hackathons, vibethons, volunteer programs, student organizations, and remote build events happening constantly. Many include access to tools, credits, mentors, or teammates. For someone actively job hunting and able to dedicate a weekend, these opportunities can produce the strongest project in their portfolio.

Sydney has used them extremely well.

Sydney’s portfolio has a strong character on the homepage and About page.

The cursor sparkles. Photos animate into view. Borders feel hand drawn. Shapes are playful. The whole experience feels personal and warm.

Then you open a case study, and much of that character disappears.

The pages become neutral, minimal, and considerably more restrained. Focusing attention on the work is a sensible rationale, but the contrast feels sharper than it needs to.

I would carry some of the visual language into the projects.

That does not require adding doodles to every section or turning the case studies into illustrated stories. Small moves would be enough.

Images could use the same irregular borders as the homepage cards. Research findings could be paired with small illustrations. Key numbers could animate into place. Section dividers could borrow from the hand-drawn language already established elsewhere.

Survey results are one obvious opportunity.

Sydney already synthesizes the findings rather than dumping the full survey into the case study. That is the correct editorial decision. But the presentation could go further. A few animated figures or small illustrations tied to each insight would make the research easier to absorb and bring the page closer to the spirit of the rest of the portfolio.

Consistency here does not mean applying one rigid template everywhere.

It means preserving the character of the designer across the full experience.

Right now, the homepage promises whimsy and personality. The case studies deliver capable product storytelling, but they feel like they belong to a more neutral portfolio.

Bringing those two halves closer together would make Sydney’s site more memorable and make some of the drier project material easier to engage with.

Sydney also has an archive containing additional work.

There is valuable material in there, but the current format asks too much from the viewer. Several projects lead directly into Figma files, decks, or prototypes.

That creates friction.

Figma links can take time to load. Navigation is less controlled. The viewer may land in a file at the wrong zoom level or have to work out where to begin. When someone is already reviewing many candidates, each additional obstacle increases the chance that they close the tab.

I usually do.

Sydney does not need to turn every archived project into another full case study. That would create too much work and leave the main portfolio bloated.

A visual gallery would work better.

She could record one or two strong moments from each project and arrange them in a large masonry or bento-style grid near the bottom of the homepage. The visuals could carry most of the presentation, with short context appearing on hover.

No long descriptions. No extra process sections. No full case studies.

Only the strongest moments from each project, presented directly.

This would also give Sydney more control over how unfinished or slightly buggy work is perceived.

One of the linked projects has a compelling concept but shows a few rough edges when opened live. In the archive, that can weaken the impression. A carefully recorded video could demonstrate the intended experience in its best state while still showing the work honestly.

A gallery could also make better use of the available space. Sydney’s homepage is not excessively long, so extending it with a rich block of additional work would not damage the experience.

At the moment, the archive hides useful evidence behind extra clicks.

Bringing that evidence onto the page would strengthen the range of the portfolio and allow the playful interaction language to continue into the supporting work.

Sydney Nguyen’s portfolio is a strong example of what an early-career designer can build without waiting for a conventional professional opportunity.

The visual direction is expressive and playful, but the underlying portfolio mechanics remain solid. Projects are easy to identify. Case studies can be understood while scanning. Motion appears when it helps communicate interaction. The writing usually places the important information in the headings.

Her ability to build functional products changes the weight of the work.

These are not only interface exercises. You can try the apps, inspect the products, and see how the ideas behave beyond a prototype. Combined with the teamwork shown through hackathons, that gives Sydney’s portfolio more credibility than her level of formal experience might suggest.

The strongest improvements are both presentational.

Carrying more of the whimsical visual language into the case studies would make the portfolio feel more cohesive and help bring dry research material to life. Replacing external archive links with a visual gallery would make the additional work far easier to discover and appreciate.

Sydney still has time left in her studies.

That makes the current state of this portfolio even more promising. She already knows how to find opportunities, tell a product story, work with others, and turn ideas into usable software. More professional experience will give her better constraints and richer material, but she is not waiting around for someone else to create the starting point.

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!