Ambika is a Seattle-based product designer with a deep background in research, including experience at Google and TikTok.

She brings more professional experience than many designers featured in this series, and her portfolio shows it. Complex projects become easy to follow, with descriptive headings, purposeful visuals, and enough context to understand the decisions behind the work.

There is plenty to borrow from her storytelling, including how she presents a confidential project. Let’s look at what she does well and where a few improvements could help the portfolio go further.

Ambika’s storytelling stands out most clearly in her BioDepot case study.

Bioinformatics workflows could take an entire page to explain before a visitor reaches the design problem. Ambika gives us enough context to understand the challenge in one heading: BioDepot had desktop tools for those workflows and wanted a mobile experience.

I do not need to understand every task a researcher performs to follow that opening. I know the industry, the existing platform, and the direction the team wanted to explore.

Supporting copy adds depth for anyone who wants it. Researchers use the desktop experience to configure workflows, compare outputs, manage datasets, and monitor different states. Those tasks benefit from larger screens.

Now the design challenge has more substance, without requiring everyone to read that explanation before moving on.

Ambika continues this approach throughout the case study. Headings communicate what happened, what she learned, and how that affected the design. Someone reading only the larger text can still follow the project.

That is what I mean when I talk about putting the important information into the heading.

“Problem” tells me what category I am about to read. A heading that explains the problem gives me something I can remember while scrolling. It can also make me curious enough to stop and read the supporting paragraph.

Ambika does this particularly well with a subject that could have become dense very quickly.

Her visuals carry their share of the explanation too. Simplified interface illustrations isolate the parts relevant to the problem, with short annotations adding context. Visitors can understand what deserves attention without decoding an entire application screen.

Recorded flows show the product in sequence. This makes the experience easier to follow than a collection of screens arranged beside one another, where the viewer has to work out how they connect.

I can tell that some of these recordings show a prototype. That does not reduce their value here. They communicate the interaction, give the work movement, and help me imagine using it.

Ambika moves between those formats according to what the story needs. A recording explains behavior. An illustration makes a complicated relationship easier to understand. A heading gives the section its meaning.

Her research background may have helped develop this skill. Research needs to reach people in a form they can understand and use, and that involves deciding what to foreground, what to simplify, and where more detail belongs.

Whatever shaped her approach, the execution works. BioDepot is a case study I would send someone who wants to understand how to make complicated work readable without stripping away its substance.

Ambika’s TikTok project handles a familiar portfolio obstacle well.

Visitors learn that the work is confidential, but they are also offered a preview. A password field is available for the full case study, while the public page already gives them something useful to explore.

That changes the experience of arriving at restricted work.

An empty gate asks a hiring manager to do more before they know whether the project deserves their time. Ambika lets them understand the relevance of her contribution first.

She opens with what the research influenced. Before going into methods, she establishes that the findings informed product and design work around advertisers’ experience of ad rejections.

From there, the preview builds enough context to follow the project. It explains the problem, uses product examples to help orient the reader, and includes illustrations created for the portfolio to make parts of the experience easier to understand.

Those illustrations are a useful presentation choice. Ambika can explain a problem or relationship without making every part of the story depend on an internal screenshot.

She also outlines her research contribution, includes reflection, and shares stakeholder feedback. Together, these give a hiring team several ways to evaluate her work: how she approached the problem, where the findings were used, and how colleagues experienced her contribution.

By the time I reached the end, I had learned far more than I expected from a preview.

For the product design roles she is moving toward, much of what I wanted to understand was already there. Someone assessing her for a research role might want more depth on the studies themselves, which gives the full case study a clear purpose.

Other designers will have different permissions around what they can share. The approach worth borrowing is how Ambika builds a useful public story from the material available to her.

Her research experience also deserves its place in the portfolio. Moving into product design does not erase the value of being able to investigate a problem, work with evidence, and help a team decide what to build.

Ambika keeps that experience visible while giving her design projects priority.

I would make one small improvement to the stakeholder quotes: highlight the phrases that say the most about her contribution. The feedback is valuable, but a few carefully chosen highlights would help someone scanning the page absorb it faster.

Even without that refinement, this is a strong example of giving restricted work enough public context to earn attention.

Ambika’s TikTok preview explains where her research influenced the product. I wanted the design case studies to communicate their contribution with the same clarity.

Some closing sections describe impact in broad terms, but leave me uncertain about what happened after the work was delivered.

