interact with backend systems. Design and develop large-scale, NoSQL and/or relational database-backed applications. Contribute to technical design discussions and participate in code reviews. Collaborate with cross-func…
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 59 · sorted by freshness
A career at Whole Foods Market is more than just the work you do- it's about your personal growth and creating meaningful change. Our purpose is to nourish people and the planet. That means improving how people eat, fund…
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…
Job Title: Technical Writer Location: Onsite San Jose, CA Duration: 12 Months (Extendable) Job Summary STAFFXPERT is Seeking an experienced Technical Writer with 5+ years of experience to develop and manage documentation…
The Senior Content Author (SCA) is responsible for designing components and providing support to web applications. The SCA is able to work independently, assuming ownership for the design and authoring of simple and comp…
Support deployments, release management, and production stability initiatives. Collaborate with engineering teams to resolve complex technical challenges. Tune applications for multi-threaded and high-concurrency environ…
of the next generation of interactive computing. Description This role requires a deep understanding of animation artistry, technical proficiency in Maya, and the ability to work within real-time constraints while mainta…
XP Services, Inc. is searching for a perceptive and meticulous data entry typist to draft typed documents for our company. The data entry typist will inspect job briefs and gather the applicable materials required for ea…
troubleshooting and collaborative innovation in a dynamic environment. ~ Excellent communication skills, able to effectively convey complex technical details and project progress to team members and non-technical stakeho…
TCS World Travel has hosted guests on adventures of a lifetime for over 30 years. We have developed and operated over 300 expeditions to more than 200 destinations. Our all-inclusive journeys deliver unparalleled and mea…
Python, or Perl for tool automation ~ Strong verbal and written communication skills to collaborate across teams and present complex technical concepts effectively Bonus Points: ~ Bachelor’s or Master’s degree in Electri…
Position Summary: The service advisor is responsible for scheduling service work in the service department and for selling additional services to customers. Come work for the best! If you are interested in a career in th…
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.