Ventures, and others. The company has more than 250 employees across offices in San Francisco, Seattle, New York, and Delhi. Technical Content Writer Role We are looking for a talented cross-functional Content Writer to…
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.
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 593 · sorted by freshness
we are building toward becoming the world’s first profitable AV technology company. About the role We're looking for a Technical Writer to build and maintain the documentation backbone of our manufacturing and engineerin…
architectures to rethink how power is converted, controlled, and deployed. About the Role Amperesand is seeking an experienced Technical Writer to join the Deployment team to lead the development and management of compre…
Technical Grant Writer About AIAF The AI Alignment Foundation is a 501(c)(3) that does hands-on technical AI alignment research and funds neglected approaches that larger labs and funders overlook. We work closely with A…
service documentation helps technicians maintain Zipline’s aircraft and equipment safely and consistently. We’re looking for a Technical Writer to own manuals and procedures that make complex systems understandable and g…
About HUD About the role Were hiring a Technical Writer to tell the stories behind what people build with HUD. Youll turn customer and partner work product developments and research into clear technically grounded conten…
one of the fastest private supercomputers in the world. (We've melted GPUs getting here.) About the Role We're hiring a Technical Writer to build the single source of truth for Alembic's science. Our founder and CEO, the…
and partner with frontier AI labs to develop training data that advances model capabilities. What You’ll Do As Senior Technical Writer, you’ll decide what Roboflow Labs should publish, write the pieces yourself, and own…
the form of a relocation bonus. About the role: As a Technical Writing Intern , you will test and document new product features... ...During your internship, you’ll partner directly with your tech writer mentor, as well…
structured content agents can parse, and automated review passes that check drafts against our quality bar. Role Overview As a Technical Writer Intern on DevX, you will write, test, and ship documentation that thousands…
model cards, risk reports, safety and security reports, and other technical material. You’ll have a front-row seat to some of the most... ...reports, or similar public disclosures Experience as a technical writer or edit…
HUD is looking for a Technical Writer to tell the stories behind what people build on our platform. You'll transform customer work, product developments, and research into clear, technically grounded content that resonat…
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.
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 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.