An application made for this job — a tailored resume and cover letter that speak straight to the posting.
City Colleges of Chicago is seeking a Senior PeopleSoft Technical Developer to design, build, test, and deploy student planning tools as upgrades to the Campus Solutions 9 environment. The role covers degree planner, schedule builder, and self-service portal enhancements for students, advisors, and faculty across CCC campuses.
The developer will join the SAILS project team, work with Academic Systems, and deliver upgrade-safe solutions with a modern, mobile-friendly experience.
City Colleges of Chicago (CCC) 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 CCC'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 across all seven City Colleges and their satellite sites. This work is part of Project SAILS (Student Access, Intention, Learning, and Success), funded by a U.S. Department of Education Strengthening Institutions Program (SIP) grant awarded to Richard J. Daley College on behalf of CCC. SAILS has two goals: (1) mandatory holistic advising for first-time students, so every new student meets with an advisor, declares a program, and leaves with a semester plan;and (2) strategic yearlong course scheduling, so colleges plan course offerings for a full academic year based on what students need. The tools in this scope are the technology foundation for both goals. They give students a clear path to completion, give advisors a shared view of that path, and give the district reliable data on which courses students need and when. The selected developer will join the SAILS project team led by the SAILS Project Manager, work closely with CCC's Academic Systems department, and build within CCC's existing PeopleSoft environment. CCC expects a modern, intuitive, mobile-friendly experience that students will choose to use, built with upgrade-safe methods that CCC staff can maintain after the engagement ends.
The SAILS Project Manager directs the day-to-day work, sets priorities, and approves hours, in partnership with the Associate Vice Chancellor, Academic Systems, Records and Policy. Academic Systems sets technical standards and approves production changes. Team: The developer works alongside CCC Academic Systems analysts, who contribute part-time development and testing, and with Information Technology for environments, security, and migrations. Delivery approach: Iterative build cycles (for example, two-week sprints) with a demo to the project team at the end of each cycle. The SAILS Project Manager owns the backlog and sets cycle priorities in a tool CCC designates. Status reporting: A brief written status report to the SAILS Project Manager each week (work completed, planned next, risks and issues, hours used), a weekly project meeting, and technical demonstrations to SAILS advisory committees as requested by the SAILS Project Manager. Time records: This work is federally funded. The developer submits weekly timesheets with task-level detail for approval by the SAILS Project Manager. Time records must be accurate and complete enough to support a federal audit. 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. Work location: Remote Work product: All code, configuration, and documentation produced under this engagement belong to CCC.