PeopleSoft Technical Consultant

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to parse the job posting. Content: It's a PeopleSoft Technical Consultant role. There's description: "This position is listed on behalf of a partner company... fully remote opportunity... design, develop, integrate, maintain solutions..." That's about the role. Then "Accountabilities" list bullet points (design and develop...). That's responsibilities. Then "Requirements" list bullet points (Bachelor's degree...). Then "Benefits" includes: "100% remote position within the United States. Full-time, direct W-2 employment. Competitive annual salary range of $100,000–$150,000, depending on experience, skills, and qualifications. Opportunity to work on enterprise PeopleSoft environments spanning HCM, FSCM, and Campus Solutions. Career growth opportunities within an established technology consulting environment. Opportunity to expand expertise across PeopleTools, integrations, reporting, Oracle technologies, and enterprise application modernization." Also there is "Equal employment opportunity workplace..." which is boilerplate to remove. Also "How Jobgether Works..." etc is boilerplate to remove. Also "Why Apply Through Jobgether?" etc remove. We need sections: About the role (prose). Responsibilities (list). Requirements (list). Benefits (list? maybe include bullet points). Pay: we have salary range; we could put Pay section with that info. Schedule: maybe not specified; we have full-time; but schedule not explicit. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated: salary range. So we can have Pay section. Benefits: we have remote, full-time, W-2, career growth, etc. So Benefits section. Schedule: we have full-time but not schedule details like hours; maybe we can include Schedule if we have info like "Full-time". The posting says "Full-time, direct W-2 employment." That could be considered schedule. But we need to decide: The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state full-time, which is schedule info. So we could include Schedule section with "Full-time". However we also have Benefits section that could include remote, etc. Might be overlapping. Better to separate: Benefits: remote, career growth, etc. Pay: salary range. Schedule: full-time. We must not repeat job title as heading. No Job ID. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from Accountabilities and Requirements and Benefits etc. Also the prose about role. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "How Jobgether Works", "Why Apply Through Jobgether?", Data Privacy Notice, etc. We need to output only HTML fragment. Structure:

About the role

... prose ...

Responsibilities

• ... each accountability ...
...

Requirements

• ... each requirement ...
...

Benefits

• ... each benefit ...
...

Pay

Competitive annual salary range of $100,000–$150,000, depending on experience, skills, and qualifications.

Schedule

Full-time position.

We need to ensure we don't include filler like "commensurate with experience". Not present. Check for duplicated lines: The posting includes "Opportunity to work on enterprise PeopleSoft environments spanning HCM, FSCM, and Campus Solutions." appears both in responsibilities? Actually it's in Benefits. Also earlier: "You’ll design, develop, integrate, and maintain solutions that translate complex business requirements into reliable technical outcomes. The role offers significant hands-on ownership across PeopleTools, PeopleCode, Application Engine, Component Interfaces, and Integration Broker." That's part of About the role. We need to include all bullet points from Accountabilities: - Design and develop PeopleSoft customizations using Application Designer, including pages, components, records, fields, and PeopleCode. - Build Application Engine programs supporting batch processing, data conversion, and ETL-style workloads. - Develop and maintain Component Interfaces, Integration Broker services, and File Layouts for internal and external integrations. - Create SQR, BI Publisher, and applicable nVision reports, including complex layouts and performance optimization. - Configure and maintain Approval Workflow Engine (AWE) functionality and related notifications. - Partner with functional consultants to conduct fit-gap analysis and translate business requirements into clean, scalable technical designs. - Follow enterprise customization standards and minimize core modifications to support future upgrades and long-term maintainability. - Lead unit testing, support functional and integration testing, and resolve defects through UAT and post-production hypercare. - Optimize SQL performance against PeopleSoft data models using explain plans, indexing, statistics tuning, and related techniques. - Support PeopleSoft upgrades and patches while assessing technical impacts and maintaining system stability. - Provide hands-on post-go-live support, rapidly triaging incidents, identifying root causes, and implementing durable fixes. - Maintain clear technical documentation, code documentation, and operational procedures in accordance with PeopleSoft governance standards. - Mentor junior PeopleSoft developers and act as a technical reference for development and troubleshooting. - Collaborate with stakeholders to ensure technical solutions are secure, well documented, maintainable, and aligned with broader enterprise standards. That's 15 bullets. Requirements list: - Bachelor’s degree in Computer Science, Engineering, or a related technical discipline. - 5+ years of professional PeopleSoft technical development experience. - Strong hands-on expertise with PeopleTools, Application Designer, and PeopleCode. - Proven experience with Application Engine, Component Interfaces, and Integration Broker. - Hands-on experience developing SQR and BI Publisher reports. - Strong SQL skills and a solid understanding of the PeopleSoft data model. - Familiarity with PeopleSoft HCM, FSCM, or Campus Solutions data structures and business processes. - Experience supporting PeopleSoft upgrades, patches, and related technical changes. - Working knowledge of Approval Workflow Engine (AWE). - Strong troubleshooting, analytical, communication, and technical documentation skills. - Ability to translate business requirements into practical technical solutions and collaborate effectively with functional consultants. - PeopleSoft certifications are preferred. - Experience with Oracle Cloud HCM/ERP integration scenarios is advantageous. - Exposure to Fluid UI development is a plus. - Familiarity with Oracle DBA fundamentals is beneficial. - Experience with Oracle Integration Cloud (OIC) for PeopleSoft integrations is preferred. - Eligible candidates may include U.S. citizens, Green Card holders, EAD holders, and candidates eligible for H-1B transfer; new H-1B sponsorship is not available. That's many bullet points. We need to keep all. Benefits list: from Benefits paragraph: - 100% remote position within the United States. - Full-time, direct W-2 employment. - Competitive annual salary range of $100,000–$150,000, depending on experience, skills, and qualifications. (But we moved salary to Pay; maybe we should not duplicate. However the instruction says preserve ALL substantive information; we could keep it in Benefits but also have Pay section. Might duplicate. Better to keep salary in Pay only, and not duplicate in Benefits. But then we would be omitting that sentence from Benefits. However the instruction says preserve ALL substantive information; we could keep it in Benefits but also have Pay section; duplication is okay? It says do NOT invent or summarize away detail. Duplication is not inventing; it's preserving. Might be okay but could be considered redundant. However they said prefer a few substantive sections over many thin ones. Duplication may be okay but could be considered thin? I'd rather keep salary in Pay and not repeat in Benefits. But then we lose that sentence from Benefits. However the sentence also includes "Competitive annual salary range..." which is pay info; we already have Pay section. So we can omit it from Benefits to avoid duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit it, we are summarizing away detail (removing it). So we must keep it somewhere. We could keep it in Benefits and also have Pay section referencing same info; but that duplicates. Might be acceptable. However they said "Prefer a few substantive sections over many thin ones." Duplication may be considered thin? Not sure. I think it's safer to keep the salary info in Benefits and also have Pay section? Actually Pay section is required only if posting states them; we could put salary in Pay and not duplicate in Benefits, but then we lose that sentence from Benefits. However the sentence is about salary, which is pay; we could treat it as Pay info and still keep it in Benefits as part of benefits? The sentence is about salary, which is a benefit? Usually salary is compensation, not benefit. But they said Benefits section includes things like remote, career growth, etc. The salary line could be considered part of Benefits but also Pay. To be safe, I'll include salary in both Benefits and Pay. That preserves the detail. Other benefits: Opportunity to work on enterprise PeopleSoft environments spanning HCM, FSCM, and Campus Solutions. Career growth opportunities within an established technology consulting environment. Opportunity to expand expertise across PeopleTools, integrations, reporting, Oracle technologies, and enterprise application modernization. Also "Full-time, direct W-2 employment." That's also schedule/benefit. We'll put in Benefits as well, and also Schedule section. Thus Benefits list: - 100% remote position within the United States. - Full-time, direct W-2 employment. - Competitive annual salary range of $100,000–$150,000, depending on experience, skills, and qualifications. - Opportunity to work on enterprise PeopleSoft environments spanning HCM, FSCM, and Campus Solutions. - Career growth opportunities within an established technology consulting environment. - Opportunity to expand expertise across PeopleTools, integrations, reporting, Oracle technologies, and enterprise application modernization. Schedule: Full-time position. Now About the role prose: We need to capture the descriptive paragraphs before Accountabilities. The posting: "This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a PeopleSoft Technical Consultant based in United States. This is a fully remote opportunity for an experienced PeopleSoft technical professional supporting enterprise applications across HCM, FSCM, and Campus Solutions. You’ll design, develop, integrate, and maintain solutions that translate complex business requirements into reliable technical outcomes. The role offers significant hands-on ownership across PeopleTools, PeopleCode, Application Engine, Component Interfaces, and Integration Broker. You’ll collaborate closely with functional consultants and stakeholders while following enterprise standards for security, quality, scalability, and maintainability. The position also involves upgrades, performance optimization, testing, production support, and continuous improvement. You’ll have opportunities to mentor junior developers and serve as a technical resource for the broader team. The environment is well suited to a technically strong consultant who values clean customization, thoughtful engineering, and durable enterprise solutions." We need to keep all that as prose in About the role. Now we must remove boilerplate: "Equal employment opportunity workplace committed to professional and inclusive employment practices." Also "How Jobgether Works..." etc. Also "Why Apply Through Jobgether?" etc. Also Data Privacy Notice etc. Now produce HTML. Check for any duplicated lines: The bullet list for Responsibilities includes "Partner with functional consultants to conduct fit-gap analysis and translate business requirements into clean, scalable technical designs." That's similar to some prose but fine. Now produce final answer. We must output only HTML fragment, no markdown fences.