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.

315
Open roles today
$33–$78/hr
Typical pay range
$109k
Median, full-time
4
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

9 shown of 315 · sorted by freshness

Technical Writer

Network Designs Inc. · Washington DC · Full-time
$80k - $90k

collaboration, career growth, and winning ideas. Military Veterans Encouraged to Apply. Job Description: NDi is seeking a Technical Writer to support a large enterprise IT environment in Washington, DC. The Technical Wri…

Posted yesterday
+ Save to tracker View listing

Technical Writer - Active TS/SCI with CI Poly

ENS Solutions, LLC · Washington DC · Full-time

Creates and reviews ITD technical products for proper grammar, punctuation, and syntax, as well as for logic, clarity, and consistency. Ensures that style and format conform to agency publication standards and that langu…

Posted 3d ago
+ Save to tracker View listing

Technical Writer Undersea Systems

Anduril · Washington DC · Full-time
$117k - $154k

Our responsibilities include product operations training and adoption and user documentation. We are seeking an experienced Technical Writer to create and maintain user documentation across our diverse business lines. We…

Posted 5d ago
+ Save to tracker View listing

Technical Writer (TW) - SME

cgsfederal · Washington DC · Full-time

Technical Writer (TW) – SME Work Location: Washington, DC Employment Type: Full-Time, Expert-Level Department: Administrative and Logistics Support CGS is seeking a skilled Technical Writer (TW) – SME to support mission-…

Posted 1w ago
+ Save to tracker View listing

Technical Writer - active Top Secret required

General Dynamics Information Technology · Washington DC

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…

Posted 1w ago
+ Save to tracker View listing

Technical Writer - TS/SCI with Polygraph

General Dynamics Information Technology · Washington DC

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…

Posted 1w ago
+ Save to tracker View listing

Technical Writer

Terrestris Global Solutions · Washington DC · Full-time

? Looking for an innovative organization and the opportunity to learn and grow professionally? We can help! We are seeking a Technical Writer for the US Capitol Police (USCP) Information Resource Management Division (IRM…

Posted 2w ago
+ Save to tracker View listing

Technical Writer

MbSolutions Inc · Washington DC · Full-time

Electrical Engineering, Physics, or Mathematics. 5 Years of experience in the related field Experience:Shall explain scientific and technical ideas in simple language.Shall meet with engineers to establish technical spec…

Posted 1mo ago
+ Save to tracker View listing

FCDO Technical Writer

IESC · Washington DC

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…

Posted 3mo ago
+ Save to tracker View listing
02

What technical writers earn in Washington

Hourly first — that's how the offer arrives

ExperienceHourlyAnnual, 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.
315 Technical Writer roles in Washington Save them into one pipeline Save them into your pipeline
Start free My tracker