Please submit your application through this posting only. We're unable to review applications or follow-ups sent via email, direct message, or website inquiry. ABOUT NEN CREATIVE Nen Creative partners with tech startups…
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.
86
Open roles today
$37–$88/hr
Typical pay range
$122k
Median, full-time
4
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 86 · sorted by freshness
$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,…
$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…
$134k - $168k
partnering with frontier labs to build Foundation Models for Physical AI that will redefine the future of automation. As a Technical Writer on the Physical AI team, you will create and maintain the training content that…
$110k - $155k
About Plaud Inc. Plaud is building the real-world AI interface for professionals to amplify intelligence, elevate productivity and performance, loved by over 2,000,000 users worldwide since 2023. With a mission to amplif…
$29.4 - $35.57 per hour
Claire Lilienthal Elementary School - Scott 3630 Divisadero St. San Francisco, CA 94123 Temporary $29.40 - $35.57 per hour Claire Lilienthal Elementary School - Scott Posted 7/29/2026 Job Class: 1426 Senior Clerk Typist,…
$115k - $170k
Harvey, Rippling, Vanta, LinkedIn, Monday.com, Nvidia, and Bridgewater. About the role We’re seeking a detail-oriented Technical Docs Writer who can take complex technical concepts and transform them into easily understa…
$120k - $166k
playable characters. In this Gameplay Animator role, you will lead a specialized strike team—including a gameplay animator and a technical animator—to ensure that movement, combat, and interactions are world-class. You w…
$105k - $183k
Figma is growing our team of passionate creatives and builders on a mission to make design accessible to all. Figma's platform helps teams bring ideas to life-whether you're brainstorming, creating a prototype, translati…
for the “kinesthetic feel” of a game. Unlike standard animation roles, this position requires a deep fusion of artistic mastery and technical engine architecture. Modma Studios are seeking a visionary Principal Gameplay…
$87k - $96k
agentic era? You're in the right place! Agentforce is the future of AI, and you are the future of Salesforce. About the Team: Technical writers in the Content Experience organization at Salesforce produce documentation a…
$140k - $185k
TECHNICAL WRITER You'll own how developers learn to use Firecrawl. Great docs are one of the biggest reasons developers pick a tool and stick with it, and for a product that lives or dies by developer experience, this ro…
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.