TL;DR: May 2026 Highlights
- 12 jobs curated across the SF Bay Area and remote, ranging from $60K (Rippling, entry-level) to $332K (Salesforce, Lead/Principal Trailhead)
- Highest-paying traditional TW role this edition: Salesforce Lead/Principal Technical Writer (Trailhead) at $180K-$332K (SF metro, hybrid)
- Most experience-heavy role: Zoox Manufacturing Operations, requiring 10-15 years
- Top skill in job listings: Docs-as-code (Git, GitHub, Markdown), appearing in 6 of 12 roles
- Fastest-rising requirement: AI tool fluency, now explicit in 5 of 12 listings and no longer optional
- Market signal: One-third of roles are onsite. Fully remote options have narrowed since 2022-2023
- Biggest trend this month: AI agents now account for over 40% of documentation traffic, up from less than 10% a year ago. Your docs are serving two audiences at once
- Bottom line: The field is not shrinking. It is stratifying. Domain expertise and AI workflow fluency are separating good salaries from great ones
By Doug Purcell | Write the Docs Bay Area
Jump to a Section
- About This Report
- Job Quick Reference Table
- San Francisco Jobs
- South Bay and East Bay Jobs
- Remote Jobs
- Data Analysis: What the May 2026 Job Market Is Telling Us
- Trends to Watch: May 2026
About This Report
As the organizer for Write the Docs Bay Area, the Scouting Report is a community resource I put together for technical writers in the San Francisco Bay Area and beyond. Each edition features a carefully curated list of recently posted jobs, plus analysis of the trends shaping the profession right now.
Think of it as your monthly briefing, whether you are actively job hunting or just keeping a pulse on the market.
May 2026 Job Quick Reference
| # | Job Title | Company | Salary Range | Exp. Required | Location | Work Arrangement |
|---|---|---|---|---|---|---|
| 1 | Data Center Process Engineer (Technical Writer) | FluidStack | $120K-$160K | 5+ years | San Francisco, CA | Onsite |
| 2 | Copy Lead, Enterprise | Anthropic | $255K-$320K | 10+ years | San Francisco, CA | Hybrid (25% min) |
| 3 | Lead/Principal Technical Writer (Trailhead) | Salesforce | $180,200-$332,600 (SF metro) | $150,100-$304,700 (standard) | 10+ years | San Francisco or Palo Alto, CA | Hybrid |
| 4 | Technical Writer | Rippling | $70K-$105K | 2+ years | Remote (US) | Remote |
| 5 | Technical Writer – AI | HCLTech | $75K-$116K | 3+ years | Mountain View, CA | Onsite |
| 6 | Technical Writer – Hardware | Nutanix | $74K-$150K | 2-3 years | San Jose, CA | Hybrid (3 days/week) |
| 7 | Senior Technical Writer | LaunchDarkly | $116K-$188K | 5+ years | Remote (US) | Remote |
| 8 | Technical Writer | Tailscale | $86K-$107K | 3+ years | Remote (US) | Remote |
| 9 | Senior Technical Writer, Manufacturing Operations | Zoox | $133K-$167K | 10-15 years | Fremont, CA | Not listed |
| 10 | Sr. Technical Writer | Illumio | $125K-$144K | 7-9 years | Sunnyvale, CA | Onsite (4 days/week) |
| 11 | Technical Writer | Intuitive Surgical | $120,500-$173,500 (Region 1) / $102,400-$147,500 (Region 2) | 5-8 years | Sunnyvale, CA | Onsite |
| 12 | Principal Technical Writer I | Elastic | $128K-$243K | 7+ years | Remote (US) | Remote |
San Francisco Jobs
Data Center Process Engineer (Technical Writer) | FluidStack
- Location: San Francisco, CA | Onsite
- Salary: $120,000-$160,000
- Experience: 5+ years | Industrial or operations-heavy environments (manufacturing, energy, utilities, oil and gas)
- Posted: May 2026
FluidStack is hiring a technical writer embedded in data center operations, making it a rare role at the intersection of industrial documentation and cloud infrastructure. Strong fit for writers with a background in operations, engineering, or energy environments rather than typical SaaS docs.
Copy Lead, Enterprise | Anthropic
- Location: San Francisco, CA | Hybrid (minimum 25% in-office)
- Salary: $255,000-$320,000
- Experience: 10+ years | B2B campaign development and copywriting across multiple formats
- Nice to have: Enterprise and developer audience experience, messaging framework background, strong design partnership skills
- Posted: May 2026
Note: This is a marketing and brand copywriting role, not a traditional technical writing position. It is one of the highest-paying content roles in the Bay Area right now. You will shape enterprise campaign copy, solutions pages, event materials, and performance marketing content at one of the most prominent AI labs in the world.
Lead/Principal Technical Writer (Trailhead) | Salesforce
- Location: San Francisco or Palo Alto, CA | Hybrid
- Salary: $180,200-$332,600 (SF metro) | $150,100-$304,700 (standard)
- Experience: 10+ years | End-to-end content development including strategic planning, writing, and editorial oversight
- Tools: XML/DITA, Markdown, Git, generative AI tools
- Nice to have: AI-first mindset, executive presence, data-driven approach to content performance, mentorship experience
- Posted: May 2026
Salesforce is hiring at the Lead or Principal level for their Trailhead team, focused on Missionforce strategy. You will create release notes, help articles, implementation guides, and Trailhead learning modules, while contributing to AI in CX research and enablement. This role also requires the ability to create technical diagrams including process flows and database architecture.
South Bay and East Bay Jobs
Technical Writer – AI | HCLTech
- Location: Mountain View, CA | Onsite
- Salary: $75,000-$116,000
- Experience: 3+ years | Robotics, engineering, or scientific research background preferred
- Tools: CMS, AI/LLM writing tools, prompt engineering
- Posted: Approximately 3 weeks ago (163 applicants)
HCLTech is hiring an AI-focused technical writer to create SOPs, process docs, test reports, and maintenance guides. Notably, the job description explicitly expects you to use prompt engineering and LLM tools as part of your daily workflow, not just as a nice-to-have. Strong fit for writers interested in the robotics and AI research space.
Technical Writer – Hardware | Nutanix
- Location: San Jose, CA | Hybrid (3 days/week onsite)
- Salary: $74,400-$150,000
- Experience: 2-3 years | Server, networking, and storage hardware/software knowledge
- Tools: DITA XML, Git/GitHub, CI/CD
- Nice to have: UNIX/Linux, storage, or virtualization background
- Posted: May 2026
Nutanix is hiring a hardware-focused technical writer to document server hardware and enterprise cloud software. You will work from technical specs, blueprints, and SME interviews, publishing via a docs-as-code workflow. The documentation team is 35+ writers across the US and India.
Senior Technical Writer, Manufacturing Operations | Zoox
- Location: Fremont, CA
- Salary: $133,000-$167,000
- Experience: 10-15 years | Manufacturing, automotive, or engineering environments preferred
- Nice to have: Training program or instructional design experience | Familiarity with 3DX or CAD visualization tools
- Posted: May 2026
Zoox, Amazon’s autonomous vehicle company, is hiring a Senior Technical Writer for their Manufacturing Operations team. With 10-15 years required, this is one of the most experience-heavy roles in this edition, designed for writers who know how to document complex, safety-critical manufacturing processes.
Sr. Technical Writer | Illumio
- Location: Sunnyvale, CA | Onsite (4 days/week)
- Salary: $125,000-$144,000
- Experience: 7-9 years
- Posted: May 2026
Illumio specializes in Zero Trust segmentation for enterprise cybersecurity. A senior role here means writing for a security-focused, technical audience. Strong fit for writers with network security or enterprise software documentation experience. This role requires four days per week onsite at Illumio’s Sunnyvale headquarters.
Technical Writer | Intuitive Surgical
- Location: Sunnyvale, CA | Onsite
- Salary: $120,500-$173,500 (Region 1) / $102,400-$147,500 (Region 2)
- Experience: 5-8 years | Hardware, software, biotech, or medical device environments
- Tools: Adobe FrameMaker, InDesign (required) | XML, DITA, CMS (strongly preferred) | Illustrator, Photoshop (preferred)
- Posted: Approximately 2 weeks ago (59 applicants)
Intuitive Surgical makes the da Vinci robotic surgery system. This role focuses on Instructions for Use (IFU) documentation with strict FDA and regulatory compliance requirements, a specialized niche that commands premium salaries. Strong fit for writers with medical device, life sciences, or regulated industry experience.
Remote Jobs
Technical Writer | Rippling
- Location: Remote (US)
- Salary: $70,000-$105,000 (Tier 1) | $65,000-$95,000 (Tier 2) | $60,000-$90,000 (Tier 3)
- Experience: 2+ years | B2B SaaS end-user documentation
- Tools: Structured content/single-sourcing principles | eLearning tools (Articulate 360, Adobe Creative Cloud, nice to have)
- Nice to have: Localization-friendly writing experience
- Posted: May 2026
Rippling is building help docs and eLearning materials across their HR platform. Strong emphasis on project management and cross-functional collaboration. You will work closely with Product and CX to close knowledge gaps and support product launches.
Senior Technical Writer | LaunchDarkly
- Location: Remote (US)
- Salary: $136,500-$187,660 (Bay Area/NYC/Seattle) | $122,800-$168,850 (LA, Austin, Chicago, Portland) | $116,000-$159,500 (all other US)
- Experience: 5+ years | Developer tools or DevOps documentation
- Tools: Markdown, HTML, Git/GitHub, CI/CD
- Nice to have: Programming language proficiency, AI tool familiarity (Copilot, Cursor, Claude)
- Posted: May 2026
LaunchDarkly builds feature management and experimentation tools for engineering teams. This role covers product, API, and SDK docs for a highly technical developer audience. Strong fit for writers comfortable with a docs-as-code workflow and technical subject matter.
Technical Writer | Tailscale
- Location: Remote (US)
- Salary: $86,000-$107,000
- Experience: 3+ years | Networking or security products
- Tools: Git, GitHub, Markdown, command-line interface | Docs-as-code workflow
- Nice to have: Open-source contributions, software development experience
- Posted: May 2026
Tailscale builds networking and security software for secure connections. You will write how-to guides, conceptual content, and reference material for engineers, infrastructure teams, and security practitioners. Benefits include $1,500/year for professional development and a $1,000 home office setup budget.
Principal Technical Writer I – Core Docs | Elastic
- Location: Remote (US)
- Salary: $153,800-$243,300 (Bay Area/Seattle/LA/NYC) | $128,200-$202,900 (all other US)
- Experience: 7+ years | SaaS or developer-focused documentation
- Tools: Git, Markdown, docs-as-code workflow | Comfortable reading Java and JSON
- Nice to have: Elasticsearch experience, open-source contributions, basic scripting
- Posted: May 2026
Elastic is hiring at the Principal level, a staff-equivalent role focused on content strategy, information architecture, and mentoring other writers. The job description explicitly calls out AI-augmented documentation as a core expectation. Strong fit for senior writers ready to step into a leadership track.
Data Analysis: What the May 2026 Job Market Is Telling Us
Top Skills Appearing Across Job Postings
Based on the 12 roles in this edition, here are the skills that show up most consistently:
| Skill / Tool | Jobs Requiring It | Example Roles |
|---|---|---|
| Docs-as-code (Git, GitHub, Markdown) | 6 of 12 | LaunchDarkly, Tailscale, Nutanix, Elastic, Salesforce |
| AI tool proficiency (LLMs, prompt engineering, Copilot, Cursor) | 5 of 12 | HCLTech, LaunchDarkly, Salesforce, Elastic, Anthropic |
| XML / DITA | 3 of 12 | Nutanix, Salesforce, Intuitive Surgical |
| Domain expertise (industry-specific background) | 8 of 12 | Nearly all senior roles |
| Cross-functional collaboration / stakeholder management | 7 of 12 | Rippling, Elastic, Intuitive Surgical, Salesforce |
| Information architecture | 3 of 12 | Elastic, Rippling, Tailscale |
| Structured content / content reuse | 2 of 12 | Rippling, Nutanix |
Takeaway: Docs-as-code is no longer a differentiator. It is table stakes. If Git and Markdown are not on your resume, they need to be. AI tool fluency is close behind, appearing in nearly half of all listings and increasingly as a hard requirement rather than a nice-to-have.
High demand / fast-rising
Dominant requirement
Specialized / niche
Salary Breakdown by Experience Level
| Experience Tier | Salary Range | Roles in This Edition |
|---|---|---|
| Entry / Early Career (2-3 years) | $60K-$150K | Rippling, Nutanix, HCLTech |
| Mid-Career (3-5 years) | $75K-$188K | Tailscale, HCLTech, LaunchDarkly |
| Senior (5-9 years) | $102K-$173K | FluidStack, Zoox, Illumio, Intuitive Surgical |
| Principal / Lead (10+ years) | $128K-$332K | Elastic, Salesforce, Anthropic, Zoox |
Notable finding: Salesforce’s Lead/Principal Trailhead role at $180,200-$332,600 is now the highest-paying listing in this edition, edging out Anthropic’s Copy Lead ($255K-$320K). The key difference: the Salesforce role is a traditional technical writing position. That makes it the highest-paying TW role in this edition and one of the strongest data points for where the senior end of the market can go. Excluding both Salesforce and Anthropic, the next highest ceiling is Elastic at $243,300 (Bay Area rate).
Remote vs. Onsite Breakdown
| Work Arrangement | Number of Jobs | Percentage of Listings |
|---|---|---|
| Remote | 4 | 33% |
| Hybrid | 3 | 25% |
| Onsite | 4 | 33% |
| Not listed | 1 | 8% |
Takeaway: The remote-only market has contracted compared to 2022-2023 peaks. One-third of listings this month require onsite presence, and another quarter require hybrid. If you are holding out for fully remote, the options exist, but the field has narrowed.
Industry Breakdown
| Industry | Number of Jobs | Companies |
|---|---|---|
| AI / Enterprise Tech | 4 | Anthropic, HCLTech, Elastic, LaunchDarkly |
| Cybersecurity / Networking | 2 | Illumio, Tailscale |
| Enterprise SaaS / HR | 2 | Rippling, Salesforce |
| Hardware / Medical Devices | 2 | Nutanix, Intuitive Surgical |
| Autonomous Vehicles / Manufacturing | 1 | Zoox |
| Data Center / Infrastructure | 1 | FluidStack |
Takeaway: AI and enterprise tech dominate this edition, but the most experience-heavy and highest-paying onsite roles are in specialized industries: medical devices, autonomous vehicles, and cybersecurity. Domain expertise continues to command a premium that generalist SaaS documentation roles do not match.
4 roles
2 roles
2 roles
2 roles
1 role
1 role
Dominant sector
Active sector
Specialized / premium pay
Are Job Postings Up or Down for May?
- 12 active postings across a mix of industries suggests the Bay Area technical writing market is active but selective, not a hiring boom and not a freeze.
- Applicant counts where visible: 163 applicants for HCLTech and 59 for Intuitive Surgical indicate competitive pipelines even for mid-level roles.
- Seniority skew: The majority of listings require 5+ years of experience. Entry-level roles are scarce in this edition, consistent with a market where companies are consolidating headcount into fewer, more experienced hires.
Skills to Add to Your Resume to Stay Competitive in 2026
- AI and prompt engineering: Not just familiarity, but demonstrated workflow integration. Job descriptions increasingly say “uses AI tools daily,” not “familiar with AI tools.”
- Docs-as-code (Git, GitHub, Markdown): If this is not on your resume, it is likely filtering you out before a human reads your application.
- Context engineering: Understanding how to structure content so AI agents can retrieve and use it accurately. Only 27% of teams have fully adopted this, which means early movers have a real advantage.
- Information architecture: Appears in senior and principal-level roles as a distinguishing competency, not just background knowledge.
- Domain expertise: Pick an industry and go deep. Medical devices, cybersecurity, autonomous vehicles, and AI infrastructure are all commanding premium salaries over generalist SaaS documentation in this edition.
- Structured content and DITA XML: Still appearing in hardware, medical, and enterprise roles. Not glamorous, but consistently required.
Trends to Watch: May 2026
1. AI Is Augmenting Workflows, and the Evidence Is in Production
Tom Johnson, a Senior Technical Writer, published a detailed account this month of using AI agents to automate his release notes workflow. He reduced the review feedback he leaves on AI output from 15-20 comments per release down to 3-5 after a dozen iterations. The framing is instructive: the AI handles the predictable parts of the process reliably. The unpredictable parts (last-minute rollbacks, broken build systems, upstream environment issues) still require human intervention.
This maps directly onto what we are seeing in job descriptions. Salesforce and Elastic both explicitly list AI tool proficiency and call out AI-augmented documentation practices as core expectations, not future considerations.
2. Automation Without Knowledge Ownership Breaks Down
Documentation consultant Cassiano Ferro Moraes shared a case study this month that puts the limits of AI automation into sharp relief. A client using an AI tool to auto-update their docs on every code push ended up with 162 open PRs, all AI-generated and none ready to ship. Technically coherent output, but practically unusable because no one owned the knowledge layer behind it: the context, the terminology, the user-facing meaning.
Alexander Muravyov, CEO of ClickHelp, put it plainly: “Drafting is getting cheaper. What becomes more valuable is context ownership, knowing what the product really does, what users struggle with, what terminology is safe.”
What this means for your career: The skill that protects your value is not writing speed. It is judgment. The ability to validate meaning, catch AI errors, and maintain the knowledge layer that AI cannot infer from source code is exactly what senior and principal-level roles are paying for.
3. Your Docs Are Being Read by Machines More Than You Think
A GitBook report published in February 2026 found that AI agents now account for over 40% of all documentation traffic, up from less than 10% at the start of 2025. That represents more than a 500% increase in AI page views in a single year. Docs are increasingly serving two audiences simultaneously: human readers and AI agents retrieving context to answer questions on their behalf.
This connects directly to the State of the Docs 2026 finding on AI-driven discovery: AI-powered search now accounts for 35% of how users find documentation, with 18% accessing docs through coding AI assistants and 16% through MCP servers. As AI agents consume documentation without visiting individual pages, traditional metrics like page views are becoming less reliable as a measure of impact.
The a16z data reinforces this: scrolling is on the decline as users shift toward AI chatbots and direct-answer interfaces rather than browsing. Content that cannot be found and accurately retrieved by AI is becoming invisible content.
4. The “Company Brain” Is a Technical Writing Problem
Y Combinator recently called for startups to build what they are calling a Company Brain, a self-reinforcing knowledge system that gets smarter as more goes into it. David Nunez, co-founder of Falconer, described the gap: “Incumbent tools like Notion and Confluence help you create, but not maintain.”
Joanna Jablonski, a member of the Python Documentation Editorial Board, observed that context engineering is rediscovering problems that technical writing has been solving for decades. Information architecture, single-sourcing, structured content, version control for documentation: the field has been building toward this for years.
The State of the Docs 2026 AI section reinforces the stakes: AI agents follow documentation literally and have no way to signal when something feels off, which means the precision and structure that technical writers have always brought to their work is now a functional requirement, not just a quality standard.
The opportunity here is real: Technical writers who can articulate their work in terms of knowledge management, content systems, and AI retrieval are speaking the language that product and engineering leadership are currently paying attention to.
5. The Job Market Is Active, But the Search Is Harder
The broader job market context matters here. Widespread tech layoffs and AI-driven restructuring throughout Q1 2026 are shaping candidate volume, which explains the 163 applicant count on the HCLTech Mountain View role.
Technical writers have been sharing candid accounts of the search this month: multi-stage interview processes requiring 8+ hours of investment across assignments and in-person rounds, only to end with companies re-evaluating their needs or going silent entirely. Others have described the psychological toll of the 2026 market: rejection volume, recruiter scams, and the cycle of ghosting after final rounds.
The 12 active listings in this edition represent real opportunities. But competition is real too. One writer who recently landed a new role attributed their success specifically to keyword optimization on their resume and removing visual clutter. In a market where ATS systems screen before humans read, that is worth noting.
6. Correlations with State of the Docs 2026
The findings from the State of the Docs 2026 report align closely with what this month’s job postings and LinkedIn conversations are showing:
| State of the Docs Finding | May 2026 Scouting Report Signal |
|---|---|
| AI/prompt engineering is the #1 priority skill (50%) | 5 of 12 job listings explicitly require AI tool fluency |
| Context engineering is emerging as a core TW skill | The 162 PR case study and community discussions both point here |
| Developer tools like Git are a priority for 35% of TW professionals | 6 of 12 listings require a docs-as-code workflow |
| 25% of doc teams track zero metrics | GitBook’s AI traffic data suggests traditional page-view metrics are becoming unreliable |
| AI-powered search accounts for 35% of docs discovery | a16z scrolling data confirms the shift toward AI-mediated content access |
| TW roles are expanding, not disappearing | Senior and principal-level salaries in this edition ($128K-$332K) support this |
7. A Practical Playbook: How to Use Claude Code to Write Docs
Alden DeSoto, a content design lead at Netflix and former global team lead at Google, shared one of the most concrete and actionable posts in my feed this month: a step-by-step breakdown of how to use Claude Code to write and maintain documentation directly from source code repositories.
His tips, distilled:
- Start with reference docs. Clone your frontend and backend repos and ask Claude to write reference documentation first. This is where AI performs most reliably and is the lowest-risk entry point.
- Write two versions of every procedural guide, one for AI agents and one for humans. Per DeSoto: the agent version tends to be solid. The human-facing version needs more work.
- Do not trust Claude on user-facing flows. Even when working from a frontend repo, Claude does not accurately document what users experience. Write the first draft of each user guide yourself, then use it as a model for Claude to follow.
- Explicitly tell Claude to verify. It will duplicate your model article unless you instruct it to check each setting and option against the actual repo before writing.
- Build a skill file for each article type. Once you have found the right balance between structure and accuracy, ask Claude to write a reusable skill stored under .claude in your project. Tell it to always re-examine the repos before writing and never to rely on previously known facts.
- Reclone and regenerate. Going forward, reclone your repos and run the skill. Each article type you systematize is one less thing requiring full manual effort.
Why this matters for the job market: Five of the twelve listings in this edition explicitly name AI tools as a requirement. DeSoto’s framework gives you a concrete, portfolio-worthy workflow to demonstrate, not just familiarity with AI, but a disciplined process for integrating it into documentation production. That is the difference between saying “I use AI in my work” and being able to show how.
The State of the Docs 2026 AI section confirms the opportunity: AI and prompt engineering ranked as the top skill for technical writers, yet only 27% of teams have fully adopted AI tools. Writers who can demonstrate a working, repeatable AI-assisted workflow are ahead of most of the field right now.
Doug Purcell is the organizer of Write the Docs Bay Area. Connect on LinkedIn.
