Director, eCommerce Engineering

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "About The Role" (which we treat as About the role). Then there is "What You'll Own" which is responsibilities. Also "Qualifications" section. There's also "Benefits" and "Pay" (salary range). There's no explicit Schedule. So we include About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Skills? The posting mentions functional expertise etc but not a separate Skills heading; we could incorporate into Responsibilities or Qualifications. Better to keep only sections with clear headings. We must not repeat job title. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to extract content. Let's parse. First paragraph about WWT etc is introductory fluff; but it's part of posting but not under a heading. Should we include? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The intro is substantive? It's about company. Might be considered boilerplate? Not exactly cookie/navigation/legal/EEO etc. It's descriptive about company. Might be okay to keep as a

  before sections? The instruction says output only HTML fragment; we can include a leading

  with that description. However they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." They didn't forbid other

  outside sections. So we can include an introductory paragraph. But we need to remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The intro about WWT is not boilerplate; it's descriptive. Keep. Then "What is the Internal WWT IT Team, and why join?" That's a heading? Not in list; but it's a section about internal IT team. However the role described later is about unified eCommerce platform, not internal IT team. The "What is the Internal WWT IT Team..." seems like a generic intro maybe not relevant to the specific role? It might be considered boilerplate? It's describing internal IT team, but the role is about eCommerce platform. Might be considered filler. However it's substantive about the team; but the role is about eCommerce platform, not internal IT. The posting seems to mix two things: first they talk about Internal WWT IT team, then "About The Role" about eCommerce platform. Could be that the role is within Internal WWT IT team. So the "What is the Internal WWT IT Team..." is relevant as context. We should keep it. Thus we will have an introductory

  covering the first paragraphs up to "What is the Internal WWT IT Team, and why join?" and its description. Then we have a heading "About The Role". We'll convert to

  About the role

  . Then the content after that until next heading "What You'll Own" maybe considered part of responsibilities. But we can treat "What You'll Own" as a subsection; but we only need to output sections as per headings. We could treat "What You'll Own" as part of Responsibilities. Or we could create a Responsibilities section and put the content from "What You'll Own" and also the bullet-like paragraphs under "About The Role" that describe responsibilities. Better: After About the role heading, we have paragraphs describing the role (own unified eCommerce platform, lead 30 employees, etc). Then there is a subheading "What You'll Own". That seems to be a list of responsibilities. So we can put all that under Responsibilities. Thus we will create a

  Responsibilities

  and include the content from "What You'll Own" bullet points (they are paragraphs with bold headings). We need to convert each bold heading into maybe a
