1. Portfolio
The portfolio is a key document to aid in the post-college transition. It should reflect your professional identity (i.e., applicable job titles) and evidence your skill sets. The portfolio gives employers a look at your abilities and thought processes in addition to being a design object in itself that will be judged. At minimum, a portfolio should include:
- Effective evidence of the skills that backup your professional identity.
- Effective information architecture.
- Class projects (a balance of team & individual is important), internship recaps, contest recaps, freelance work, and/or personal work. (Note: Work done outside the classroom is valuable.)
How Should I set up a portfolio?
The debate regarding how to display/explain your work is open and contestable. How do you set up a portfolio that can grab the attention of recruiters and hiring managers alike? How much info should you include? How much process do you show? What should you focus on?
There are lots of opinions about how to “show your work” and no real consensus. This means that, like a good designer, you need to trust your gut and do what works for you (and iterate!).
That said, there are thoughts and trends you should be aware of when crafting a portfolio:
- Portfolios depend on the job you are applying for. For instance, you would set up a portfolio for a UI design job differently than a real (i.e., not UX theatre↗︎) UX or product job.
- I recommend that you organize work in your portfolio by building two parts for every project: showcase and case study.
- A showcase is a quick recap of your work. (This video↗︎ [3/1/25] makes the case for showing less work. While this video is contradictory, I’m point you to it because it's emblematic of statements I've seen lately.) A showcase covers:
- What is your project? (A hook that draws the reader in.)
- How long did the project take? (Length is important to assess quality.)
- Role? (What specifically did you do if it’s a team project?)
- Tools? (What tools were used to create this?)
- Links? (Link to important files—FigJam, Figma—and to the case study.)
- Key outcomes? (What changed?)
- Tools? (What tools were used to create this?)
- Solution? (Show impactful images/gifs of things you’re proud of that speak to problems and solutions.)
- Lessons learned? (What did you learn in the process of creating this design? What would you do differently if the chance to do it again?)
- A case study shows process. Meaning? It walks through, in detail, the method you used and work you (and your team) did to achieve the final product. The case study should only be separated from the showcase (e.g., clear demaraction on one page or on separate pages).
- Include content (i.e., hobbies) that fleshes you out as a human on your about page.
- Don't neglect nurturing and representing your "soft skills↗︎."