US Manager, BD Pursuits & AI Enablement

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, disability accommodation, etc). Must not invent or summarize away detail. Must not create sections with filler like "commensurate with experience". Must only include sections when posting has real specific content. Let's parse the posting. We have: - Overview of the Firm and Function (descriptive about Freshfields). This could be "About the role"? Actually "Overview of the Firm and Function" is about the firm, not role. But we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content to these headings. We have "About Marketing & Business Development (MBD)" which describes the team. Could be "About the role"? Possibly. We have "Key responsibilities and deliverables" then description of role, then "What you'll do" list of duties. We have compensation range: $140,000 to $180,000 for NY/CA. We have no explicit Benefits, Schedule, Qualifications, Skills, Requirements sections. However we might infer some from text: "You bring strong BD knowledge and operational discipline, and understand how AI tools can be applied..." That's like qualifications/skills. Also "This role is suited to someone who knows pursuit work well and wants to transform how it gets done." That's qualifications. We need to decide: Should we create sections only if there is real specific content. For Qualifications, we have statements about required experience/knowledge. That's specific enough. For Skills, we have "strong BD knowledge and operational discipline, understand how AI tools can be applied". That's skills. For Requirements maybe similar. We must not invent details; we can extract from text. Let's extract: About the role: Could be the overview of the firm and function plus About MBD. But "About the role" maybe summarises the role purpose. We have description: "The US Manager, BD Pursuits & AI Enablement is a US-based role focused on raising the quality, consistency, and speed of how the firm pursues and wins work." That's about the role. So we can put that in About the role. Responsibilities: The list under "What you'll do" (bullet points). Also earlier description of day-to-day: owning and streamlining US pitch process, leveraging AI to develop global pitch content library, etc. So we can combine. Requirements: Might be "You bring strong BD knowledge and operational discipline, and understand how AI tools can be applied to the specific, high-friction moments in the pursuit process". Also "This role is suited to someone who knows pursuit work well and wants to transform how it gets done." That's more qualifications. Qualifications: Could be similar but we need differentiate. Perhaps Requirements: experience in BD, pursuit work, AI enablement. Qualifications: maybe education? Not given. Could skip Qualifications if not specific. Skills: Could list: BD knowledge, operational discipline, AI application, process improvement, stakeholder coordination, content management, training development, etc. Benefits: Not mentioned. So we should not include Benefits section. Pay: We have compensation range $140,000 to $180,000 for NY/CA. So we can include Pay section with that. Schedule: Not mentioned (no info about full-time/part-time, hours). So skip Schedule. We must not include boilerplate like EEO, disability accommodation. We must not include navigation, cookie, legal, etc. We must output only HTML fragment. Structure: Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to ensure we don't repeat job title as heading. Let's craft:

  About the role

  The US Manager, BD Pursuits & AI Enablement is a US-based role focused on raising the quality, consistency, and speed of how the firm pursues and wins work. Day to day, that means owning and streamlining the US pitch process with AI enablement, working closely with the BD teams, and leveraging AI to develop and manage the global pitch content library/repository.

  Maybe also include overview of firm? But that's not about the role. Could add a short paragraph about Freshfields as context? The instruction says preserve ALL substantive information; do not invent or summarize away detail. The overview of the firm is substantive but not about the role. However we have no section for "About the Firm". The allowed sections are limited to those headings. We could put firm overview under About the role? That might be stretching but it's still substantive info about the firm. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It also says "include a section ONLY when the posting has real, specific content for it". So we could include About the role with content that includes firm overview? Might be okay but better to keep About the role focused on role. The firm overview could be placed under About the role as context, but it's not strictly about the role. However we have no other section to place it. The instruction says preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. Perhaps we can include a brief paragraph under About the role that mentions the firm's global presence etc. That would preserve it. Thus About the role paragraph could include both role purpose and firm overview. Let's draft:

  Freshfields is a global law firm with over 2,400 lawyers in 28 offices, providing business law advice to national and multinational corporations, financial institutions and governments. The firm emphasizes teamwork, diversity, global collaboration, and adding value to clients and communities. The US Manager, BD Pursuits & AI Enablement is a US-based role focused on raising the quality, consistency, and speed of how the firm pursues and wins work. Day to day, that means owning and streamlining the US pitch process with AI enablement, working closely with the BD teams, and leveraging AI to develop and manage the global pitch content library/repository.

  That preserves firm overview. Now Responsibilities: We'll list the "What you'll do" bullet points. Also earlier responsibilities: owning and streamlining US pitch process, leveraging AI to develop global pitch content library, owning content/experience data/process infrastructure, building shared data spine, developing reusable pursuit assets, partnering with BD/lawyers/business services, identifying high-friction points, developing best practices/training materials, supporting US Chambers submissions, providing hands-on support on priority pitches. We'll combine into a

  • list. We need to ensure we don't lose any detail. Let's extract each bullet from "What you'll do": - Sort out and streamline the US pitch process end to end, embedding AI enablement at each stage and working closely with the BD teams to drive adoption and impact on live opportunities. - Leverage AI to develop and manage the global pitch content library/repository, ensuring it is comprehensive, current, well-structured, and easy to search, retrieve, and reuse across teams. - Own the content, experience data, and process infrastructure behind US pitches, proposals, awards, and directory submissions, with a focus on quality, consistency, and speed. - Build and maintain the shared data spine that powers AI-enabled pursuit work, including pitch content, matter experience, credentials, and lawyer bios, ensuring information is complete, current, and structured for AI retrieval and reuse. - Develop and maintain reusable pursuit assets, including pitch modules, matter descriptions, credential sets, templates, and prompt frameworks, so teams spend their time on strategy and tailoring, not building from scratch. - Partner with BD, lawyers, and business services teams to ensure experience data and CRM records are accurate, current, and complete enough to power AI-drafted pitches and submissions. - Identify high-friction points in the pursuit workflow and translate them into clear, specific improvement briefs with measurable outcomes. - Develop best practices, training materials, prompt libraries, and process documentation to support consistent execution and user adoption across the US team. - Support US Chambers and other legal directory submissions, including process management, stakeholder coordination, and quality control. - Provide hands-on support on priority pitches and submissions, applying AI tools to support drafting, content refinement, and knowledge retrieval. Also earlier responsibilities: "owning and streamlining the US pitch process with AI enablement, working closely with the BD teams; and second, leveraging AI to develop and manage the global pitch content library/repository." That's covered. Now Requirements: We have statements: "This role is suited to someone who knows pursuit work well and wants to transform how it gets done. You bring strong BD knowledge and operational discipline, and understand how AI tools can be applied to the specific, high-friction moments in the pursuit process: building credentials, finding the right matter experience, drafting a pitch under time pressure, managing a directory submission." Also maybe "You bring strong BD knowledge and operational discipline". That's a requirement. We could also include "experience in BD, pursuit work, AI enablement". Not explicit but implied. We'll craft a

    for Requirements. Qualifications: Not explicitly listed besides maybe education? Not present. Could skip Qualifications section. Skills: Could list: BD knowledge, operational discipline, AI application, process improvement, stakeholder coordination, content management, training development, etc. But we might combine with Requirements. However we need to decide if we have enough for Skills separate. The posting mentions "strong BD knowledge and operational discipline, and understand how AI tools can be applied". That's skill. Also "develop best practices, training materials, prompt libraries, process documentation". That's skill. Could create Skills section with bullet list. But we must not invent details; we can extract skill statements. Let's extract skill phrases: - Strong BD knowledge - Operational discipline - Understanding how AI tools can be applied to pursuit process (building credentials, finding matter experience, drafting pitch under time pressure, managing directory submission) - Ability to own and streamline US pitch process end to end - Ability to leverage AI to develop and manage global pitch content library/repository - Ability to own content, experience data, process infrastructure - Ability to build and maintain shared data spine for AI-enabled pursuit work - Ability to develop and maintain reusable pursuit assets (pitch modules, matter descriptions, credential sets, templates, prompt frameworks) - Ability to partner with BD, lawyers, business services teams - Ability to identify high-friction points and translate into improvement briefs with measurable outcomes - Ability to develop best practices, training materials, prompt libraries, process documentation - Ability to support US Chambers and legal directory submissions (process management, stakeholder coordination, quality control) - Ability to provide hands-on support on priority pitches/submissions using AI tools for drafting, content refinement, knowledge retrieval That's a lot; could be considered responsibilities rather than skills. But we can still list skills. Given the instruction to prefer a few substantive sections over many thin ones, maybe we combine Requirements and Skills into one section? But headings are fixed; we could have Requirements and Skills both if they have content. However we risk thin sections. But we have decent content for both. We could make Requirements focus on experience/knowledge needed, and Skills focus on abilities. Let's craft Requirements paragraph: "Candidates should have strong business development knowledge and operational discipline, with experience in pursuit work and an understanding of how AI tools can be applied to high-friction moments such as building credentials, finding matter experience, drafting pitches under time pressure, and managing directory submissions." Skills: bullet list of abilities (maybe summarised). But we need to avoid repetition. We could instead put Skills as bullet list of specific competencies: BD knowledge, operational discipline, AI application, process streamlining, content management, data spine development, reusable asset creation, stakeholder partnership, process improvement, training development, directory submission support, hands-on AI-assisted drafting.