Discuss confidential work in an interview without revealing restricted details

Describe your permitted responsibilities, decision process and lessons—not confidential customer names, internal documents or restricted implementation details. Before practising, check what you are actually allowed to disclose. If a safe version would still reveal protected information, choose another example or explain that you cannot discuss that project.

This is editorial preparation guidance, not legal advice about an NDA, trade secrets, employment duties or disclosure rights. The worksheet cannot determine whether a particular statement is permitted. It also does not describe an InterviewRep redaction feature: you must decide what to exclude before sharing it with any person or tool.

Decide what is shareable before polishing the answer

Do not begin by copying the original project narrative into an AI prompt and asking it to remove sensitive material. That would share the material before you have decided whether sharing is allowed.

Start from the applicable rules and any approved public description. Check your agreement and organisational policies through authorised channels. Where the boundary is unclear, seek appropriate guidance before disclosing the information. An interview deadline does not resolve that uncertainty.

Then choose one of three editorial paths:

• Use an already permitted example with details you are authorised to discuss.
• Develop a higher-level version only if that version is also permitted.
• Decline the example and use a different event or a clearly labelled hypothetical explanation.

A higher-level version is not automatically safe. Removing a name may leave a distinctive combination of timing, industry, location, technology and outcome. Do not assume that a listener—or a service receiving your prompt—cannot identify the project from the remaining details.

Copy the disclosure-boundary worksheet

Complete this privately without pasting the restricted facts into the table. “Exclude customer identity” is enough; do not write the customer's name in the next cell to remind yourself.

These are questions, not clearance rules. The alternatives are conditional. A public announcement does not necessarily authorise you to disclose everything you know about the same engagement.

Keep permission separate from factual accuracy. A number can be true but not shareable. An invented replacement number can avoid the original figure while making your personal history false. Neither is a reason to include it.

Preserve useful specificity without inventing facts

All examples in this section are fictional and show editing choices, not legal approval of comparable real disclosures.

Too vague: “I worked on a confidential project and did a good job.”

Possible higher-level account, only if permitted: “I was responsible for comparing two delivery options against the team's agreed requirements. I documented the assumptions, asked the technical owner to check the dependencies and presented the unresolved trade-off to the decision maker. I cannot share the customer's identity or the commercial terms.”

The revised version is specific about actions and boundaries. It does not need a customer name, a contract value or a diagram of the system. But if those actions or even the existence of the engagement are restricted, this version is not usable either.

Overstated substitute: “I led a major transformation for a global customer and saved millions.”

Replacing confidential detail with a grander story is not sanitisation. Remove unsupported status, scale and outcomes. You can say, “I can explain my evaluation process, but I cannot discuss the engagement's financial result,” when that statement is accurate and permitted.

For a team project, also retain attribution. Do not use confidentiality as a reason to claim all the work yourself. The contribution worksheet helps separate your action from a shared result without requiring private names.

Prepare a boundary sentence and an alternative

Use language that is clear without inviting a guessing game. These are adaptable editorial examples:

“I cannot discuss the client's identity or internal implementation. I can explain the part of my decision process that I am permitted to share.”

“I do not have clearance to show that document. I have a separate public or personal-project example I can use instead.”

“I cannot confirm those details. Would a hypothetical explanation of my approach answer the skills question?”

Do not confirm a restricted fact because the interviewer guessed it. Do not offer to send the document after the call as a way around the boundary. If the question cannot be answered without disclosure, say that and move to a genuinely usable example.

Label a hypothetical answer before giving it. “Here is how I would approach that situation” is not the same as “Here is what I did.” If the interviewer needs past evidence, a hypothetical may not satisfy the requirement. Acknowledge that rather than quietly changing the type of answer.

Treat preparation tools as another disclosure destination

Consider every place the story will go: a personal notebook, a shared document, an AI prompt, a resume upload, an audio connection or a saved transcript. A decision to speak a limited version does not automatically authorise sending source material to all of those destinations.

Canadian privacy regulators' generative-AI principles recommend using anonymised, synthetic or de-identified data rather than personal information where personal information is not required for the purpose.[23] That guidance concerns personal information; it is not a blanket permission to share employer-confidential material, nor proof that removing identifiers makes a particular story safe.

The practical recommendation here is narrower: create a permitted practice version first. If you cannot do that confidently, use another example. Do not rely on a vendor name, a private browser window or an AI-generated reassurance as disclosure approval.

Use the data-sharing checklist to separate audio, transcript, resume, provider, storage and deletion questions. Those vendor questions are distinct from your authority to disclose the underlying work.

Handle requests for proof without sending restricted files

If asked to substantiate a result, explain what you can verify and what you may disclose. A reference, portfolio item or public case study is useful only if you are authorised to use it and it actually supports the claim. Do not promise that a former employer or colleague will confirm details without knowing that they can.

You may need a less impressive but fully discussable example. Keep that backup in your story bank, with a note about its limits. This avoids having to improvise a supposedly safe replacement while being questioned.

Common questions

Is changing the client name enough?

Do not assume so. Other details may still identify the work, and restrictions may cover more than names. This guide cannot clear a rewritten account for disclosure.

Can I change the numbers?

Do not invent a different achievement and present it as your own. Omit a restricted figure, use an authorised description or switch examples. Only use a range if that range is both truthful and permitted.

Can InterviewRep redact confidential content for me?

This page makes no such product claim. The editing worksheet is a manual preparation aid. Decide what may be shared before providing content to a tool.

Use only the assistance you are permitted to use

InterviewRep's public page says to use it where AI assistance and audio capture are permitted, obtain any required consent, and keep answers grounded in your experience because suggestions can be inaccurate.[16] Its live assistance guide describes the workflow, not a confidentiality clearance service.

If both the interview rules and your disclosure obligations permit the intended use, try 10 free minutes; the current public offer states no credit card is required.[16] Otherwise, keep the tool out of that interview and prepare with an example you may actually discuss.

Method: the regulator source supports only the stated personal-information principle; product statements come from current public copy. The worksheet, boundary sentences and fictional rewrites are original editorial recommendations. No contract interpretation, anonymisation guarantee or tested redaction capability is asserted.

Sources

16. InterviewRep | Live interview help, in your own words
23. Principles for responsible, trustworthy and privacy-protective generative AI technologies - Office of the Privacy Commissioner of Canada