How to Ask Which Portfolio Project a Hiring Team Wants to See

To ask which portfolio project a hiring team wants to see, offer two relevant options and explain what each demonstrates. Ask which better matches the team's priorities, while checking any existing instructions about format or number of samples. A useful question is: "Would a project showing workflow design or one showing visual design be more helpful for this role?"

You can make an initial choice before asking. Compare the responsibilities in the posting with work you can explain in detail and are permitted to share. The most recent project or the one with the most recognizable client may offer less useful evidence than a smaller project where your contribution is clear.

Identify the decision hidden in the request

"Please send your best work" leaves several possibilities open. The team might want a link to review before a call, a project to discuss during an interview, or a particular type of sample. Read the request alongside the interview invitation and application instructions before asking for clarification.

Write down the uncertainty that would change your choice:

• Does the team want to see a particular responsibility from the posting?
• Should the example show individual execution or leadership across a team?
• Is this an existing project to discuss, or a request to create something new?
• How many examples are requested, and will the team review them beforehand or during a conversation?

If the request already specifies two research case studies, use that instruction. Asking whether they would prefer a visual redesign would reopen a settled requirement. If they are asking you to produce new work, use the take-home assignment clarification guide to resolve the scope before starting.

Employer guidance can be quite specific. In its portfolio review advice for design candidates, HubSpot describes a review built around one project and a 30-minute presentation, with attention to the candidate's design choices and tradeoffs. Those are HubSpot's stated expectations for that review, not a standard format for every employer. Read the instructions for your own process.

Compare the projects before emailing

Use this worksheet for each realistic option. It is a suggested selection method, not an employer scoring rubric.

Role responsibility I want to demonstrate:
Project and available version:
My personal contribution:
One decision I can explain, including an alternative I considered:
Evidence available to show that decision:
Outcome I can support, or limitation I need to name:
Permission to share with this audience:
Reason to choose this over my other option:

Permission is a prerequisite. Do not offer restricted material while waiting to see whether the hiring team wants it. The portfolio permission guide explains how to request approval for a specific version and audience.

The following projects and roles are fictional. They illustrate how to make a choice, without implying that a particular selection will produce an interview or offer.

Example: choose for a workflow design role

Imagine a Product Designer posting emphasizing complex setup workflows and collaboration with engineers. You have three cleared projects:

1. Public launch website. You designed the typography and page layouts; the positioning was set by another designer. This offers good evidence of visual execution, but limited evidence of workflow decisions.
2. Admin setup redesign. You mapped error states, tested two recovery flows, and agreed a simpler implementation with an engineer. Screens and decision notes are available. This is a strong candidate for explaining workflow choices and implementation constraints.
3. Recent mobile concept. You made a personal prototype using fictional data. It has not been tested or shipped. It is useful for explaining a hypothesis, with limited evidence of collaboration or implementation.

Choose the admin setup redesign as your provisional lead. You can explain why one error-recovery path was rejected and how an engineering constraint changed the final design. The website's polish does not answer those responsibilities as directly.

Your clarification can now be narrow: "I plan to share the admin setup redesign because it shows complex workflow decisions and engineering collaboration. Would that be the most useful focus, or is the team prioritizing visual execution for this conversation?"

Example: change the choice when the requirement changes

Now imagine a different opening focused on brand consistency across public web pages. The same launch website becomes the stronger lead: you can show the layout system you created and explain how you applied it across pages. The admin project still demonstrates useful experience, but its strongest evidence addresses another problem.

Do not claim ownership of the website's positioning. Introduce it as "the page system I designed within an existing brand direction." A specific account of your part is more useful than implying you led everything because the project is relevant.

Example: handle a newer project with unfinished results

Suppose a Customer Education Specialist role asks for clear troubleshooting materials. Your older setup guide contains a revised troubleshooting sequence you wrote and checked with colleagues. Your newer training launch looks more substantial, but you coordinated scheduling and have no shareable writing from it.

Lead with the guide if the request is for writing evidence. Explain the confusing step you rewrote and what the review established. If you have no measured change in support volume, leave that claim out. The guide to describing work without metrics can help you state what you can actually support.

Send a choice the recruiter can route

Reply in the existing thread to the person coordinating the request. Name the role and describe the difference between your options in terms the hiring manager can assess. Avoid asking the recruiter to evaluate your entire portfolio or attaching several files just to ask which one to use.

Hi Priya,

Thank you for arranging the Product Designer conversation. I'm choosing the project for the portfolio discussion.

I can share an admin setup redesign showing error-recovery flows and engineering tradeoffs, or a launch website showing visual consistency across public pages. I led the workflow decisions on the first and designed the page system on the second.

The posting emphasizes complex workflows, so I plan to focus on the admin project. Would that best match the team's priorities? I understand the invitation requests one project; I'll use the stated presentation format.

Best,
Alex

Use only options that are ready and cleared for the requested use. If the recruiter cannot answer, ask whether they can confirm the focus with the interviewer. You are seeking direction on the evidence to present; the team may reasonably leave the final selection to you.

What if there is no clarification before the deadline?

Keep the original deadline and submission instructions. An unanswered question does not extend them. Choose the eligible project that most directly demonstrates a stated responsibility, using the worksheet to check that you can explain your own work.

Introduce the choice without pretending the team approved it:

I selected the admin setup redesign because the role emphasizes complex workflows. The case study shows the error-recovery decisions I owned and the implementation tradeoff I worked through with engineering. I can discuss the launch website as a separate example if useful.

If a required format or permission remains unresolved and prevents submission, tell the coordinator exactly what is missing and ask for direction. Do not send restricted work to meet a deadline or invent an exception to the instructions.

Once you have chosen the project, use the work-sample email guide for delivery and access checks. When reviewing a role-specific outreach draft in Personal Reach, connect your chosen example to the responsibility that made it relevant. Keep the comparison worksheet for your own preparation so you can explain that choice when the conversation starts.