Global Head of Enterprise Standards

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. The posting includes "About Analog Devices" (company description) but not "About the role". There's a section "The Opportunity" describing role. Could map to "About the role". The posting includes "Responsibilities" heading. It includes "Qualifications" heading. It includes "Preferred Qualifications" but not separate "Skills". Could treat "Preferred Qualifications" as part of Qualifications or Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to include only sections with real content. We have content for About the role (The Opportunity). Responsibilities. Qualifications (including Preferred Qualifications maybe). There's no explicit "Requirements" separate; qualifications cover requirements. There's no Benefits, Pay, Schedule content. There's mention of "Required Travel: Yes, 10% of the time Shift Type: 1st Shift/Days" but that's metadata; we should fold minor metadata into a short

or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we could include a short paragraph for travel/shift info maybe under a generic meta? But we shouldn't create a Benefits/Pay/Schedule section unless posting actually states them. It does not state benefits, pay, schedule beyond shift type and travel. Those are minor metadata; we could include them in a

after the sections, maybe as a note. But we should not create a Schedule heading unless posting actually states schedule; it does state Shift Type: 1st Shift/Days. That's schedule info. Should we create a Schedule section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state shift type, so we could include a Schedule section with that info. However also says "Prefer a few substantive sections over many thin ones." So maybe better to fold that minor metadata into a short

rather than a whole Schedule section. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So shift type and travel are minor metadata; we can fold into a short

. So we will not create Schedule heading. Thus we will have sections: About the role (from The Opportunity), Responsibilities, Qualifications (including Preferred Qualifications maybe as part). Possibly Skills? Not present. We'll not create Skills. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the content from each section verbatim (or close) but formatted as HTML lists/paragraphs. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the EEO paragraph, the export licensing note, the equal opportunity statement, the "EEO is the Law: Notice of Applicant Rights Under the Law." Also the "Job Req Type: Experienced Required Travel: Yes, 10% of the time Shift Type: 1st Shift/Days" we will fold into a short

maybe after sections. Also remove the "About Analog Devices" company description? That's not a heading but it's content about the company; maybe we should keep it as part of About the role? 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." The company description is not a heading; we could keep it as a paragraph before the About the role section? But the instruction says to reformat a job posting into clean, well-structured semantic HTML. Likely we should include the company description as part of the About the role section or maybe as an introductory paragraph. Since there is no explicit "About the role" heading, we could treat the first paragraph after the job title as the About the role content. The posting starts with "About Analog Devices Analog Devices, Inc...." That's company overview. Then "Global Head of Enterprise Standards The Opportunity ..." So we could combine company overview into About the role? Might be okay. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

About the role

Analog Devices, Inc. (NASDAQ: ADI) is a global semiconductor leader that bridges the physical and digital worlds to enable breakthroughs at the Intelligent Edge. ADI combines analog, digital, AI, and software technologies into solutions that combat climate change, reliably connect humans and the world, and help drive advancements in automation and robotics, mobility, healthcare, energy and data centers. With revenue of more than $11 billion in FY25, ADI ensures today's innovators stay Ahead of What's Possible. Learn more at www.analog.com and on LinkedIn and X.

The Opportunity: Analog Devices is seeking a Global Head of Enterprise Standards to provide executive leadership for software quality, functional safety, product security assurance, and Responsible AI governance across products, software, systems, and emerging technologies. This role will shape the strategies, operating models, capabilities, and assurance practices that enable ADI to deliver safe, secure, reliable, and trustworthy products while accelerating responsible innovation. As the enterprise leader for these four critical disciplines, you will partner with executive leadership, engineering organizations, product groups, Legal, Regulatory Affairs, and business teams to embed quality, safety, security, and responsible AI throughout the product and technology lifecycle. A core part of Responsible AI governance will be establishing effective data governance for AI, recognizing that trustworthy outcomes depend on the quality, provenance, ownership, protection, permitted use, and ongoing stewardship of the data used to train, validate, deploy, and monitor AI systems. Standards engagement, certification readiness, regulatory coordination, and governance frameworks will serve as key enablers of this mission, strengthening customer trust, managing enterprise risk, and supporting ADI’s technology leadership.

Then Responsibilities: we have a big block. We'll convert each sentence or bullet? The posting uses line breaks but not bullet list. We need to use

