Senior PeopleSoft Technical Developer

VIVA USA Inc; United States; Remote; USD 120,000 - 160,000; Full time

Job summary

VIVA USA Inc. seeks a Senior PeopleSoft Technical Developer to design, build, test, and deploy upgrades to Campus Solutions 9. The role focuses on three tools: degree planner, schedule builder, and self-service portal enhancements, serving students, advisors, and faculty.

You will work within the SAILS project team, collaborating with Academic Systems and IT to use upgrade-safe methods and deliver a modern, mobile-friendly experience that is maintainable after engagement ends.

Qualifications

• Seven or more years in a technical PeopleSoft role including analysis, configuration, programming, and administration.
• Five or more years programming and troubleshooting with PeopleTools 8.5x or higher: application designer, etc.
• Experience with upgrade-safe customization, PeopleSoft Update Manager, and Selective Adoption.
• Experience with degree planning, student self-service tools, or related CS9 modules is preferred.

Responsibilities

• Lead technical analysis, design, development, testing, and technical documentation for CS9 upgrades.
• Build upgrade-safe customizations using Fluid, Event Mapping, and Page and Field Configurator.
• Collaborate with Academic Systems and IT on standards, access, and migration processes.
• Ensure deliverables meet WCAG accessibility and FERPA data standards.

Skills

Fluid development

PeopleSoft analysis & programming

Agile delivery experience

Certification in PeopleSoft

Education

PeopleSoft certifications

Bachelor's degree in a technical field

Tools

PeopleTools 8.5x+

PS Query

BI Publisher

Pivot Grids

Data extracts

Job description