• with the heading as strong? But instruction: Use
  • for any list of duties/requirements/benefits. So we need to make a list. The content includes several bold headings: "Our unified eCommerce platform — the foundation of this role.", "Order Status — including AI-powered agents...", "Customer Projects — a single digital experience...", "Build and unify the organization", "Design and implement a staffing plan...", "Hold your leaders accountable...", "Stay hands-on and set the technical direction", "Know the product as well as the platform", "Partner with Product and UX...", "Deliver results", "Communicate and partner". Each is a paragraph with bold heading then description. We can turn each into
  • with the bold heading as inside the li, then the rest as text. We must preserve all substantive information; not invent or summarize away detail. So we need to copy the text exactly as given, preserving punctuation. Let's extract each. From the posting: "What You'll Own Our unified eCommerce platform — the foundation of this role. One platform delivering a consistent customer experience across multiple brands, digitally connecting our customers to the products and services they purchase from us. It is early in its rollout, so its architecture and direction are still yours to shape. Today that also means the WWT and Softchoice storefronts and customer enablement, run in parallel while the new platform comes online." That's first bullet. Next: "Order Status — including AI-powered agents that surface order details, and shaping where we take AI in the product: how internal and external users interact with order data, and what we're willing to automate." Next: "Customer Projects — a single digital experience representing every phase of a customer engagement, bringing quoting, inventory, services, and the KPIs customers need to succeed into one view, with self-service security and access controls inside their account." Next: "Build and unify the organization Finish unifying the eCommerce engineering organization across WWT and Softchoice — one cohesive team culture, shared engineering standards, and consistent delivery practices across every team.Design and implement a staffing plan that builds healthy, high-performing teams capable of delivering across all platform areas.Hold your leaders accountable for execution and results, and ensure that each team has what it needs to hit their goals." Wait that seems to be three bullet points combined? Actually after Customer Projects, there is "Build and unify the organization" then a long sentence without period? Let's parse: "Build and unify the organization Finish unifying the eCommerce engineering organization across WWT and Softchoice — one cohesive team culture, shared engineering standards, and consistent delivery practices across every team.Design and implement a staffing plan that builds healthy, high-performing teams capable of delivering across all platform areas.Hold your leaders accountable for execution and results, and ensure that each team has what it needs to hit their goals." It seems missing punctuation; but we need to keep as is. Probably intended three separate bullets: Build and unify the organization; Design and implement a staffing plan; Hold your leaders accountable. We'll treat each as separate li. Next: "Stay hands-on and set the technical direction Participate in design as a contributor, not only a reviewer — working through architecture decisions with the team.Pick up a story often enough to know how the codebase and deploy path actually feel.Provide technical leadership and direction, working directly with the teams.Bring AI-native engineering practices into the day-to-day work of your teams — how they design, build, review, and ship.Raise the engineering bar: testing discipline, code quality, observability, and recovery speed." Again seems multiple bullets: Stay hands-on and set the technical direction; Participate in design...; Pick up a story...; Provide technical leadership...; Bring AI-native engineering practices...; Raise the engineering bar... We'll split. Next: "Know the product as well as the platform Become a functional expert in our commerce capabilities — quoting, ordering and checkout, punchout, catalog and pricing, configurators, fulfillment — fluent enough to discuss them with sellers, customers, and business stakeholders without a translator.Partner with Product and UX to make the customer experience an ideal one, not merely a working one. Weigh in on flows, friction, and trade-offs early, while designs are still cheap to change.Bring the customer's and the seller's point of view into engineering decisions — you should be able to say what a change will actually feel like for the person on the other end of it.Use usage data, support escalations, and direct customer feedback to shape what your teams take on next." Again multiple bullets: Know the product as well as the platform; Become a functional expert...; Partner with Product and UX...; Weigh in on flows...; Bring the customer's and seller's point of view...; Use usage data... Next: "Deliver results Own the outcomes and the operation of the platform in every way. Delivery, quality, reliability, cost, and customer experience all land with you.Deliver Customer Projects — quoting, inventory, services, and KPI views, plus the self-service access and security controls — to a high bar.Define the KPIs and SLAs across the platform, Order Status, and Customer Projects, and use the data to measure adoption, performance, and customer impact." Again multiple bullets: Deliver results; Own the outcomes...; Deliver Customer Projects...; Define the KPIs and SLAs... Next: "Communicate and partner Serve as the primary voice for eCommerce engineering strategy with senior leadership, stakeholders, and cross-functional partners — including progress, risks, and the trade-offs behind your decisions.Translate the needs of internal operations teams and external customers into clear priorities your teams can act on.Partner across IT, the business, and Softchoice to make the eCommerce integration succeed on both sides.Work closely with Product Managers to shape and pressure-test the roadmap — influencing priorities while respecting product ownership." Again multiple bullets: Communicate and partner; Serve as the primary voice...; Translate the needs...; Partner across IT...; Work closely with Product Managers... We need to decide how granular to be. The instruction: "Use
    • for any list of duties/requirements/benefits". It doesn't require us to split combined sentences; we could keep each paragraph as a li, even if it contains multiple ideas. That would preserve the content without inventing splitting. Safer: keep each paragraph as a li, preserving the exact text (including missing punctuation). That way we don't invent structure. Thus we will take each paragraph after "What You'll Own" as separate li. Let's extract paragraphs exactly as they appear in the text. I'll copy the relevant section from the posting: "What You'll Own Our unified eCommerce platform — the foundation of this role. One platform delivering a consistent customer experience across multiple brands, digitally connecting our customers to the products and services they purchase from us. It is early in its rollout, so its architecture and direction are still yours to shape. Today that also means the WWT and Softchoice storefronts and customer enablement, run in parallel while the new platform comes online.Order Status — including AI-powered agents that surface order details, and shaping where we take AI in the product: how internal and external users interact with order data, and what we're willing to automate.Customer Projects — a single digital experience representing every phase of a customer engagement, bringing quoting, inventory, services, and the KPIs customers need to succeed into one view, with self-service security and access controls inside their account.Build and unify the organization Finish unifying the eCommerce engineering organization across WWT and Softchoice — one cohesive team culture, shared engineering standards, and consistent delivery practices across every team.Design and implement a staffing plan that builds healthy, high-performing teams capable of delivering across all platform areas.Hold your leaders accountable for execution and results, and ensure that each team has what it needs to hit their goals.Stay hands-on and set the technical direction Participate in design as a contributor, not only a reviewer — working through architecture decisions with the team.P