SAP Solution Architect Lead

The user wants me to convert this job posting into clean semantic HTML. I need to follow the rules: use

for section headings,

• for lists,

  for prose. Don't repeat job title as heading. Don't include Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate. Only include sections with real content. No filler text. Output only HTML fragment. Let me analyze the content: 1. There's an intro paragraph about company culture - this could be "About the Company" or similar, but the rules say use specific headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". The intro is about the company, not the role. But the posting starts with "About The Role" then "About the Role" again. Actually the first paragraph is company mission, then "About The Role" heading, then "About the Role" again? Let's read: "We believe in bold ideas... About The Role About the Role Wiley is seeking..." So there's a company intro, then a section "About The Role" (maybe heading), then "About the Role" again? Might be duplicate. I'll treat the first paragraph as company overview, but the rules say only include sections when posting has real specific content for it. The headings suggested: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting has "About The Role" (description), "Key Responsibilities" (with subsections), "Required Qualifications & Experience" (with Education, Experience, Technical & Functional Skills, AI & Emerging Technology). Also there's "Clean Core & SAP Best Practices", "Documentation & Design Artefacts", "Cross-Functional Collaboration & Stakeholder Engagement", "AI, Innovation & Forward-Thinking", "Governance & Delivery Oversight", "Project Delivery & Operational Excellence". Those are all responsibilities subsections. The "Key Responsibilities" heading includes multiple sub-headings. I need to decide how to structure. The rules: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I should map the content to these standard headings. The posting has "About The Role" (description), "Key Responsibilities" (with many sub-points), "Required Qualifications & Experience" (with Education, Experience, Technical & Functional Skills, AI & Emerging Technology). There's no explicit Benefits, Pay, Schedule sections. So I should not create those. I'll create sections: - About the role (the introductory paragraph after "About The Role") - Responsibilities (all the key responsibilities subsections combined into a list) - Qualifications (education and experience) - Skills (technical & functional skills, AI & emerging technology) But the responsibilities are grouped into sub-categories: Architecture & Solution Design, Clean Core & SAP Best Practices, Documentation & Design Artefacts, Cross-Functional Collaboration & Stakeholder Engagement, AI, Innovation & Forward-Thinking, Governance & Delivery Oversight, Project Delivery & Operational Excellence. Each has bullet points. I could either make each a sub-list under Responsibilities, or flatten into one big list. The rule: use

  • for any list of duties/requirements/benefits. I think it's okay to have multiple
    under Responsibilities, each preceded by a subheading? But the rule says only

    for section headings. Subheadings maybe not allowed? The example headings are top-level sections. Could use

    ? Not specified. Safer to keep only

    for main sections. For sub-categories, I could include them as bold text within list items or as separate paragraphs. But the content is substantial. I'll include them as separate

    groups with a leading

    Architecture & Solution Design

    then
    . That's acceptable. Similarly for Qualifications: Education, Experience, Technical & Functional Skills, AI & Emerging Technology. I'll make a Qualifications section with sub-lists. Now, the company intro paragraph: "We believe in bold ideas..." This is not a standard heading. Could be "About the Company" but not in the list. The rules say prefer a few substantive sections over many thin ones. I could include it as a paragraph before the first heading, but the output should be HTML fragment. Could just include as a

    at top. But the rules say "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "SAP Solution Architect". Not in the text. The first paragraph is company mission. I'll include it as a

    before the first

    . Now, ensure no boilerplate: there's no EEO, cookie, etc. Good. Now, produce HTML. Let's draft:

    We believe in bold ideas, diverse perspectives, and the drive to transform knowledge into impact. Here, your curiosity fuels progress, your voice shapes innovation, and your ambition helps redefine what’s possible within science and learning. We are a culture that obsesses over impact, challenges, and drives what’s next to power infinite possibilities for our customers, colleagues and society at large.

    About the role

    Wiley is seeking an experienced SAP Solution Architect to serve as a technical and functional authority across our enterprise SAP landscape. Spanning Finance & Controlling (FI/CO), Order-to-Cash (OTC), Revenue Accounting & Reporting (RAR), Warehouse Management (WM), Production Planning (PP), and adjacent modules, this role is central to designing, governing, and guiding end-to-end SAP solutions in alignment with enterprise standards, SAP best practices, and Wiley’s broader digital transformation objectives. The SAP Solution Architect acts as the design authority across the SAP ecosystem — integrating SAP ECC (and/or S/4HANA), BTP, Ariba, Concur, SuccessFactors, finance, supply chain, and third-party systems — while championing a Clean Core approach and enabling Wiley’s strategic roadmap. Working at the intersection of Business, Product, Technology, and Delivery teams, this role translates complex business requirements into well-structured, scalable SAP solutions and produces clear design artifacts that empower delivery teams to execute with confidence. The successful candidate brings deep functional and technical SAP expertise across multiple modules, strong command of integration and architecture patterns, proven experience leading complex transformation programs, and the ability to act as a trusted advisor and thought leader across business and technology functions.

    Responsibilities

    Architecture & Solution Design

    • Lead and architect end-to-end SAP solutions with a strong focus on ECC (and/or S/4HANA), across diverse business domains and enterprise-wide programs.
    • Define comprehensive solution architectures for the full SAP ecosystem, including technical blueprints, integration architectures, cost models, and staffing strategies for significant initiatives.
    • Design scalable, secure, and resilient solution approaches that balance functional requirements, technical soundness, long-term maintainability, and Wiley’s enterprise technology roadmap.
    • Assess and recommend SAP deployment options (ECC, S/4HANA, PCE, RISE with SAP, BTP extensions) for assigned business domains, applying recognized solution architecture methodologies and frameworks.
    • Drive build vs. configure vs. extend vs. integrate decisions to maximize ROI, minimize technical debt, and preserve Clean Core integrity.
    • Evaluate and ensure the scalability, reliability, and performance of SAP solutions, defining non-functional requirements and validating that implemented solutions meet them.
    • Drive solutioning for complex proposals, transformation business cases, and competitive initiatives, clearly articulating value through compelling storytelling and executive-level communication.
    • Leverage AI, intelligent tooling, and automation to create innovative and efficient solution architectures, continuously raising the quality and speed of delivery.

    Clean Core & SAP Best Practices

    • Champion and enforce Clean Core principles across all SAP programs, minimizing customizations and ensuring solutions leverage standard SAP capabilities wherever possible.
    • Architect integrations using standard SAP APIs, events, and SAP Integration Suite (CPI), establishing extension patterns for requirements not met by standard functionality.
    • Oversee the configuration and customization of SAP modules, ensuring all changes are governed, documented, and aligned with enterprise architectural standards.
    • Ensure data consistency and integrity across procurement, finance, reporting, and downstream platforms.
    • Maintain expertise in SAP S/4HANA innovations, BTP services, Clean Core evolution, and RISE/GROW offerings, proactively identifying adoption opportunities.
    • Support SAP Document and Reporting Compliance (DRC) requirements across relevant business and financial processes.

    Documentation & Design Artefacts

    • Produce and maintain comprehensive, clear, and actionable design artefacts including Solution Architecture Documents, Functional Design Documents (FDDs), Technical Design Documents (TDDs), Interface/API Design Specs, and Data Migration blueprints.
    • Create architecture and process flow diagrams that are consumable by both technical and non-technical stakeholders, using tools such as SAP Signavio, LeanIX, or equivalent enterprise process and architecture modelling platforms.
    • Contribute to and maintain the architecture decision logs, capturing rationale, trade-offs, and constraints for key design choices.
    • Ensure all documentation is current, accessible, and serves as a reliable reference for delivery teams, auditors, and governance bodies throughout the project lifecycle.
    • Develop clear technical specifications and integration plans that bridge business requirements and engineering execution without ambiguity.

    Cross-Functional Collaboration & Stakeholder Engagement

    • Act as the primary architecture liaison between IT, Finance, Operations, Procurement, and external partners — ensuring alignment, transparency, and confidence across all stakeholders.
    • Partner with Product Owners, Business Analysts, and executive stakeholders to assess capability requests, validate requirements, estimate effort and feasibility, and contribute to roadmap and investment decisions.
    • Facilitate design workshops, architecture reviews, sprint planning, and transition sessions to ensure clarity before implementation begins and continuity through go-live and stabilization.
    • Translate complex SAP architecture concepts into plain-language guidance for business audiences, and business requirements into precise technical specifications for engineering teams.
    • Collaborate with external SAP partners, system integrators, and SAP advisory teams to leverage best practices, drive quality, and deliver outcomes within architectural guardrails.
    • Provide architectural leadership and governance across system integrators and vendor delivery teams, ensuring solution consistency and accountability.
    • Act as a thought leader and trusted advisor within the SAP community and broader technology landscape, representing Wiley’s architecture perspective in external forums where relevant.
    • Mentor and coach functional and technical team members on SAP architecture principles, integration patterns, and best practices, helping to uplift capability across the SAP practice.

    AI, Innovation & Forward-Thinking

    • Identify and support opportunities to embed AI/ML capabilities — including SAP Joule, BTP AI Core, embedded analytics, and third-party AI integrations — into core SAP processes.
    • Contribute to the assessment and piloting of generative AI use cases for SAP configuration assistance, test automation, intelligent document processing, and predictive operations.
    • Leverage proficiency in AI tooling and intelligent automation to create more efficient, innovative solution architectures and accelerate delivery effectiveness.
    • Support the introduction of modern integration paradigms — event-driven architecture, API-first design, SAP Integration Suite — to modernize Wiley’s SAP footprint.
    • Stay current with SAP’s evolving product landscape and bring relevant adoption ideas to the team, contributing to internal knowledge-sharing, communities of practice, and technology discussions.

    Governance & Delivery Oversight