How much detail should a civil engineer give about work covered by an NDA?
By Olive Jobs · Updated August 25, 2026 · 3 min read
A civil engineer who signed an NDA still lists the project, the dates, and the role; the open question is wording the detail, not hiding the work. Describe what you'd defend in a review: discipline, structure type, the drawing sets and permit submittals you sealed or checked, with client names swapped for categories. At a remote-first company, that written version carries the whole first impression.
Keep the work on the résumé and reword the detail
An NDA-covered engagement stays on your résumé with its dates, your title, and its discipline, exactly like any other project. What changes is the noun level: a confidential client becomes a category — a utility, a logistics operator, an industrial owner — and a named site becomes a structure type. The engineering survives the swap. The identifiers don't.
Discipline does more work in civil engineering than any client name. Structural, geotechnical, transportation, and water read as near-separate professions, so a bullet that names its discipline places a civil engineer even while the owner stays generic.
The deliverable class carries the rest: a stamped drawing set, a permit submittal package, and a site inspection report each describe scope without pointing at any one owner.
Build each bullet from what a principal engineer can verify
A principal engineer reading your résumé starts with licensure, and your licence record sits with the state board that issued it, not with any client. Print that credential line in full before you spend a word worrying about protected projects. After licensure, the same reviewer wants the drawing sets and submittal packages you've actually produced, in whatever wording your agreement leaves you.
A guarded bullet can still read precisely: "Sealed the structural drawing set for a mid-rise industrial facility in a coastal wind zone, with the permit submittal approved by the local jurisdiction." Nothing in that line identifies an owner, yet it names discipline, deliverable, governing condition, and outcome.
If a phrase wouldn't survive being read aloud to the client who asked for confidentiality, it doesn't belong in your bullet.
Where doubtful NDA detail gets resolved
Your own copy of the agreement, not résumé custom, settles what a doubtful line may say. Terms differ from client to client, so a habit formed on the last project doesn't transfer to this one. Reread the language that covers the work, ask the client contact who requested confidentiality when it's ambiguous, or put the phrasing in front of a lawyer before anything goes out.
A résumé travels to a chosen reader. A LinkedIn profile is public to every client you've ever served.
Run the two at different settings — the résumé can carry your fuller guarded wording, while the LinkedIn version keeps to discipline and deliverable class alone. Neighboring calls, like how far back a work history should run, are collected at Resume Questions, Answered.
At a remote-first company
No reviewer at a company with no default office ever walks your finished site. The written record is the whole tour, and that raises the pressure to attach proof. Decide before any video interview which drawing sets you're cleared to put on a shared screen, and keep a described-not-shown answer ready for everything else.
An uploaded portfolio deserves the same caution: a permit submittal package saved to a personal drive feels like your work while carrying a client's name on the title block. Strip it, or skip it. Browse Civil Engineer jobs to see how much written evidence each posting requests before deciding what you'll prepare.
If you are senior
Once the work is assumed and the judgment is the point, the question isn't proof of drafting — it's evidence of sign-off. Write the decisions: review comments you cleared, criteria you set for a submittal package, inspection findings you escalated. Judgment travels with fewer identifiers than a deliverable does, so the guarded version of your record can still read specific.
Rewrite your most guarded bullet tonight: client reduced to a category, discipline named, deliverable spelled out. Then hand it to an engineer outside the project — if they can say what you built and what you decided, but not for whom, the detail level is right.