Business Systems Analyst

We need to output HTML fragment with sections: About the role? The posting includes summary paragraphs. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. The posting includes: Summary (intro), then "Here’s what you need to succeed in the role:" which is requirements/qualifications. Then "You will be responsible for:" which is responsibilities. Then "At ALOM, we are committed to fair and equitable pay. Compensation ..." includes pay info but vague: "Compensation is determined based on relevant skills and experience, the position’s location, internal equity, and local market considerations." That's not specific numbers, but it's still pay info. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation discussion, but not specific numbers. It says "We offer competitive salaries, benefits including health and welfare coverage, 401(k) match, and paid leaves." That's benefits info. So we can include Benefits section. Pay section: we have generic statement; is that considered specific? It says "Compensation is determined based on relevant skills and experience, the position’s location, internal equity, and local market considerations." That's not a specific figure but it's still pay info. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The phrase "Compensation is determined based on relevant skills and experience..." is somewhat generic but not placeholder like "commensurate with experience". It's still vague but maybe acceptable. However they said "Prefer a few substantive sections over many thin ones." Might combine Pay and Benefits into one? But they want separate headings if content exists. We have Benefits: health and welfare coverage, 401(k) match, paid leaves. That's substantive. Pay: we have statement about determination; maybe we can include Pay section with that sentence. It's not a specific number but it's still info. I'd include Pay. We also need About the role? The summary paragraphs could be About the role. The posting starts with a promotional paragraph then "Summary Are you excited by the idea of shaping the future of technology‑enabled supply chains? As part of the Program Management Team at ALOM, you will drive strategic initiatives..." That's essentially About the role. So we can have

About the role

with that paragraph. We should not repeat job title as heading. No Job ID. We need to remove boilerplate: EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. The posting includes "ALOM is an exciting company committed to equal opportunities for all people." That's EEO boilerplate; should remove. Also "We encourage you to submit your resume..." is application instruction; remove. Also "See your career grow..." maybe keep as part of About? It's promotional but not boilerplate; could keep. But we need to preserve substantive information. The EEO line is boilerplate; remove. The "We encourage you to submit your resume..." is application instruction; remove. Also "Bottom line: ALOM is a great place to work!" maybe keep? It's promotional but not boilerplate; could keep in About. We need to output only HTML fragment. Let's craft:

About the role

Are you excited by the idea of shaping the future of technology‑enabled supply chains? As part of the Program Management Team at ALOM, you will drive strategic initiatives across ERP, WMS, OMS, and TMS platforms, connecting business needs, customer requirements, and engineering execution to deliver seamless, high‑compliance operations. You will have the opportunity to: ...

But we need to keep the bullet list of opportunities as

