Technical Writer- High Tech Data Center Product

Posted 2 days ago

pinnacle groupSeattle (WA)

Technical Writers Computer Systems Design Services

SENIORITY

Senior

SALARY

$70-75/hr

Apply

About the role

Technical Writer Seattle WA$70-75/hr w 2 + benefits The Product you'll be writing about is the integrated product data center operations teams use to plan and execute the work required for data center lifecycle management. The Product ties together the three core pillars of data center activity — Processes (how work is performed), Parts (materials needed to complete work), and People (technicians with the right skills, in the right place, at the right time).Its customers are Data Center Technicians, Data Center Managers, and Service Owners operating across regions worldwide. As The Product transforms from a suite of bespoke tools into a single, modernized product launching globally, client need clear, accurate, and scalable technical documentation to help operators onboard fast and execute work safely and frugally. Client is looking for a Technical Writer to own the creation of end-user and technical documentation — including user guides, onboarding content, process-authoring developer guides, API references, and release notes. Candidates will partner closely with product managers, software engineers, UX designers, and central operations teams to translate complex workflows into content that a data center technician can follow under time pressure. Candidates will establish documentation standards, build reusable content, and continuously improve docs based on user feedback and product changes. This is a high-impact role:candidate’s work directly reduces onboarding time, prevents operational errors, and protects safety, security, availability, and compliance across AWS data centers.

Key Job Responsibilities: Plan, write, edit, and maintain user-facing documentation for The Product, including task-based user guides, onboarding materials, FAQs, and release notes. Produce developer-facing technical content such as API references, process authoring/developer guides, and content-management (form/flow/variable set) documentation. Work directly with engineers, PMs, and UX to understand features, then translate complex data center workflows into clear, concise, step-by-step instructions. Develop and enforce documentation standards, style guidelines, templates, and information architecture that scale across regions and audiences. Validate documentation for technical accuracy by testing procedures and reviewing against the product. Manage documentation as part of the release cycle, keeping content current as features launch across regions. Gather and act on feedback from technicians, managers, and service owners to continuously improve content quality and findability. Work with localization team to structure content appropriately for a global, multi-region operator audience.

Basic Qualifications: 3 plus years of experience as a technical writer producing software or technical product documentation. Bachelor's degree in Technical Communication, English, Computer Science, a related field, or equivalent practical experience. Demonstrated ability to write clear, concise, task-based documentation for both technical and non-technical audiences. Experience authoring in structured documentation tools and formats (e.g., Markdown, HTML, wikis, docs-as-code, or a component content management system).Experience partnering with software engineers and product managers to gather and verify technical information. Strong portfolio or writing samples demonstrating end-user guides and/or API/developer documentation.

Preferred Qualifications: Experience documenting enterprise or operational software, workflow/process-automation tools, or hardware/infrastructure operations. Familiarity with data center operations, hardware lifecycle, inventory management, or field operations tooling. Experience with docs-as-code workflows, version control (Git), and integrating documentation into CI/CD or release pipelines. Experience creating API reference documentation from specifications (e.g., OpenAPI/Smithy) and developer guides. Experience building information architecture and content standards for a growing product from the ground up. Familiarity with localization/globalization and writing for a multi-region, ESL-inclusive audience. Experience with UX writing, in-product help/microcopy, or instructional design. Ability to create diagrams, screenshots, and visual aids to support written content.

Required Individual Skills: Core Technical-

Writing Skills: Technical writing and editing Clear, concise, task-based writing User-guide development Onboarding-content creationFAQ development Release-note writingAPI-reference documentation Developer-guide creation Process and workflow documentation Writing for technical and nontechnical audiences Simplifying complex technical concepts Step-by-step procedure development Documentation Management: Documentation planning and maintenance Structured authoring Information architecture Content reuse and modular writing Documentation standards development Style-guide and template creation Content lifecycle and version management Release-cycle documentation Content findability and usability improvement Documentation quality assurance Tools and Technical Knowledge: MarkdownHTMLWikis Docs-as-code workflows Component content management systems Git and version controlCI/CD and release-pipeline integration OpenAPI or Smithy specificationsAPI and software-product fundamentals Validation and Research: Technical information gathering Subject-matter expert interviewing Procedure testing Documentation accuracy validation Product and feature analysis User-feedback analysis Continuous content improvement

Collaboration Skills: Cross-functional collaboration Working with software engineers Working with product managers Working with UX designers Stakeholder management Requirements gathering Technical review coordination Domain and

Preferred Skills: Enterprise or operational-software documentation Workflow and process-automation documentation Hardware or infrastructure-operations knowledge Data-center operations Hardware lifecycle management Inventory-management systems Field-operations tooling Globalization and localization Writing for multi-region and ESL-inclusive audiencesUX writing and microcopy Instructional design Diagram and visual-aid creation Screenshot development

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.