How to Show Engineering Work When the Code Is Private
You can describe private engineering work only within the boundaries of your confidentiality obligations: check your agreement, ask about uncertain details, and focus on an approved description of your contribution rather than sharing code. This is not legal advice.
To show software engineering work under an NDA, check your agreement before sharing anything, then describe the problem, your contribution and an approved outcome without exposing protected details. Keep your GitHub linked, but add evidence from people and records so public code isn’t your only way to explain your experience.
Your strongest engineering work may sit in a repository you cannot share. That doesn’t leave you with nothing to discuss. The useful task is to separate evidence of your contribution from the company’s implementation—and check the boundary before publishing.
Can you put NDA or private-repo work in a portfolio?
You may be able to include a limited description, but check your agreement rather than assuming what it permits. Treat code, data, customer identities and unreleased plans as details requiring particular care. Ask the appropriate person when a detail is uncertain. This guide is not legal advice.
Start with the question you actually need answered: can you publish this particular description? Permission to name an employer doesn’t necessarily answer whether you can describe a client engagement, an incident or a system’s architecture.
If you’ve already written careful CV bullets, you’ve done useful groundwork. Review those descriptions before expanding them into project entries. A longer explanation can introduce details the original bullet avoided.
A practical request for clarification could be:
I’d like to describe my contribution to this project in a job application without sharing code, customer information or internal documents. Could you review the proposed wording and confirm what I’m permitted to share?
Send the proposed wording rather than asking for blanket approval of a portfolio. Keep the response with your application notes, and seek qualified advice if your obligations remain unclear. This approach applies whether you’re applying in Australia, Canada, New Zealand, the UK, Ireland or the USA; don’t assume a local CV convention settles a confidentiality question.
What are you allowed to say about confidential work?
Start from material already public, then check whether you may describe your own part in general terms. Consider describing the system by type rather than name. If a metric is sensitive, ask whether an approximate or relative version is permitted; changing its format doesn’t automatically make it safe to publish.
A public product page or engineering talk can help you identify a starting point. It isn’t blanket permission to explain the internal implementation. Likewise, a public job advert naming a technology doesn’t establish that you can identify every system using it.
Use this table as a review aid, not a statement of what your agreement allows. Even the descriptions in the opening column need checking against your obligations.
| Usually safe to describe | Check your agreement first | Leave out |
|---|---|---|
| General role description, if permitted | Employer or client identity | Unapproved source code |
| Broad problem category, if permitted | System architecture and dependencies | Customer data and credentials |
| Your contribution in approved terms | Exact, approximate or relative metrics | Unapproved internal screenshots |
| Already-public skills, if permitted | Colleague names and endorsements | Confidential incident records |
| Approved qualitative outcome | Diagrams and technical details | Protected unreleased plans |
A common, easy-to-fix mistake is assuming that anonymising a project removes every concern. A distinctive combination of industry, incident and infrastructure can still reveal what you’re discussing. Read the entry as a whole, not just as separate sentences.
If you can’t obtain approval for a measurement, describe the outcome qualitatively. A clear, permitted explanation is more useful than an impressive figure you shouldn’t disclose.
How do you show backend work with no UI?
Describe what the system had to survive: load, failure, cost, latency or a deadline. Use a compact explanation and, when permitted, a defensible measurement. The aim is to make your engineering judgement understandable without requiring a reader to open a repository or see a screen.
Instead of looking for a screenshot substitute, look for the decision that made the work difficult. What constraint shaped your approach? What alternative did you reject? What did you personally change?
You could build the explanation around:
- The constraint: a dependency could become unavailable during processing.
- The decision: separate processing from the immediate request path.
- Your contribution: implement retry handling and document recovery behaviour.
- The outcome: explain the approved improvement and how you assessed it.
These are illustrative prompts, not claims to copy into your history. Use only details that match your actual work and that you may disclose.
From the recruiter’s side, the entry needs to make your relevance legible. From the engineering interviewer’s side, it needs to give them a decision they can ask about. Naming a stack helps orient the reader, but explaining why you chose an approach gives the conversation somewhere to go.
Keep your GitHub and link it. If you want a public demonstration, consider an independently built example of the same general skill—not a reconstruction of a confidential system. Use your own code and synthetic data, and check any applicable restrictions before publishing.
What counts as proof when nobody can read the code?
Useful evidence gives a reader something to check beyond your own summary: a named endorsement tied to the role, an independently confirmed employment record, issuer-verifiable credentials, a permitted measurement and a clear explanation of your decisions. These support different parts of your story; none needs to expose the code.
Match the evidence to the claim. A certification can support a credential claim, but it doesn’t establish that you led a migration. A former colleague can describe work they witnessed, but shouldn’t be asked to endorse responsibilities they didn’t observe.
For an endorsement, ask about the contribution rather than requesting general praise:
Would you be comfortable describing the work you saw me do on this role, especially my contribution and what changed? Please leave out anything confidential, and only include details you’re happy to stand behind.
Ask permission before publishing someone’s identity or words. Give them room to decline or suggest safer wording.
For a measurement, prepare the explanation behind it. What did you measure? What was the comparison? Was it production behaviour, a test result or an estimate? What else changed? If the supporting records are confidential, don’t upload them as evidence; explain only what you’re permitted to discuss.
According to Wipperoz’s Virtual CV product information, its endorsements attach to a specific role and display the endorser’s name, title and verified work-email domain. That makes the attribution visible; it shouldn’t be described as independent verification of every statement in the endorsement.
The same source describes a video introduction of up to 60 seconds. If you use it, focus on the problem, your decision and the approved result rather than reading your CV aloud.
How do you write a project entry for private work?
Give each element its own short sentence: the problem, your contribution, the scale, the result and the stack. Keep protected details out, and use only approved measurements. The reader should understand what was hard, what you personally did and what evidence you can discuss in an interview.
Copy this structure into your draft. The brackets are prompts to replace, not gaps that require invented detail.
| Element | Copy-and-paste template |
|---|---|
| Problem | [Permitted system description] needed [business or technical outcome] under [approved constraint]. |
| Contribution | I [built, led or contributed to] [specific permitted work], owning [your actual responsibility]. |
| Scale | The work involved [approved workload, operational scope or qualitative context]. |
| Result | [Approved outcome], assessed through [permitted measurement method]. |
| Stack | [Technologies you may disclose], used for [relevant purpose]. |
Here’s an illustrative rewrite of a vague backend entry. It contains no performance figures because those should come from your own permitted evidence.
Make private backend work understandable
The stronger version names a contribution and sets a clear boundary. It doesn’t claim ownership of the entire system or imply an outcome the writer hasn’t established.
To complete the entry, add approved scope, stack and outcome details from your actual work. If you don’t have permission to disclose a result, say what you can explain rather than filling the gap with a vague superlative.
Before publishing, use this review:
Before you publish the project entry
What do you say if an interviewer asks to see the code?
Explain that you can’t share your employer’s confidential code, then offer a permitted alternative: a generic design discussion, a fresh exercise in the same technical area or an independent public project. Keep the boundary clear without making the conversation stop at a refusal.
You might say:
That implementation is confidential, so I can’t share it. I can explain the general problem and trade-offs within what I’m permitted to discuss, or work through a fresh example in the same technical area. I can also show you my public work.
Prepare that alternative before the conversation. If a generic diagram is permitted, draw it from scratch without copying an internal document. Avoid production identifiers, real customer data and details that would reconstruct protected architecture.
Another common mistake is treating screen-sharing as less consequential than sending a file. Don’t open a private repository, dashboard or incident report to demonstrate experience unless you have explicit authority to do so.
If the interviewer needs more detail than you can provide, ask what skill they’re trying to assess. Could you demonstrate failure handling in a fresh exercise? Could you discuss how you’d evaluate a migration plan? That keeps the discussion focused on capability rather than access to someone else’s material.
Where should all of this live?
Keep the permitted evidence together, next to the rest of your professional record: the role, its project description, supporting endorsements and your explanation. A Virtual CV can be part of that presentation, while a PDF remains useful when an application form requests a file. Keep your public code linked too.
Choose a presentation you can maintain rather than building a separate website simply to have one. Make it easy to connect a project to the role where you did it, and distinguish personal work from employer-owned work.
For the product-specific options, Wipperoz’s product information describes role-linked endorsements, a short video introduction and an ATS-safe PDF export. Review the exported file before sending it, just as you’d review any application document.
If the format is unfamiliar, what a Virtual CV is gives you a starting point. For the file-based side of applications, see how an ATS filters resumes.
Start with a project you can describe safely: draft the entry, check its disclosure boundaries and ask someone who witnessed the work whether they’d be comfortable supporting it. Bring the permitted evidence together with Virtual CV, free to start.
Common Questions
Do I need a portfolio website as a backend engineer?
You can present your experience without building a separate website. Put permitted project descriptions, supporting evidence and your GitHub link somewhere accessible alongside your CV.
Is it a problem that my GitHub is nearly empty?
Don't rely on GitHub alone to explain your experience. Keep it linked, and supplement it with permitted descriptions of your contribution and evidence from people who witnessed the work.
Can I name the company I worked for?
Check your agreement before naming an employer or client in a confidential project description. If you're unsure, ask the appropriate person to review the proposed wording.
Should I blur a screenshot of an internal tool?
Don't assume blurring makes an internal screenshot suitable to share. Check your agreement and obtain permission; otherwise, use an approved written description or a permitted generic diagram.
Can I ask a former colleague for an endorsement?
Ask someone who directly observed your contribution and give them room to decline. Request a specific, non-confidential account of your work and confirm permission before publishing their words or identity.
See Also
Some professionals use virtual CV platforms to combine structured work history with a video introduction and a shareable link, alongside an optional PDF download. Others get creative with their digital CVs by designing mock-up Facebook profiles to showcase their careers or using infographic-style visuals to highlight skills and experience. These innovative approaches not only make a digital CV more memorable but also allow you to present your strengths in a visually engaging way, helping you stand out from the crowd.