Job Summary: The Full Stack Developer will focus on modernizing ETL processes, migrating data, implementing database solutions, and developing backend application functionality. This role involves working with .NET/C#, O…
Engineering & IT · Richmond, VA
Technical Writer jobs in Richmond, VA
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.
23
Open roles today
$26–$62/hr
Typical pay range
$87k
Median, full-time
10
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
11 shown of 23 · sorted by freshness
$70.24 per hour
dynamic engineering or testing environment with evolving requirements. Excellent communication and collaboration skills across technical team Job Type & Location This is a Contract position based out of Richmond, VA. Pay…
participate in peer review, defect resolution, performance tuning, demos, UAT support, and release hardening. Maintain source code and technical documentation in DEQ GitLab using team standards. Minimum / Required Profil…
Job Summary: The Senior Full Stack Developer (.NET / Vue) will lead the design and development of user-facing applications, APIs, validation workflows, reporting modules, and integration components. This role requires ex…
$102.5k - $170.9k
integrate, transform, and operationalize enterprise dataCollaborating with cross-functional teams to define requirements, resolve technical issues, and deliver scalable solutionsApplying DevOps and statistical programmin…
$179.4k - $204.7k
NoSQL databases, Container Orchestration services including Docker and Kubernetes, and a variety of AWS tools and services Provide technical leadership and direction across Agile teams, setting standards for design, deve…
$197.3k - $225.1k
NoSQL databases, Container Orchestration services including Docker and Kubernetes, and a variety of AWS tools and services Provide technical leadership and direction across Agile teams, setting standards for design, deve…
$179.4k - $204.7k
NoSQL databases, Container Orchestration services including Docker and Kubernetes, and a variety of AWS tools and services Provide technical leadership and direction across Agile teams, setting standards for design, deve…
$179.4k - $204.7k
deliver high-performing, quality features for 100M+ customers that are engaging, purposeful and powerful in their simplicity Provide technical leadership for front-end architecture and design patterns, acting as a multip…
$123.3k - $140.7k
years of experience using Git-based version-control systems (e.g., Git, Github, Bitbucket) ~1+ years of experience troubleshooting technical issues within cloud environments ~ Experience leveraging modern AI-based coding…
$36 per hour
Job Description The Technical Writer partners with Training and Operations to create, maintain, and improve Standard Work documentation that supports a safe, productive, and highly skilled workforce. This role ensures lo…
02
What technical writers earn in Richmond
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $26–$36 | $54k–$74k |
| Mid level | $36–$48 | $74k–$99k |
| Senior | $47–$62 | $97k–$129k |
Adjusted for the Richmond 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 Richmond?
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.