Did a team adopt the proposed direction? Did anything reach development or launch? Did testing change a decision? Did the work help people complete a task more successfully?

Those questions matter because the case studies have already made the problem and design reasoning understandable. I am invested in the work by that point, and I want to know where it led.

I do not know why that information is missing. Ambika may have left before results became available, or completed a contract without hearing what happened afterward. It would be unfair to assume there was no impact because the portfolio does not describe it.

If that is the situation, following up with former collaborators could help.

She could ask what was implemented, what changed during development, and whether the team gathered feedback after her involvement ended. A short conversation may uncover enough to write a more informative closing section.

Useful evidence does not always arrive as a percentage.

A team adopting a recommendation, changing its product direction, or using the work to make a decision can be worth explaining. Feedback from people using the experience can also add substance, provided the case study makes clear what was observed and who reported it.

The status of the work matters too. Something proposed, prioritized, tested, or shipped should be described accordingly. If an outcome remains unknown, Ambika can state what she delivered and what the team did with it up to the point she can confirm.

Her research experience gives her a strong foundation for making those distinctions. I would bring that same care into the endings of the design stories.

There is also an opportunity to use the homepage project titles more effectively.

Names such as BioDepot or Building H tell me where the work happened. They do less to explain why I should open it. Ambika could keep the organization name as a label and use a larger heading to communicate the challenge, contribution, or supported outcome.

She already writes this way inside her case studies. Bringing that approach onto the homepage would help the work earn attention earlier.

Google and TikTok have more immediate recognition, but those names still become more persuasive when paired with an explanation of what she contributed.

Ambika makes the opening and middle of her stories easy to understand. More evidence at the end would give hiring managers a fuller picture of what her work enabled.

Ambika’s portfolio contains thoughtful details, including an easy way to copy her email address. There is care behind the site.

A number of smaller issues remain across interactions, layout, and writing. Taken together, they make parts of the experience feel less finished than the case-study storytelling.

Clickable elements are one example.

Project images open case studies, but do not consistently provide a pointer cursor or another clear signal that they are interactive. Her avatar also returns visitors to the homepage without making that behavior obvious.

An image can work well as the entrance to a project. It needs enough feedback for someone to recognize it as an entrance.

A consistent pointer cursor, a visible hover treatment, or a clear action would help. Similar elements should communicate their behavior in similar ways throughout the site.

The carousel containing additional work has another interaction problem. I could navigate through the small dots, but could not drag or scroll through the cards.

That makes a quick browse more demanding than it needs to be. Larger navigation controls or support for dragging would let visitors move through the collection at their own pace.

Layout issues appear in the resume and case studies as well.

Some text aligns with the edge of a logo rather than the text column beside it, which makes the composition feel off. Wrapped bullet text does not always line up with the first line. In a few places, related items have more space between them than the gap separating them from unrelated information.

These decisions affect how easily someone can understand the page.

Spacing should make relationships visible. Text alignment should give the eye a stable path through a section. A timeline needs enough separation to be understood as its own piece of information.

Ambika would benefit from reviewing these patterns across the portfolio, rather than correcting each instance in isolation.

Writing needs a similar pass. There are lowercase instances of “I,” inconsistent capitalization of terms such as HTML and CSS, and missing punctuation. One visual arrangement makes it unclear whether the text continues a sentence or begins a separate item.

Each issue is small. Seeing several during the same visit makes them harder to overlook.

I would avoid treating this as proof that Ambika lacks the underlying skills. Time, implementation, and an incomplete review process can all leave this kind of residue. Hiring managers still experience the finished site, though, and some will connect its polish with the care she brings to product work.

A final review devoted to interaction feedback, alignment, spacing, and copy would be worth doing before adding more content. The portfolio already gives visitors plenty to explore; it needs that exploration to feel consistently considered.

Ambika has built a portfolio I would recommend for its case-study storytelling.

Her BioDepot project makes a complicated subject accessible through descriptive headings, selective context, and visuals that help the reader follow the work. The TikTok preview shows how much a hiring team can learn before opening the full confidential case study.

Her research background comes through as a strength, and it deserves to remain visible as she moves further into product design. I would also consider giving that depth slightly more emphasis in the opening introduction.

For the next round of improvements, I would focus on explaining what happened after the design work and completing a careful review of the site’s interactions and presentation.

I came away understanding how Ambika approaches difficult problems. In several projects, I wanted to stay a little longer and find out what the teams did with her work afterward.

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!