Job Summary: The DLCP Technical Writer Journeyman is responsible for developing, reviewing, editing, and maintaining clear, accurate, and user-friendly documentation that supports agency operations, business processes, a…
Engineering & IT · Washington, DC
Technical Writer jobs in Washington, DC
Technical writers turn complex products into documentation people can actually use — API references, user guides, and internal docs — working closely with engineers to get the details right.
439
Open roles today
$33–$78/hr
Typical pay range
$109k
Median, full-time
3
Fresh in this list
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
01
Open technical writer roles
7 shown of 439 · sorted by freshness
by using your expertise to protect our country from threats. Job Description Transform technology into opportunity a Technical Writer with GDIT. A career in enterprise IT means connecting and enhancing the systems that m…
Technical Writer Location: On Site (DC - VACO) Department: Department of Veterans Affairs (VA) Type: Full Time Minimum Experience: Experienced Security Clearance Level: Ability to pass a background check Military Veteran…
nation’s safety and security. Make an impact by using your expertise to protect our country from threats. Job Description Technical Writer Advance how our customers operate while you advance your career. Join GDIT as a T…
Experienced FCDO Technical Writer Improving Economies for Stronger Communities (IESC) is a leading U.S. nonprofit organization that catalyzes private sector growth and creates economic opportunity for people and communit…
$85k - $141k
Job Family Technical Documentation & Writers Travel Required Up to 10% Clearance Required Active Top Secret (TS) What You Will Do Guidehouse is seeking an experienced Technical Writer – Senior to support a large-scale fe…
$88k - $122k
partners to develop lifesaving drugs, forecast supply chain disruptions, locate missing children, and more. The Role As a technical writer and editor, you’ll play a key role in helping our customers succeed by creating,…
02
What technical writers earn in Washington
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $33–$45 | $69k–$94k |
| Mid level | $45–$60 | $94k–$125k |
| Senior | $59–$78 | $122k–$162k |
Adjusted for the Washington market from national ranges.
03
What employers ask for
The skills these listings keep naming
Clear, plain-language writingDocs-as-code (Markdown, Git)API documentation (OpenAPI)Information architectureInterviewing engineersStyle guides and consistencyBasic scripting or code readingDocs tooling (Docusaurus, etc.)Editing and review workflows
04
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Walk me through your process for documenting a feature you know nothing about.
Show the sequence: use the product yourself, interview the engineers, draft, and validate with real users or support tickets. Trying the product firsthand is the key beat.
How do you decide what not to include in documentation?
Anchor on audience and task: what does this reader need to succeed right now. Cutting is the craft — show you treat concision as a feature.
An engineer gives you inaccurate or incomplete information. How do you handle it?
Verify against the product, ask precise follow-ups, and build review loops into your process. Show persistence without friction.
How do you keep documentation from going stale?
Talk about docs-as-code tied to release workflows, ownership models, feedback channels, and auditing high-traffic pages. Staleness is the industry's chronic disease — show a system.
How do you measure whether documentation is working?
Page analytics, search terms, support-ticket deflection, and user feedback. Connecting docs to reduced support load is the strongest business case.
Tell me about a doc set you restructured. What drove the changes?
Describe the user problem — findability, task mismatch — and the information architecture you moved to. Evidence of user thinking beats aesthetic preference.
05
Resume tips that move the needle
For technical writers specifically — generic advice costs you here
01
Link writing samples matched to the job: API docs for API roles, user guides for product roles — the portfolio is the interview.
02
Quantify impact where possible: support tickets deflected, onboarding time cut, docs traffic and satisfaction scores.
03
List your toolchain (Markdown, Git, Docusaurus, OpenAPI) because docs-as-code fluency is now a standard screen.
04
Show technical depth honestly — languages you can read, APIs you have called yourself — since it defines which roles fit.
05
Mention style guide ownership or editing responsibilities; they signal you raise a whole team's quality, not just your own pages.
06
Where this role goes
Typical progression
01
Junior Technical Writer
02
Technical Writer
03
Senior Technical Writer
04
Documentation Manager
Ten quiet minutes a day
Applying for technical writer jobs in Washington?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.