Today: Jessica Hsu
Jessica Hsu is a Seattle-based product designer with a background in Human-Centered Design and Engineering at the University of Washington.
She designs information-rich products where business goals, complicated workflows, and high-stakes decisions meet.
Her work spans enterprise SaaS, fintech, banking, aviation, and an Uber-sponsored project focused on large-event pickups. These are products that can become dense very quickly.
Jessica knows how to keep them readable.
Her case studies are light on body copy, deliberate with headings, and generous with visuals. Alongside that disciplined business work, her portfolio has cursor effects, playful interactions, crafts, experiments, and a small product she shipped herself.
That contrast gives the portfolio much of its character.
Two parts deserve a closer look.
The Good
Case studies that make complicated work easy to scan
Jessica’s strongest skill here is information design.
Many of her projects deal with products that were complicated before she touched them. Enterprise banking workflows, fintech balances, operational tools, and large-event transportation all come with unfamiliar terminology, multiple actors, and decisions that need context.
Explaining that work creates a second design problem.
Jessica solves it well.
Her project cards begin with what changed rather than stopping at a client or product name. Someone does not see “Uber mobile app” and have to guess what she worked on. They see a project about improving rider decisions during large-event pickups, paired with an outcome.
Similar descriptions appear across the portfolio.
Financial visibility becomes the story of helping enterprise teams understand their balances. Banking work becomes a story about reducing drop-off in high-risk workflows. Aviation research is introduced through the usability failures Jessica uncovered.
You know what each project is about before opening it.
Small tags provide another layer of orientation. They identify industries, surfaces, and product types so a hiring manager can find whichever project resembles their own work.
A few labels could become more consistent. “Fintech” and “banking,” for example, operate at slightly different levels. That is a small editorial pass rather than a structural problem.
Once a case study opens, Jessica keeps supporting the scan.
Body-copy density stays low. Full-sentence headings carry the central point. Large visuals provide context without asking someone to study every screen. More complicated relationships are often redrawn as diagrams or grouped into digestible cards.
Nothing follows a mechanical text-left, image-right rhythm.
Jessica changes the composition when the information calls for it. Cards tilt slightly. Visual groups interrupt long sections. Small diagrams replace paragraphs. Each page feels composed rather than poured into a template.
She also gives the solution enough space near the beginning.
One case study quickly shows what she changed and what the improved experience looks like. Someone can understand the core contribution before deciding whether to continue into research, decisions, and iteration.
That ordering matters.
Portfolio viewers keep deciding whether the next section deserves their attention. A promising opening can earn another few seconds. A clear outcome can earn another scroll. A useful heading may create a question they want to bring into an interview.
Jessica keeps earning those seconds.

This is a brilliant way to give an overview over the key bits of the work before diving into the details
She does not treat the initial solution summary as permission to unload every detail afterward. Later sections remain restrained, and supporting paragraphs stay short enough to read when the heading creates curiosity.
Consistency across her projects makes this stronger.
Each case study has its own visual character, but the editorial principles remain familiar. You learn how Jessica communicates, then move through new material without having to learn a new reading pattern every time.
That is hard to achieve with work this dense.
Serious business work with room for play
Jessica’s project history could have produced a very sober portfolio.
Enterprise SaaS, fintech operations, commercial banking, and aviation software often lead designers toward safe grids, restrained typography, and little personality outside the work itself.
Jessica gives herself more room.
Cursor trails, click effects, playful transitions, and small interactive moments run through the site. Her Play section introduces crafts, environmental projects, artwork, personal experiments, and an extension she built.
None of that weakens the business work.
It shows that Jessica can handle information-heavy products without being limited to the visual language those products already use.
That range matters as the craft bar rises across B2B software.
Smaller SaaS companies increasingly want products that feel considered and alive. They still need clarity, dense workflows, permission systems, data tables, and operational reliability. They also want customers to enjoy using them.
Jessica can work on both sides of that equation.
Her case studies prove that she can structure difficult information and account for business outcomes. Her portfolio experience suggests that she also notices interaction details, visual character, and moments of delight.
A playful portfolio does not mean she would turn a banking platform into a toy.
It means she has more than one visual gear.
Jessica can read the context, choose an appropriate level of expression, and make a functional product feel more considered. Her Uber project already demonstrates how naturally she can move toward a consumer-facing environment when the product asks for it.

