Blue Yonder WMS Technical Architect

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to preserve all substantive information. Let's parse the posting. First paragraph: "We Are We are a global collective of innovators applying the New every day to improve the way the world works and lives. New doesn’t mean being ahead of the curve; new is pushing forward the curve, riding the edge where the impossible meets the transformational and making it reality where it matters. Help us show the world what’s possible as you partner with clients to unlock hidden value and deliver innovative solutions. Empowered with innovative tools, continuous learning and a global community of diverse talent and perspectives, we drive success in a new business architecture that disrupts conventional practices. Our expertise spans 40+ industries across 120+ countries and impacts millions of lives every day. We turn ideas into reality." That's about the company; could be "About the role"? Actually "About the role" is typical heading for description of role. But we have "You Are A highly experienced Blue Yonder (JDA/RedPrairie) WMS Technical Architect..." That's role description. So we can put that under "About the role" or maybe "Responsibilities"? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - About the role: description of role (You Are...). Could include the "You Are" paragraph. - Responsibilities: The Work section includes "Solution Architecture & Technical Leadership", "Implementation Delivery & Systems Integration", "Cross-Functional Collaboration & Client Leadership", "Practice Growth, Governance & Leadership". Those are responsibilities. - Requirements: "Here’s What You Need" bullet list: Minimum of 3 years experience architecting..., Minimum of 5 years experience leading..., Minimum of 10 years overall corporate experience..., Bachelor's degree or equivalent... Also maybe "Bonus Points If You have..." could be considered "Qualifications" or "Skills". The instructions separate Requirements, Qualifications, Skills. We need to decide. We have "Bonus Points If You have ..." which are additional qualifications/skills. Could be placed under "Qualifications" or "Skills". Since they are "Bonus Points If You have ..." they are desirable qualifications. Could go under "Qualifications". The "Requirements" could be the mandatory minimum experience/education. We also have "Compensation at Accenture varies..." and then salary ranges per location. That's Pay info. Also "Accenture offers a market competitive suite of benefits..." that's Benefits. Travel may be required: "Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements." That's Schedule? Actually schedule could be travel expectation. Could be under "Schedule" (maybe travel). But schedule often refers to work schedule (full-time, part-time, shift). Not present. Travel is more like "Travel". Could be under "Schedule" if we interpret as travel requirement. But instructions: include Schedule section only if posting actually states them. It does state travel may be required and amount varies. So we can include a Schedule section with that info. We also have location list: many cities. That could be under "Location" but not a required heading. Not needed. We must not include boilerplate: EEO statement, accommodation request, etc. Remove those. We must preserve all substantive information: company description, role description, responsibilities, requirements, qualifications/skills, benefits, pay, travel schedule. We must not invent or summarize away detail. Must keep specifics. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

... (company description + You Are paragraph? Actually company description is about the company, not role. But we could include it under About the role as context. Might be okay.) Better: About the role includes the "You Are" paragraph describing the ideal candidate. The company description could be considered part of About the role? Might be okay. But we could also put company description under About the role as introductory. It's substantive. Let's include both: first paragraph about company, then the You Are paragraph. Then Responsibilities: we need to list each responsibility as

