PeopleSoft Technical Developer, Senior

We need to output HTML fragment with sections: About the role? Actually description includes "About The Position Type", "In This Position, You Will", "Need To Have", "Nice To Have", "About The Department", "About Hennepin County". Also location/hours, schedule maybe. Also pay? Not mentioned. Benefits? Not mentioned. So we should include sections only if content present. We need headings:

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use appropriate headings based on content. We have: - Location and hours: location and schedule info. Could be under Schedule? Actually schedule is hours. Could be "Schedule" heading. Also location maybe part of schedule? Could be separate? The instruction: Use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use Schedule for location/hours. - About The Position Type: could be "About the role" heading. - In This Position, You Will: responsibilities. - Need To Have: requirements/qualifications. - Nice To Have: skills? Could be "Skills" heading. - About The Department: maybe "About the role"? Already used. Could be omitted? But we need to preserve all substantive info. Could include as a paragraph under About the role? Or separate heading like "About the Department" not in list but we can still use

with custom text? The instruction says use

for section headings (e.g. About the role, Responsibilities, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. We can map content accordingly. We have: About The Position Type -> About the role. In This Position, You Will -> Responsibilities. Need To Have -> Requirements (or Qualifications). Could be Requirements. Nice To Have -> Skills. About The Department -> maybe also About the role? But we already used. Could add another heading like "About the Department" but not in list. Might be okay but risk. Perhaps we can include as a paragraph under About the role? But we need to preserve info. Could add a separate heading "About the Department" as

though not in examples but still a heading. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections, but not strictly limited. Safer to use those headings only. We could merge Department info into About the role section. About Hennepin County -> could be part of About the role as well. Location and hours -> Schedule. Pay/Benefits not present, so omit. Thus final HTML:

About the role

... combine About The Position Type, About The Department, About Hennepin County ...

Responsibilities

• ... each responsibility ...

Requirements

• ... each need to have bullet ...

Skills

• ... nice to have bullets ...

Schedule

Location and hours: This position is hybrid ...

We must preserve all substantive info, not invent. Let's extract content. About The Position Type: "This is a full-time benefit earning position. This position is internally classified as an IT Developer level III. Click here to view the job classification specification." We should keep that but remove the link? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is part of the posting; we can keep as plain text maybe? It says "Click here to view the job classification specification." That's a link; we could keep as text but not as actual link? Probably keep as plain text. About The Department: "The Office of Budget & Finance works hard to ensure sound credit conditions, working capital, and overall financial health within Hennepin County by supporting strategic objectives through leveraging technology, effective management of financial and human resource systems and services, as well as Hennepin County's commitment to equal opportunity, affirmative action, diversity, and inclusion." About Hennepin County: "Hennepin is the largest county government organization in Minnesota. Our employees work every day to improve the health, safety and quality of life for our residents and communities. All of our jobs align with our mission to serve residents through transformative services that eliminate disparities, eliminate inequities, and create opportunity for all and our vision of a community where all people are healthy, all people are valued, and all people thrive. Our employees receive a combination of competitive benefits and positive workplace culture not found at other organizations. This includes meaningful work that impacts our community, competitive pay, work-life balance, a variety of benefits and opportunities to grow. Learn more at The Bridge (login as Guest). Hennepin County envisions an organization where our commitment to diversity and the elimination of disparities is fundamental in providing excellent service to your community. Your future. Made here. This posting may be used to fill current and future vacancies. Applications will be forwarded to the hiring supervisor on a weekly on-going basis until the position is filled. This position may have access to systems or other documentation that contains HIPAA data. Watch this video for application best practices and tips. Invitations to interview will be based upon an assessment of education and experience. Final candidates will be required to complete a background check. If You Have Any Questions, Please Contact Roberta Arpinar Roberta.Arpinar@hennepin.us" We need to remove boilerplate like EEO, legal, scam-warning, duplicated lines, application instructions. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we should remove lines like "Learn more at The Bridge (login as Guest)." maybe not boilerplate but it's a reference. Might be okay. Also "Watch this video for application best practices and tips." is application instruction; remove. "Invitations to interview will be based upon an assessment of education and experience." maybe not instruction but could be considered process; but it's substantive? Might be considered part of hiring process; but instruction says remove application instructions. This is about interview process; could be considered application instruction. Safer to remove. "Final candidates will be required to complete a background check." also application instruction; remove. "If You Have Any Questions, Please Contact Roberta Arpinar Roberta.Arpinar@hennepin.us" is contact info; maybe keep? It's not application instruction but contact. Might keep. Also "This posting may be used to fill current and future vacancies. Applications will be forwarded to the hiring supervisor on a weekly on-going basis until the position is filled." That's application instruction; remove. Also "This position may have access to systems or other documentation that contains HIPAA data." That's substantive? It's about data access; could keep. Thus we need to filter. Let's construct About the role paragraph combining: - About The Position Type: full-time benefit earning, IT Developer level III. (Keep "Click here to view the job classification specification." maybe as text.) - About The Department: as above. - About Hennepin County: keep substantive mission, benefits, etc but remove application instructions lines. We'll keep: "Hennepin is the largest county government organization in Minnesota. Our employees work every day to improve the health, safety and quality of life for our residents and communities. All of our jobs align with our mission to serve residents through transformative services that eliminate disparities, eliminate inequities, and create opportunity for all and our vision of a community where all people are healthy, all people are valued, and all people thrive. Our employees receive a combination of competitive benefits and positive workplace culture not found at other organizations. This includes meaningful work that impacts our community, competitive pay, work-life balance, a variety of benefits and opportunities to grow. Hennepin County envisions an organization where our commitment to diversity and the elimination of disparities is fundamental in providing excellent service to the community. Your future. Made here." We removed "Learn more at The Bridge (login as Guest)." and the later sentences about posting usage, applications forwarded, HIPAA data? Keep HIPAA data maybe as separate sentence. We could keep HIPAA data sentence: "This position may have access to systems or other documentation that contains HIPAA data." Contact info: keep. Now Responsibilities: list from "In This Position, You Will Provide PeopleSoft technical knowledge..." etc. Let's extract each bullet: - Provide PeopleSoft technical knowledge to determine standards/best practices and technical feasibility for business processes. - Translate functional specifications into a technical design. - Develop, test, and document PeopleSoft applications based on technical specifications. - Serve as a senior technical developer and participate in the following activities as part of support for the PeopleSoft Enterprise Resource Planning: - Develop applications to extract and load data using Component Interfaces, Application Engine, Database Utilities, and SQR. - Develop system interfaces using PeopleSoft integration broker; create new definitions to interface between internal/external systems and PeopleSoft. - Develop custom processes or modifications to meet functional requirements. - Develop custom reports using BI Publisher, SQR, and PeopleSoft COBOL. - Analyze and troubleshoot system performance and technical issues; provide on-call support for critical problems as needed. We need to flatten into

• items. Could keep the main bullet as separate items. Thus list items: - Provide PeopleSoft technical knowledge to determine standards/best practices and technical feasibility for business processes. - Translate functional specifications into a technical design. - Develop, test, and document PeopleSoft applications based on technical specifications. - Develop applications to extract and load data using Component Interfaces, Application Engine, Database Utilities, and SQR. - Develop system interfaces using PeopleSoft integration broker; create new definitions to interface between internal/external systems and PeopleSoft. - Develop custom processes or modifications to meet functional requirements. - Develop custom reports using BI Publisher, SQR, and PeopleSoft COBOL. - Analyze and troubleshoot system performance and technical issues; provide on-call support for critical problems as needed. Also "Serve as a senior technical developer and participate in the following activities as part of support for the PeopleSoft Enterprise Resource Planning:" is introductory; we already captured the sub-activities. Now Requirements (Need To Have): list each option. We need to preserve all options exactly as given. List: - Six years or more of IT experience. - Completion of five college/vocational technical technology courses and five years or more of IT experience. - Completion of an approved IT Hennepin County internship and five years or more of IT experience. - An approved IT certificate and five years or more of IT experience. - Two year college/vocational technical degree in a technology field and five years or more of IT experience. - Bachelor's degree or higher in a technology field and three years or more of IT experience. - Master's degree or higher in a technology field and one year or more of IT experience. Now Skills (Nice To Have): list each bullet. We need to capture: - Three or more years of technical development experience with PeopleSoft v9.2 Applications (Financial Management (FIN), Human Capital Management (HCM), Supply Chain Management (SCM), Enterprise Learning Management (ELM), and Customer Relationship Management (CRM)). - Experience: Using PeopleSoft's IDE, PeopleCode, Application Package, Application Engine, Integration Broker, BI Publisher, COBOL, and/or PHIRE change management. - Working in object-oriented technologies. - With Oracle Cloud infrastructure. - Supporting high priority systems/applications, including developing technical designs, coding, testing, and troubleshooting computer applications. - With data conversion and system interface programs. - Working with SQL. - PeopleSoft application security. - Ability to: - Analyze problems and troubleshoot. - Work in a project team environment and develop/maintain a positive partnering relationship with business and technical project team staff. - Actively contribute to creating a workplace that values diversity