Lead Technical Writer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like cookie/navigation/legal/EEO etc. Must preserve all substantive info. We need to parse the posting. Key parts: - Intro: "To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months to ensure you are not duplicating efforts." This is advice, maybe not substantive? It's not about role. Could be considered boilerplate? It's not about job details. Probably we can drop it. - Job Category Enterprise Technology & Infrastructure (maybe metadata, could be minor metadata, we can fold into short p or drop). Probably drop. - Job Details About Salesforce ... paragraphs about Salesforce, Agentforce, etc. This is "About the role" maybe? Actually "About Salesforce" is company description. Could be part of "About the role" or maybe we treat as "About the role". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role section containing description of role and company context. - Role Overview: "We're looking for a Lead Technical Writer..." This is role overview. Could be part of About the role. - Key Responsibilities: bullet list (though not formatted as list but sentences separated by periods). We need to extract responsibilities and put into

• . - Required Experience/Skills: list of requirements. - Desired Experience: list. - Unleash Your Potential: benefits description? It mentions benefits and resources, AI agents accelerate impact. Not specific benefits. Later there is a benefits paragraph: "Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program." Also mention link. - Pay: salary range: "The typical base salary range for this position is $143,400 - $216,900 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $172,200 - $236,700 annually." - Schedule: not mentioned. So we should not create Schedule section. - Benefits: we have specific benefits list. So include Benefits section. - Qualifications: maybe combine Required Experience/Skills and Desired Experience? The instruction says use headings Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements = required experience/skills. Qualifications = desired experience? Skills maybe separate? But we can map: Requirements = Required Experience/Skills. Qualifications = Desired Experience. Skills maybe could be extracted from required? But we might not need Skills if not distinct. However we should include only sections with real content. We have required and desired. Could also include Skills section if we can extract skills like "Experience using AI tools for content creation and research. Experience with Claude Code, Codex, Cursor, Markdown, and Git". That is skills. Could put under Skills. Better to follow typical pattern: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We'll omit Schedule. Now extract content. About the role: combine company description and role overview. Company description paragraphs: "About Salesforce Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets action. Tech meets trust. And innovation isn’t a buzzword — it’s a way of life. The world of work as we know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce. Agentforce Operations (AFO) is part of Salesforce, built to develop and foster AI-native technologies at start-up speed, leveraging the full power of Salesforce. Originating from the acquisition of Regrello, the team brings its own product culture, cadence, and technical stack. This is a unique opportunity to shape documentation and content practices for a fast-moving, expanding AI-driven product area within Salesforce." Role Overview: "We're looking for a Lead Technical Writer who's energized by fast-paced environments and developer collaboration. As the Agentforce Operations writer, you'll manage and build upon an established documentation set—including Agentforce Operations Help and Developer Documentation—while driving content strategy as the startup team continues to integrate into Salesforce. You'll need to move fast, ask sharp questions, and collaborate closely with engineering and product teams." Combine into About the role section. Responsibilities: list from "Key Responsibilities". The text: "Create and maintain documentation for Agentforce Operations' agentic workflow platform, working directly with product and engineering teams. Quickly learn and iterate on documentation for a product built outside Salesforce's traditional conventions — updating established documentation and translating startup-speed processes into clear, usable content. Partner with stakeholders across a newly forming org structure where roles, ownership, and reporting lines are still being defined — proactively identify who owns what rather than waiting for it to be assigned. Staff cross-functional prototyping pods to co-create content, develop UI labels and user assistance in code, and validate solutions. Use AI tools for content creation, review, and research to work at the speed the org requires. Navigate cultural integration between a startup mindset and Salesforce's documentation standards, advocating for customer needs on both sides. Adapt continuously as the org's acquisitions, priorities, and even leadership structure evolve — comfort with frequent change is essential." We'll make each a
• . Requirements (Required Experience/Skills): "5+ years of professional technical writing, ideally including developer or API documentation. Demonstrated ability to maintain and scale existing documentation architecture and strategy while continuously adapting to new product features. Strong appetite for ambiguity: comfortable operating without a finalized org chart or roadmap. Experience working directly with engineers/founders in a fast-paced, startup-like environment (prior startup or M&A-integration experience a strong plus). Excellent stakeholder-management skills — able to build trust quickly with teams that may be skeptical of "corporate" process or formal technical writing. Growth mindset with genuine flexibility to reprioritize week to week. Experience using AI tools for content creation and research. Experience with Claude Code, Codex, Cursor, Markdown, and Git" We'll put each as
• . Qualifications (Desired Experience): "Familiarity with agentic workflow, process automation, or AI/agent-building tools. Prior experience documenting a recently acquired product/team integrating into a larger company." Skills: maybe we could extract specific technical skills: "Experience with Claude Code, Codex, Cursor, Markdown, and Git" but that's already in Requirements. Could also list "Experience using AI tools for content creation and research." Might be redundant. Perhaps we can skip Skills section if not distinct. But we have to decide. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Skills into Requirements or Qualifications. But we have headings list; we can omit Skills if not substantive distinct content. However we have specific skills like Claude Code etc. Could be considered Skills. But we already have them in Requirements. To avoid duplication, maybe we put them under Skills and keep Requirements more about experience years etc. Let's split: Requirements: years, ability to maintain/scale, appetite for ambiguity, experience working with engineers/founders, stakeholder-management, growth mindset. Skills: Experience using AI tools for content creation and research; Experience with Claude Code, Codex, Cursor, Markdown, and Git. Qualifications: Desired experience. That seems reasonable. Now Benefits: list: "time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program." Also maybe mention link but we can drop link as it's not substantive? It's a reference; we could keep as part of benefits but it's a URL. Probably okay to include as part of benefits paragraph. But we need to use
  • for list of benefits. So each benefit as li. Pay: include salary ranges. Schedule: none, omit. Now ensure we don't include boilerplate: remove lines like "To get the best candidate experience...", "Job Category Enterprise Technology & Infrastructure", "Accommodations ...", "Please note that Salesforce uses artificial intelligence (AI) tools...", "Please see our Candidate Privacy Statement...", "Posting Statement Salesforce is an equal opportunity employer..." etc. Also remove "Unleash Your Potential When you join Salesforce, you’ll be limitless..." maybe that's fluff but could be considered benefits? It's vague. We already have benefits section; we can ignore that fluff. Also remove "Apply today to not only shape the future — but to redefine what’s possible — for yourself, for AI, and the world." That's application instruction, drop. Now produce HTML fragment. Structure:

    About the role

    ... combined paragraphs ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Skills

    • ...
    ...

    Qualifications

    • ...
    ...

    Benefits

    • ...
    ...

    Pay

    The typical base salary range for this position is $143,400 - $216,900 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $172,200 - $236,700 annually.

    Make sure no extra whitespace? It's fine. Now craft the About the role paragraph: combine company description and role overview into maybe two paragraphs? Could be one

    with both. But we can split into two

    under same heading? The instruction: use

    for prose. Could have multiple

    under heading. We'll do two paragraphs. First paragraph: company description. Second paragraph: role overview. Now ensure we keep all substantive info: mention Agentforce Operations (AFO) part of Salesforce, built to develop and foster AI-native technologies at start-up speed, leveraging full power of Salesforce. Originating from acquisition of Regrello, team brings its own product culture, cadence, technical stack. Unique opportunity to shape documentation and content practices for fast-moving, expanding AI-driven product area within Salesforce. Role overview: Lead Technical Writer, energized by fast-paced environments and developer collaboration. Manage and build upon established documentation set—including Agentforce Operations Help and Developer Documentation—while driving content strategy as startup team integrates into Salesforce. Need to move fast, ask sharp questions, collaborate closely with engineering and product teams. Now Responsibilities list as above. Requirements list: we need to decide which items go to Requirements vs Skills. Let's define: Requirements (experience/background): - 5+ years of professional technical writing, ideally including developer or API documentation. - Demonstrated ability to maintain and scale existing documentation architecture and strategy while continuously adapting to new product features. - Strong appetite for ambiguity: comfortable operating without a finalized org chart or roadmap. - Experience working directly with engineers/founders in a fast-paced, startup-like environment (prior startup or M&A-integration experience a strong plus). - Excellent stakeholder-management skills — able to build trust quickly with teams that may be skeptical of "corporate" process or formal technical writing. - Growth mindset with genuine flexibility to