How to discuss a confidential project in an interview
Prepare an account within your disclosure boundaries. A decision tree, worksheet and fictional dialogue show how to handle pressure and offer other evidence.

To discuss a confidential project in an interview, first establish what you may say, show and send in that situation. Prepare an accurate account within that scope and preserve the boundary when more detail is requested. If the scope is uncertain, choose another experience while seeking clarification.
Removing names does not automatically release information for disclosure. A private conversation does not establish permission either. This workflow prepares your communication; it does not interpret contracts or confidentiality agreements.
Choose evidence according to actual permission
Amazon advises its candidates to omit proprietary information when discussing previous work. That guidance concerns its own process; it cannot predict every interviewer's behavior or authorize disclosure of a particular project.
Start with the skill the question examines: comparing information, clarifying a decision or organizing a deliverable. Then choose an experience you can explain accurately. You do not need to start with the most restricted or best-known project in your history.
Check the scope of guidance received from the responsible organization. Permission to describe your role does not necessarily cover showing a screen, sending a file or citing an outcome. If uncertain, use the appropriate clarification route without copying restricted material into an external recruitment exchange.
Our STAR outline helps reconstruct context and contribution. Prepare using information you may use; do not transcribe an internal document with the intention of “cleaning it up” later.
Follow four possible routes before speaking
The University of Florida Career Connections Center recognizes that some work details need to remain confidential. This is university portfolio guidance, rather than individual permission or a universal method for removing restrictions.
Use this original decision tree. Start with: does confirmed permission cover the content, audience and means of disclosure?
| Condition checked | Route for the conversation |
|---|---|
| Description and material are authorized for this use | Present only the confirmed version and scope |
| An oral account is authorized, but files and details are not | Explain your contribution within that boundary, without attaching or opening the materials |
| The scope remains uncertain | Leave the detail out, seek appropriate clarification and use another experience meanwhile |
| No permitted account answers the question | Offer another experience or a separate personal demonstration, if the process accepts it |
Access to a file, having produced part of it or remembering its figures does not settle disclosure permission. Do not assume permission for another audience or occasion automatically extends to the current selection process.
Prepare an account with specific boundaries
Fictional case created by FoxApply. People, project, permission and dialogue are invented; they represent no customer or completed interview. Lívia wants to demonstrate how she handles conflicting instructions for an administrative role.
In this scenario, the responsible channel at her previous organization confirmed that she may describe comparing instructions in general terms, consulting the person responsible and forwarding an approved communication. The document, its contents, identifiers and metrics remain outside that scope. This confirmation belongs only to the fictional case.
One possible account is: “In administrative support, I identified a discrepancy between two instructions used to prepare a communication. I took the question to the person responsible, who decided which instruction applied. My part was preparing the approved version and forwarding it. I can explain that contribution, but cannot show the document or describe its internal contents.”
The account preserves the responsible person's decision and Lívia's contribution. It adds no error reduction, savings or leadership. The boundary does not erase her experience; it defines what she will explain in this conversation.
Before rehearsing, Lívia records categories without storing secrets in her notes:
| Field | Illustrative record |
|---|---|
| Skill | Clarifying conflicting instructions |
| Permitted account | General comparison, consultation and approved forwarding |
| Outside speech and attachments | Contents, identifiers, files and metrics |
| Basis for the check | Guidance from the responsible channel, with oral scope confirmed in the scenario |
| Prepared alternative | Another permitted experience or an identified personal demonstration |
| Next action | Preserve the boundary; clarify a new request before expanding disclosure |
Respond to pressure without expanding the scope
Continuation of the fictional dialogue. The initial question concerned how Lívia handled the discrepancy. Requests for another level of detail meet a boundary she prepared beforehand.
“Can you share your screen with the document?”
“The guidance I received does not include showing files. I can explain how I recognized the need for confirmation and my part in forwarding the communication.”
“Then just remove the company name.”
“That change would not authorize the file. I will keep the explanation within the confirmed oral scope, without reproducing the document.”
“It stays between us. What was the content, and how much did it improve?”
“I cannot discuss those details or provide a metric for that project. I can clarify my responsibility and what I forwarded within the permitted scope.”
“Without seeing it, how can I assess what you can do?”
“We could use another experience I can discuss or, if appropriate for this process, a personal demonstration with entirely invented data. Which alternative addresses the activity you need to observe?”
Lívia waits for guidance before sending anything. If the same restricted content is requested again, she maintains that boundary and consults the recruitment contact about an alternative. She does not promise to deliver a file later without confirmed disclosure permission or infer why the person asked.
Keep a demonstration separate from employment history
An alternative can start from scratch: two invented instructions for a reading club specify different registration channels. Lívia proposes showing how she would record the discrepancy and request confirmation, without assuming which instruction applies.
She identifies its origin: “This is a personal demonstration using a fictional scenario, not my employer's document or a professional outcome.” She does not reuse restricted layouts, rules or data under substituted names. If another type of evidence was requested, check whether this alternative is suitable.
Our portfolio guide develops sample creation. For an account with a requested duration, see the five-minute case presentation.
Rehearse the insistent question and check two things: did the listener understand your contribution, and did you preserve the boundary? If the account only works by exposing prohibited content, change the experience. Record the request by category and the agreed alternative, without copying restricted information.
FoxApply can compare permitted resume text with an opening. Do not submit confidential documents or information to the tool. The analysis does not verify permissions or assess this article's dialogue. Sources consulted on November 12, 2026.