Her playground is a stark but welcomed contrast to the business-focussed work she presents in the main part
Personal work supports that impression too.
Crafts, recycling projects, artwork, and experiments show curiosity beyond interface production. Her extension deserves more space because it adds another useful signal: Jessica can carry an idea far enough for someone else to use it.
Hiring teams looking at her enterprise work may arrive for the clarity.
Playfulness gives them a glimpse of what else she could bring once she is inside the product.
The Potential
Give every project thumbnail the same chance to attract attention
Jessica’s Uber project has the strongest presentation on the homepage.
Its thumbnail combines a contextually relevant background with a phone mockup and a moving product flow. Someone gets an immediate taste of the environment, the interface, and the interaction she designed.
Other project thumbnails remain static.
That difference makes Uber the visual magnet, even when another project may be more relevant to the role someone is hiring for.
A fintech hiring manager should be drawn toward Jessica’s financial visibility or banking work. A SaaS team may care more about her operational products. Yet movement naturally pulls the eye toward Uber first.
Jessica already has better material available.
Several case studies contain videos or interaction clips that communicate more than the static homepage images. Those clips could be brought forward and placed inside the same thumbnail treatment she uses for Uber.
No new interaction concept is needed.
Existing material can show how balances change, how a user moves through a workflow, or how the redesigned interface responds. A short loop would communicate more about Jessica’s contribution than a single screen.
Small inconsistencies could be cleaned up during the same pass.
One card lacks the logo treatment used elsewhere. Recording the Uber prototype on a phone would remove the cursor from a mobile interaction. Backgrounds and overlays could follow a shared set of rules while remaining tailored to each project.
Equal treatment does not require every card to look identical.
Each project needs enough movement, context, and polish to compete for attention on its own terms.
Jessica’s case studies already prove that the material is there. Bringing more of it onto the homepage would help viewers choose based on relevance rather than whichever card moves first.
Rework visuals that ask the viewer to zoom
Jessica is good at reducing complicated information, but a few sections push beyond what the page can comfortably hold.
This appears most clearly in the enterprise banking case study.
Some flows contain several screens connected across a narrow image. Other diagrams combine interfaces, annotations, and relationships at a scale where labels become difficult to read.
Parts of the product also appear in Chinese.
Language alone does not make a visual unusable. Screen scale does. When text, interface details, and annotations are all small, neither Chinese-speaking nor English-speaking viewers can extract much from the image.
A case study should not depend on zooming.
Lightboxes rarely solve this. Many viewers will not click an image to enlarge it, and needing that interaction suggests the first presentation is carrying too much information.
Jessica could divide these visuals into smaller moments.
One large workflow might become three stages, each with a cropped screen and one sentence explaining what changed. A dense diagram could begin with a simplified overview and reveal individual branches below. Product screens could focus on the area being discussed rather than showing an entire interface at once.
English annotations can explain the behavior without translating every label in the product.
Stronger cropping would help too.

This is a tough visual to take in. I suspect there won’t be much takeaway
If a section discusses one control, state, or decision, that part of the interface should receive enough space to be understood immediately. Supporting screens can appear afterward when they add something new.
Jessica already applies this discipline across much of the portfolio.
Several diagrams are readable while scrolling because they contain only the information needed for that moment. Bringing the banking case study to the same standard would remove one of the few places where her otherwise controlled storytelling becomes demanding.
The Verdict
Jessica Hsu has built a portfolio that handles difficult material with impressive restraint.
Her projects include dense workflows, unfamiliar product contexts, and business outcomes that could easily turn into long explanations. Jessica keeps them visual, uses headings to carry meaning, and gives readers enough information to understand the work without removing every question.
That last part helps her.
A portfolio should create enough understanding to earn an interview while leaving enough depth for a conversation. Jessica’s case studies make you want to ask how she reached the decisions rather than making you feel that you have already read the meeting transcript.
Her playful side adds another dimension.
Cursor effects, experiments, crafts, and personal projects keep the site from inheriting the stiffness of the products she has worked on. They also suggest that Jessica could bring more life into B2B software without losing the clarity those products require.
Improvements sit mainly in how work is presented before and during the case studies.
More motion across project thumbnails would stop Uber from absorbing so much attention and help relevant enterprise or fintech work compete. Breaking down the densest banking visuals would bring that project closer to the scanning standard Jessica establishes elsewhere.
Neither issue changes the quality of the portfolio underneath.
Jessica already knows how to structure information, connect design decisions to business outcomes, and adapt her visual language to different product categories. I would give the extension more space too. It currently feels like a side note, even though shipping a small tool adds another useful piece to the picture.
If you’d like to craft a similarly impressive portfolio Framer is likely your best choice.
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:
Flat learning curve: The interface feels familiar if you’ve used Figma — plus, there’s a plugin to bring your designs straight in.
Plenty of learning support: Framer Academy is packed with free tutorials, videos, and guides to help you go from zero to published.
A huge template library: Tons of high-quality (often free) templates in the marketplace to help you launch quickly without starting from scratch.
Free if you are a student: Although Framer already offers a generous free plan for everyone, if you are an enrolled student you can get Framer Pro completely for free!
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.
How I can help 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!
Book a mentoring session with me
Book a quick 15 min chat to ask a question and see if we vibe

Florian Boelter
Florian Boelter is a product designer, mentor and builder focussed on helping early-career designers navigate the job search and the first steps on the job.
If my content helps you in any way I’d appreciate you sharing it on social media or forwarding it to your friends directly!



