Plan and complete assigned work, communicate effectively orally and in writing; motivate and work with people; quickly adapt to new technical environments (multiple disciplines); manage multiple projects with dynamic pri…
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.
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.
Open technical writer roles
11 shown of 22 · sorted by freshness
Location: Remote hybrid at Huntsville, AL, McLean, VA, or Richmond, VA Required Clearance: Must be a U.S. citizen Required Education: HS/GED Required Experience: Minimum 3 years of experience in front-end development, da…
Risk Tech is responsible for transforming risk management into a real time, intelligent discipline powered by modern products and technical capabilities. Our mission is divided into two primary functional pillars: Risk M…
Specific responsibilities for the Full-Stack Developer position include: Collaborate with team members and clients to deliver a technical solution that meet the unique needs of our clients Create quality deliverables to…
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…
that strategically enable the Finance organization and the broader Enterprise to remain efficient. This mission is driven by four technical and functional pillars: Forecasting & Resiliency, providing advanced decision su…
provide will be kept confidential and will be used only to the extent required to provide needed reasonable accommodations. For technical support or questions about Capital One's recruiting process, please send an email…
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…
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…
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…
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…
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.
What employers ask for
The skills these listings keep naming
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.
Resume tips that move the needle
For technical writers specifically — generic advice costs you here
Link writing samples matched to the job: API docs for API roles, user guides for product roles — the portfolio is the interview.
Quantify impact where possible: support tickets deflected, onboarding time cut, docs traffic and satisfaction scores.
List your toolchain (Markdown, Git, Docusaurus, OpenAPI) because docs-as-code fluency is now a standard screen.
Show technical depth honestly — languages you can read, APIs you have called yourself — since it defines which roles fit.
Mention style guide ownership or editing responsibilities; they signal you raise a whole team's quality, not just your own pages.
Where this role goes
Typical progression
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.