• for any list of duties/requirements/benefits. The responsibilities are a series of statements separated by periods. We could treat each as a list item. Let's extract each duty: - Set the global strategy and operating model for software quality, functional safety, product security assurance, and Responsible AI governance. - Lead and develop global teams of technical leaders and subject-matter experts across these four disciplines. - Drive software development quality and process maturity through risk-based assurance, lifecycle governance, measurement, independent oversight, and continuous improvement. - Establish functional safety capabilities that integrate hazard analysis, safety planning, safety cases, assessment, and assurance into product and system development. - Direct product security assurance across secure development lifecycles, security risk assessment, vulnerability management, product incident readiness, and independent assurance. - Lead Responsible AI governance, including integrated AI and data governance, use-case risk classification, lifecycle controls, human oversight, evaluation, monitoring, and accountability. - Establish data governance as a foundational element of AI governance, with clear accountability for data ownership and stewardship, data quality and fitness for purpose, provenance and lineage, access and usage rights, privacy and security, retention, third-party data, documentation, and controls for training, validation, deployment, and monitoring data. - Partner with enterprise data, privacy, security, legal, and engineering leaders to ensure AI data practices are consistent, traceable, risk-based, and aligned with business objectives and responsible-use commitments. - Ensure development processes support safe, secure, reliable, high-quality, and trustworthy products and solutions. - Define performance measures and assurance reporting that provide executive visibility into maturity, risk, product readiness, and business outcomes. - Enable responsible innovation at scale by embedding proportionate quality, safety, security, and AI governance practices early in the product and technology lifecycle. Then Standards, Certification, and Regulatory Enablement block: - Use relevant standards, regulatory requirements, and certification programs to strengthen software quality, functional safety, product security, and Responsible AI capabilities. - Lead the ADI Standards Office and focus external engagement on standards that materially support product assurance, innovation, customer needs, and market access. - Monitor emerging requirements, assess their implications for the four core disciplines, and sponsor timely readiness plans. - Coordinate enterprise product regulatory activities for CE marking, including applicable EU requirements, conformity-assessment planning, technical documentation, testing and certification evidence, EU Declarations of Conformity, and cross-functional market-readiness decisions. - Oversee certification readiness and continuous improvement where certification provides strategic, customer, regulatory, or operational value. External Engagement and Industry Influence: - Represent ADI in selected standards organizations, industry consortia, certification organizations, and regulatory forums relevant to software quality, functional safety, product security, and Responsible AI. - Build strategic relationships with customers, regulators, certification partners, standards bodies, and industry peers. - Influence future industry practices and benchmarks in areas important to ADI’s products, technologies, and customers. - Position ADI as a recognized leader in safe, secure, high-quality, and trustworthy technology development. Organizational Leadership and Business Impact: - Lead global, multidisciplinary teams and subject-matter experts across software quality, functional safety, product security assurance, Responsible AI, and supporting standards activities. - Set organizational direction, deploy resources, develop talent, and build succession plans for critical technical and governance capabilities. - Drive alignment among business units, engineering organizations, and corporate functions on risk-based product assurance priorities. - Advise and mentor technical and business leaders on quality, safety, security, trustworthy AI, and responsible innovation. - Establish measures for process maturity, product readiness, risk reduction, assurance effectiveness, audit and certification outcomes, and business value. We'll put all these under a single
  • list under Responsibilities heading. Qualifications: we have bullet-like sentences. We'll extract: - Bachelor’s degree in engineering, computer science, software engineering, quality, or a related field, or an equivalent combination of education and relevant experience. - Extensive leadership experience in the semiconductor, technology, software, embedded systems, or a related industry. - Demonstrated executive expertise in multiple core areas among software quality, functional safety, product security assurance, and Responsible AI governance, with the ability to integrate them into an enterprise operating model. - Proven experience building and leading global technical organizations and influencing complex, cross-functional stakeholder groups. - Strong understanding of product and software development lifecycles, risk-based assurance, independent assessment, governance, and continuous improvement. - Demonstrated success improving organizational maturity and embedding quality, safety, security, or trustworthy AI practices into engineering execution. - Exceptional executive communication, influencing, collaboration, and stakeholder-management skills. Preferred Qualifications (we could include as part of Qualifications or separate Skills? The instruction says use headings for Skills if present. Not present. We'll incorporate preferred qualifications as part of Qualifications maybe as a sub-list? But we should preserve all substantive information; we can add a second
    under Qualifications for "Preferred Qualifications". However heading would still be Qualifications; we could have two lists: one for Required Qualifications, one for Preferred Qualifications. That's okay. Thus:

    Qualifications

    • Bachelor’s degree in engineering, computer science, software engineering, quality, or a related field, or an equivalent combination of education and relevant experience.
    • Extensive leadership experience in the semiconductor, technology, software, embedded systems, or a related industry.
    • Demonstrated executive expertise in multiple core areas among software quality, functional safety, product security assurance, and Responsible AI governance, with the ability to integrate them into an enterprise operating model.
    • Proven experience building and leading global technical organizations and influencing complex, cross-functional stakeholder groups.
    • Strong understanding of product and software