Your best project is the one you cannot show.
The interesting part is in an internal document. The result belongs to a customer. The screenshot would explain everything, but it is not yours to put in a presentation.
To discuss confidential work in an interview, establish what you may share, explain that boundary briefly, and prepare the useful detail that remains. If nothing meaningful remains, choose a different example. A more dramatic story is not automatically a better one.
Separate the writing problem from the permission question
Rajan Matharu's LinkedIn discussion of confidential engineering projects raises a recognizable candidate problem: showing useful skills when project specifics are unavailable. His emphasis on explaining the process is a helpful starting point for preparation.
It does not follow that changing a name makes any example shareable. A percentage can be sensitive. So can the combination of a project date, location, and technical description.
This exercise helps you explain permitted material. It cannot determine what your agreement or organization allows you to disclose. Resolve that boundary with the responsible person before building the story around it.
Give the interviewer a useful boundary
“It's confidential” may be an accurate response. On its own, it leaves the conversation with nowhere to go.
When the scope permits it, try something more specific:
“I can't discuss the customer, internal findings, or commercial figures. I can explain how I organized the review and handled conflicting feedback.”
You have told the interviewer what the example can demonstrate. They can ask about that work, or you can agree to use another example. You have not promised access to a document you cannot share.
Only use a boundary like this when the remaining discussion is actually permitted. The phrasing itself does not make it so.
A fictional example with a clear limit
Question: “Tell me about a difficult decision you made.”
“I can discuss the review process for this project, but not the client, findings, or figures. My responsibility was to prepare a recommendation after several reviewers gave conflicting feedback. I noticed that some comments challenged the evidence and others concerned how the recommendation was written. I separated those into two lists and asked the project lead which questions needed a decision before we could proceed. The lead assigned the evidence questions to the relevant reviewers. I revised the explanation after their checks and recorded what still needed approval. We completed that review with the open decisions assigned. I can't share the recommendation itself, but I can explain why I separated those types of feedback.”
This is a fictional demonstration, assuming that the described process is permitted to discuss. It shows a decision about handling feedback, rather than substituting hidden project details with impressive-sounding numbers.
A weak version would rely on the project's secrecy to imply importance. A credible version explains a contribution. A stronger version also makes the candidate's reasoning and the observed result understandable within the stated boundary.
Prepare an alternative before you need it
The interviewer may need evidence that this story cannot provide. That does not require a lengthy debate about the missing detail.
“I can't share that part. Would an example from my public volunteer project help demonstrate the same skill?”
Choose the alternative in advance. It could come from another job, study, open-source work, or a community project. Identify the context accurately and explain what transfers. Do not present a fictional substitute as work you actually performed.
The same care applies when practicing with another person or an online tool. Use only material you are permitted to share there. You can rehearse the structure without uploading the original document or copying the private findings into your notes.
Rehearse the boundary and the decision
Use the difficult decision question. Prepare two answers: a permitted version of your first example and a different experience you can discuss more fully.
Say the boundary in one sentence, then move to the decision you owned. Ask a practice partner for a detail you have left out. Rehearse returning to the useful part of the answer without revealing that detail or becoming vague about everything else.
If the result is hard to describe, the guide to results without metrics helps you separate an observable outcome from a claim you cannot support.
Common questions
How do I discuss confidential work in an interview?
First establish what you are permitted to discuss. Explain that boundary briefly, then describe your contribution using only permitted context, actions, and outcomes. If the example cannot be explained usefully within that boundary, choose another experience.
Is removing a client name enough to make an interview example shareable?
Removing a name alone does not establish permission to share the remaining information. Dates, metrics, screenshots, and a combination of project details may still be restricted. Confirm the permitted scope rather than treating anonymization as permission.
What should I say if an interviewer asks for a detail I cannot share?
State the boundary and offer a relevant alternative: explain a permitted part of your decision process or use another example. Keep the explanation brief and direct. Do not invent a replacement number or imply that a hypothetical example actually happened.
Prepare the part of the story you can stand behind. Its value is in what the listener can understand about your work, not in what they are asked to imagine behind the restriction.
