Technical Writer (CBP)

• You can name the documents an engineer opens during an incident, and the ones they skip and why.
• You have mapped what exists against what the program is required to produce.
• You have stopped maintaining at least one thing nobody reads.

• Questions that used to route to one specific person get answered by something findable.
• New team members reach useful work without booking time with whoever holds the knowledge.
• A search for a current procedure returns the current version rather than three candidates.
• Engineers send people to the documentation instead of explaining it again themselves.

• Documents required by the contract arrive complete and on schedule.
• Reviewers ask about substance rather than returning things over format and completeness.
• Handling and marking requirements are correct before a document leaves the team.

• Updating the document is part of making the change rather than something that happens afterward, if anyone remembers.
• Content that has gone stale is visible as stale rather than quietly wrong.
• Templates and standards exist that other people follow, so quality does not depend on who happened to write it.

Preferred Experience

• You have documented technical systems you were not an expert in, and can describe how you got up to speed.
• You have worked on a federal program and know in practice what handling controlled information requires.
• You have built documentation standards that outlasted your own involvement.
• You have gotten busy engineers to contribute to documentation without having any authority over them.
• You hold an active CBP BI, a fitness determination at another DHS component, or an active DoD clearance. Any of these shortens your start date.
• You work fluently in Markdown, Confluence, SharePoint, and a standard document toolchain.
• A portfolio of documents people actually used tells us more than a certification does.