Executive Director, API Development, Small Molecule

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, no summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to parse the posting. Key sections: - About The Role: paragraph after "About The Role". That is a prose description. - What You'll Do: list of duties/responsibilities. Should go under Responsibilities. - Who You Are: qualifications, requirements, skills. Could be split into Requirements (education/experience), Qualifications (maybe same), Skills (specific abilities). But we need to decide based on content. - Nice To Have (but Not Required): could be Skills? Or maybe additional qualifications. - Where You'll Work: location info (fully remote, occasional travel). That could be Schedule? Actually schedule is about work hours; location is not schedule. Could be a separate section like Work Location but not in allowed headings. Since only allowed headings are those listed, we might put location info under Schedule? Not appropriate. Could put under Benefits? Not. Maybe we can omit location if not covered by allowed headings? But we must preserve ALL substantive information. However instructions: "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it". Allowed headings are given; we can only use those headings. If content doesn't fit any, maybe we omit? But we must preserve all substantive info; maybe we can incorporate location info into a

under a relevant heading like Responsibilities? Not ideal. Could create a "Schedule" section for travel expectations? Travel is occasional travel 25%; that could be under Schedule (maybe work schedule includes travel). Could also put location info under Benefits? Not. Pay Range: we have Pay Range $247,000.00-337,000.00 Annual. So we need a Pay section. Benefits: we have "Life at Insmed" with highlights of US offerings: medical, dental, vision, mental health, wellbeing reimbursement, EAP, PTO, fertility benefits, caregiver support, flexible work schedules, 401(k), equity awards, ESPP, company-paid life/disability, Learning Institute, ERGs, service/recognition programs, volunteer opportunities. That's benefits. Thus we can have Benefits section. About the role: we have a paragraph. Responsibilities: from "What You'll Do" bullet list. Requirements: education/experience: "You have a PhD along with 10 years of CMC experience or MS and 12 years of CMC experience or BS and 15 years of CMC experience within the pharmaceutical industry." Qualifications: maybe the list of expertise: "Extensive expertise in route design, process development, technology transfer, process validation, manufacturing sciences, regulatory strategy, and commercialization readiness for small molecule APIs" etc. Could be under Qualifications. Skills: maybe the list of abilities: "strong commitment to experimental work... ability to independently identify and solve complex problems... Thorough understanding of cGxP, CMC, ICH and compendial (USP/EP/JP) regulatory requirements... Experienced with authoring, reviewing and approving CMC sections of regulatory submissions... Demonstrated track record of managing multiple programs, resources and staff... Extensive expertise in working with CRO/CMO's... Track record of driving transformational change... Exceptional communication, negotiation, and influencing skills..." Nice To Have: "Experience with compounds used for inhalation and combination products" could be under Skills as a nice-to-have bullet. Where You'll Work: remote, occasional travel 25%. Could be under Schedule? Schedule could include travel expectations. Or we could create a separate section not in allowed headings but instructions say use those headings for section headings. It didn't say we cannot add other headings, but says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the allowed headings; we should stick to them. So we need to fit location/travel into one of those. Perhaps Schedule can include travel expectations and remote work. So we can put a Schedule section with remote work and travel 25%. Pay section: we have Pay Range. Now we must not include boilerplate like EEO, legal, application instructions, etc. So we need to strip out all that. We must preserve all substantive information: that includes the description about Insmed, mission, recognition, etc. That is in the opening paragraph before About The Role. Should we include that? It's substantive about company. Could be placed under About the role? Actually About the role section is about the role, not company. But we could include a brief intro before headings? The instruction: "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." It doesn't forbid having a leading paragraph before any heading. So we can include an introductory paragraph about Insmed mission etc. That is substantive. Thus output HTML fragment: maybe start with a

containing the introductory sentences: "At Insmed, every moment and every patient counts — and so does every person who joins in. As a global biopharmaceutical company dedicated to transforming the lives of patients with serious and rare diseases, you’ll be part of a community that prioritizes the human experience, celebrates curiosity, and values every person’s contributions to meaningful progress. That commitment has earned us recognition as Science magazine’s No. 1 Top Employer for five consecutive years, certification as a Great Place to Work® in the U.S., and a place on The Sunday Times Best Places to Work list in the UK. For patients, for each other, and for the future of science, we’re in. Are you?" Then

About the role

with paragraph about role. Then

Responsibilities

with

