Help me plan and write a portfolio website for [TARGET ROLE] applications. My background and real work are below. The site should persuade [PRIMARY AUDIENCE] while accurately representing my contribution. Experience and project evidence: [EXPERIENCE NOTES] Target role or job requirements: [ROLE REQUIREMENTS] Available assets and links: [AVAILABLE ASSETS] Constraints and boundaries: [CONSTRAINTS] Ask up to 3 clarifying questions only if a required input is missing. Otherwise, create a portfolio package with:
1. A positioning statement of 20 to 30 words that connects my strongest relevant capability to the target role without inflated titles or claims. 2. A sitemap for a focused one-page or small multi-page portfolio, explaining the purpose of each section and its order for a recruiter or hiring manager. 3. A recommendation for which 2 to 4 projects to feature, with the role requirement each one demonstrates and any evidence gap it leaves. 4. A case-study outline for each selected project: context, problem, my role and collaborators, constraints, decisions, execution, outcome, and reflection. State what artifacts to include at each stage. 5. Draft homepage copy: headline, 50-word introduction, project-card summaries of 35 to 50 words, and a contact call to action. 6. A checklist of claims or metrics that need evidence before publication. Do not invent results, client names, awards, team sizes, confidential details, or personal responsibilities. If a project was collaborative, distinguish my work from the team’s. Recommend anonymizing or omitting confidential material rather than revealing it. Before answering, self-check that every featured project supports a target-role requirement and that every outcome claim is traceable to my notes or labeled as unavailable.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [TARGET ROLE] | Enter the specific role or role family you are pursuing. | Senior product designer at a B2B SaaS company |
| [PRIMARY AUDIENCE] | Identify who will review the portfolio, such as recruiters, hiring managers, or prospective clients. | Product design hiring managers and internal recruiters |
| [EXPERIENCE NOTES] | Paste your real projects, responsibilities, outcomes, collaborators, and relevant career background. | Four years at Ledgerline. Led onboarding redesign with a PM and two engineers; ran six interviews; created a prototype and design specs; activation rose from 41% to 53% over one quarter. Also redesigned invoice approvals and built a component library. |
| [ROLE REQUIREMENTS] | Paste requirements from target job postings or describe the capabilities employers seek. | Job posts emphasize end-to-end product design, B2B workflow complexity, research, cross-functional collaboration, and design systems. |
| [AVAILABLE ASSETS] | List screenshots, prototypes, documents, links, testimonials, and work samples you may share. | Before-and-after onboarding screens, redacted Figma prototype, research synthesis, approval-flow screenshots, component-library documentation. |
| [CONSTRAINTS] | State confidentiality limits, time available, preferred platform, and any accessibility or technical requirements. | Cannot name customers or show production financial data; build in Framer over two weekends; meet WCAG AA color contrast. |
How to use
- Paste two or three actual job descriptions so the site plan reflects the roles you will apply for.
- Include your contribution, collaborators, and evidence for each project before asking for copy.
- Check every result metric, ownership statement, and confidential artifact against what you can substantiate or publish.
- Follow up with: "Draft the full case study for [PROJECT] in 700 words, leaving [MISSING EVIDENCE] as a clearly marked placeholder."
Variations
Case study writer
Use when one project is selected and you need a credible narrative for it.
Write a portfolio case study for [PROJECT] aimed at [TARGET ROLE]. Facts I can support: [PROJECT NOTES]. Assets I can show: [ASSETS]. Use 600 to 850 words with sections for context, problem, role, process, key decisions, outcome, and reflection. Make my individual contribution distinct from team work, and connect decisions to evidence or constraints. Mark any missing metric or artifact as [NEEDS EVIDENCE] instead of guessing. End with a suggested image-caption list. Self-check that no claim exceeds the notes and that the narrative demonstrates the target-role capability.
Portfolio homepage
Use when you need concise copy and structure for the top-level site.
Create homepage copy and structure for a [TARGET ROLE] portfolio. Background: [CAREER NOTES]. Featured projects: [PROJECT FACTS]. Audience: [AUDIENCE]. Give a 25-word headline, 60-word introduction, three project-card summaries of 40 words each, an about-section outline, and a contact call to action. Explain the recommended section order. Use concrete evidence, not adjectives such as passionate or innovative. Do not invent outcomes or responsibilities. Self-check that each project card establishes context, contribution, and a reason to click.
Career pivot portfolio
Use when your past experience must be reframed for a different target role.
Plan a portfolio for moving from [CURRENT FIELD] to [TARGET ROLE]. Transferable experience: [EXPERIENCE]. Target-role requirements: [REQUIREMENTS]. Work samples available: [ASSETS]. Identify the strongest credible bridge between the fields, choose projects or exercises to feature, and propose a sitemap plus a 90-day evidence-building plan for gaps. Clearly distinguish completed work from practice projects. Do not portray a self-directed exercise as client work. Self-check that the positioning statement makes a truthful transition case without overstating prior experience.
Tips
- Select projects for relevance and evidence, not simply prestige; a smaller project with clear decisions and outcomes often makes the stronger case study.
- Name your exact role in collaborative work, including who made the final decision and what you personally delivered.
- Show enough process to explain decisions, but lead with the problem and outcome so a reviewer can scan quickly.
- Use redacted artifacts only when the redaction still lets a reviewer understand the problem, design choices, and result.
FAQ
How many projects should a portfolio include?
Two to four strong, relevant projects are usually more useful than a long archive. Choose projects that together cover the core requirements of your target role.
Can I include confidential client work?
Only with permission and appropriate redaction. If the story cannot be understood without sensitive details, describe the challenge at a high level or choose another project.
What if I do not have measured outcomes?
State the work and decision honestly, then use available evidence such as usability findings, adoption feedback, or a reflection on what you would measure next.