Intro
I wrote this because I’ve been on the wrong side of “quiet rejection” more times than I want to admit. I used to think good work would speak for itself. Then I watched solid projects get skimmed, misunderstood, or ignored because I wasn’t making the right things obvious.
Over a few job searches, a lot of portfolio reviews, and a handful of humbling conversations with hiring managers, I started to see a pattern. When I got traction, it was usually because I made three things easy to understand fast: what I’m great at, what I actually owned, and how I tell the story.
I’m a designer who grew up in Honolulu and has been working for 5+ years. I’ve done work at local companies of all sizes, from small startups to larger orgs like Servco and University of Hawaiʻi at Mānoa, and I’ve also had exposure to global teams like NVIDIA and Gen.G. My path has not been linear. That is kind of the point.
Getting Noticed
When I say “innovative companies,” I mean teams that are more open to new ways of designing and building. They tend to blur the cross-functional workflow (less handoff, more building together), hold a high bar for craft, and have designers who are deeply curious. They usually have a heavy prototyping culture, and a “prove it” culture: show it working, show the tradeoffs, show the decision.
If you're aiming for more mature orgs, some of this still applies, but the signals they reward can be different. Either way, the main idea is the same: treat job searching like a design problem. Build a system. Iterate it. And most importantly, start with clarity.
Job searching is a design problem (and it starts with you)
Job searching is weirdly introspective. If you are not honest about what you want, you end up making work that tries to appeal to everyone. That sounds safe, but it usually makes your portfolio feel generic. And "generic" is a quiet rejection.
Most early-career designers make the mistake of not thinking about what makes them stand out. They don't consider what's the best way to showcase their work, whether that's a traditional portfolio, a different format entirely, or some other method. If you don't know what makes you unique, you'll just create someone else's portfolio but worse or more generic.
In my experience, the fastest way to improve your odds is to stop designing for "any company" and start designing for your actual future. Who do you want to become as a designer? What kind of team would you thrive on? What kind of work do you want to be known for?
If you can't answer those, it is hard to make good decisions about what to show, what to cut, and what story your portfolio tells.
Start with your “north stars”
Before you start building: understand what "craft" looks like
Study portfolios from designers you admire, at your target companies and beyond. Notice patterns: what makes something feel polished? What makes a case study easy to follow? What signals craft, judgment, and taste?
Once you have that baseline, be selective. Take principles that resonate with your strengths and leave behind what doesn't fit. A great portfolio isn't about checking every box. It's about showing your best work authentically and intentionally.
Pick a short list of companies you genuinely want to work at, not because they're prestigious, but because the work aligns with the designer you want to become.
Then look at portfolios of designers already working there. Not to copy them, but to calibrate. What signals does their work emphasize? Craft? Product thinking? Systems? Speed? Strong POV? Every team rewards a specific "language." Your portfolio should speak it fluently.
I also noticed: great portfolios aren't packed with projects. They're edited, skimmable, and feel inevitable.
Build a strategy around your strengths (not around being “well-rounded”)
Don't try to be good at everything. It takes too long and reads as shallow. Instead, know your strengths and build artifacts that make them obvious in seconds.
That said, generalists are thriving right now. Show you have a foundation of craft and the range to adapt. Don't try to be everything to everyone, but do show you can handle ambiguity and wear multiple hats when needed.
Be honest about where you are in your career. Recruiters are actively trying to place you on a ladder. If your portfolio hides the truth, it creates confusion. Confusion leads to "no," even if your work is good.
Ask yourself:
- What are your strengths?
- Where are you in your career right now?
- What's your take on AI?
Then design your artifacts around that reality:
- How do you highlight your strengths quickly?
- What artifacts prove it?
- What should you strip away because it distracts?
Portfolio system: mix and match what you need
Your portfolio is a product with one job: reduce doubt. Recruiters skim (often just one or two projects) scanning for reasons to say yes or no. Design for that reality.
Make ownership clear. If your case studies say "we" everywhere, the reader has to guess what you did. Make it obvious.
Make the product the hero. Show outcomes, decisions, and taste. Process matters when it clarifies judgment, not when it becomes a documentary.
Be ambitious. Side projects often show your ceiling: what you do when no one is constraining you.
Have a point of view. Being opinionated is a strength. A blog can show how you think outside "presentation mode."
Get feedback early. Don't build in isolation. Calibrate with recruiters, hiring managers, and peers, but filter advice through your own judgment.
Interview Process
The moment you hear back is too late
A lot of designers (me included) scramble after they get the interview. That is the wrong moment to start building your story.
If you are actively searching, you want to be “presentation ready” before you ever hear back. Have a flexible outline of your work. Know what you can swap in and out depending on the role. Do the basic research early so you can spend the interview week refining, not panicking.
Also, show recent work. If you can, prioritize projects from the last one to two years. It signals that your current level is real and your momentum is now.
Put on your UX hat: what is the team trying to learn?
Every interview loop is a product experience, and the hiring team is the user. Your job is to make it easy for them to understand three things: what you are good at, how you think, and what kind of environment you will thrive in.
That means tailoring your emphasis without becoming fake. It also means being transparent about where you could use training, while still projecting confidence in your trajectory.
And it means showing up with real questions. Interesting, well-researched questions signal maturity. A strong POV on the product signals taste. Together, they make you feel like a teammate, not an applicant.
Final Thoughts
Job searching sucks. It forces you to be vulnerable, strategic, and patient, sometimes all in the same day. If you treat it like a design problem (start with clarity, build a system, iterate), you actually give yourself leverage.
The best portfolios aren't perfect. They're honest. They feel like you, not some template you downloaded. And they make it easy for someone to say yes.
So start small: pick your north stars, be real about your strengths, and build one thing that proves what you can do. Then do it again. Eventually, you'll have a portfolio that doesn't just show your work but who are and where your headed.
And when you finally get that interview? You won't be stressed out trying to get everything together at the last minute. You'll be ready.
If this was helpful, feel free to reach out. I'm always down to talk portfolios, career stuff, or just swap notes on what's working. Good luck out there.