• items from What You'll Do. Then

  Requirements

  with paragraph about education/experience. Then

  Qualifications

  with
  • items from the expertise list (the long list after "You Are Or You Also Have"). Then

    Skills

    with
    • items from the abilities list (commitment to experimental work, problem solving, understanding of cGxP, authoring CMC sections, managing programs, working with CRO/CMO, driving transformational change, communication/negotiation/influencing skills) plus Nice To Have item. Then

      Benefits

      with
      • items from Life at Insmed highlights. Then

        Pay

        with paragraph about Pay Range. Then

        Schedule

        with paragraph about fully remote role, occasional travel approx 25%. We must not include any filler like "commensurate with experience". Not present. We must not include duplicated lines. Ensure we don't repeat. Now craft HTML. Check for any content that might be considered boilerplate: The "Life at Insmed" section includes "Eligibility for specific programs may vary and is subject to the terms and conditions of each plan." That's a bit boilerplate but still substantive? It's a disclaimer. Might be considered boilerplate but it's about benefits eligibility. Could keep but maybe it's okay. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." That line is not exactly legal but could be considered a disclaimer. Might be safe to keep? It's not EEO. It's about eligibility. I'd keep it as part of benefits. Also "Current Insmed Employees: Please apply via the Jobs Hub in Workday." That's application instruction; must remove. All the EEO statement etc must be removed. Now produce final HTML. Let's draft. Intro paragraph: combine the first few sentences up to "Are you?" Actually the posting includes that as a tagline before About The Role. We'll include that as intro. Then About the role paragraph: "We’re looking for an Executive Director, API Development, Small Molecule on the CMC Product Development team to help us expand what’s possible for patients with serious diseases. Reporting to the Vice President of Product Development – CMC, Small Molecule, you’ll lead the strategic direction of the API Development for the company’s small molecule pipeline within Technical Operations. You’ll oversee synthesis and process development activities for preclinical and clinical candidates, including laboratory experimentation for compound preparation. You will serve as a key advisor to executive leadership on development strategy, manufacturing technologies, and portfolio decisions, while building organizational capabilities and developing future leaders." Now Responsibilities: list items from "What You'll Do" and the bullet list after "You’ll also:" (the bullet list). Let's extract each bullet: - Establish and execute the long-term vision, strategy, and operating model for API Development, ensuring alignment with portfolio objectives and corporate strategy - Provide strategic leadership for API development, API process development, technology transfer, process validation, manufacturing readiness, and lifecycle management across development programs - Serve as a key member of the Technical Operations leadership teams, influencing portfolio decisions, resource allocation, risk mitigation strategies, and investment priorities - Direct the design and scale-up of processes, instruments and equipment from the laboratory through pilot plant and manufacturing scale-up - Manage the science and engineering underlying the development, implementation, and maintenance of process methods and equipment for the production of process formulas, technologies and products to achieve cost effectiveness and improved product quality - Plan and implement the development of new process formulas, establishes operating equipment specifications and improves manufacturing techniques and new process equipment production - Regularly interact with vendors, regulatory bodies and other external stakeholders exerting influence and negotiating to drive business results - Represent the company externally through scientific publications, conference presentations, industry forums, advisory boards, and strategic collaborations - Develop organizational talent through coaching, succession planning, leadership development, and creation of a high-performing and inclusive culture - Establish enterprise metrics and performance frameworks that ensure execution excellence, accountability, and continuous improvement across the Pharmaceutical Development function Check for duplicates: none. Now Requirements: paragraph: "You have a PhD along with 10 years of CMC experience or MS and 12 years of CMC experience or BS and 15 years of CMC experience within the pharmaceutical industry." Now Qualifications: list from "You Are Or You Also Have" (the long list). Let's extract each bullet: - Extensive expertise in route design, process development, technology transfer, process validation, manufacturing sciences, regulatory strategy, and commercialization readiness for small molecule APIs - A strong commitment to experimental work is essential, as well as the ability to independently identify and solve complex problems to advance projects through the development process - Thorough understanding of cGxP, CMC, ICH and compendial (USP/EP/JP) regulatory requirements - Experienced with authoring, reviewing and approving CMC sections of regulatory submissions including INDs, NDAs/MAAs and other required documentation - Demonstrated track record of managing multiple programs, resources and staff from early discovery through commercialization - Extensive expertise in working with CRO/CMO's both as a lead and a team member - Track record of driving transformational change, organizational capability building, and continuous improvement initiatives - Exceptional communication, negotiation, and influencing skills, including interactions with executive leadership, regulatory agencies, external partners, and scientific organizations Note: Some of these overlap with Skills; but we already put some in Skills. To avoid duplication, we need to decide split. The instruction: "Prefer a few substantive sections over many thin ones." We could combine Qualifications and Skills maybe. But we need to follow headings list; we can still have both but ensure content