Principal Enterprise Architect, Retail Systems

We need to output HTML fragment with sections as per rules. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Content includes: - Category/Area of Expertise: IT & Technology (maybe not needed) - Job Requisition: 536012 (metadata, drop) - Address: USA-MA-Quincy-1385 Hancock Street (metadata) - Description: Ahold Delhaize USA ... (intro paragraph) - Then "As the Principal Enterprise Architect for Core Retail Systems, you will shape..." (intro) - Then "This role requires a rare blend..." (intro) - Then "Our flexible/hybrid work schedule includes 3 in-person days at one of our core locations and 2 remote days. Our core office locations are Salisbury, NC, Chicago, IL, & Quincy, MA." (Schedule info) - "Applicants must be currently authorized to work in the United States on a full-time basis." (maybe part of Requirements) - Then "Primary Purpose" heading (maybe About the role) - Then "Sets the enterprise technology vision and operating model, orchestrating cross domain roadmaps, standards, and governance to ensure technology investments deliver measurable business value." (About the role) - Then "Duties and Responsivities" (typo) list of duties (multiple bullet-like sentences). We'll treat as list items. - Then "Qualifications" heading with bullet list. - Then "Preferred Qualifications" heading with bullet list. - Then "Salary Range: $163,280-$244,920" (Pay) - Then paragraph about incentive bonus etc. - Then paragraph about company values etc (maybe About the role or Benefits? Not specific benefits). Benefits not listed explicitly; we have no benefits details besides maybe incentive bonus? There's mention of incentive bonus based on company performance. Could be considered Benefits? But we need specific content for Benefits section; we have incentive bonus mention. Could include that as Benefits? However Benefits section should be for benefits like health, retirement etc. Not present. So we should not create Benefits unless real specific content. Incentive bonus could be considered compensation, not benefits. So we may omit Benefits. - Pay: we have salary range. So include Pay section with that range. - Schedule: we have flexible/hybrid work schedule details. So include Schedule section. - About the role: we have Primary Purpose and intro paragraphs. Could combine into About the role. - Responsibilities: Duties and Responsivities list. - Requirements: maybe the qualifications (Bachelor's degree etc) and authorization to work. Could be Requirements. - Qualifications: we have Qualifications and Preferred Qualifications. Could combine? But we have both Qualifications and Preferred Qualifications headings. According to rules, we can have Qualifications section (maybe required) and Skills? But we have Skills not explicitly listed. Could treat Qualifications as required qualifications, and Preferred Qualifications as maybe Skills? But better to follow: Qualifications section for required qualifications; Skills maybe not present; we could omit Skills. We need to avoid duplicate content. Let's extract. Intro paragraphs: "Ahold Delhaize USA, a division of global food retailer Ahold Delhaize, is part of the U.S. family of brands, which includes five leading omnichannel grocery brands - Food Lion, Giant Food, The GIANT Company, Hannaford and Stop & Shop. Our associates support the brands with a wide range of services, including Finance, Legal, Sustainability, Commercial, Digital and E-commerce, Technology and more. As the Principal Enterprise Architect for Core Retail Systems, you will shape the technology foundation that enables ADUSA's omnichannel grocery strategy across stores, e-commerce, loyalty, merchandising, supply chain, fulfillment, customer engagement, and enterprise platforms. You will partner with business, product, and engineering leaders to design and govern scalable platforms that connect physical and digital experiences, improve operational agility, and enable consistent, personalized shopper journeys across ADUSA's family of brands. Your contributions will advance the platforms that power retail operations, customer engagement, digital commerce, loyalty, merchandising, supply chain, and store fulfillment. This role will help ensure ADUSA can serve customers consistently across channels, whether they shop in-store, online, through pickup, delivery, loyalty offers, or future digital experiences. This role requires a rare blend of strategic vision, architectural expertise, and a passion for innovation. You'll craft enterprise roadmaps that influence long-term strategy while ensuring solutions remain flexible, scalable, and aligned to the ever-changing needs of customers. By bridging business and technology, you'll enable platforms that don't just support retail-they redefine it." That's good for About the role. Primary Purpose: "Sets the enterprise technology vision and operating model, orchestrating cross domain roadmaps, standards, and governance to ensure technology investments deliver measurable business value." Could be part of About the role as well. Duties and Responsibilities list: - Aligns enterprise technology strategy and multiyear roadmaps to business objectives, omnichannel growth - Defines enterprise blueprints that synthesize business, customer journey, information, application, integration, infrastructure, data, and security viewpoints across store, digital, fulfillment, loyalty, and enterprise capabilities. - Establishes architecture principles, reference architectures, technology standards, and rationalization guidelines. - Chairs enterprise design authority/governance to guide decisions on scope, quality, risk, and total cost of ownership. - Measures the value of enterprise architecture services; reports outcomes, adoption, and technical debt trends. - Advises executives on industry trends and emerging technologies; shapes build/buy/retire decisions. - Mentors' principal/solution/domain architects; raises architecture maturity, methods, and tooling across Tech. - Drives alignment across major transformation initiatives, ensuring architecture consistency across portfolios, domains, and strategic programs. - Partners with product, engineering, and platform leaders to embed architecture practices into delivery, ensuring solutions adhere to enterprise standards and long-term technology strategy. We'll put each as

. Qualifications (required): - Bachelor's degree or equivalent years of work experience. - 12+ years in architecture with demonstrated leadership across complex, multi domain portfolios. - Expertise in enterprise architecture practices (principles, standards, governance), roadmap development, and cost/value modeling. - Exceptional communication, executive influence, and decision framing skills. - Strong understanding of GenAI & Agentic patterns, including RAG, fine-tuning, prompt engineering, agent orchestration, and model serving approaches. Preferred Qualifications: - Experience with architecture frameworks (e.g., TOGAF), modeling (e.g., ArchiMate/UML), and portfolio governance. - Background spanning cloud, data, integration, security, and end user domains - Experience architecting omnichannel retail capabilities across store systems, e-commerce, loyalty, merchandising, supply chain, fulfillment, customer engagement, and enterprise platforms. - Demonstrated ability to connect business strategy, customer journeys, operational processes, data flows, and technology platforms into executable architecture roadmaps. - Experience with modern retail architecture patterns, including API-led integration, event-driven architecture, master/reference data, inventory visibility, order orchestration, personalization, and platform rationalization. - Ability to evaluate technology investments through both business and architecture lenses, including customer experience, operational resilience, speed to market, platform reuse, and total cost of ownership. Pay: Salary Range: $163,280-$244,920 Schedule: Our flexible/hybrid work schedule includes 3 in-person days at one of our core locations and 2 remote days. Our core office locations are Salisbury, NC, Chicago, IL, & Quincy, MA. Also mention Applicants must be currently authorized to work in the United States on a full-time basis. Could be part of Requirements. We could add a Requirement: "Must be currently authorized to work in the United States on a full-time basis." Now we need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. Possibly also Skills? Not present. We should not repeat job title as heading. Already not. We should not include Job ID etc. We should not include boilerplate like EEO etc (not present). Good. We need to wrap each section in

heading then content: for prose use

, for lists use

• . We need to decide what goes into About the role: combine intro paragraphs and Primary Purpose maybe as a paragraph. Let's craft:

  About the role

  Ahold Delhaize USA, a division of global food retailer Ahold Delhaize, is part of the U.S. family of brands, which includes five leading omnichannel grocery brands - Food Lion, Giant Food, The GIANT Company, Hannaford and Stop & Shop. Our associates support the brands with a wide range of services, including Finance, Legal, Sustainability, Commercial, Digital and E-commerce, Technology and more. As the Principal Enterprise Architect for Core Retail Systems, you will shape the technology foundation that enables ADUSA's omnichannel grocery strategy across stores, e-commerce, loyalty, merchandising, supply chain, fulfillment, customer engagement, and enterprise platforms. You will partner with business, product, and engineering leaders to design and govern scalable platforms that connect physical and digital experiences, improve operational agility, and enable consistent, personalized shopper journeys across ADUSA's family of brands. Your contributions will advance the platforms that power retail operations, customer engagement, digital commerce, loyalty, merchandising, supply chain, and store fulfillment. This role will help ensure ADUSA can serve customers consistently across channels, whether they shop in-store, online, through pickup, delivery, loyalty offers, or future digital experiences. This role requires a rare blend of strategic vision, architectural expertise, and a passion for innovation. You'll craft enterprise roadmaps that influence long-term strategy while ensuring solutions remain flexible, scalable, and aligned to the ever-changing needs of customers. By bridging business and technology, you'll enable platforms that don't just support retail-they redefine it.

  Sets the enterprise technology vision and operating model, orchestrating cross domain roadmaps, standards, and governance to ensure technology investments deliver measurable business value.

  That's fine. Responsibilities:

  Responsibilities

  with each duty. Requirements: maybe combine authorization and maybe basic eligibility? Could also include Bachelor's degree etc but those are qualifications. We'll treat Requirements as eligibility: "Must be currently authorized to work in the United States on a full-time basis." Could also include that it's full-time. We'll put as

  . Qualifications:

  Qualifications

  with required qualifications. Pay:

  Pay

  Salary Range: $163,280-$244,920

  Schedule:

  Schedule

  Our flexible/hybrid work schedule includes 3 in-person days at one of our core locations and 2 remote days. Our core office locations are Salisbury, NC, Chicago, IL, & Quincy, MA.

  We might also include mention of incentive bonus? That's compensation but not base salary; could be part of Pay? But we already have Pay. Could add sentence: "This position is eligible for an incentive bonus based on company performance." Could add to Pay paragraph. Let's incorporate: Pay paragraph: "Salary Range: $163,280-$244,920. This position is eligible for an incentive bonus based on company performance." Now ensure we didn't invent content. All content is from posting. Check for duplication: We included intro paragraphs and Primary Purpose; we didn't repeat the same sentences elsewhere. Check for any missing content: We omitted the "Preferred Qualifications" section; we could treat them as Skills? But we have no Skills section. Could we add a Skills section for preferred qualifications? The rules say use Skills heading for skills. Preferred qualifications could be considered skills. But we already have Qualifications section for required qualifications. We could add a Skills section for preferred qualifications. However the instruction: "Prefer a few