, and Leadership: Co-own the end-to-end MaaS system design with the Principal Architect, authoring decision records and defending technical trade-offs. Drive the platform through its maturity roadmap by delivering operab…
Engineering & IT · San Jose, CA
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.
37
Open roles today
$37–$86/hr
Typical pay range
$121k
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 37 · sorted by freshness
$130k - $150k
content engine. This role will evolve into managing additional writers and designers within a few months. What You'll Do Content... ...writing skills with a strong portfolio (long-form + creative + technical) ~ Experienc…
$180k - $190.63k
Collaborate with cross-functional teams to influence product direction and define functional requirements.Identify opportunities for technical and product innovation, and proactively design solutions that elevate system…
$21 - $31.5 per hour
safety regulations including Food Safety and regulatory duties required in the department. Job Responsibilities Completes Order Writer training Replenishes products through proper buying procedures. Orders perishable and…
$185k - $230k
establish patterns and best practices that other engineers can build on.You’ll also play a key role in elevating the team: guiding technical decisions, mentoring engineers, and raising the bar for both product thinking a…
$210k - $275k
, and adaptable as both product requirements and underlying models evolve.This role goes beyond individual features. You’ll drive technical direction across product areas, aligning product, AI, and infrastructure teams o…
$136k - $185k
effectively support AI-based product features.Communicate effectively with stakeholders across multiple teams, clearly articulating technical strategies related to AI-enabled infrastructure.We're looking for someone whoH…
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…
$45 - $85 per hour
Nex is on a mission to help families rediscover the joy of movement. Created by parents for parents, Nex combines technology and play to deliver fun, social, and interactive experiences powered by natural body motion, en…
· Translate complex cybersecurity concepts into simple, engaging visual stories that resonate with technical and business audiences · Collaborate with designers, writers, and product marketing to develop concepts, storyb…
$197.3k - $225.1k
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…
$55 per hour
wide variety of technologies and systems ~ Excellent written and verbal communication skills with the ability to present complex technical information in a clear and concise manner to a variety of audiences. ~ Work cross…
02
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.
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 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.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.