Lead Technical Writer (Remote)

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are", "What We Do", "What You'll Do", "What You'll Bring", "What We Offer". Also we have Pay Range. Also maybe Benefits. The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to extract sections: "Who We Are" could be "About the role"? Actually "Who We Are" is company description, not role. Could map to "About the role"? The instructions list example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use those headings if appropriate. We need to decide which sections to include based on content. We have: - Who We Are: company overview. Could be "About the role"? Not exactly. Could be "About the company". But not in list. However we can still use

  for any section heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we can use other headings if needed? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where applicable. But we can also use other headings if needed? Safer to stick to those headings. However we have content that doesn't fit exactly: "Who We Are" could be "About the role"? Not really. Maybe we can treat it as "About the role" (description of the team/company). Or we could omit it? But we must preserve ALL substantive information. So we need to include that info somewhere. Could put it under a heading like "About the role" (though it's about company). Or we could create a custom heading like "Who We Are" but that deviates from examples. The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. I'd include a heading "About the role" for the company overview. Then "What We Do" describes the role: could be "Responsibilities"? Actually "What We Do" is about the role's purpose. Could be "Responsibilities". But we also have a separate "What You'll Do" which is more specific duties. So we could map: - About the role: Who We Are + What We Do? Might be too much. Better to separate: "About the role" for Who We Are (company). "Responsibilities" for What You'll Do. "Requirements" for What You'll Bring. "Benefits" for What We Offer (including benefits). "Pay" for Pay Range. We also have "What We Do" which is a description of the role's purpose; could be part of "About the role" or maybe "Responsibilities". But we already have responsibilities. Could incorporate "What We Do" into "About the role" as a summary. Let's extract content: Who We Are: "Join a team that puts its People First! Since 1889, First American (NYSE: FAF) has held an unwavering belief in its people. They are passionate about what they do, and we are equally passionate about fostering an environment where all feel welcome, supported, and empowered to be innovative and reach their full potential. Our inclusive, people-first culture has earned our company numerous accolades, including being named to the Fortune 100 Best Companies to Work For® list for eleven consecutive years. We have also earned awards as a best place to work for women, diversity and LGBTQ+ employees, and have been included on more than 50 regional best places to work lists. First American will always strive to be a great place to work, for all. For more information, please visit www.careers.firstam.com." What We Do: "As Lead Technical Writer, you'll play a key role in enabling a great developer experience at First American. You'll evolve our technical documentation practice to make technical and product knowledge easier to create, maintain, discover, and use at scale. You'll strengthen the standards, tooling, workflows, and contribution models that help teams create and maintain high-quality documentation for internal and external consumers. This is a hands-on role that leads through influence. You'll work across product and engineering teams to advance Docs as Code, AI-assisted documentation, and the role of authoritative knowledge in Agentic Product Development, while contributing high-value technical, product, and API documentation directly. *This is a remote role" What You'll Do (Responsibilities): List bullet points: - Guide and execute our technical documentation strategy and roadmap, aligning documentation priorities with user needs and organizational goals. - Advance our Docs as Code approach, including standards, tooling, contribution workflows, governance, and automation that integrate documentation into product and development workflows. - Shape information architecture and content structure to improve how technical and product knowledge is organized, connected, discovered, and used. - Enable and coach teams to own and contribute documentation, creating practical guidance and low-friction contribution models that make high-quality documentation easier to create and maintain. - Create and improve high-value technical, product, and API documentation for internal and external consumers, working directly with product and engineering teams on documentation priorities. - Evolve AI-assisted documentation practices and support Agentic Product Development, applying AI to improve knowledge capture, creation, quality, and maintenance while shaping how authoritative knowledge is discovered and used by AI agents. - Drive measurable improvements in the developer experience, using data, research, and feedback to identify friction, prioritize opportunities, and evaluate the impact of documentation. - Build trusted relationships across teams, influencing builders and leaders to strengthen documentation ownership and embed high-quality documentation into how products and technology are built and maintained. What You'll Bring (Requirements/Qualifications): List: - 8+ years of technical writing or developer documentation experience, including experience shaping or scaling documentation practices in a modern software, SaaS, or developer-platform environment. - Exceptional technical writing and information architecture skills, with the ability to translate complex technical and product concepts into clear, useful content and organize knowledge for effective discovery and use. - A portfolio or examples of relevant work should demonstrate the quality and breadth of your experience. - Demonstrated experience with Docs as Code and modern developer workflows, including Git-based contribution and review, documentation platforms, automated quality checks and publishing workflows, and tools such as Vale or comparable documentation tooling. - Technical fluency and experience creating high-quality API documentation, with the ability to work comfortably with APIs, OpenAPI specifications, software development workflows, and modern developer tooling. - Experience building scalable documentation practices, including standards, governance, contribution models, and workflows that enable teams to own, create, and maintain high-quality documentation. - Hands-on experience applying AI to documentation or knowledge workflows, with an understanding of how well-structured, authoritative knowledge supports AI-assisted and agentic experiences. - Strong collaboration and influence skills, with the ability to build credibility with teams and leaders, navigate ambiguity, and drive progress without relying on direct authority. - Bachelor's degree or equivalent combination of education and relevant experience. - #ST2 (maybe a tag, ignore) - Note that the following statements only apply to candidates who will be working from an unincorporated area within Los Angeles County. ** First American will consider for employment all qualified applicants, including those with arrest or conviction records, in a manner consistent with the requirements of applicable state and local laws (e.g., the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act). First American intends to conduct a review of an applicant’s criminal history in connection with a conditional offer. First American reasonably believes that a criminal history may have a direct, adverse and negative relationship with the following material job duties for this position potentially resulting in the withdrawal of the conditional offer of employment: handling of confidential, proprietary or trade secret information belonging to First American or its customers, administrating or facilitating financial transactions, and the ability to meet customer-imposed criminal history requirements. We need to remove boilerplate like EEO etc. The above includes Fair Chance statements which might be considered EEO/legal boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the Fair Chance statements and the note about Los Angeles County. Also remove the "#ST2". Also remove the note about "Based on eligibility, First American offers a comprehensive benefits package..."? That is part of What We Offer, not boilerplate. Keep. What We Offer: "By choice, we don’t simply accept individuality – we embrace it, we support it, and we thrive on it! Our People First culture is inclusive for all employees - not just because it's the right thing to do, but because it's the key to our success. We are proud to foster an authentic and inclusive workplace For All. You are free and encouraged to bring your entire, unique self to work. First American is an equal opportunity employer in every sense of the term. Based on eligibility, First American offers a comprehensive benefits package including medical, dental, vision, 401k, PTO/paid sick leave and other great benefits like an employee stock purchase plan. Pay Range: $97,700.00 - $130,300.00 Annually This hiring range is a reasonable estimate of the base pay range for this position at the time of posting. Pay is based on a number of factors which may include job-related knowledge, skills, experience, business requirements and geographic location." We need to remove EEO statement: "First American is an equal opportunity employer in every sense of the term." That's boilerplate EEO. Remove. Also remove "Based on eligibility, First American offers a comprehensive benefits package including medical, dental, vision, 401k, PTO/paid sick leave and other great benefits like an employee stock purchase plan." That's benefits info, keep. Pay Range: keep. Now we need to format. Sections: -

  About the role

  (maybe combine Who We Are and What We Do). Let's decide: We'll put Who We Are as a paragraph under About the role. Then What We Do could be part of About the role as well, but maybe better to have a separate section "Role Overview". However not in list. Could use "About the role" for Who We Are, and "Responsibilities" for What You'll Do. What We Do could be included in About the role as a brief description. Let's combine Who We Are + What We Do into About the role. Thus About the role paragraph: combine both. Then Responsibilities:

  Responsibilities

  with
  • for each bullet from What You'll Do. Then Requirements:

    Requirements

    with
    • for each bullet from What You'll Bring (excluding boilerplate). Also maybe include "Bachelor's degree or