• . The posting lists opportunities after "You will have the opportunity to:" with a series of sentences each starting with a verb. We'll turn each into
• . Similarly for "Here’s what you need to succeed in the role:" list of requirements; turn into
  • . Similarly for "You will be responsible for:" list; turn into
    • . Benefits: "We offer competitive salaries, benefits including health and welfare coverage, 401(k) match, and paid leaves." Could be a
      • list? Might just be a

        . But we can make a Benefits section with

        • each benefit. Pay: we have paragraph about compensation determination. Let's extract exact text. From posting: "See your career grow in an environment where fresh ideas, results, and professional development are encouraged. Sound exciting? Summary Are you excited by the idea of shaping the future of technology‑enabled supply chains? As part of the Program Management Team at ALOM, you will drive strategic initiatives across ERP, WMS, OMS, and TMS platforms, connecting business needs, customer requirements, and engineering execution to deliver seamless, high‑compliance operations. You will have the opportunity to: Lead high‑impact, cross‑functional programs across ALOM’s core supply chain technology stack (ERP, WMS, OMS, TMS) that improve system integration, order‑to‑fulfillment efficiency, and operational visibility Serve as an integral link between our customers and our engineering teams, translating complex business requirements into scalable technology solutions Analyze end‑to‑end order and warehouse workflows (order entry, allocation, receiving, put‑away, picking, packing, shipping, returns) to identify efficiency gains and automation opportunities Assess and apply AI‑enabled tooling and process engineering methods to re‑engineer legacy workflows — solving business problems rather than simply automating the status quo Support the department through process development, documentation, resource management, implementation, testing, external communications, and end‑user training/adoption across enterprise platforms and services Lead change management and training efforts so new systems and processes are successfully adopted across the organization" Then "Here’s what you need to succeed in the role:" list: "7+ years of experience in supply chain, logistics, or operations technology, with at least 3+ years in program/project management In‑depth functional knowledge of at least two of the following: ERP, WMS, OMS, TMS systems (hands‑on experience with all four is strongly preferred) Practical familiarity with AI/automation tools and how they apply to business process improvement, including the ability to evaluate feasibility and ROI Experience applying process engineering or continuous improvement methodologies (Lean, Six Sigma, BPR) to real workflows Proven track record leading complex, multi‑stakeholder programs from initiation through go‑live and stabilization Strong analytical skills with experience using data to drive operational decisions Excellent communication, stakeholder management, and executive presentation skills Preferred: PMP, PgMP, and/or Six Sigma/Lean certification; experience leading system modernization or replatforming initiatives (e.g., migrating legacy on‑prem Bachelor’s degree in Supply Chain Management, Operations, Engineering, Information Systems, or related field (Master’s a plus) Systems to cloud platforms); familiarity with EDI, API integrations, and supply chain analytics/BI tools" Note there is a line break weird; but we keep as is. Then "You will be responsible for:" list: "Developing program charters, roadmaps, timelines, and resource plans; tracking milestones and reporting status to stakeholders Managing risk, scope, and change control across multiple concurrent workstreams; driving design decisions to closure rather than allowing projects to stall in open‑ended discussion Creating clear, well‑organized business documentation outlining as‑is and to‑be process capabilities for stakeholder evaluation and decision‑making Building a deep understanding of internal processes and functionality to recommend optimization opportunities and implement process design changes Providing technical oversight across WMS/ERP systems and dependent applications, with an understanding of integration layers and awareness of emerging technologies Performing research to scope processes, recommend products, and contribute to complex system designs across multiple applications Ensuring clean data flow and process alignment across ERP, WMS, OMS, and TMS platforms, with particular attention to order lifecycle handoffs (order capture → allocation → warehouse execution → shipment) Liaising with external customers to understand requirements, onboard them to ALOM systems/capabilities, and develop roadmaps for new or enhanced features Collaborating with ALOM partners and external software vendors to explore product options, monitor performance, and ensure business needs are met within project timelines Partnering with IT and system integrators to translate business requirements into functional specifications for development and infrastructure projects Driving visibility, prioritization, planning, and delivery of work for the engineering team, including backlog management, sprint/release planning, UAT, implementation oversight, and post‑deployment support Applying process engineering/continuous improvement methods (Lean, Six Sigma, value stream mapping) to redesign workflows before layering on new technology Developing training materials, supporting SOP and system topology documentation, and closing gaps where “tribal knowledge” currently substitutes for documented process" Then compensation paragraph: "At ALOM, we are committed to fair and equitable pay. Compensation Compensation is determined based on relevant skills and experience, the position’s location, internal equity, and local market considerations. We regularly review our pay practices to help ensure employees are compensated fairly for comparable work We offer competitive salaries, benefits including health and welfare coverage, 401(k) match, and paid leaves. Bottom line: ALOM is a great place to work! We encourage you to submit your resume and be a part of a growing, firmly established, and success-driven company that values its staff." We need to remove EEO line earlier: "ALOM is an exciting company committed to equal opportunities for all people." Remove. Also remove "See your career grow in an environment where fresh ideas, results, and professional development are encouraged. Sound exciting?" Might keep as part of About? It's promotional but not boilerplate. Could keep. We also need to remove duplicated lines: there is "Compensation Compensation" duplicate; we should fix to single "Compensation is determined...". Now craft HTML. Structure:

          About the role

          [intro text]

          • ...
          Then

          Requirements

          maybe use Requirements heading. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have requirements list; we can use Requirements. Also we have qualifications list (education, certifications). Could combine into Requirements or separate Qualifications. The posting includes education and certifications within the same list after "Preferred:" line. Might be better to have Requirements section for experience/skills, and Qualifications for education/certifications. But we can keep one Requirements section covering all. However they want prefer few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one Requirements section. But we have separate headings allowed; we could do Requirements and Qualifications both if content is substantive. Let's see: Requirements list includes experience, knowledge, familiarity, experience applying methodologies, track record, analytical skills, communication skills. Qualifications list includes Preferred certifications, degree, etc. Both are substantive. Could split. But we need to avoid thin sections; each has multiple items, so fine. Thus:

          Requirements

          • 7+ years of experience in supply chain, logistics, or operations technology, with at least 3+ years in program/project management
          • In‑depth functional knowledge of at least two of the following: ERP, WMS, OMS, TMS systems (hands‑on experience with all four is strongly preferred)
          • Practical familiarity with AI/automation tools and how they apply to business process improvement, including the ability to evaluate feasibility and ROI
          • Experience applying process engineering or continuous improvement methodologies (Lean, Six Sigma, BPR) to real workflows