• . The responsibilities are broken into four headings with bullet-like paragraphs. We'll extract each bullet. Responsibilities content: - Solution Architecture & Technical Leadership: Lead the architecture, design, and technical delivery of Blue Yonder WMS and WLM solutions across retail, CPG, manufacturing, logistics, and omnichannel fulfillment environments. Facilitate solution blueprinting, architecture workshops, functional mapping, and end-to-end design sessions to validate business requirements and translate them into scalable technical designs. Develop integrated supply chain execution solutions including warehouse management, labor management, automation integration, parcel/carrier systems, and upstream/downstream connections (ERP, OMS, TMS, WCS/MHE, Voice, ASRS). Create and validate technical specifications, configuration scripts, trace file analysis, data structures, and integration frameworks (API, MOCA, Web Services, Middleware). Serve as the technical liaison between project managers, solution architects, product management, and customer stakeholders—including executive sponsors. - Implementation Delivery & Systems Integration: Oversee full lifecycle implementation activities including environment setup, software installation, configuration, performance tuning, technical testing, and operational readiness. Lead the configuration and technical build of BY WMS, ensuring alignment to solution design, business rules, and operational needs. Guide and support integration testing, user acceptance testing, regression testing, and stabilization/hypercare. Ensure delivery architecture, technical components, and interfaces are consistent, scalable, secure, and aligned across the enterprise. Troubleshoot complex system issues using in-depth knowledge of trace files, data flows, database structures, and integration logs. - Cross-Functional Collaboration & Client Leadership: Act as a trusted technical advisor to senior client stakeholders, influencing architecture decisions, platform strategy, automation readiness, and integration approaches. Collaborate with Delivery Leads on planning, estimating, and shaping new opportunities, RFP responses, and solution proposals. Lead business and technical workshops including maturity assessments, gap analysis, value mapping, requirements gathering, and solution validation. Build strong working relationships with product development teams, ecosystem partners (KNAPP, conveyor systems, parcel systems, WCS providers), and client operations/IT leaders. Drive knowledge transfer, best practices, and architectural standards to both clients and project teams. - Practice Growth, Governance & Leadership: Mentor junior team members, build technical capability, and elevate delivery practices across the Blue Yonder practice. Contribute to internal accelerators, best-practice collateral, reusable assets, and technical frameworks. Stay ahead of technology trends including cloud platforms (Azure/GCP), IoT/automation, AI-driven optimization, and advanced warehouse technologies. Ensure adherence to delivery methodology, quality standards, and governance processes including time/expense compliance and solution documentation. Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements. Note: Travel sentence appears here; we might move travel to Schedule section. But it's within this responsibility block. We could keep it there, but then we would also have a Schedule section duplicating. Better to extract travel to Schedule section and remove from responsibilities. However we must preserve all substantive information; moving is okay as long as we keep it somewhere. We'll put travel under Schedule. Thus responsibilities will exclude the travel sentence. Now Requirements: The "Here’s What You Need" list: - Minimum of 3 years of experience architecting, designing, or implementing Blue Yonder/JDA/RedPrairie WMS and/or WLM solutions. - Minimum of 5 years of experience leading medium to large-scale WMS projects through full lifecycle delivery. - Minimum of 10 years of overall corporate experience in supply chain, warehouse operations, logistics technology, or enterprise system integration. - Bachelor's degree or equivalent (minimum 12 years work experience). If Associate’s Degree, must have equivalent (minimum 6 years work experience) We'll put these as
  • . Now Qualifications: Could be the "Bonus Points If You have ..." list. That's a bunch of bullet points. We'll put under Qualifications. Skills: Could be maybe we don't have separate skills beyond qualifications. But we could treat the bonus points as Skills. However we already have Qualifications. The instructions list both Qualifications and Skills as possible headings. We need to decide if we have content for both. The bonus points are more like "desired qualifications/skills". Could split: Qualifications = education/experience requirements? But we already used Requirements for mandatory. Qualifications could be the bonus points. Skills could be maybe we don't have separate. Could we treat the bonus points as Skills? But then Qualifications would be empty. Better to put bonus points under Qualifications and leave Skills omitted (since no specific skill list beyond that). However the instructions say: Prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one section? But headings are fixed; we can only output those headings if we have content. If we have only one of them, we output that heading. If we have both, we output both. Since we have bonus points that could be considered both qualifications and skills, we could split them arbitrarily but risk duplication. Better to output Qualifications for the bonus points, and omit Skills. Now Benefits: "Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more information on our benefits here: U.S. Employee Benefits | Accenture" We'll keep the link as is. Pay: Compensation section includes salary ranges per location. We'll output as
    • each location range. Schedule: Travel may be required... We'll output that. We must not include boilerplate: EEO statement, accommodation request, equal opportunity statement, etc. Also remove the "Requesting an Accommodation" paragraph, the EEO statement, the "Other Employment Statements" about work authorization, etc. Also remove the "We Are We are a global collective..." duplication? It appears at start: "We Are We are a global collective..." There's a duplicate "We Are". We'll keep the content but fix duplication? The text says "We Are We are a global collective..." Likely a typo; we should preserve the substantive information but not invent. We'll keep as is? Might be weird but we must preserve all substantive information; we cannot edit to fix duplication unless it's clearly a mistake? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say we cannot correct obvious typos. But safer to keep as is. However the duplication "We Are We are" is likely a mistake; but removing a word could be considered summarizing away detail? It's minor. I'd keep the exact text as given. Now we need to ensure we don't include any navigation/footer etc. Let's craft HTML. We'll start with

      About the role

      We Are We are a global collective of innovators applying the New every day to improve the way the world works and lives. New doesn’t mean being ahead of the curve; new is pushing forward the curve, riding the edge where the impossible meets the transformational and making it reality where it matters. Help us show the world what’s possible as you partner with clients to unlock hidden value and deliver innovative solutions. Empowered with innovative tools, continuous learning and a global community of diverse talent and perspectives, we drive success in a new business architecture that disrupts conventional practices. Our expertise spans 40+ industries across