you’ll create aesthetically captivating visual effects that communicate essential game information. You’ll use your artistic and technical skills to breathe life into undead spells, channel primal emotions and capture th…
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.
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
12 shown of 95 · sorted by freshness
Senior Motion Designer Remote (Washington State) 3-month contract (possible extension or conversion) $71-$76/hr Join the largest coffee retail company in the country! This global brand team is seeking a Senior Motion Des…
however, ad hoc meetings occur between 8am-6pm Pacific time. #LI-remote Who We Need You’re a seasoned writer who understands how scientific , technical , and commercial buyers evaluate real-world data and analytics, and…
newsletter lands in inboxes every week — and it needs to be the kind of email people actually look forward to opening. As our Newsletter Writer, you'll research, write, and produce a weekly newsletter that keeps our audi…
Thistledown Tech, a logistics software company based in Seattle, WA, is hiring a Backend Engineer (Go) (3 openings). You will build fast, dependable services in Go that handle millions of requests a day. This is a hybrid…
changed so it would not happen again.Our process:1. Intro call (30 min) with the CTO about your background and what you want next.2. Technical deep dive (60 min) on a system you built: the design, the tradeoffs, what fai…
immersive learning to agile, just-in-time assets to maximize engagement and speed in a fast-moving environment. Fast learner with technical aptitude that enables you to gain expertise across our products, roles and instr…
passionate about making complex technology accessible and empowering developers to build with confidence We are looking for a Senior Technical Writer who thrives on turning intricate technical concepts into clear usable…
About Us: Based in San Francisco California Turing is the worlds leading research accelerator for frontier AI labs and a trusted partner for global enterprises deploying advanced AI systems. Turing supports customers in…
industry. Discover our vibrant culture to get an inside look into life at Ware Malcomb and the programs we offer. As a Technical Specifications Writer at Ware Malcomb, you will be responsible for developing comprehensive…
design and product You enjoy working closely with designers and product teams. You are comfortable translating design concepts into technical implementations and proposing improvements when necessary. Ownership and produ…
challenging problem of scaling these services to serve hundreds of thousands of Amazonians across the globe in real-time - Be a technical innovator that is not afraid to challenge the norms and innovate. - Execute agains…
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.
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 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.