Remote The client is seeking a Senior PeopleSoft Technical Developer from its pool of staff augmentation vendors to design, build, test, and deploy a set of student planning tools as upgrades to the client's PeopleSoft Campus Solutions 9 (CS9) environment. The work covers three tools: a degree planner, a student schedule builder, and enhancements to the student self-service portal. These tools will serve students, advisors, and faculty and their satellite sites. The selected developer will join the SAILS project team led by the SAILS Project Manager, work closely with the client's Academic Systems department, and build within the client's existing PeopleSoft environment. The client expects a modern, intuitive, mobile-friendly experience that students will choose to use, built with upgrade-safe methods that client staff can maintain after the engagement ends. SCOPE OF WORK The work is organized in seven phases. Phases overlap; the approved release plan will set the final sequence. Roles. The SAILS Project Manager leads the project: requirements, stakeholder engagement, priorities, schedule, user acceptance testing, training, change management, and release decisions. The developer leads technical analysis, design, development, technical testing, and technical documentation. Academic Systems sets technical standards and approves production changes. Phase 1: Discovery, Assessment, and Technical Design The developer completes this phase in partnership with the SAILS Project Manager, who leads stakeholder engagement, owns project requirements, and approves the build plan with Academic Systems. Review client's current CS9 setup, including Academic Advisement (degree audit) requirements and academic plans, Student Records, Enrollment, Class Schedule, Campus Community, self-service pages (Classic and Fluid), and security roles. Review requirements documented by the SAILS Project Manager. Take part in working sessions, led by the SAILS Project Manager, with advisors, students, faculty, and Academic Systems staff, and identify technical gaps, constraints, and options. Conduct a technical fit/gap analysis of delivered Oracle Campus Solutions functionality, including Fluid self-service features, against client's requirements. Recommend what to configure, what to extend, and what to build, favoring delivered functionality where it meets the need. Produce a technical design covering architecture, data flow, integration points, security, and the customization approach. Use upgrade-safe methods (such as Fluid, Event Mapping, and Page and Field Configurator) to limit the impact on future PeopleSoft updates. Provide effort estimates, technical dependencies, and a recommended build sequence so the SAILS Project Manager can finalize the project backlog and release plan, for approval by the SAILS Project Manager and Academic Systems. Confirm development and test environments, system access, source control, and the migration process with Academic Systems and Information Technology. Phase 2: Degree Planner (Priority 1A) Student experience Generate a personalized, term-by-term plan from the student's program requirements, completed and in-progress courses, and transfer credit. Recommend a course sequence that respects prerequisites, typical course offering patterns, and the student's intended course load (full-time or part-time). Update the plan automatically when grades post, requirements are met, or the student changes programs. Show progress clearly: percent complete, requirements remaining, and projected completion term. Let students explore "what-if" scenarios, such as a program change, and see the effect on time to completion. Support exploration for new and undeclared students. Advisor experience View and edit advisee plans, and record notes tied to the plan. Send recommended courses or a full plan to a student. The student can accept or decline, and the response is recorded. Build a first-semester plan with a student during advising sessions, in support of the mandatory advising goal. Approve or lock plans where client policy requires it. Data Capture planned courses by term, program, and college to feed course demand reporting (Phase 5). Phase 3: My Academic Schedule (Priority 1B) Let students block out personal commitments (work, family, commute) on a real-time calendar. Generate multiple valid schedule options from the courses in the student's plan and the sections open for the term, in real time. Check prerequisites, holds, enrollment appointments, time conflicts, and seat availability before a student enrolls. Filter by campus location (including satellite sites) and modality (in person, online, hybrid). Let students lock preferred sections, compare schedule options side by side, and move a chosen schedule into enrollment using delivered enrollment processing. Let advisors build and propose schedules to students. The student can accept or reject, and the response is recorded. Pull courses directly from the client Degree Planner so the plan and the schedule stay connected. Capture aggregate data on requested courses, unmet demand, and times students are unavailable for Phase 5 reporting. Phase 4: Student Experience Portal (Priority 2) Modernize the CS9 student self-service experience in Fluid: a single, mobile-friendly home that brings together the client Degree Planner, My Academic Schedule, class schedule, grades, holds, to-do items, enrollment appointments, advisor information, and links to financial aid and account pages. Deliver related advisor and faculty views as prioritized by the client, such as advisee lists and a "view as student" option for planning. Provide sizing for each page or feature so the SAILS Project Manager and Academic Systems can set final priorities. The SAILS Project Manager will confirm the specific pages in scope during the project. Phase 5: Usage Analytics and Course Demand Data Build usage tracking for the measures defined by the SAILS Project Manager across all three tools, including active users by role and college, plans created and updated, schedules generated, advisor proposals sent and accepted, enrollments completed through the My Academic Schedule, and points where users drop off. Build course demand reports from student plans by term, course, program, and college. Compare planned demand to scheduled seats and flag likely shortages, in support of yearlong course scheduling. Build reports on aggregate student availability patterns to inform section times and modality. Deliver reports and data extracts in formats client can use for internal decisions, its district data platform, and federal grant reporting. Follow FERPA and client data standards. Reporting for external use is aggregate only. Phase 6: Testing, Quality, and Accessibility Build and test in non-production environments only. Move changes to production through the client's change management process. Complete unit, system, integration, and regression testing. Document test scripts and results. Support user acceptance testing planned and coordinated by the SAILS Project Manager with advisors, students, faculty, and Academic Systems staff: prepare test environments and data, and log, track, and resolve defects. Support usability testing with students, coordinated by the SAILS Project Manager before each major release, and build the approved changes. Test performance at peak registration volume. Meet Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Learn more at the ADA website Apply role-based security and protect student records in line with FERPA and the client security review requirements. Phase 7: Deployment, Documentation, and Knowledge Transfer Execute technical deployment for each release according to the release and rollout plan set by the SAILS Project Manager and Academic Systems, starting with a pilot at one or more colleges before districtwide rollout. Provide post-launch support after each release to stabilize the tools and resolve issues. Deliver technical documentation: design specifications, an inventory of all objects and customizations, configuration settings, integration and security mappings, environment diagrams, and support runbooks. Provide technical content, demonstrations, and quick-reference materials for training designed and led by the SAILS Project Manager. Transfer knowledge to the client Academic Systems staff through paired work during the build and a documented handoff, so the client can maintain and extend the tools after the engagement. SCOPE DELIVERABLES The developer will be responsible for delivering the following: 1. Current-state assessment and fit/gap analysis 2. Technical design document 3. Effort estimates, technical dependencies, and recommended build sequence 4. Client Degree Planner, tested and deployed 5. My Academic Schedule, tested and deployed 6. Student Experience Portal enhancements, as prioritized by the client 7. Usage analytics and course demand reports 8. Technical test plans, scripts, and results, and defect resolution during user acceptance testing 9. WCAG 2.1 Level AA accessibility test results 10. Technical documentation and support runbooks 11. Knowledge transfer plan and completed handoff to Academic Systems 12. Weekly status reports and approved timesheets QUALIFICATIONS Required Seven or more years in a technical PeopleSoft role that included analysis, configuration, programming, and administration. Five or more years programming and troubleshooting with PeopleTools 8.5x or higher: application designer, etc. Preferred Experience building or implementing degree planning, schedule building, or student self-service tools at a college or university. Experience in a multi-campus or community college district. Experience meeting WCAG accessibility standards. Experience with upgrade-safe customization, PeopleSoft Update Manager, and Selective Adoption. Reporting and analytics experience (PS Query, BI Publisher, Pivot Grids, data extracts). Experience integrating PeopleSoft with advising platforms such as EAB Navigate. Experience working in agile or iterative delivery teams. Experience on federally funded projects. PeopleSoft or related technology certifications. Candidates must have advanced PeopleSoft technical skills, including Fluid development. Notes: Remote Hours: Full time (40 hours per week). Occasional work outside normal hours may be needed for registration periods, migrations, and maintenance windows, within approved hours. VIVA is an equal opportunity employer. All qualified applicants have an equal opportunity for placement, and all employees have an equal opportunity to develop on the job. This means that VIVA will not discriminate against any employee or qualified applicant on the basis of race, color, religion, sex, sexual orientation, gender identity, national origin, disability or protected veteran status