DSS EXECUTIVE PROJECT MANAGER (EPM)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, etc. We need to parse the job posting. First, we need to extract sections: - About the role: description of role, overview. The posting starts with description of DSS, then "The Office of the DSS First Deputy Commissioner is recruiting for a DSS Executive Project Manager who ...". That is about the role. So we can put that in

About the role

with paragraphs. - Responsibilities: The posting lists many responsibilities: "The DSS EPM will also be responsible for: Collaborating with Chief Officers ...", etc. Also earlier: "The Executive DSS Project Manager serves as a special advisor and as an executive project manager with authority for operations and program development." etc. So we can gather responsibilities. - Requirements: Minimum qualifications: "A baccalaureate degree from an accredited college and four years of progressively more responsible, full-time, satisfactory experience using information technology ...". Also alternative education/experience. Also "However, all candidates must have at least a four-year high school diploma or its educational equivalent ...". So we can put that under Requirements or Qualifications. The spec says we can have both Requirements and Qualifications sections; but we should avoid thin sections. We could combine into one section maybe "Qualifications". But we need to follow instruction: use headings for those specific labels if content exists. We have content for Qualifications (minimum qualifications). Also we have Preferred Skills. So we can have Skills section for preferred skills. Also we have Benefits: "Public Service Loan Forgiveness ..." maybe also residency requirement? That's more like additional info. Benefits: mention loan forgiveness programs. Also maybe "Public Service Loan Forgiveness" is a benefit. Also maybe residency requirement is not a benefit but additional info. We'll include Benefits section with that info. Pay: Not mentioned. So we should NOT include Pay section. Schedule: "Hours/Shift: Managerial Work Schedule DEPUTY COMMISSIONER OF IT - 95614". That seems like schedule info: Managerial Work Schedule. So we can include Schedule section with that line. We need to avoid repeating job title as heading. Not include Job ID/requisition numbers as headings. The "DEPUTY COMMISSIONER OF IT - 95614" appears after Hours/Shift; that is likely a job code. We should not put that as heading; we can include it in schedule paragraph maybe but we should drop the ID? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include the schedule info but maybe drop the ID. The schedule line: "Hours/Shift: Managerial Work Schedule DEPUTY COMMISSIONER OF IT - 95614". We can keep "Managerial Work Schedule" and drop the ID. Or we can include the whole line but it's minor metadata; better to drop the ID. We'll output just "Managerial Work Schedule". Now we need to preserve all substantive information, not invent or summarize away detail. We need to keep details but can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should not lose details; we can keep them as is, maybe in bullet lists. We need to use

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

  for prose. Thus for responsibilities we should make a

  list of each responsibility bullet. Similarly for qualifications (minimum qualifications) we can make a list? It's a paragraph with alternatives; we can keep as

  but maybe better as

  if it's a list of options. However it's not a simple list; it's a compound statement. We'll use

  . For preferred skills we have bullet list starting with "-". We'll make

  • . For benefits we have Public Service Loan Forgiveness description; we can keep as

    . Now we need to strip boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is "Additional Information The City of New York is an inclusive equal opportunity employer..." That's EEO boilerplate; we should remove it. Also "Public Service Loan Forgiveness" is not boilerplate; it's a benefit. Keep. Also "Residency Requirement" is additional info; not a benefit but maybe we can keep under Additional Information? But we only have sections defined; we could put residency under Benefits? Not exactly. Could we create a separate section? Not in list. The instruction says we should only include sections when posting has real specific content for it, using those headings. So we cannot add a custom heading like "Additional Information". We could fold residency requirement into Benefits or Schedule? Probably better to include it under Benefits as a note? But it's not a benefit. Could we put it under Requirements? Not really. Maybe we can drop it as it's not essential? The instruction says preserve ALL substantive information; we cannot drop residency requirement if it's substantive. However we could incorporate it into a

    under Benefits or maybe under Qualifications? It's not qualification. Could we add a generic

    without heading? The instruction says output ONLY the HTML fragment; we can include

    elements not under headings? The instruction says use headings for sections; but we can still have

    outside headings? It didn't forbid; but they said "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." It implies we should structure content under those headings; but we could have a

      not under a heading if it's just a stray paragraph? Probably better to include residency requirement under Benefits as a note, or maybe under Schedule? Not appropriate. Could we add a heading "Additional Information"? Not allowed per list. But maybe we can treat it as part of Benefits? It's not a benefit but it's still info about eligibility. Could we put it under Requirements? Not really. We could decide to keep it as a

      after the last section without a heading; risk being considered stray but maybe acceptable. However instruction: "Prefer a few substantive sections over many thin ones." It doesn't forbid stray paragraphs. But to be safe, we could incorporate residency requirement into Benefits section as a note: "Benefits: Public Service Loan Forgiveness ... Residency Requirement: ..." That would be combining two distinct things but still under Benefits heading. Might be okay. Alternatively, we could create a section "Requirements" and include residency requirement there? Not really. Given the instruction to preserve ALL substantive information, we need to include residency requirement somewhere. I'll add it as a

      under Benefits section, after the loan forgiveness paragraph. Now let's extract content. **About the role**: We'll combine the introductory description about DSS and the role. Paragraph: "The Department of Social Services (DSS) is comprised of the administrative units of the New York City Human Resources Administration (HRA) and the Department of Homeless Services (DHS). HRA is dedicated to fighting poverty and income inequality by providing New Yorkers in need with essential benefits such as Food Assistance and Emergency Rental Assistance. DHS is committed to preventing and addressing homelessness in New York City by employing a variety of innovative strategies to help families and individuals successfully exit shelter and return to self-sufficiency as quickly as possible. The Office of the DSS First Deputy Commissioner is recruiting for a DSS Executive Project Manager who under executive management of the DSS First Deputy Commissioner, with broad latitude for the exercise of independent judgement and action, carries out the responsibility for managing DSS initiatives in information and technology, including cross DSS-HRA-DHS initiatives. As the Executive DSS Project Manager, exercises authority, makes executive level decisions, with and without review of the DSS First Deputy Commissioner (FDC), in critical matters/situations and in the implementation of initiatives. The Executive DSS Project Manager serves as a special advisor and as an executive project manager with authority for operations and program development. The DSS Executive Project Manager will oversee the DSS portfolio of IT work. The candidate will brainstorm, develop, manage projects, and implement program policy and operations initiatives with the highest quality standards of practice as these pertain to program areas under the DSS FDC, DSS General Counsel, and DSS Chief Financial Officer. This portfolio includes the following program areas: Office of Program Accountability; Office of Human Resources Solutions; Information Technology Services; Office of Operations; Office of General Counsel (Legal Affairs, Contracts, Policy Procedures and Training); Office of Emergency Management; Office of Program Planning and Financial Management. The DSS EPM advises on the development of a stronger integration of citywide and agency-wide services." That seems like a lot; we can keep as prose

      . **Responsibilities**: The bullet list after "The DSS EPM will also be responsible for:" includes multiple items separated by line breaks. Let's list them: - Collaborating with Chief Officers and Deputy Commissioners on critical agency concerns, i.e., budget, fulfillment of mission by program areas, functional/staffing concerns, cross-program initiatives, interagency communication, that are central to improving the quality of life of individuals to whom DSS/HRA/DHS programs are tailored while ensuring adherence to federal, state and local mandates. - Responsible for making time-sensitive operational and policy decisions in collaboration with the DSS FDC, Chief Officers, and Deputy Commissioners that will have agency wide impact, affecting service delivery within any functional area under the auspices of DSS. - Acting as the lead, and on behalf of the DSS FDC, collaborates with executives from HRA-DHS on critical interagency initiatives, (i.e., IT system solutions, program monitoring, resource allocation and fiscal management, legal settlement compliance, contract management, interagency project and operation coordination), where seamless integration effort would serve to enhance the quality of life for agency clients, and in special projects relating to IT and budget management. - On behalf of FDC and Commissioner office, coordinate enterprise IT initiatives pre-project planning sessions by establishing working committee and leads the agency’s steering committee of executive project managers and IT counterparts to coordinate, manage, prioritize and streamline the operation, staffing and executive of IT solutions. - Exploring current operations, program services and governing rules and regulations to recommend new initiatives that address the needs of the DSS program participants. - Serves as agency liaison to task forces and other city-wide efforts relating to new initiatives and governing rules and regulations in the areas of data, technology and information systems. - Advises the DSS FDC and Commissioner on emerging trends and opportunities in information and technology. - Researching and keeping abreast of current practices, programs and legislative enactments on DSS operational and program issues; disseminates new information, best practices and funding opportunities to the Chief Officers. - Participating in, and in the DSS FDC’s absence, represents the DSS FDC in regular meetings with DSS Leadership, such as with the Commissioner, the Chief Officers and others, as well as leaders of the City and State partner agencies in the formulation of long and short-range plans with respect to policy formulation/implementation issues. We'll put each as

    • . **Requirements**: Minimum qualifications paragraph. We need to include both the primary qualification and the alternative. Let's capture: "A baccalaureate degree from an accredited college and four years of progressively more responsible, full-time, satisfactory experience using information technology in computer applications programming, systems programming, computer systems development, data telecommunications, database administration, planning of data/information processing, user services, or area networks, at least 18 months of this experience must have been in an executive, managerial, administrative capacity in the areas of computer applications programming, systems programming, computer systems development, data telecommunications, data base administration, or planning of data processing or in the supervision of staff performing these duties; or Education and/or experience equivalent to '1' above. However, all candidates must have at least a four-year high school diploma or its