Business System Analyst

We need to output HTML fragment with sections: About the role (but note the page already shows job title, we should not repeat job title as heading). The posting includes "About Wing" (company description) and "About the Role". The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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. We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions). So we need to strip out the EEO paragraph, accommodation request, etc. Also remove "Wing is an equal opportunity employer..." etc. Also remove "If you have a need that requires accommodation..." etc. We need to include sections only when posting has real, specific content. We have About Wing (company description) - maybe we treat as "About the company"? Not listed as allowed heading but we could use

for "About Wing"? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Probably we should stick to those headings where applicable. The posting includes "About Wing" (company overview) and "About the Role". The "About the Role" could map to "About the role". The "About Wing" could be considered company description; maybe we can put it under a heading like "About the company" but not in list. However instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but we should follow the spirit: use those headings for sections. Could we treat "About Wing" as a

without heading? Probably better to include a heading "About the company" but not in list; but maybe they'd accept. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings. So we should map content to those headings. We have: - About Wing: company description. Could be placed under a heading like "About the company" but not in list. Maybe we can omit heading and just put as

after an

"About the role"? No, that would be confusing. Alternatively, we could treat "About Wing" as part of "About the role" section? Not ideal. Maybe we can create a section "About the company" using

even though not listed; the instruction says "e.g." meaning examples, not exhaustive. So it's okay. Thus we will have:

About Wing

Wing offers drone delivery as a safe, fast, and sustainable solution for last mile logistics. Consumer appetites for on-demand services are increasing, but current delivery methods are inefficient, costly, and contribute to road accidents and air pollution. Wing’s fleet of highly automated delivery drones can transport small packages directly from businesses to homes on-demand, in minutes. We design, build, and operate our aircraft, and offer drone delivery services on two continents. Our technology is designed to be easy to integrate into existing delivery and logistics networks, offering a scalable drone delivery solution for a broad range of businesses. Wing is a part of Google's parent company, Alphabet, and our mission is to create the preferred means of delivery for the planet. If you're ready to do the greatest work of your life, come join us.

Then

About the role

We are looking for a seasoned Business System Analyst with deep expertise in SAP MM/SCM/S2P (Material Management, Supply Chain Management and Source to Pay). This role is based remotely in the United States.

Then responsibilities: "What You’ll Do:" list. We need to convert each bullet into

