physics, bringing the world years ahead in AI quality and availability. What We’re Looking For MatX is looking to hire a Technical Editor to make our technical writing clear and correct. You’ll join talented engineers, h…
Technical Writer jobs in San Jose, 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 105 · sorted by freshness
Overview Baker Tilly is a leading advisory tax and assurance firm providing clients with a genuine coast-to-coast and global advantage in major regions of the U.S. and in many of the worlds leading financial centers New…
role offers the opportunity to contribute to meaningful public sector work, collaborate with cross-functional teams, and grow your technical leadership capabilities. The position is located in Downtown Los Angeles. Key R…
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…
narratives. This is a hands-on role that requires a strong writer. Working with external resources, you'll use search and performance... ..., social, and comms. Write and edit content across formats: technical blog posts…
50 megawatts of scale, transforming key workloads with ultra high-speed inference. About the Role We’re looking for a Dex Technical Writer with deep expertise in AI hardware or software to produce original research and t…
About us: At Reevo, we're reimagining the entire revenue stack from the ground up, and we're doing it with speed. We're building software that orchestrates every go-to-market motion, enabling B2B teams to operate faster,…
the table Extreme grit and hustle: You are relentless, move fast, and thrive in a high-intensity startup environment. Highly technical: You understand how software is built and can speak the same language as our engineer…
it. In this role you'll: ● Design, build, and ship features end to end, from spec through deployment. ● Own significant technical work and drive best practices and standards across the team. ● Use AI tooling fluently acr…
our Santa Clara, CA HQ, reporting to the VP, Culture and Community in our People & Culture organization. This individual is a superb writer and visual storyteller who thrives on finding new and unexpected ways to connect…
NoSQL databases, Container Orchestration services including Docker and Kubernetes, and a variety of AWS tools and services Provide technical leadership and direction across Agile teams, setting standards for design, deve…
Category: Creative, Media & Design Evaluation · Pay: Hourly rate confirmed after the interview process · Location: Remote — US-eligible · Contractor VFX Artist / 3D Animator is a remote review track for evaluating AI out…
What technical writers earn in San Jose
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $37–$50 | $76k–$103k |
| Mid level | $50–$66 | $103k–$138k |
| Senior | $65–$86 | $135k–$179k |
Adjusted for the San Jose 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 Jose?
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.