$143.7k - $194.4k
Do you aspire to be a world class front-end engineer, and learn from experts in the field? Are you passionate solving user interface and UX problems in a large scale environment? Do you want to be a part of a fast-paced…
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.
30
Open roles today
$33–$78/hr
Typical pay range
$109k
Median, full-time
8
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 30 · sorted by freshness
$206.09k - $285.6k
Who we are About StripeStripe, LLC. is a financial infrastructure platform for businesses. Millions of companies - from the world’s largest enterprises to the most ambitious startups - use Stripe to accept payments, grow…
$80k - $173.8k
Wipro Limited (NYSE: WIT, BSE: 507685, NSE: WIPRO) is a leading technology services and consulting company focused on building innovative solutions that address clients’ most complex digital transformation needs. Leverag…
$108k - $216k
resolve issues to ensure a seamless user experience.Software Craftsmanship: Consistently produce high-quality, maintainable code. Technical Documentation: Document designs, implementations, and best practices.Engineering…
$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…
experience is welcomed#LI-CV1QualificationsRequired QualificationsTechnical degree or a minimum of 3 years related industry experience Technically qualified with 3D design software and document management infrastructure…
$171.6k - $338.3k
closely with business, solution engineers, team members and leadership to understand business requirements and deliver high quality technical solutions Analyzing, implementing user requirements/business needs as new and/…
$46 - $50 per hour
multiverse, we continue to innovate and build new ways to foster friendship and connection. That’s where you come in! Are you a creative writer who loves the intersection of mechanics and flavor? Can you write art briefs…
$35 - $50 per hour
A leading organization specialized in VR simulation training is seeking a Senior Technical Animator to support their team. The role involves developing high-quality character animations and gameplay systems within Unity…
This is a paid freelance, remote position. CBR is the #1 entertainment website and publishes up-to-the-minute news on blockbuster movies, TV shows, video games, comic books, music and other forms of entertainment. As a w…
in Azure and Kubernetes environments. Troubleshoot, debug, maintain, and upgrade software applications. Prepare and maintain technical documentation for applications, programs, and architecture. Ensure development activi…
$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…
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.