• . The bullet points: - Configure SAP Materials Management (MM), Logistics Execution (LE), Source to Pay (S2P) while collaborating with global business and technology teams to deliver successful SAP solutions. - Support business development initiatives by project estimation and system demonstrations to capture SAP S/4HANA implementation. - Serve as the primary functional architect for SAP PP/MM, ensuring seamless integration across warehouse, execution, and broader supply chain systems - Configure S4 HANA for end to end business requirements including material master, Vendor Master, Purchase orders, Stock transfer orders, Vendor Invoice, Source List , Shipment Documents, Returns and Refurbishment, EDI integrations, Idocs Integration with other boundary systems. - Collaborate with cross-functional teams including SAP SD and FI to ensure end-to-end process integration. - Create functional specifications, support testing, deployment, and user training activities. We'll put under

  Responsibilities

  with a
  . Then requirements: "What You’ll Need:" list. - 8 years of experience in implementing & configuring SAP MM/ Logistics / Source to Pay modules and integration with boundary systems. - SAP SCM experience with at least 3 end-to-end SAP Implementations. - Exceptional analytical skills and attention to detail, with an ability to quickly grasp technical concepts. - Hands-on SAP ERP MM / Logistics Execution/ Shipment / S2P configuration experience. - Experience integrating SAP with non-SAP applications using Idocs, EDI, APIs, file transfer technologies, and related integration tools. - Cross-functional understanding of SAP SD, EWM/TMS and SAP FI modules. We'll put under

  Requirements

  with
  . Then we have salary info: "The US base salary range for this full-time position is the salary range below + bonus + equity + benefits. Wing’s salary ranges are determined by role, level, and location. Your recruiter can share more about the specific salary range for your location during the hiring process. Salary Range: $140,000 USD - $185,000 USD" We need to include Pay section only if posting actually states them. It does state salary range. So we should create

  Pay

  with

  The US base salary range for this full-time position is $140,000 USD - $185,000 USD, plus bonus, equity, and benefits.

  (We should preserve the info about bonus+equity+benefits). Also note that the text says "The US base salary range for this full-time position is the salary range below + bonus + equity + benefits." So we can combine. We should not include Benefits or Schedule sections unless stated. There's no explicit benefits description beyond "bonus + equity + benefits". Could we create a Benefits section? The posting mentions benefits generically but not specific. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits in general (bonus + equity + benefits). That is a statement of benefits existing, but not specific details. Might be considered stating them. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "bonus + equity + benefits". So we could include a Benefits section with that statement. But we already included benefits in Pay section. Might be redundant. Better to keep Pay section only, and not create a separate Benefits section unless there are specific benefits listed (like health insurance, 401k, etc). There aren't. So we will not create Benefits section. Schedule: not mentioned, so omit. We also need to remove boilerplate: EEO paragraph, accommodation request, etc. Also remove duplicated lines (none). Also remove "Wing is an equal opportunity employer..." etc. We also need to remove "If you're ready to do the greatest work of your life, come join us." That's part of About Wing; it's substantive? It's a call to action but maybe considered boilerplate? It's not EEO/legal; it's a motivational tagline. Might be okay to keep. It's part of the company description. We'll keep. Now produce HTML fragment:

  About Wing

  Wing offers drone delivery as a safe, fast, and sustainable solution for last mile logistics. Consumer appetites for on-demand services are increasing, but current delivery methods are inefficient, costly, and contribute to road accidents and air pollution. Wing’s fleet of highly automated delivery drones can transport small packages directly from businesses to homes on-demand, in minutes. We design, build, and operate our aircraft, and offer drone delivery services on two continents. Our technology is designed to be easy to integrate into existing delivery and logistics networks, offering a scalable drone delivery solution for a broad range of businesses. Wing is a part of Google's parent company, Alphabet, and our mission is to create the preferred means of delivery for the planet. If you're ready to do the greatest work of your life, come join us.

  About the role

  We are looking for a seasoned Business System Analyst with deep expertise in SAP MM/SCM/S2P (Material Management, Supply Chain Management and Source to Pay). This role is based remotely in the United States.

  Responsibilities

  • Configure SAP Materials Management (MM), Logistics Execution (LE), Source to Pay (S2P) while collaborating with global business and technology teams to deliver successful SAP solutions.
  • Support business development initiatives by project estimation and system demonstrations to capture SAP S/4HANA implementation.
  • Serve as the primary functional architect for SAP PP/MM, ensuring seamless integration across warehouse, execution, and broader supply chain systems
  • Configure S4 HANA for end to end business requirements including material master, Vendor Master, Purchase orders, Stock transfer orders, Vendor Invoice, Source List , Shipment Documents, Returns and Refurbishment, EDI integrations, Idocs Integration with other boundary systems.
  • Collaborate with cross-functional teams including SAP SD and FI to ensure end-to-end process integration.
  • Create functional specifications, support testing, deployment, and user training activities.

  Requirements

  • 8 years of experience in implementing & configuring SAP MM/ Logistics / Source to Pay modules and integration with boundary systems.
  • SAP SCM experience with at least 3 end-to-end SAP Implementations.
  • Exceptional analytical skills and attention to detail, with an ability to quickly grasp technical concepts.
  • Hands-on SAP ERP MM / Logistics Execution/ Shipment / S2P configuration experience.
  • Experience integrating SAP with non-SAP applications using Idocs, EDI, APIs, file transfer technologies, and related integration tools.
  • Cross-functional understanding of SAP SD, EWM/TMS and SAP FI modules.

  Pay

  The US base salary range for this full-time position is $140,000 USD - $185,000 USD, plus bonus, equity, and benefits.

  Check for any leftover boilerplate: We removed EEO, accommodation request. Also removed "Wing’s salary ranges are determined by role, level, and location. Your recruiter can share more about the specific salary range for your location during the hiring process." That's generic but still substantive? It's about salary determination; we could incorporate into Pay section maybe. But we already have Pay section with range. The extra sentence is generic but could be considered filler. The instruction: "Preserve ALL substantive information; do