Senior SAP Functional Analyst

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: - About the role (the first paragraph) - Responsibilities (What You'll Bring seems like requirements, but there's also "What You'll Bring" which lists experience/skills) - Requirements (Education, Management Experience, Related Experience) - Benefits (What We Offer) - Pay (Pay Range, Incentive Eligibility) - Schedule? Not mentioned. - Skills? Not explicitly a separate section. The job title is not given in the text, but the instruction says not to repeat the job title as a heading. The page already shows it. So I won't include a title heading. I need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But only include sections with real content. Let's parse the content: 1. "About The Job" paragraph: "Join a technical role focused on developing and supporting enterprise ERP client/server applications that power critical business processes. You will design data conversions, build and maintain system interfaces, troubleshoot testing challenges, and produce clear technical documentation to ensure reliable integration and performance. This position offers the opportunity to contribute independently while supporting team success through knowledge sharing and technical guidance. The role of an individual contributor within the organization focuses on completing specific tasks and projects; contributing directly through their skills and expertise. Performs specialized technical tasks to support operations. Work is primarily achieved independently, however may collaborate with a team." This is "About the role" section. 2. "Pay Range: $115940 per year - $150040 per year Incentive Eligibility: Eligible to participate in Sodexo's incentive plan and earn variable compensation in addition to base salary" -> Pay section. 3. "What’s In It For You" list: bullet points about hands-on work, shaping data conversion, high-impact initiatives, strengthening quality, technical resource, exposure. This seems like benefits or perks, but it's more about the role's attractions. Could be "Benefits" or "Why join us". The instruction says use Benefits for benefits package. But "What We Offer" later includes benefits package. "What's In It For You" is more about the role's opportunities. Might be part of "About the role" or separate. I'll treat as "Benefits" or maybe "Highlights". But the instruction says use Benefits for benefits package. However, the user said: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Benefits is for benefits package. "What's In It For You" is not typical benefits; it's more like role highlights. Could be "Responsibilities"? No. Could be "About the role" extended. I'll include it as a separate section maybe "Why this role" but not in the list. The instruction says only use those headings. But it says "e.g." so maybe we can use other headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That suggests those are the allowed headings. But we can use others if needed? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can use other headings if they match content. However, the example list is given. I think we should stick to those headings where appropriate. "What's In It For You" could be "Benefits" but it's not the benefits package. The benefits package is under "What We Offer". So maybe "What's In It For You" is part of "About the role" or "Responsibilities"? Actually, it's more like "What you'll do" or "Impact". But there is no "Impact" heading. I'll include it as a subsection under "About the role" or as a separate "Highlights" but not in the list. The instruction says "use

for section headings (e.g. ...)". It doesn't forbid other headings. But to be safe, I'll map to the given headings. Let's see: "What You’ll Bring" is a list of experience/skills. That's "Requirements" or "Qualifications". The posting also has a "Requirements" section with Education, Management Experience, Related Experience. So "What You’ll Bring" is like qualifications/skills. I'll combine into "Requirements" and "Qualifications"? The instruction says "Requirements, Qualifications, Skills" as separate headings. But we can merge if they overlap. The posting has "What You’ll Bring" (experience, proficiency, expertise, experience producing documentation, self-directed work style) and then "Requirements" (Education, Management Experience, Related Experience). I'll create a "Requirements" section for the formal requirements, and a "Qualifications" section for the "What You’ll Bring" list. Or maybe "Skills" for the proficiency items. But the instruction says "Qualifications" and "Skills" are separate. I'll do: - Requirements: Education, Management Experience, Related Experience. - Qualifications: the bullet points under "What You’ll Bring". But "What You’ll Bring" includes experience, proficiency, expertise, documentation, self-directed. That's qualifications. Also "What We Offer" includes compensation philosophy and benefits list. That's "Benefits" and "Pay". Pay already has a section. Benefits should include the list: Medical, Dental, Vision, 401k, PTO, Career Growth, Tuition Reimbursement. "Who We Are" is company description, boilerplate? The instruction says remove EEO/equal-opportunity boilerplate. "Who We Are" includes purpose, values, diversity, EEO statement. That's boilerplate. Should remove. Also "If you need assistance with the application process..." is application instruction, remove. Also "Compensation is fair and equitable..." is part of benefits/compensation philosophy, but we have Pay section. Could include in Pay or Benefits. I'll include in Pay section as a note. Now, structure: - About the role: the first paragraph. - Responsibilities? The posting doesn't have a clear "Responsibilities" list. The first paragraph describes what you will do: design data conversions, build and maintain system interfaces, troubleshoot testing challenges, produce clear technical documentation. That's responsibilities. Also "What's In It For You" includes some responsibilities? Actually "What's In It For You" is more about opportunities. I'll create a "Responsibilities" section with the duties from the first paragraph and maybe from "What You’ll Bring"? But "What You’ll Bring" is qualifications. The first paragraph says "You will design data conversions, build and maintain system interfaces, troubleshoot testing challenges, and produce clear technical documentation". That's responsibilities. I'll extract those as a list. - Requirements: Education, Management Experience, Related Experience. - Qualifications: the bullet points under "What You’ll Bring". - Pay: Pay Range and Incentive Eligibility. - Benefits: the list under "What We Offer" (Medical, Dental, Vision, 401k, PTO, Career Growth, Tuition Reimbursement). Also the compensation philosophy sentence. - Schedule: not mentioned, so omit. - Skills: not separate. Now, I need to output HTML fragment with

