2

Remote Technical Writing Jobs in Washington, DC (NOW HIRING)

Experience a remote-first culture that empowers you to work with purpose and accountability in a ... To succeed in this role, you must have a solid foundation in UX and technical writing practices and ...

Experience a remote-first culture that empowers you to work with purpose and accountability in a ... To succeed in this role, you must have a solid foundation in UX and technical writing practices and ...

New

This remote contract-to-hire position will be originated in Falls Church, VA. * SELECTED CANDIDATES ... Familiarity with AI tools and capabilities to perform technical writing. * Good working knowledge ...

Senior Proposal Writer

Columbia, MD · Remote

$101K - $150K/yr

Strong knowledge of technical writing and editing best practices, working in a remote environment. * Exceptional organizational and time management skills. Ability to successfully work (in a lead or ...

Content Writer

Centreville, VA · Remote

$35 - $41/hr

Remote - EST Hours Start Date Is: August 10, 2026 Position Type: Contract (5 Months) Pay Rate: $35 ... Minimum Requirements: * 3-5 years of experience in technical writing, product documentation ...

Minimum of 5-7 years of relevant experience writing proposal responses and related technical ... Remote Company Information Yudrio, Inc. is a high-end Information Technology (IT) solutions ...

Proposal Writer Remote (Travel as needed) Our client is seeking an experienced Proposal Writer to ... Perform additional technical writing and marketing tasks as assigned * Ability to travel as needed

New

Showing results 21-40

Remote Technical Writing information

See Washington, DC salary details

$15

$44

$74

How much do remote technical writing jobs pay per hour?

As of Aug 8, 2026, the average hourly pay for remote technical writing in Washington, DC is $44.11, according to ZipRecruiter salary data. Most workers in this role earn between $32.69 and $53.37 per hour, depending on experience, location, and employer.

What is the difference between Remote Technical Writing vs Remote Content Writing?

AspectRemote Technical WritingRemote Content Writing
Required SkillsTechnical knowledge, clarity, documentation skillsCreativity, SEO, audience engagement
Work EnvironmentTech companies, software firms, engineering teamsMarketing agencies, media outlets, blogs
Common CertificationsTechnical writing certifications, IT backgroundContent marketing, SEO certifications

Remote Technical Writing focuses on creating detailed technical documentation for products and services, often requiring technical expertise. Remote Content Writing involves producing engaging content for marketing, blogs, and websites, emphasizing creativity and SEO. While both roles involve writing skills, they serve different purposes and industries, making them distinct career paths within the remote writing field.

What are the key skills and qualifications needed to thrive as a remote technical writer, and why are they important?

To thrive as a Remote Technical Writer, you need strong writing, editing, and research skills, usually supported by a background in English, communications, or a related field. Familiarity with documentation tools like Microsoft Word, Adobe FrameMaker, Markdown, and content management systems is often required, along with knowledge of version control software. Excellent communication, self-motivation, and time management are crucial soft skills for collaborating with remote teams and meeting deadlines. These abilities ensure that complex information is conveyed clearly and efficiently, supporting user understanding and business goals in a distributed work environment.

What is remote technical writing?

Remote technical writing involves creating instruction manuals, user guides, FAQs, and other supporting documents for products or services, all while working from a location outside of a traditional office. Remote technical writers communicate complex information clearly and concisely, often collaborating with engineers, developers, and other subject matter experts via digital tools. They need strong writing skills, technical understanding, and the ability to work independently. The remote aspect allows for flexibility in schedule and location, making it a popular choice for writers with technical expertise.

How do remote technical writers typically collaborate with subject matter experts and development teams?

Remote technical writers frequently use a variety of digital collaboration tools to communicate with subject matter experts (SMEs) and development teams. Regular video meetings, chat platforms, and shared documentation spaces like wikis or version control systems help bridge the distance. Proactive communication and clear documentation requests are essential, as writers may not have in-person access to SMEs. Building strong virtual relationships and maintaining organized records of feedback and updates are key strategies for success in a remote environment.
What are the most commonly searched types of Technical Writing jobs in Washington, DC? The most popular types of Technical Writing jobs in Washington, DC are:
What are popular job titles related to Remote Technical Writing jobs in Washington, DC? For Remote Technical Writing jobs in Washington, DC, the most frequently searched job titles are:
Infographic showing various Remote Technical Writing job openings in Washington, DC as of July 2026, with employment types broken down into 86% Full Time, 9% Part Time, 4% Contract, and 1% Nights. Highlights an 88% Physical, 4% Hybrid, and 8% Remote job distribution, with an average salary of $91,741 per year, or $44.1 per hour.

Business Process Analyst / Technical Writer

H & R Computer Consulting Services inc

Silver Spring, MD • Remote

$85K - $100K/yr

Full-time

Medical, Dental, Vision, PTO

Posted 3 days ago

New

Be Seen First

After you apply to this job, you can share why you’re interested to jump to the top of the candidate list.


Job description

Title - Business Process Analyst / Technical Writer
Client - NOAA
Location - Remote
Duration - 1 year contract
Key Responsibilities

Meeting Attendance and Information Gathering

•     Attend up to four to five virtual meetings per week with NOAA OAR administrative teams and up to three to four per week with portal development staff.
•     Come to each session prepared with a structured agenda and specific open questions rather than attending passively.
•     Capture meeting minutes, decisions, and action items, and issue them within one business day.
•     Maintain a running action item register with named owners and due dates, reconciled at each subsequent session.
SOP Compilation and Formatting

•     Compile administrative workflows into clear, accurate Standard Operating Procedures suitable for handoff to developers.
•     Apply a single standardized template across all teams so the SOP library is consistent from the first document to the last.
•     Return drafts to the owning team for validation, adjudicate comments, and manage version control and change logs.
•     Deliver SOPs iteratively as teams complete them, and assemble a consolidated final package at the end of the engagement.

Portal Requirements Documentation

•     Decompose validated SOPs into discrete, testable requirement statements written for programmers, not administrators.
•     Assign each requirement a unique identifier, a source reference, a priority, and an acceptance criterion.
•     Map user workflows to ticketing system capabilities, including roles, request types, routing rules, status transitions, approvals, notifications, and exception handling.
•     Maintain full traceability from SOP section to requirement to portal capability, and manage the requirements baseline through a logged change process.

Cross-Team Coordination

•     Identify where administrative teams handle the same function differently, and log each discrepancy with both variants and the rationale behind them.
•     Convene the affected team leads and drive reconciliation at the working level, escalating only where teams cannot agree — and escalating with options and a recommendation, not an open question.
•     Communicate approved documentation changes to affected team leads proactively so alignment is maintained rather than periodically restored.

Portal Developer Coordination

•     Serve as the single interpretive channel between administrative intent and system configuration.
•     Acknowledge developer questions within one business day and provide a substantive answer or a scheduled working session within three.
•     Where a technical constraint makes a documented workflow unbuildable, return to the process owner with the constraint and a proposed alternative.
•     Deliver workflow and configuration data in the structure the development team has agreed to consume.

User Instruction Development

•     Write step-by-step end-user portal instructions organized by the task the user is trying to accomplish rather than by system menu structure.
•     Validate instructions by walking the documented steps in the built system before release.

Deliverable and Quality Management

•     Produce weekly meeting summaries and monthly status reports on a fixed cadence.
•     Run a documented quality check against accuracy, clarity, completeness, and template conformance before every submission.
•     Track and report risks, blockers, and stalled reviews before they threaten the schedule.

Required Qualifications

•     Bachelor's degree in English, Communications, Information Systems, Business Administration, or a related field. Additional directly relevant experience may substitute for the degree.
•     Five (5) or more years of professional experience in technical writing, business analysis, process documentation, or requirements development.
•     Demonstrated experience authoring Standard Operating Procedures, process documentation, or workflow documentation for an organizational audience.
•     Demonstrated experience translating business or administrative processes into system requirements for a development team.
•     Experience facilitating working sessions and eliciting process detail from subject matter experts who are not documentation professionals.
•     Experience coordinating across organizational boundaries and resolving conflicting process definitions between groups.
•     Advanced proficiency with Microsoft Word, including templates, styles, and version control, plus working proficiency in Microsoft Excel.
•     Proficiency with virtual meeting platforms such as Microsoft Teams, Zoom, or Google Meet, and with shared document repositories such as SharePoint or Google Drive.
•     Exceptional written English, with the ability to produce documents that require minimal editing before client delivery.
•     U.S. work authorization and the ability to pass standard Federal contractor onboarding.
•     Reliable high-speed internet and a suitable home office. This role is fully remote and no Government equipment is provided.

Preferred Qualifications

•     Prior experience supporting NOAA, the Department of Commerce, or another Federal agency.
•     Experience documenting requirements for a ticketing, service request, ITSM, or workflow platform such as ServiceNow, Jira Service Management, Salesforce Service Cloud, Remedy, or Zendesk.
•     Experience with shared services, administrative consolidation, or business process improvement initiatives.
•     Familiarity with requirements traceability practices and requirements management tooling.
•     Experience producing end-user training materials, quick reference guides, or job aids.
•     Working knowledge of process mapping notation such as BPMN, swimlane diagrams, or Visio-based workflow modeling.
•     Certification such as CBAP, CCBA, PMI-PBA, or a technical writing credential.
•     Experience working under an ISO 9001 quality management system.