Title: AI Engineer / AI Platform Engineer Experience: 8+ years preferred Location: San Deigo, CA Role Overview We are looking for a hands-on AI Engineer / AI Platform Engineer to design, build, and integrate enterprise A…
Engineering & IT · San Diego, CA
Technical Writer jobs in San Diego, 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.
9
Open roles today
$31–$74/hr
Typical pay range
$103k
Median, full-time
1
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
9 shown · sorted by freshness
$60 - $90 per hour
deep expertise in Angular 17+, modern web technologies, and enterprise-scale UI development. The ideal candidate combines strong technical expertise with a passion for user experience, accessibility, scalability, and eng…
$18.5 - $30.2 per hour
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…
$160k - $210k
ensure what you build works in both theory and practice. Role Details: As a senior member of the team, you'll help guide the technical direction of the team and elevate software engineering practices across our company.…
general supervision, performs a wide variety of complex clerical work requiring specialized knowledge. Reads, Translates, and types technical and non-technical brochures, safety guides, specific educational programs invo…
Understanding of key design principles. Proficiency in HTML, CSS, JavaScript, and jQuery. Understanding of server-side CSS. Experience with responsive and adaptive design. Determining the structure and design of web page…
$40.7 - $48 per hour
RESPONSIBILITIES Unique position identifying and assessing issues with technical documentation for Command, Control, Communications, Computers (... ...to this posting please reference job # SD26-103 Technical Writer II (…
$30 - $40 per hour
Job : Social Media Manager Location : Mission Beach, San Diego Compensation: $30 - $40 per hour, depending on experience ($62,400-$83,000 annually). Schedule : 40 hours per week (Hybrid) Nothing else is a sensitive skinc…
Full Stack Software Engineer (C#, Angular, ASP.Net MVC, ADO.Net, Web API, REST, Entity Framework, HTML5, CSS3) in San Diego, CA Angular JS, ASP.Net MVC, C#, CSS, HTML5, JavaScript, jQuery, REST API, Software Design, T-SQ…
02
What technical writers earn in San Diego
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $31–$42 | $65k–$88k |
| Mid level | $42–$57 | $88k–$118k |
| Senior | $56–$74 | $116k–$153k |
Adjusted for the San Diego 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 Diego?
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.