Liquid Development was founded in 2000 and is the largest outsourcing art studio in North America. We offer a fun and cooperative work atmosphere, where collaboration is encouraged among a diversely talented team to rema…
Technical Writer jobs in Portland, OR
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
9 shown of 21 · sorted by freshness
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…
photorealistic, and sci-fi tailored VFX Varied and specializations (characters, environments, weapons, etc) Ability to troubleshoot technical problems A self-driven, positive attitude towards critique, and leaning from y…
industry standard 3D modeling, sculpting, and texturing software ~ Experience shipping environment art in multiple game engines. ~ Technical proficiency in game environment art workflows such as topology, UVs, and optimi…
existed, and we hire people who actually get it. THE ROLE Words drive traffic — and traffic drives everything. As an SEO Content Writer at NoGigiddy, you'll create articles, guides, and landing pages that rank on Google…
passion to a challenging and constantly evolving game. WHO WE ARE LOOKING FOR The Digital Experience 3D Artist is a creative and technical practitioner responsible for creating digital experiences that bring product stor…
Since the dawn of aviation, pilots have faced the constant challenge of air resistance, much like sailors navigating the friction of water. Amidst this relentless struggle, the trim tab emerges as an ingenious yet unders…
against common vulnerabilities . * **Collaboration:** Work closely with product managers and designers to translate requirements into technical specifications and deliver user-friendly Web3 experiences. **Required Qualif…
transportation design. We're looking for a Marketing and Communications Writer to join our Portland, OR team-someone who loves finding the... ...Working HereWe are an employee-owned, purpose-driven team of technical expe…
What technical writers earn in Portland
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $29–$39 | $61k–$82k |
| Mid level | $39–$53 | $82k–$110k |
| Senior | $52–$69 | $108k–$143k |
Adjusted for the Portland 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 Portland?
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.