What a career change
portfolio should include.
A career change portfolio should lead with the transferable skills that actually carry from your old field into the new one, backed by a short line on why you are switching, then a small set of bridge projects, courses, or volunteer work you did on purpose to get into the field, with your prior job titles reframed in the target field's language and pushed further down the page. It should read as one person moving deliberately toward a new direction, not two unrelated careers stapled together. Below is the full list of what to include, the terms a target-field hiring manager searches, and which Portfolio designs put the bridge work first.
The sections a career changer needs.
A career changer is hired on evidence that they can already do the new job, not on the job title they used to hold, so the portfolio has to supply that evidence directly. Work through these in order, and read the flagged block twice.
The why, in one line
A short, honest reason for the move near the top of your about section. "I spent six years teaching and moved into UX because the part of teaching I was best at was watching where a lesson confused people, then redesigning it" tells a hiring manager more than a paragraph of justification.
Transferable skills, named and mapped
Do not just claim "transferable skills." Name the specific skill from your old field and the specific place it shows up in the new one. A sales quota holder already does stakeholder management and pipeline forecasting, which are also product manager skills, so say that directly rather than hoping the reader connects it.
Bridge projects, courses, and certifications
The work you did specifically to enter the new field: a certificate, a bootcamp, a self-directed project, freelance or volunteer work in the target domain. This is the strongest section on the page, because it is proof you did not just decide to change fields, you started doing the new work.
Prior titles, reframed
Rewrite what you did in your old job using the target field's vocabulary. A classroom teacher who built curriculum, ran usability-style feedback loops with students, and managed competing stakeholder needs from parents and administrators can describe that work in terms a UX or product hiring manager recognizes.
Target-field tools and terms
List the specific tools, methods, and vocabulary of the field you are moving into, and only the ones you have actually used. A hiring manager scanning for domain fluency needs to see the right nouns, not just a general claim of enthusiasm.
A short narrative that ties it together
One tight paragraph, not a full career retrospective, that connects the old field, the deliberate bridge work, and the target role into a single line of reasoning. The goal is for a reader to finish it and think "that makes sense," not "that's a lot to explain."
Leave out: the old career at equal weight
Do not give your prior field the same space and prominence as the new one. A page that spends half its length on a career you are leaving reads as unfinished, not honest. Compress the old-field history into a line or two and let the bridge work and transferable skills carry the page.
Also leave out apology or over-explaining the gap, and jargon that only makes sense inside your old field. "I know this is unconventional, but" undercuts you before the reader has even judged the evidence. State the move plainly and let the bridge projects do the persuading.
Terms a target-field recruiter searches.
A recruiter filling a role in your target field searches for that field's terms, not your old title. If these are true of you, use the exact words, because a system indexes the words you wrote, not the story behind them.
Paste your resume into the free ATS score checker with a real job posting in your target field to see which of its exact terms your resume is missing.
Which designs suit a changer's story.
A career changer's page has one job: get the bridge work and transferable skills in front of the reader before the old job titles register. Of the 60 Portfolio designs and 48 resume layouts, these are the shapes that do it.
Pick a design that opens on your bridge projects and skills, not a chronological work history. The reader should see what you can do in the new field before they see what you used to be called.
Of the 48 resume layouts, choose a single-column one and tune the wording to your target field's keywords. A two-column resume can scramble when an applicant tracking system parses it, and a career changer cannot afford a parsing failure on top of an unfamiliar title.
Order the page so certifications, bridge projects, and mapped skills come first, and the old-field job history sits lower, compressed. A reader forms their first impression from what is above the fold, so put your best target-field evidence there.
Write about the switch as a deliberate decision, not something to justify. A design with a clean, direct about section supports that tone better than one built around a long personal story.
Who a career changer portfolio is not for.
A portfolio earns its keep when it solves a real problem: a resume that shows the wrong titles for the job you want. Read this before you spend an evening building one.
Worth building if you
- +Are switching fields entirely and your resume's job titles do not match the roles you are applying for.
- +Have completed at least one deliberate bridge project, course, or certification in the target field.
- +Can name concrete transferable skills with real examples, not just the word "transferable."
- +Want a matched cover letter to carry the narrative a resume's format cannot hold.
Skip it, for now, if you
- −Are making a lateral move within the same field. A normal resume already shows the fit and a portfolio adds little.
- −Have not started any bridge project yet. Build one first, then build the page around it.
- −Are targeting a field that hires strictly on a licence or exam you have not passed yet, such as law or accounting. Pass that gate first.
- −Are applying only through a portal that never surfaces an external link. Fix the resume for that system first.
Questions career changers ask.
Straight answers on framing, gaps, and whether the effort is worth it.
Do I actually need a portfolio to change careers?
You need something that shows evidence beyond your old job title, and a portfolio is usually the most efficient way to do that. If your resume already lists a role or a certification in the target field, a strong resume alone can work. If your titles are all from a different field, a portfolio gives a hiring manager somewhere to see what a resume's job-title line cannot show.
How much should I explain the career change?
One short, direct line, not a paragraph of justification. State the move and the reason plainly, then let the bridge projects and transferable skills do the persuading. Over-explaining reads as uncertainty, even when the reason for the switch is a good one.
What if I have no paid experience in my target field?
Build at least one project, however small, before you build the portfolio around it: a real deliverable, a course capstone, freelance work, or volunteer work done in the target domain. A page with genuine bridge work outperforms a page that only lists intentions.
Should I include my old career in detail?
Include it, briefly. Compress the job history into a line or two per role and describe it using target-field vocabulary where it is honestly accurate. The old career should support the story, not compete with it for space.
Will an applicant tracking system understand my old job titles?
Not on its own. A system matches the words on the page against the words in the posting, so if your resume only has old-field titles, it will not surface target-field keywords. Rewrite your accomplishments using the vocabulary of the role you want, in addition to your actual former title.
Where to go next.
Build the site, test your resume, or read how the paste-a-resume flow works.
Turn your career-change
resume into a site.
Paste your resume and Portfolio drafts a site in about a minute. Bridge projects and transferable skills up front, old-field history compressed lower, published to your own domain with TLS handled for you.