Director, Platform Infrastructure

We need to output HTML fragment with sections: Overview? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. The posting includes Overview, Responsibilities, Qualifications, About Alnylam, Pay range, Benefits description. Also there is a hybrid role location etc. We need to include sections only when posting has real specific content. So we can have sections: Overview (maybe "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting has Overview (which is like About the role). We can map Overview to

About the role

. Responsibilities:

Responsibilities

. Qualifications:

Qualifications

. Benefits:

Benefits

. Pay:

Pay

. Possibly Schedule? Not present. There's mention hybrid role, primarily based in Cambridge, MA. That's location info; could be part of Overview or maybe a separate section? Not required. We'll include location in Overview paragraph. We must not include boilerplate like EEO, E-Verify, privacy notice, application instructions, etc. Also remove duplicated lines. We need to preserve all substantive information. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities list items, we need bullet list. For Qualifications list items, bullet list. For Benefits list items, bullet list. For Pay maybe just a paragraph with the range. We need to avoid filler like "commensurate with experience". Not present. Let's extract content. Overview paragraph: "The Director, Platform Infrastructure will lead Alnylam’s enterprise infrastructure platform strategy, building the secure, resilient, and scalable technology foundation that supports enterprise applications, data and AI, Science, laboratories, Manufacturing, facilities, and critical business operations. This leader will define and execute a multi-year roadmap for platform infrastructure, including cloud services, hosting, storage, data protection, observability, automation, lifecycle management, resiliency, and cloud financial management. The role will lead a team of architects, engineers, and platform/product owners and will govern managed service providers and strategic technology partners to deliver durable, scalable platform capabilities. The ideal candidate brings deep technical expertise, strong enterprise leadership, and financial discipline, with the ability to translate complex infrastructure strategy into practical business outcomes that improve reliability, speed, security, and scalability across Alnylam. This is a hybrid role and will primarily be based in Cambridge, MA." We can keep that as a paragraph under About the role. Responsibilities: list each bullet after "Responsibilities". The text after "Responsibilities" includes a paragraph then bullet-like sentences separated by periods? Actually it's a paragraph with multiple sentences each starting with a verb. We need to turn each into
• . Let's extract: - Define and execute the enterprise platform infrastructure strategy and multi-year roadmap across public cloud, on-premises hosting, storage, data protection, observability, automation, lifecycle management, and FinOps. - Evolve infrastructure services into a platform engineering model that delivers standardized, reusable, automated, and self-service capabilities, including Infrastructure as Code, policy-as-code, platform patterns, and architectural guardrails. - Own the architecture, engineering, and lifecycle of secure, resilient, and scalable hybrid cloud and on-premises platforms supporting enterprise applications, Science, Manufacturing, laboratories, facilities, data, AI, and regulated OT environments. - Partner with Manufacturing, Facilities, Quality, Cybersecurity, laboratory technology, automation, and OT engineering teams to align platform services with validated-state, data-integrity, change-control, security, and business-continuity requirements. - Set enterprise standards for availability, recoverability, observability, capacity, disaster recovery, backup, cyber recovery, technical debt management, lifecycle planning, SLOs, SLIs, and operational health measures. - Lead cloud financial management and FinOps practices, including tagging, allocation, budgeting, forecasting, cost transparency, optimization, unit economics, and financial accountability for cloud consumption. - Build and lead a high-performing infrastructure platform organization across cloud, infrastructure, storage, data protection, observability, automation, and platform engineering. - Govern managed service providers, cloud providers, infrastructure vendors, and technology partners while retaining internal ownership of strategy, architecture, engineering standards, and platform direction. - Manage operating and capital budgets, cloud consumption forecasts, modernization investments, lifecycle roadmaps, capacity plans, and vendor strategies that improve scalability, reliability, security, performance, and financial sustainability. We'll put each as
• . Qualifications: after "Qualifications". The text includes bullet-like sentences separated by periods. Let's extract: - Bachelor’s degree in computer science, information technology, engineering, or a related field required; advanced degree preferred. - 12+ years of progressive experience across enterprise infrastructure, cloud, hosting, storage, data protection, observability, automation, FinOps, or platform engineering, including 5+ years leading infrastructure engineering, architecture, cloud, technical operations, or platform teams. - Demonstrated experience defining and executing infrastructure, cloud, or platform transformation strategies within a complex global enterprise environment. - Strong technical understanding of public and hybrid cloud, compute, virtualization, operating platforms, storage, backup, disaster recovery, cyber recovery, observability, automation, identity integration, networking, and infrastructure security controls. - Experience establishing cloud platforms and governance, including landing zones, account structures, platform guardrails, Infrastructure as Code, automation, policy-as-code, and self-service capabilities within AWS, Azure, or comparable hyperscale environments. - Experience supporting or partnering with teams responsible for regulated OT, laboratory, Manufacturing, facilities, automation, or validated environments; biotechnology, pharmaceutical, life sciences, manufacturing, or other regulated industry experience preferred. - Experience with cloud financial management, FinOps, budgeting, forecasting, capital planning, vendor management, technology investment governance, and managed service provider oversight. - Strong executive communication, stakeholder management, and influencing skills, with the ability to translate complex platform strategies into clear business outcomes. We'll list each as
• . Benefits: after "About Alnylam" there is a paragraph about benefits. Let's extract substantive benefits: "We offer comprehensive benefits including medical, dental, and vision coverage, life and disability insurance, a lifestyle reimbursement program, flexible spending and health savings accounts and a 401(k)with a generous company match. Eligible employees enjoy paid time off, wellness days, holidays, and two company-wide recharge breaks. We also offer generous family resources and leave." We can turn each sentence into list items or keep as paragraph? The instruction: use
  • for any list of duties/requirements/benefits. So we should list benefits as items. Thus: - Medical, dental, and vision coverage - Life and disability insurance - Lifestyle reimbursement program - Flexible spending and health savings accounts - 401(k) with a generous company match - Paid time off, wellness days, holidays, and two company-wide recharge breaks - Generous family resources and leave We could also mention "Alnylam’s robust Total Rewards package is designed to support your overall health and well-being." That's more generic; could be omitted as filler? It's substantive but not a specific benefit. Might keep as paragraph before list. Pay: we have "U.S. Pay Range $186,400 - $252,200 USD". Also mention eligibility for short-term incentive award and long-term incentive award. Also mention base pay determined by factors. We'll include that as paragraph under Pay. Schedule: not present, so omit. We must not include boilerplate like "About Alnylam" description of mission etc. The "About Alnylam" paragraph includes mission statement etc. That's not a section heading per instruction; we could incorporate into Overview or maybe omit as it's not required? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The About Alnylam paragraph is substantive about company. Should we include it? It could be part of Overview or a separate section like "About the company". But the allowed headings list does not include About the company. However we could still include a paragraph without heading? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to include a heading like "About Alnylam" as

    About Alnylam

    though not in list but similar. However they said "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could still use other headings if needed. But to be safe, we could incorporate the About Alnylam description into the Overview paragraph or maybe a separate

    without heading. 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 other headings. I'd include a short paragraph about Alnylam after Overview maybe as

    without heading. But we must preserve ALL substantive information. So we need to include the Alnylam mission description. Let's include it as a paragraph after Overview, maybe under a heading "About Alnylam". Since they didn't forbid, I'll use

    About Alnylam

    . That seems reasonable. Now compile HTML. Structure:

    About the role

    ... overview paragraph ...

    About Alnylam

    ... mission paragraph ...

    Responsibilities

    • ...
    ...

    Qualifications

    • ...
    ...

    Benefits

    • ...
    ...

    Pay

    ... pay range and incentive info ...

    Make sure no extra whitespace? It's fine. Now craft the overview paragraph exactly as given but maybe trim extra spaces. Overview paragraph: "The Director, Platform Infrastructure will lead Alnylam’s enterprise infrastructure platform strategy, building the secure, resilient, and scalable technology foundation that supports enterprise applications, data and AI, Science, laboratories, Manufacturing, facilities, and critical business operations. This leader will define and execute a multi-year roadmap for platform infrastructure, including cloud services, hosting, storage, data protection, observability, automation, lifecycle management, resiliency, and cloud financial management. The role will lead a team of architects, engineers, and platform/product owners and will govern managed service providers and strategic technology partners to deliver durable, scalable platform capabilities. The ideal candidate brings deep technical expertise, strong enterprise leadership, and financial discipline, with the ability to translate complex infrastructure strategy into practical business outcomes that improve reliability, speed, security, and scalability across Alnylam. This is a hybrid role and will primarily be based in Cambridge, MA." Now About Alnylam paragraph: "We are the leader in RNAi therapeutics – a revolutionary approach with the potential to transform the lives of people with rare and common diseases. Built on Nobel Prize-winning science, Alnylam has delivered the breakthroughs that made RNAi therapeutics possible and are just at the beginning of what’s possible. Our deep pipeline, late-stage programs, and bold vision reflect our core values: fierce innovation, passion for excellence, purposeful urgency, open culture and commitment to people. We're proud to be a globally recognized top employer, where an authentic, inclusive culture and breakthrough thinking fuel one another. At Alnylam, we commit to an inclusive recruitment process and equal employment opportunity." We should stop before EEO boilerplate?