Startup Growth Hacker (AI, Creator Economy) Location: Remote / Seattle-area (University of Washington students welcomed) About Vivu.ai An AI-powered video creation platform whose vision is to help everyone tell a better…
Engineering & IT · Seattle, WA
Technical Writer jobs in Seattle, WA
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.
67
Open roles today
$33–$78/hr
Typical pay range
$109k
Median, full-time
3
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
12 shown of 67 · sorted by freshness
SMILE is seeking a Content Marketer to develop compelling, strategic content across the member journey. The role leverages AI tools to optimise content performance, drive sales growth and improve member retention. This i…
$63 - $79 per hour
world. About the Role Armada is looking for a Senior Brand Writer to shape how the company sounds across every surface where words... ...to a social post. You will go deep on our products, learn the technical substance,…
$140k - $165k
Gradial is the marketing operations system of work that helps marketers and creatives move from idea to execution faster. Our platform orchestrates across martech stacks, workflows, and people to automate marketing execu…
timeline and platform requirements. You should be comfortable pitching motion concepts to creative leads and stakeholders, and have the technical range to move between styleframes, animation, and edit. You should have wo…
$31 - $47 per hour
ensuring the final output is polished and timely. Summary of Requirements We are looking for an artist who possesses a strong technical foundation and a collaborative spirit. Artistic Foundation: Proven skills in 3D and/…
$108k - $150k
continue to push the boundaries of immersive interactive experiences, we are looking for an artist who thrives at the intersection of technical precision and creative storytelling. In this role, you will be the driving f…
$106k - $158k
with event, tournament operations, and communications to support content before, during, and after live events. Manage freelance writers and other external contributors. Provide editorial direction and ensure content mee…
$110k - $150k
ZGF is seeking a Specifications Writer to join our team in our Seattle office with at least 10 years of experience. Each day we... ...rounded strategic thinker with an integrated approach to design and technical project…
sets who also exhibit deep expertise in their chosen craft. The animators at Valve are a world-class group of artists working with writers, software engineers, and designers who are continually creating and releasing com…
to add talented individuals to our team. Character artists at Valve work with a world-class group of software engineers, artists, writers, animators, and designers who are continually building and releasing entertainment…
will join a world-class group of software engineers, artists, writers, animators, and designers who continually build and release entertainment... ...has the following: ~Strong understanding of the artistic and technical…
02
What technical writers earn in Seattle
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $33–$45 | $69k–$94k |
| Mid level | $45–$60 | $94k–$125k |
| Senior | $59–$78 | $122k–$162k |
Adjusted for the Seattle 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 Seattle?
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.