SS
Key Takeaways
- Almost nobody in HR, finance, operations or administration has a portfolio, which is exactly why one works.
- You do not need a website — a well-made PDF or a single page is enough.
- Confidentiality is manageable through generalisation and relative figures rather than a reason not to bother.
- Two short case studies of processes you improved is the whole thing.
- It differentiates most at the interview stage, where it gives you something concrete to walk through.
The advice to build a portfolio is aimed almost entirely at designers and developers, which leaves everyone else assuming it does not apply to them.
That assumption is the opportunity. In fields where nobody has one, a modest two-page document showing how you improved something makes you memorable in a way that a stronger resume alone does not.
This guide covers what to include when your work does not produce visual output.
Before anything, make sure the resume linking to it works — the free ATS score checker.
Why it works precisely because it is unusual
Everyone's resume looks similar in these fields. Same titles, same responsibilities, same vocabulary. A hiring manager reading twenty HR generalist resumes has very little to distinguish them.
A portfolio gives them something concrete. Not because the work is more impressive, but because you can show the shape of it rather than asserting it.
It is strongest at interview stage. When asked "tell me about a process you improved", having a documented example you can walk through — and leave behind — separates you from candidates describing something from memory.
What goes in one
The structure is the same as any case study — problem, constraint, options, decision, outcome — applied to non-visual work. See portfolio case study writing.
HR and people operations
- An onboarding process you redesigned, with before-and-after time to productivity
- A recruitment funnel you improved, with conversion figures at each stage
- A policy you wrote and how you handled the consultation
- An engagement or retention initiative and what it moved
Finance and accounting
- A reporting process you automated, with the time saved
- A month-end close you shortened, with the day count before and after
- A reconciliation error rate you reduced
- A budgeting model you built and what decisions it informed
Operations and supply chain
- A workflow you redesigned, with throughput or error rates
- A vendor process you restructured
- An inventory or scheduling problem and how you solved it
Marketing
- A campaign with targeting, channels, tests and results
- Content that performed, with the traffic or conversion behind it
- A brand or messaging project and the reasoning
Project and programme management
- A project recovered from difficulty — what was wrong, what you changed
- A stakeholder conflict resolved
- A delivery process improved
Administration and customer operations
- A support process redesigned, with response times
- A knowledge base you built and its effect on repeat queries
Handling confidentiality
The objection most people raise, and it is manageable.
Generalise the employer. "A mid-size insurance company" rather than the name.
Use relative figures. "Reduced processing time 40%" rather than absolute volumes you should not disclose.
Describe the shape, not the specifics. The structure of a problem is rarely confidential even when the data is.
Never include customer information, internal financials, personnel data or anything under NDA.
Ask your employer. A sanitised write-up is frequently permitted, and asking is safer than assuming.
If you genuinely cannot use recent work, use something older, something from volunteering, or a personal project — a spreadsheet model you built for a community organisation still demonstrates the same thinking.
The format
You do not need a website. For non-technical roles a PDF is entirely acceptable and frequently better, because you can attach it or leave it behind after an interview.
Two to four pages. One case study per page or two.
Plain and readable. Headings, short paragraphs, a simple before-and-after table or chart where it helps. This is a document, not a design exercise.
If you prefer a page online, one simple page is enough — see portfolio hosting options.
Name it properly — Ananya_Sharma_Case_Studies.pdf.
Using it
Do not attach it to applications by default. The resume is what gets screened, and unsolicited attachments add friction — see portfolio vs resume.
Link it on your resume if it is online, on the contact line.
Bring it to interviews. When asked about a process you improved, you have a documented example rather than a recollection — and offering to leave it behind is memorable.
Send it as a follow-up. After an interview where a relevant topic came up: "You asked about onboarding — I've attached the write-up of the redesign I mentioned."
Mention it in a cover letter where one is expected.
Common Mistakes
Assuming portfolios are only for creative and technical roles. In fields where nobody has one, a modest document differentiates far more than it would in design.
Not building one because of confidentiality. Generalising the employer and using relative figures resolves it, and employers frequently permit sanitised write-ups when asked.
Over-designing it. This is a document demonstrating thinking, not a design exercise — plain and readable is correct.
Describing responsibilities rather than a change. The point is a before-and-after, not a job description in longer form.
Omitting the numbers. A process improvement without a measure is an assertion.
Attaching it to every application. The resume is what gets screened; the portfolio belongs at interview stage or as a follow-up.
Making it eight pages. Two to four, one case study per page or two.
Waiting until you have something impressive. A modest, well-documented improvement beats an undocumented significant one.
Frequently Asked Questions
Do non-technical roles really need a portfolio?
Not expected, which is exactly why one works. In HR, finance and operations almost nobody has one, so a short document of documented improvements stands out.
What if my work is confidential?
Generalise the employer, use relative rather than absolute figures, and describe the shape of the problem. Ask your employer — sanitised write-ups are frequently permitted.
Do I need a website?
No. A well-made PDF of two to four pages is entirely acceptable and often more useful, because you can attach it or leave it behind.
What should each case study include?
The problem, the constraint, what you considered, what you did, and the measurable outcome — the same structure as any case study.
When should I share it?
At interview stage or as a follow-up, not attached to every application. The resume is what gets screened.
What if my improvements were small?
A modest improvement documented well beats a significant one you can only describe from memory. The thinking is what is being assessed.
Can I use volunteering or personal work?
Yes, particularly if recent employment is too sensitive to write about. The reasoning it demonstrates is the same.
The resume still gets you the interview. Check your ATS score free.
Make This Practical
Pick two things you improved at work and write them up as a page each — the problem, the constraint you worked within, what you considered, what you did, and the measurable before-and-after. That document is the whole portfolio, and it takes an afternoon.
Then solve the confidentiality problem rather than accepting it as a blocker. Generalise the employer, use relative figures instead of absolute ones, describe the shape of the problem rather than the data, and ask your employer whether a sanitised version is acceptable.
Finally, use it at the right moment. Do not attach it to applications, where the resume does the screening — bring it to interviews so that "tell me about a process you improved" has a documented answer you can walk through and leave behind.
See what your portfolio could look like
This theme is built straight from your resume — pick one and your portfolio is live in minutes.
Was this guide useful?
Be the first to rate it.
