How to design your portfolio review to get the job you deserve: Tales from the other side of the recruiting table.

Josh Shiau
May 17, 2017 · 7 min read
Image for post
Image for post
Sammy J ready with his portfolio presentation. (Pulp Fiction, http://static.snopes.com/app/uploads/2016/03/briefcase.gif)

First, some background.

Three months ago, during dinner-time, without any dinner, I was knee deep in the fully reclined seatback in front of me on a plane from Texas back to Providence, Rhode Island. I now live in Austin, a place with the unique distinction of being able to drive for 5 hours straight in any given direction without nearing a border.

Image for post
Image for post
“The best country in the USA.” (https://rigea.files.wordpress.com/2014/04/ri-texas.jpg)
Image for post
Image for post
Sol LeWitt: All about that process. (Sol LeWitt, Wall Painting, http://res.cloudinary.com/bombmagazine/image/upload/v1412020949/lewitt_03_body.jpg)

The Review.

When I review design portfolios, I’m excited when people talk about user research. Just as you need to listen before you speak, you have to understand before you design.

your design prompt:

How can you best improve my user experience as a portfolio reviewer?

your user:

Yours truly worked a full day the previous day before leaving just early enough to catch a 5:40 pm flight that landed today at midnight.

your constraints:

  • We are in a large room, and there will likely be someone talking loudly right beside you.
  • However many bars of wifi you see, it will soon bear the load of an entire graduating class trying to load their squarespaces at the same time.
  • I have all of 10 mins to make an uncomfortable amount of assumptions about you from your presentation and make a decision. The quicker and easier it is for me to get to the most relevant work, the better off we both are. Prioritize your work so that if we do run out of our wonderful but brief time together, I’ll remember the best and most relevant work first. Two to three projects is realistic. On that note, there is no need to walk through each iteration and permutation you tested, just the ones that provided crucial insights for your end product.
  • I don’t expect everyone to have read all the job descriptions (researcher, UX designer, visual, FED) but the more you know ahead, the more precious time you can spend communicating your design process, confidence, fire-in-the-eyes, etc. instead of me communicating things that can be found on our website. A good thing to shoot for is you talking for at least two thirds of the whole ten minutes.
  • Finally, even if I’m just reviewing your portfolio application remotely, same goes — I have the same amount of time, just have less context about who you are and what I should look at first.
Image for post
Image for post
One thousand full-bleed Squarespaces descend upon you. (300, http://www.movpins.com/big/MV5BMjEzNTgxNzIxMF5BMl5BanBnXkFtZTcwNTg1NTIyMw/300-2006-large-picture.jpg)

your product:

ie: your mind and your thinking process.

  1. Why did you choose the method you did?
    Why is this the most impactful/efficient way to solve it?
  2. What did you discover and make?
    What interesting and actionable thing did you discover? It needs to be non-obvious to have value — if I could have guessed it, someone likely wouldn’t have prioritized the time and money for you to research and design it.
  3. How does it work?
    Bonus points for showing solid consideration behind the guts of how a product, service, or system would work IRL. What do you foresee being easy or a major friction point?

your other product:

ie: you as a potential collaborator.

  1. How you collaborate.
    Thinking transparently means being very open with your ideas and being able to explain your whole thought process. It strikes me as both humble and useful when designers mention caveats in their method of inquiry or design. On the opposite end of transparency it is possible to expose your audience to too much, but like a good museum curator, your job here is to shield from the unnecessary and distracting. Interesting facts are fun, but if I am learning about something that does not in some way help me understand you or your thinking process, it is a waste of time and a disservice to you.
    Objective agility is not only a lack of defensiveness, but also the ability to hop on other people’s trains of thought. Defend your ideas with the conviction that you did it the best way you knew how, but be open to feedback and quickly move, ideate, and build with your critics.
  2. How you answer questions.
    How do you respond to the unexpected? Don’t worry about speed here, quick wits and nimble neurons are great for navigating unruly workshops and improvising during user interviews, but that’s only a fraction of actual day-to-day work, and can be largely addressed with good planning. Listening objectively and responding thoughtfully is always a good strategy. Never be afraid to restate what you heard in your own words, it actually helps me (and users) to be confident that you understand and care about precision.
    How do you adapt to difficult questions that broaden scope or grapple with strategy? ex:
  • If I was an investor — how is this objectively different and better than what is out there?
  • What is/how does this inform strategy? — I saw a lot of social impact-focused projects this year, which I am so tremendously happy about, but I especially appreciate if you can present a solid business logic beyond should to can be self-sustaining because…

In summary:

You are an awesome designer and have no doubt ruthlessly applied thoughtful design to everything else in your portfolio, now do it for the thing that will get you a job, dammit.

Image for post
Image for post
At the beginning the briefcase was your portfolio, this time its your illustrious career in designing enterprise software. (Pulp Fiction, http://static.snopes.com/app/uploads/2016/03/briefcase.gif)

IBM Design

Stories from the practice of design at IBM

Thanks to Greg Storey

Josh Shiau

Written by

Designer for HealthTap, based in San Francisco. Let’s talk community and culture. www.joshshiau.com

IBM Design

Stories from the practice of design at IBM

Josh Shiau

Written by

Designer for HealthTap, based in San Francisco. Let’s talk community and culture. www.joshshiau.com

IBM Design

Stories from the practice of design at IBM

Medium is an open platform where 170 million readers come to find insightful and dynamic thinking. Here, expert and undiscovered voices alike dive into the heart of any topic and bring new ideas to the surface. Learn more

Follow the writers, publications, and topics that matter to you, and you’ll see them on your homepage and in your inbox. Explore

If you have a story to tell, knowledge to share, or a perspective to offer — welcome home. It’s easy and free to post your thinking on any topic. Write on Medium

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store