Confidential Work in Your Interview Portfolio: What Can You Show?

Your strongest work may live in a private dashboard, an internal training course, a client campaign, or a system you cannot show. When an interviewer asks for a portfolio, the useful question is: what evidence can you share that demonstrates your judgment and contribution?

A good answer combines an accurate account of your experience with material you are permitted to present. You can explain a difficult decision, show an independently created demonstration, and be precise about the difference between that demonstration and your employment history.

Before you send a portfolio

• Ask which skills the interviewer wants to assess and whether a new demonstration or verbal walkthrough is acceptable.
• Check your agreements, employer policies, ownership, and any permission covering the exact material and audience.
• Choose one shareable example that exposes a decision, an alternative, and a limitation.
• Label fictional data, independent demonstrations, team contributions, and unmeasured outcomes clearly.
• Review the final file, speaker notes, links, and screen-sharing setup before the interview.

Resolve permission before choosing the format

A password, a private call, or a different company logo does not establish permission to disclose information. Neither does the fact that you personally created the work. The U.S. Copyright Office explains work made for hire, and WIPO explains trade-secret protection and confidentiality. These are different issues; a missing NDA is not a complete answer to either.

Check the actual terms that apply to you. If they are unclear, ask the appropriate owner or obtain qualified advice for your jurisdiction. This guide helps you prepare evidence; it cannot determine whether a particular disclosure is permitted. While permission is unresolved, choose different material rather than treating anonymization as clearance.

When requesting permission, make the request narrow: “May I use these two approved screenshots in a private interview presentation? I would describe my contribution, omit customer information, and would not distribute the source files. Please confirm any restrictions on recording or retention.” Use the authorized channel, and do not move restricted files to a personal account just to make the request.

Choose an evidence route

A fresh demonstration should answer the hiring team's question. If they want to assess instructional design, show a learning objective and an exercise that tests it. If they want analysis, show how a decision follows from data. If they want engineering, show a small working behavior and its failure cases. Elaborate branding rarely substitutes for the skill they are trying to evaluate.

Worked example: replace a restricted course with a useful demonstration

Fictional example: Mira is an instructional designer. Her best project is an internal employee-onboarding course. She cannot share the course, its screenshots, or its assessment data. The interviewer wants to see how she turns a confusing process into useful instruction.

Mira asks whether an independent sample is acceptable. With agreement, she creates the following job aid and exercise from a blank document. The community center, rules, requests, and people are invented. She does not adapt her employer's course or export its assets.

Sample job aid: select a room for a booking request

Learning objective: given a request, identify missing information and select a room that meets the stated capacity rule, or explain why no room can be selected.

• The Small Room holds up to eight people; the Large Room holds up to twenty. Choose the smallest room that fits, regardless of the requester's initial choice.
• A request needs a date, start time, attendance count, and contact person. Count everyone attending, including organizers.
• Attendance must be a positive whole number. Zero, negative numbers, fractions, and nonnumeric values need correction.
• This exercise checks required fields and capacity only. Supplied dates, times, and contacts are otherwise valid. Availability and other booking checks happen separately; selecting a room does not confirm a reservation.

Apply the table from top to bottom and stop at the first matching row. After information is corrected, start again. This makes the action clear when a request has more than one problem.

Learner exercise: decide the next action

For each fictional request, write the next action and the rule supporting it. All requests have a valid date, start time, and contact except where a missing field is listed. No availability check has occurred.

Answer key: A: select Large; twelve exceeds eight. B: select Small; eight fits, and the rule chooses the smallest suitable room. C: select Large; twenty is allowed. D: neither room; twenty-one exceeds both capacities. E: request a positive whole-number count; do not round 7.5. F: first request the missing start time and contact. Once supplied, the zero count still needs correction before room selection. None of these answers confirms a booking.

Check understanding: ask the learner to explain why A's requested room changes, why C fits but D does not, and why F needs another check after its missing fields arrive. If they choose the right room but promise a reservation, revisit the difference between capacity selection and availability.

A short presentation script

“My employment work is restricted, so this is an independent demonstration with fictional rules and data. The task is to select an appropriate room or identify why the request cannot proceed. I used an ordered table so missing information and invalid counts are resolved before room selection.

“Request A gives us a concrete test: twelve people cannot use the Small Room, so the learner must change the selection. F tests whether the learner follows the sequence instead of guessing from the count. The answer key exposes both the decision and its reason.

“I have not evaluated this sample with learners. I would observe whether they complete the exercise without help and explain the boundaries, then revise instructions that cause confusion. This demonstrates my current approach; it does not establish results from my former employer.”

Adapt the structure to your discipline: a small artifact, explicit rules, a task someone can attempt, and an honest explanation of what it demonstrates. Do not present this supplied sample as work you independently invented.

Keep the real project story specific

Confidentiality can make candidates overcorrect into statements such as “I worked on important projects and improved the process.” That leaves the interviewer little to assess. Prepare the shareable parts of a story in advance:

• Problem: what kind of difficulty were people experiencing?
• Your responsibility: what did you personally own, and what did colleagues own?
• Decision: what options did you consider, and what constraint shaped your choice?
• Evidence: what permitted observation supports the outcome?
• Learning: what would you change next time?

Use only facts you can share. A result does not need an invented percentage. An approved qualitative outcome can be meaningful: a team adopted the document, an agreed review was completed, or an error was corrected. If even those details are restricted, say so and move to the independent demonstration.

Do not automatically replace an exact confidential metric with a rounded one. The magnitude, direction, customer segment, or combination of details may itself be sensitive. Permission determines what belongs in the story.

Respond when the interviewer asks for more

“Can you send the original deck?” “I cannot distribute that material. I can send the approved demonstration we discussed, including its assumptions and limitations.”

“Could you just hide the customer name?” “The restrictions extend beyond the name. I can explain the decision using a separate fictional example.”

“How do we know you did the work?” “I can walk through my responsibilities, the alternatives I considered, and the follow-up questions you would expect someone doing that work to answer. If another assessment would help, could we agree on a bounded exercise using your supplied or public material?”

If the process requires evidence you cannot provide, clarify that before building a large portfolio. You may be able to agree on an alternative; you may also find that the process is incompatible with your obligations. Avoid promises that you will obtain permission when you do not control that decision.

Rehearse the explanation and inspect the artifact

Practice with the documentation and knowledge-sharing question. Give a two-minute answer using only permitted facts. A listener should be able to identify the audience, your contribution, and how you checked usefulness. Then answer how feedback changed a project, explaining one revision and the reason for it. These public practice prompts may show additional account or subscription requirements for some site features.

For a final rehearsal, let someone interrupt with “Why that option?” and “What did you personally do?” Your response should add useful detail without crossing the boundary you set. Use the clear interview answers guide if the explanation becomes lengthy.

Inspect the actual file you will share. Check notes, comments, hidden slides, embedded attachments, screenshots, file properties, and link destinations. Open it as the recipient would. For a live demonstration, share only the intended window and close unrelated material. If you discover restricted content, stop sharing and follow the relevant reporting process.

Sources and scope

This guide addresses a recurring problem raised in public discussions: an instructional designer unable to show proprietary work, September 25, 2026, and a remote video editor facing portfolio restrictions, September 26, 2026. These are individual accounts from different work contexts, including a Philippines-focused community. They establish the practical question, not the legal answer or its prevalence. The examples and preparation steps above are original guidance.