Integrations Developer

We need to output HTML fragment with sections: About the role? Actually we have "About JMU" and "General Information". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have: - About JMU (mission, benefits). This is about the organization, not role. Could be "About the role"? But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can adapt: "About JMU" is not exactly "About the role". But we could treat it as "About the role"? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use other headings if appropriate? Probably we should stick to those headings where applicable. The posting includes "About JMU" which is about the employer, not role. Could we put that under a heading like "About JMU"? Not in list but maybe acceptable. However they said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That implies we should use those headings when we have that content. For "About JMU", we could treat as "About the role"? Not exactly. Might be better to omit that section? But we need to preserve ALL substantive information. The "About JMU" paragraph is substantive. We need to include it somewhere. Perhaps we can put it under a heading "About JMU" even if not in the example list; the instruction says use

  for section headings (e.g. ...). It doesn't forbid other headings, just gives examples. So we can use

  About JMU

  . Similarly "General Information" includes description of Reengineering Madison initiative. Could be a section "General Information" or maybe "About the role". But we have specifics about the role in "Duties And Responsibilities". So we can have sections: About JMU, General Information (or maybe "About the role"?), Responsibilities, Qualifications, Benefits, Pay. We have Pay Rate: $70,000 - $75,000. So we need a Pay section. We have Benefits: described in "Why Work at JMU?" with bullet list: Generous Leave, Comprehensive Health Coverage, Retirement Options, Employee Well-Being, Tuition Waiver Program. So we need Benefits section with list. We have Schedule: The posting mentions "This position is eligible for a remote work schedule." That's schedule info. So we can include Schedule section. We have Responsibilities: list of duties. We have Qualifications: Required and Additional Considerations. Could combine into Qualifications section with sublists? Probably we can have Required Qualifications and Preferred Qualifications as subheadings? But instruction says use headings for sections; we could have a Qualifications section with two
  lists: one for Required, one for Preferred (Additional Considerations). Or we could split into Requirements and Qualifications? They listed both Requirements and Qualifications as possible headings. The posting has "Qualifications Required:" and "Additional Considerations". So we could have a Requirements section for required qualifications, and a Qualifications section for additional considerations (preferred). Or we could combine. Let's follow: Requirements = required qualifications. Qualifications = additional considerations (preferred). We'll output both. We also have "Knowledge and experience with Boomi and PeopleSoft Campus Solutions will be helpful" under Responsibilities? Actually it's in Responsibilities paragraph. But we already captured that. We need to remove boilerplate: EEO statement, Reasonable Accommodation, Conditions of Employment, E-Verify notice, etc. Also remove duplicated lines, application instructions, etc. We need to preserve all substantive information: that includes the description of JMU, the Reengineering Madison initiative, duties, qualifications, pay, benefits, schedule, remote work eligibility. We need to output only HTML fragment. Let's structure:

  About JMU

  At James Madison University (JMU), we’re more than just a publicly funded institution — we’re a vibrant, welcoming community located on a stunning campus where innovation, collaboration, and personal growth thrive. Our mission is to prepare students for a bright future, and we believe that starts with supporting the people who make it all possible: our employees.

  Maybe also include "Why Work at JMU?" as part of About JMU? Could incorporate benefits there but we have separate Benefits section. We could include the "Why Work at JMU?" paragraph as part of About JMU. Let's combine: At JMU ... Why Work at JMU? We offer a comprehensive benefits package... Then we will have Benefits section listing specifics. Thus About JMU paragraph includes the mission and the Why Work at JMU? description. Next:

  General Information

  JMU is in the midst of implementing a very large strategic initiative, Reengineering Madison (https://www.jmu.edu/computing/projects/reengineering-madison/index.shtml). Replacing our Enterprise Resource Management (ERP) applications is the final phase of the project, and we are excited to offer this position for Integration Developer to support the University's Oracle HCM, Finance, and Student applications.

  But note: The instruction says do not put Job ID/requisition numbers as headings; we are not. Next:

  Responsibilities

  • Serve as a technical resource for Enterprise Applications with a primary focus on integrations supporting Oracle HCM, Finance (ERP/EPM), and Student applications.
  • Initial implementation phases will focus on Oracle HCM and Finance (ERP/EPM) with a planned go-live of Summer 2027.
  • Design, develop, implement, monitor, maintain, and support integrations between Oracle Cloud applications and other university systems.
  • Partner closely with business offices, technical teams, implementation partners, vendors, and other stakeholders to understand data exchange requirements and develop secure, scalable, and maintainable integration solutions.
  • Gather and analyze requirements, develop and test integrations, troubleshoot issues, optimize performance, maintain documentation, and provide ongoing operational support.
  • Stay current with Oracle Cloud, Oracle Integration Cloud (OIC), API technologies, security best practices, and emerging integration capabilities to ensure the University continues to leverage modern and effective integration solutions.
  • Knowledge and experience with Boomi and PeopleSoft Campus Solutions will be helpful as those integrations will continue to be maintained until that system is replaced.
  But we need to ensure we didn't lose any detail: The responsibilities paragraph also includes "This position is eligible for a remote work schedule." That's schedule, not responsibility. We'll move to Schedule. Also "The successful candidate will stay current..." we included. Now Qualifications: Required.

  Requirements

  • Significant professional experience designing, developing, implementing, and supporting enterprise system integrations using Oracle Integration Cloud (OIC).
  • Professional experience with Oracle Cloud applications, including HCM, ERP, EPM, Financials, Payroll, Recruiting, or Student systems.
  • Demonstrated experience gathering business and technical requirements and translating those requirements into effective integration solutions.
  • Professional experience working with integration technologies, APIs, web services, data exchange processes, or middleware platforms.
  • Professional experience managing multiple priorities and projects simultaneously.
  • Demonstrated strong analytical, troubleshooting, and problem-solving skills.
  • Exceptional communication skills, both verbal and written.
  • Significant professional experience partnering with business users, technical staff, vendors, and stakeholders of varying technical backgrounds.
  • Demonstrated ability to learn new technologies and deliver effective technical solutions.
  Now Qualifications (preferred):

  Qualifications

  • Experience in a Higher Education environment.
  • Experience with Boomi integration platform and/or PeopleSoft Campus Solutions.
  • Experience supporting complex enterprise application ecosystems.
  • Experience with integration architecture, security protocols, authentication methods, and data governance principles.
  • Experience building strong and long-lasting partnerships with key stakeholders.
  • Experience supporting system modernization, cloud migration, or enterprise transformation initiatives.
  Now Benefits:

  Benefits

  • Generous Leave: paid vacation, sick leave, parental leave, community service leave, and 19 paid holidays annually.
  • Comprehensive Health Coverage: access to high-quality health insurance options.
  • Retirement Options: retirement benefits through the Virginia Retirement System.
  • Employee Well‑Being: Balanced Dukes program promotes wellness and work‑life integration through resources, events, and support.
  • Tuition Waiver Program: advance education with tuition waiver for undergraduate and graduate courses taken at JMU.
  Now Pay:

  Pay

  $70,000 - $75,000

  Now Schedule:

  Schedule

  Full‑time position eligible for a remote work schedule.

  We should also include that it's Full-time Staff (Classified) etc. But we already have schedule and maybe we could include position type in a short paragraph under General Information? The instruction says do not repeat job title as heading, but we can include metadata like Position Type: Full-time Staff (Classified) etc. Could fold into a short

  under General Information or a separate "Position Details" but we don't have a heading for that. Perhaps we can add a short paragraph after General Information about position details: "Position Type: Full-time Staff (Classified); FLSA Status: Exempt; Not Eligible for Overtime; Pay Band: 5." But we need to avoid filler like "not specified". This is specific. So we can include that. But we must ensure we don't create a heading for it unless we have a proper heading. Could add a

  after General Information. Let's think: The instruction says "fold minor metadata into a short

  or drop it." So we can add a short paragraph with that info. Thus after General Information paragraph, we can add a

  containing: Position Type: Full-time Staff (Classified); FLSA Status: Exempt (Not Eligible for Overtime); Pay Band: 5. We should also include that it's Opening on: Sep 21 2026, Beginning Review Date: 9/29/2026. Those are dates; maybe we can include them