Career / Recruiter Evidence
How to Evaluate a Business Analyst or Product Owner Portfolio: What Evidence Actually Means
I have seen the portfolio screen from both sides. The recruiter side: 60 candidates, a CV with the same five bullet points, and 45 seconds to decide whether to call. The candidate side: trying to prove I can do the work without leaking a client name. This is a guide for the person doing the screening — written by someone who has tried hard to make their own portfolio easy to read.
Stop looking for screenshots. Look for decisions.
A polished screenshot of a backlog tells you the person can take a screenshot. It does not tell you whether they would have caught the regulatory exception that broke the last release. The evidence you actually want is in the language: what was unclear at the start, what options existed, what tradeoff got made, what changed because of that tradeoff.
Read a case study with one filter: where is the moment a decision had to be made? If there is no moment, it is a deliverable summary, not evidence. A good practitioner cannot help themselves — the decision is the thing they want to talk about.
Live tools are worth more than slides
If a candidate has built a working tool you can open and try, that is the strongest signal you will get short of a private reference. A tool forces them to choose what to ask the user, how to structure the input, what to do with edge cases, and what output is worth showing. Every one of those choices is the work.
Open it. Type in a real example from your current project. If the output is something you would actually send to a stakeholder, the candidate is showing you how they think. If it is decorative, you have your answer too.
Confidentiality is not a red flag — it is a green one
I have read portfolios that publish a client name, a project value, and a logo wall. None of that is appropriate for regulated work. The strong candidates are the ones who can show the method without violating the trust their previous client gave them. Anonymised case studies. Composite patterns. Reasoning visible, names not.
When you ask for private references later in the conversation, see what shows up. The candidate who says “here are three people you can call, here is what each of them can speak to” is the same one who will protect your company’s confidentiality when they move on.
Match the evidence to the actual role — not the job description
Job descriptions are written by committee and end up listing everything. The real role usually has one shape. Discovery-heavy roles need stakeholder framing and ambiguity comfort. Delivery roles need acceptance criteria, dependencies, release judgment. Regulated roles need controls and exception paths. Greenfield product roles need the willingness to throw work away.
Look at the portfolio with the actual shape of the role in your head, not the bullet list HR wrote. The evidence either lines up or it does not. A great candidate for one of those shapes can be the wrong candidate for another.
How I built this site for the person on your side of the table
Everything here is structured so a recruiter can move fast. The hire page has the role fit, availability, and CV without scrolling. The portfolio shows method, not client names. The tools page lets you test the thinking in three minutes before you decide to schedule a call. Recommendations are public on LinkedIn. References are private until the conversation is serious.
That is the standard I held myself to: the proof should be visible before the conversation, so the conversation can be about your actual problem — not about whether I can do the work.