and

• for lists,

  for prose. Let's write. First, About the role: prose paragraph. But the first paragraph is multiple sentences. I'll keep as one

  or multiple? The instruction: use

  for prose. I'll put the whole paragraph as one

  . But the first paragraph includes "The role of an individual contributor..." which is also prose. I'll include all. Second, Responsibilities: list of duties. I'll create a

  with li for each: design data conversions, build and maintain system interfaces, troubleshoot testing challenges, produce clear technical documentation, contribute independently while supporting team success through knowledge sharing and technical guidance, perform specialized technical tasks to support operations, work primarily independently but may collaborate with a team. Third, Requirements: list of three items: Bachelor's degree in computer science or equivalent experience, 5 years management experience, 5 years related experience. Fourth, Qualifications: list from "What You’ll Bring": Experience supporting ERP client/server enterprise applications in production environments, Proficiency developing system integrations, external interfaces, and data conversion solutions, Expertise diagnosing test cycle issues and resolving integration or performance defects, Experience producing structured technical documentation aligned with development standards, Self-directed work style complemented by experience guiding peers on technical approaches and best practices. Fifth, Pay: prose for pay range and incentive eligibility. Could be two paragraphs or one. I'll do two

  or a list? The instruction says use

  • for any list of duties/requirements/benefits. Pay is not a list, but two items. Could be a list. I'll do a
    with two li: Pay Range: $115,940 - $150,040 per year, Incentive Eligibility: Eligible to participate in Sodexo's incentive plan and earn variable compensation in addition to base salary. Also include the compensation philosophy: "Compensation is fair and equitable, partially determined by a candidate's education level or years of relevant experience. Salary offers are based on a candidate's specific criteria, like experience, skills, education, and training." That's prose. I'll add as a

    after the list. Sixth, Benefits: list of benefits. The posting says "Sodexo offers a comprehensive benefits package that may include:" then bullet list. I'll make a

    with li for each: Medical, Dental, Vision Care and Wellness Programs, 401(k) Plan with Matching Contributions, Paid Time Off and Company Holidays, Career Growth Opportunities and Tuition Reimbursement. Also note "More extensive information is provided to new employees upon hire." as a

    . Now, "What's In It For You" - I haven't placed. It's a list of 6 items. Could be part of "About the role" or a separate "Highlights". Since the instruction says only include sections with real content, and we have a list, maybe create a "Why join us" but not in the example headings. The example headings include "Benefits" but that's for benefits package. "What's In It For You" is more about the role's appeal. I'll include it as a separate section with heading "What you'll gain" or "Role highlights". But the instruction says use

    for section headings (e.g. ...). It doesn't forbid other headings. However, to stay consistent, maybe I can put it under "About the role" as a list. But the instruction says "use

    • for any list of duties/requirements/benefits". This is a list of benefits (non-monetary). Could be considered "Benefits" but the benefits package is separate. I'll create a section "Role highlights" with

      Role highlights

      and list. But the instruction says "include a section ONLY when the posting has real, specific content for it". It does have content. I think it's okay to add a heading not in the example list. But the user might expect only those headings. The instruction: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. I'll include "What you'll gain" as a heading. Alternatively, I could merge "What's In It For You" into "About the role" as a list after the prose. But the instruction says use