$165k - $220k
evolves as our fleet, and the data it generates, grows. Role Details: As a senior member of the team, you'll help inform technical direction and raise the bar for how we build software at Seasats. On a day-to-day / week-…
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.
14
Open roles today
$31–$74/hr
Typical pay range
$103k
Median, full-time
3
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 14 · sorted by freshness
$28.5 - $33 per hour
writing and product messaging, along with the ability to simplify technical details without losing accuracy.Responsibilities:• Create... ...technical accuracy.• Collaborate with editorial partners and fellow writers to s…
focus of this Department of Homeland Security (DHS), Immigration and Customs Enforcement (ICE) effort is to deliver comprehensive technical services essential for the support and continuity of systems critical to operati…
Description ActioNet is seeking a part-time Technical Writer / Program Support Specialist to support a Navy technology modernization program in San Diego, CA. This is a dual-function role. As the program’s shared documen…
$149.8k - $262.2k
, and consumed. We’re moving from a world where large teams of writers produce content manually to one where AI-powered, agentic systems... ...a strong foundation in object-oriented programming ~ Strong technical breadth…
school project all count. ~ A portfolio or two to three writing samples you can share with your application. This is how we evaluate writers, so please include it. ~ You have written something whose job was to get found…
$115k - $140k
seeking a highly strategic and creatively driven Senior Brand & Technical Copywriter to help define and evolve the voice of one of the... ...and consumer marketing. The ideal candidate is an exceptional writer who can mo…
$90k - $115k
Services team. This is a client-facing delivery role: you will sit in on client conversations, translate their business needs into technical requirements, and explain tradeoffs in plain language when a client isn't techn…
$31.25 - $40.87 per hour
Position Summary: Under the general supervision of an attorney, Word Processors revise, format and create documents according to the firm’s standard format. Location: Onsite or hybrid preferred Compensation: $31.25 - $40…
$110k - $120k
stronger. For more information, visit or follow MMS on LinkedIn . Responsibilities Under minimal supervision, the Medical Writer will critically evaluate, analyze, and interpret the medical literature to select primary r…
$65k - $72k
team takes pride in serving our children with the highest level of excellence and care ABOUT THE POSITION JOB TITLE: Grant Writer DEPARTMENT: Philanthropy – San Diego REPORTS TO: Institutional Giving Manager STATUS: Regu…
$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…
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.