$65k - $70k
Salary: $65,000 - 70,000 per year Requirements: ~6–8 years of technical writing experience, including proven Grade IV-level expertise.... ...serving the U.S. and Canada. This remote Technical Writer IV contract is expect…
Engineering & IT · San Francisco, CA
Technical Writer jobs in San Francisco, CA
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.
64
Open roles today
$37–$88/hr
Typical pay range
$122k
Median, full-time
9
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 64 · sorted by freshness
$136k - $187k
Why HarveyAt Harvey, we’re transforming how legal and professional services operate. By combining frontier agentic AI, an enterprise-grade platform, and deep domain expertise, we’re reshaping how critical knowledge work…
$189k - $237k
In 1958, graphic designer Saul Bass opened Alfred Hitchcock's Vertigo with a spiral of color and line that told you everything about obsession before a single line of dialogue was spoken. Bass didn't think of the title s…
$74.09k - $125.95k
that strengthen learner retention, capacity, confidence, and job-related competencies. Translate complex policy, procedural, and technical information into clear, accessible, and action-oriented instructional content. Vi…
$110k - $170k
hands-on content leader who loves writing and editing SEO content, ebooks, guides, and one-pagers, and who is excited to go deep on technical product narratives—translating complex capabilities into clear, compelling, co…
ABOUT KREA At Krea, we are building next-generation AI creative tools. We're dedicated to making AI intuitive and controllable for creatives - our mission is to build tools that empower human creativity, not replace it.…
patterns to life in the front end.• Write, improve, and maintain high-quality code within modern JavaScript and React-based applications.• Share technical input throughout the development lifecycle, including feasibility…
Job Overview We are seeking an experienced Technical Writer to join our team. The successful candidate will have a strong background in technical writing, excellent writing and communication skills, and the ability to wo…
$100k - $150k
packages that strengthen the Astranis brand. Collaborate with creatives, engineers, marketers, and leadership to translate complex technical concepts into clear visual stories. Contribute to creative development from con…
$95k - $210k
Motion Graphics Designer / Animator: We are looking for motion graphics designer / animators to work on a newly forming team, in a dynamic environment, making short-form videos for product & feature release, PR & Comms,…
Full Time /
$150k - $200k
the world building infrastructure that moves over $10b a year. The problem is, almost nobody knows it yet. We're looking for a Technical Writer to change that. You'll be the voice of Slash engineering: turning the hard,…
02
What technical writers earn in San Francisco
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $37–$50 | $77k–$105k |
| Mid level | $50–$67 | $105k–$140k |
| Senior | $66–$88 | $137k–$182k |
Adjusted for the San Francisco 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 San Francisco?
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.