I recently updated my portfolio for junior product design roles and replaced rougher project files with polished mockups. Since then, recruiters have asked fewer questions about my process, and one suggested that the work looked too close to finished agency projects for my experience level. I want the portfolio to look professional without hiding what I actually contributed.
Is this a normal concern with junior portfolios, and should I include earlier drafts, constraints, or more detail about my specific role?
2 Answers
-
A polished final screen looks impressive, but showing decisions and constraints proves authorship; for example, annotate one discarded flow with “removed after usability feedback.”
-
Could a reviewer tell which decisions were yours if the final mockups were removed? If not, add one compact “ownership” panel to each case study: your role, the constraint, one decision you made, and the evidence that changed it. The practical point is not to make the portfolio rougher; it’s to make authorship verifiable. Include earlier drafts only when they show a decision you can explain. Can you name one key choice in each project that you personally owned?
Want to answer?
Log in or create an account to post answers, vote, and build your professional profile.
Log in or registerHow thoughtful discussions stay useful
How we moderate answers
We review contributions for clear, actionable, professionally relevant guidance. Duplicate, promotional, low-quality, or unsupported content may be removed.
What makes a high-quality answer
Strong answers directly address the question, explain the reasoning, and include specific steps, examples, tools, or frameworks when they add value.
Expert participation rules
Professional expertise should be grounded in real experience and presented objectively. Answers must stay career-focused and avoid undisclosed promotion.