Oracle EPM Cloud

We need to output HTML fragment with sections: maybe About the role (job summary), Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule? The posting includes location, job type, salary range, work hours? It says "Work Hours" but no details. It says education: Bachelors. It says salary: $59.75 - 69.75 per hour. Benefits: described. Pay offered based on factors, plus benefits package. So we have Pay and Benefits sections. Schedule? Not given specifics; only "Work Hours" label but no value. Should we include Schedule? The rule: include a section ONLY when posting has real, specific content for it. "Work Hours" without detail is not specific; we should not create Schedule section. So we will have sections: About the role (maybe using job summary), Responsibilities, Qualifications, Skills, Benefits, Pay. Also maybe location and job type could be in a short paragraph under About the role or separate? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So location, job type, education can be in a paragraph. We must not repeat the job title as a heading. The job title not given explicitly but we can ignore. We need to preserve all substantive information: job summary, responsibilities (duplicate), qualifications list, skills list (the long comma-separated list), benefits description, pay range, education, location, job type. We must remove boilerplate: Equal Opportunity Employer text, accommodation statement, etc. Also remove "This posting is open for thirty (30) days." That's maybe not substantive? It's metadata but could be considered minor; we can drop. We need to use

for section headings. Use

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

  for prose. We need to decide what goes into each section. About the role: could be the job summary paragraph plus location, job type, education maybe. Responsibilities: the responsibilities paragraph (same as summary). Could be a

  . Qualifications: maybe list of qualifications? The posting lists "Qualifications Oracle Cloud Oracle Enterprise Profitability and Cost Management Skills ..." Actually that line seems garbled: "Qualifications Oracle Cloud Oracle Enterprise Profitability and Cost Management Skills BI Publisher,Calc,Cloud ecosystem,Data Management,data flow,Data Exchange,Groovy,Metadata,Oracle Cloud,Oracle Enterprise,Oracle EPM,EPM Cloud,REST APIs,scripting,application design,integrations,UAT,financial statements,Automate,automation,Balance Sheet,business requirements,business needs,Business Rules,cost allocations,cost management,Dashboards,Data models,ERP,financial analytics,forecasting,General Ledger,finance,modeling,Management Reporting,executive presentations,Requirements gathering,scheduling,solution designs,deep technical expertise,Testing". That seems like a list of skills under Qualifications. Then there is a separate "Skills" line? Actually after Qualifications there is "Skills BI Publisher,Calc,..." It seems the qualifications and skills are combined. We need to separate Qualifications and Skills sections if there is distinct content. The posting shows "Qualifications" then a long list; then "Skills" then same list? Actually it's: "Qualifications Oracle Cloud Oracle Enterprise Profitability and Cost Management Skills BI Publisher,Calc,Cloud ecosystem,Data Management,data flow,Data Exchange,Groovy,Metadata,Oracle Cloud,Oracle Enterprise,Oracle EPM,EPM Cloud,REST APIs,scripting,application design,integrations,UAT,financial statements,Automate,automation,Balance Sheet,business requirements,business needs,Business Rules,cost allocations,cost management,Dashboards,Data models,ERP,financial analytics,forecasting,General Ledger,finance,modeling,Management Reporting,executive presentations,Requirements gathering,scheduling,solution designs,deep technical expertise,Testing". It seems the word "Skills" appears after "Qualifications". Might be a formatting error: they intended Qualifications then Skills. We'll treat the list as skills. For Qualifications we could have education Bachelors maybe? But they also have "education: Bachelors". So Qualifications could be education requirement. But we also have a list of technical qualifications. To follow instruction: prefer a few substantive sections over many thin ones. We could combine Qualifications and Skills into one section called "Qualifications & Skills" but headings must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to have Qualifications and Skills separate if we have content for each. We have education (Bachelors) as qualification, and we have a long list of skills. So we can put education in Qualifications as a

  or

  . And skills list in Skills as
  • . Responsibilities: we have a paragraph. Benefits: we have description. Pay: we have salary range. Location, job type maybe in About the role paragraph. We must not include filler like "commensurate with experience". Not present. Now construct HTML. Start with

    About the role

    then

    containing job summary plus location, job type, education. Job summary: "The candidate will be responsible for designing, configuring, and implementing profitability and cost management solutions within the Oracle EPM Cloud ecosystem. This role combines deep technical expertise (rules, scripting, integrations) with strong finance domain knowledge (cost allocations, profitability modeling, GL processes) to deliver scalable, high-performing solutions." Add location: "Location: Plano, Texas". Job type: "Job type: Contract". Education: "Education: Bachelor's degree". Could combine. Make sure not to repeat the job title. Then

    Responsibilities

    same as summary? Actually responsibilities paragraph is same as summary. We'll output that. Then

    Qualifications

    Bachelor's degree

    maybe also include any other qualifications? Not given. Then

    Skills

    with each skill as
    • . Need to split the long comma-separated list into items. The list includes many items; we need to preserve all. We'll split by commas, but some items have commas inside like "Oracle Enterprise Profitability and Cost Management". Actually the list starts with "Oracle Cloud Oracle Enterprise Profitability and Cost Management Skills". That seems messy. Let's extract the list after "Skills". The text: "Skills BI Publisher,Calc,Cloud ecosystem,Data Management,data flow,Data Exchange,Groovy,Metadata,Oracle Cloud,Oracle Enterprise,Oracle EPM,EPM Cloud,REST APIs,scripting,application design,integrations,UAT,financial statements,Automate,automation,Balance Sheet,business requirements,business needs,Business Rules,cost allocations,cost management,Dashboards,Data models,ERP,financial analytics,forecasting,General Ledger,finance,modeling,Management Reporting,executive presentations,Requirements gathering,scheduling,solution designs,deep technical expertise,Testing". Also earlier there was "Oracle Cloud Oracle Enterprise Profitability and Cost Management". Might be part of qualifications. To be safe, we can include that as a skill too: "Oracle Cloud", "Oracle Enterprise Profitability and Cost Management". But the list already has Oracle Cloud, Oracle Enterprise, Oracle EPM, EPM Cloud. We'll just use the list after "Skills". We'll split by commas and trim. Let's produce items: - BI Publisher - Calc - Cloud ecosystem - Data Management - data flow - Data Exchange - Groovy - Metadata - Oracle Cloud - Oracle Enterprise - Oracle EPM - EPM Cloud - REST APIs - scripting - application design - integrations - UAT - financial statements - Automate - automation - Balance Sheet - business requirements - business needs - Business Rules - cost allocations - cost management - Dashboards - Data models - ERP - financial analytics - forecasting - General Ledger - finance - modeling - Management Reporting - executive presentations - Requirements gathering - scheduling - solution designs - deep technical expertise - Testing We should preserve case as given. Now Benefits: description: "In addition, Randstad Digital offers a comprehensive benefits package, including: medical, prescription, dental, vision, AD&D, and life insurance offerings, short-term disability, and a 401K plan (all benefits are based on eligibility)." Also earlier: "Pay offered to a successful candidate will be based on several factors including the candidate's education, work experience, work location, specific job duties, certifications, etc." That's more about pay determination, but we have Pay section for salary range. We'll put benefits in Benefits section as
      • each benefit? Could be a

        but rule: Use

        • for any list of duties/requirements/benefits. So we should list benefits as list items. Benefits list: medical, prescription, dental, vision, AD&D, life insurance offerings, short-term disability, 401K plan. Also note "all benefits are based on eligibility" maybe as a note. We'll create
          • Medical
          etc. Pay: salary range: "$59.75 - 69.75 per hour". Also note that pay offered based on factors; we could include that as a

          inside Pay section. Schedule: not present. Now ensure we don't include boilerplate: Remove Equal Opportunity Employer text, accommodation statement, "This posting is open for thirty (30) days." Also remove "Job Summary" heading? We'll not use that as heading; we incorporate into About the role. Now output HTML fragment. Let's craft:

          About the role

          The candidate will be responsible for designing, configuring, and implementing profitability and cost management solutions within the Oracle EPM Cloud ecosystem. This role combines deep technical expertise (rules, scripting, integrations) with strong finance domain knowledge (cost allocations, profitability modeling, GL processes) to deliver scalable, high-performing solutions. Location: Plano, Texas. Job type: Contract. Education: Bachelor's degree.

          Responsibilities

          The candidate will be responsible for designing, configuring, and implementing profitability and cost management solutions within the Oracle EPM Cloud ecosystem. This role combines deep technical expertise (rules, scripting, integrations) with strong finance domain knowledge (cost allocations, profitability modeling, GL processes) to deliver scalable, high-performing solutions.

          Qualifications

          Bachelor's degree

          Skills

          • BI Publisher
          • Calc
          • Cloud ecosystem
          • Data Management
          • data flow
          • Data Exchange
          • Groovy
          • Metadata
          • Oracle Cloud
          • Oracle Enterprise
          • Oracle EPM
          • EPM Cloud
          • REST APIs
          • scripting
          • application design
          • integrations
          • UAT
          • financial statements
          • Automate
          • automation
          • Balance Sheet
          • business requirements
          • business needs
          • Business Rules
          • cost allocations
          • cost management
          • Dashboards
          • Data models
          • ERP
          • financial analytics
          • forecasting
          • General Ledger
          • finance
          • modeling
          • Management Reporting
          • executive presentations