Words n Logic · Scouting Report
Technical Writing Scouting Report: July 2026 Edition
Fresh technical writing jobs posted in the San Francisco Bay Area this month, the skills employers keep asking for, and where AI is showing up in the job requirements themselves.
Salary spotlight
This month’s snapshot focuses on the jobs that surfaced in the Bay Area and the signals they send about pay, experience, and the growing role of AI in the work itself. The salary chart below gives a quick read on the range of compensation across the postings, while the rest of the report explains how those figures connect to the broader market.
Median band across the 7 disclosed: about $128K low, $160K high, almost unchanged from last edition even with a $286K posting added. Outliers stretch the ceiling; they don’t move the middle.
At a glance
These figures are a quick read on the month’s mix of location, pay, and AI expectations; they’re directional rather than a census, but they help show where the market seems to be putting pressure right now.
The roles
Eight full-time roles in the Bay Area within the last 30 days, each broken down the same way so you can compare at a glance. Seven are first-time postings; one (Supermicro) is a repost I’m including on purpose, since I work there. One (Google) is dual-posted to Sunnyvale, CA and Kirkland, WA; I’m counting it as a Bay Area role because of the Sunnyvale option.
Technical Writer – Spacecraft & Manufacturing
Early-stage aerospace startup building Pulsar, a low-Earth-orbit satellite constellation for centimeter-level positioning: a next-gen, backwards-compatible alternative to GPS.
4–7 yrs experience
Salary not listed
First TW hire
Xona’s first technical writer, spanning satellite engineering documentation (ICDs, test procedures, design specs) and manufacturing work instructions/SOPs on the production floor, plus contract deliverables and mission-ops docs.
- Skills
- Work instructions, SOPs, ICDs, document control, Confluence, Google Workspace
- Qualifications
- US citizen / permanent resident / ITAR-eligible required; self-directed
- Department
- Embedded with the Program team, cross-functional
- Benefits
- Not listed
Technical Writer, Docs Content
Financial infrastructure platform for businesses: payments and revenue tooling used from startups to the largest enterprises.
4+ yrs experience
$135,800–$203,800
Writes conceptual overviews, task-based guides, API docs, and tutorials for docs.stripe.com across both developer and everyday-user audiences, including content-quality work via user feedback and performance analysis.
- Skills
- HTML, Markdown, Git, VS Code
- Qualifications
- Collaborates well with other writers; backend language exposure a plus
- Department
- Stripe Docs Content team
- Benefits
- Equity, bonus, 401(k), medical/dental/vision, wellness stipend
Senior Technical Writer
Front-to-back cloud system of record for investment managers, founded by Dave Duffield (co-founder, PeopleSoft and Workday).
5+ yrs experience
$128,000–$159,500
Owns user guides, release notes, API reference, UI text, and in-app guidance using structured, topic-based authoring for consistency and reuse across the doc set.
- Skills
- DITA, XML-structured authoring, Heretto/CCMS, Git/GitHub, Confluence
- Qualifications
- SaaS/enterprise background; fintech and AI-in-content-workflow knowledge a bonus
- Department
- Reports to Director of Technical Documentation & Content Experience
- Benefits
- Stock plan, unlimited vacation, $0-cost employee insurance
Technical Writer
Top-tier provider of servers, storage, and networking hardware for data centers, cloud, and HPC: one of Silicon Valley’s fastest-growing hardware companies.
5+ yrs experience
$107,000–$117,000
Repost, my employer
Produces and revises user manuals, quick-reference guides, and software manuals for motherboards, working across engineering, sales, and customers on content and schedules.
- Skills
- MadCap Flare (required), Adobe InDesign/Illustrator, MS Project
- Qualifications
- BA in English or Technical Writing
- Department
- Hardware department (motherboard documentation)
- Benefits
- Unspecified comprehensive package; bonus/equity eligible
A note from me
This is a repost, the one exception to this edition’s first-time-postings rule, and I’m including it because I work at Supermicro. If you meet the minimum requirements and want to send me your resume, or would just like a quick 10-minute call about the role and the culture, message me on LinkedIn: linkedin.com/in/doug-purcell.
Sr Technical Writer, Energy
Electric vehicle and clean-energy company; this role sits on the Tesla Energy team (Megapack, Superchargers).
4+ yrs experience
$84,000–$156,000 + equity
Bridges Tesla’s global service-technician network with engineering, and explicitly optimizes content for AI parsing (structure, metadata) alongside human readers.
- Skills
- HTML, XML, DITA, JIRA, SharePoint, visual/photo content creation
- Qualifications
- Active AI-tool use; comfortable with frequent priority changes
- Department
- Tesla Energy team, partners with diagnostics & training
- Benefits
- $0-deduction medical option, HSA match, 401(k)+ESPP, disability, commuter benefits
Technical Writer – Commerce Cloud
Enterprise CRM and cloud software platform; role sits on the Commerce Cloud product line.
Entry-level / new grad
Posted Jul 7, 2026
Writes docs, tutorials, guides, code samples, API references, and in-app assistance for developer and admin audiences, and is the most explicit posting in this batch about using AI tools (Cursor, Claude) as part of the job itself.
- Skills
- Markdown, XML, DITA, source control, Cursor & Claude
- Qualifications
- Degree within 12 months of graduation, in tech writing/English/CS
- Department
- Commerce Cloud Content Experience team
- Salary
- $75,000–$113,500 national band; $90,200–$124,000 if based in SF/NYC metro, a pay-transparency disclosure, not a confirmed office location.
- Benefits
- Time off, medical/dental/vision, mental health support, parental leave, 401(k)
Senior Technical Writer
VC-backed robotics startup building AI-driven robotic storage and material-handling systems for the supply chain industry.
5+ yrs experience
$145,000–$160,000
Owns documentation infrastructure across disciplines: installation manuals, SOPs, maintenance guides, and troubleshooting content, for manufacturing and field-service audiences.
- Skills
- Confluence, Notion, Adobe CS, Arena PLM/QMS, MkDocs/Sphinx a plus, Git/GitHub
- Qualifications
- Comfortable reading CAD drawings and electrical schematics
- Department
- Systems Engineering team
- Benefits
- Equity, subsidized health coverage, subsidized lunch, commuter stipend, onsite gym
Head of AI Documentation
AI & Infrastructure org: the team behind TPUs, Vertex AI, global networking, and data center operations, serving Googlers, Google Cloud customers, and billions of Google users.
15+ yrs experience
$205,000–$286,000 + 25% bonus + equity
Arrangement not stated
The only leadership-track posting in this batch, and the most explicit about AI of any role here. Its mandate, verbatim: “driving the shift to a dual-interface, AI-native content infrastructure for developers and autonomous agents,” docs built to serve human developers and AI coding agents as first-class readers, by design.
- Skills
- Editorial process & content-ops design at scale, vendor/freelancer management, developer workflows, APIs/SDKs, coding agents
- Qualifications
- “Deep understanding of artificial intelligence, machine learning concepts, and LLMs,” the only posting in this batch that asks for AI architecture literacy
- Department
- Leads & scales a team of technical writers within AI & Infrastructure
- Benefits
- Standard Google benefits; 25% bonus target + equity on top of base
My thoughts on July’s trends
- Fewer postings than May and June. Could be a summer slump, or just noise in an 8-role sample. Worth watching next edition before calling it a trend.
- Pay range: this batch spans $84,000–$286,000 across the 7 roles that disclosed a number, but the median band ($128K–$160K) barely moved from last edition even with Google’s $286K posting added. One outlier stretches the ceiling; it doesn’t shift the middle.
- Onsite still leads. Four of eight roles read as onsite, two are explicitly hybrid, two didn’t say, and fully remote postings were absent entirely this month.
- Startups vs. established: two roles at venture-backed startups (Xona, Mytra), six at established or public companies.
- First leadership-track posting in this series. Every prior role has been individual-contributor. Google’s Head of AI Documentation is the first “build and run the team” opening, and arguably this month’s single clearest signal about where the field is headed.
I believe knowledge workers, not just technical writers, should be constantly leveling up and expanding their skill sets. A wider skill set opens up more adjacent opportunities and provides a cushion during downturns, when openings in any one field shrink.
Three concrete ways to actually do that:
- Ship one real project, not a private tutorial. A live link an interviewer can click, a documentation site, or a contribution to an open-source project’s docs, is worth more than a resume line, because it’s proof rather than a claim.
- Pick a specific skill gap from a job posting you actually want, not a generic “learn AI” goal. This report’s skills tables are built for exactly this.
- Get weekly reps with AI tools on real writing tasks, not occasional casual use. Four of the eight postings in this edition already treat that as baseline fluency, not a bonus.
Top skills employers require
Recurring keywords across this month’s 8 postings, a mention counts whether it was listed as required or preferred.
Docs-as-code isn’t actually the single most in-demand line in this table on its own; HTML, XML, Git, and AI tooling all tie or edge it out at 4 of 8. It’s still the best first project for most writers to build, though, because doing it properly means picking up several of those other skills at once instead of one at a time.
Experience levels required
This batch skewed senior: 5 of 8 postings asked for 5+ years or more, against exactly one true entry-level opening. That entry-level role (Salesforce) is also the most AI-explicit IC posting; the sole 15+ year role (Google) is the most AI-explicit posting overall. AI fluency now brackets both ends of the seniority ladder.
AI trends for technical writers
Pulling together what this month’s postings and the industry chatter below are actually saying about AI, not as a threat narrative, but as a description of what’s showing up in job requirements right now.
The clearest AI signal this month isn’t a requirement line. It’s a job title. Google’s Head of AI Documentation posting is close to a thesis statement for where this field is headed: funded at $205K–$286K base plus a 25% bonus target and equity, well above every IC role in this batch, with a mandate to drive “a dual-interface, AI-native content infrastructure for developers and autonomous agents.”
- AI shows up in two distinct ways in job requirements, not one. First, as a tool writers are expected to already use. Second, as a new audience the content itself has to serve.
- AI-tool fluency now brackets the whole seniority range, not just the middle. The one entry-level posting is the most AI-explicit IC listing; the one executive-level posting asks for AI/ML literacy well beyond tool use.
- Nobody in this batch frames AI as a headcount reducer. Every AI-related line item across these 8 postings describes AI expanding what writers cover, not shrinking how many a team needs.
- This connects directly to the Coinbase discussion below. If readers increasingly route through an AI assistant instead of a table of contents or search bar, “well-structured docs” stops being only a human-readability concern and becomes a retrieval-accuracy concern too.
This section reads employer requirements. The social roundup below reads the other side: how working technical writers are actually talking about AI this month.
What’s up in social media?
My favorite LinkedIn posts this month about writing, AI, and the job market.
Documentation & information architecture
How Coinbase organizes their documentation
“Most companies organize their documentation by product. Coinbase gives you two ways in: by product, or by what you’re trying to build.”
Cassiano Ferro Moraes, CEO @ WriteChoice
Studying how other doc sites organize content is a great way to sharpen your information-architecture instincts. I’d love to see more meetups built around reviewing doc sites the way developers do code review.
Doc teams & org positioning
Engineering leaders are rethinking documentation’s place in the org
Dave Nunez didn’t soften this one. His post is about how engineering leadership is currently perceiving doc teams, and what he thinks writers should do about it.
- Learn coding agents by building things. This tracks with what I’ve done myself: built a complete documentation site and implemented docs-as-code while working full-time.
- Measure the impact of your docs. Plain analytics paired with qualitative reader feedback is a reasonable floor if you don’t know where to start.
- Consider a title change. Content engineer, knowledge engineer, agent experience: I’ve been tracking this drift across previous editions.
AI & the craft of writing
“First drafts are still sacred”
Technical writer Olena Kravchenko posted about where she draws the line on AI in her own workflow. She uses GitHub Copilot inside her Docusaurus project with project-specific instructions, agents for language and style review, and automation for repetitive checks like consistency passes and pre-release reviews. First drafts, though, stay off-limits.
AI usually lacks full context for a reason that goes beyond the tool itself: the source material it gets fed doesn’t have full context either. When a subject-matter expert hands over specs or notes for a new feature, those documents are almost always incomplete, written by someone who already understands the feature deeply enough to unconsciously skip the details a new user would actually need explained.
There’s also a subtler risk in letting AI write a first draft, even when the content ends up factually fine: once you’ve seen a full draft, it’s hard not to be anchored by its structure. The blank page is uncomfortable for a reason. Some of the real thinking happens there.
“`
