Group Chief Information Officer - Government & Public Employees

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: Intro: "Are you looking for a rewarding career with an organization that values their staff? The Department of Innovation & Technology (DoIT) is seeking to hire qualified candidates with the opportunity to work in a dynamic, creative thinking, problem solving environment. This position serves as the Government & Public Employees (GPE) Group Chief Information Officer (GCIO) and principal policy formulating administrator for the total management process of the GPE Group supporting the Capital Development Board, Department of Revenue, Department of Lottery, Illinois Liquor Control Commission and Governor’s Office on Management & Budget. In this role you will develop and implement policies and procedures for the long and short term strategic goals of the GPE Group consistent with DoIT’s mission. If you possess these knowledges, skills, abilities and experience, we invite you to apply for this position to join the DoIT Team!" That's about the role. Then benefits list: "As a State of Illinois employee, you receive a comprehensive benefits package including:Competitive Group Insurance benefits including health, life, dental and vision plansFlexible work schedules (when available and dependent upon position)10 -25 days of paid vacation time annually (10 days for first year of state employment)12 days of paid sick time annually which carry over year to year3 paid personal business days per year13-14 paid holidays per year dependent on election years12 weeks of paid parental leavePension plan through the State Employees Retirement SystemDeferred Compensation Program – voluntary supplemental retirement planOptional pre-tax programs -Medical Care Assistance Plan (MCAP) & Dependent Care Assistant Plan (DCAP)Tuition Reimbursement Program and Federal Public Service Loan Forgiveness Program eligibility" We need to format as list. Then "Essential Functions" list: bullet points. Then "Minimum Qualifications": list. Then "Preferred Qualifications": list. Then "Conditions of Employment": list. We need to map to sections: About the role (intro). Responsibilities (Essential Functions). Requirements (Minimum Qualifications). Qualifications (Preferred Qualifications). Skills (maybe from preferred qualifications? Could also include abilities). Benefits (benefits list). Pay (not mentioned; no pay info). Schedule (maybe flexible work schedules mentioned under benefits; but schedule section only if posting actually states them. It does mention flexible work schedules (when available and dependent upon position). That's schedule info. Could include schedule section with that detail. However we already have flexible work schedules in benefits list; but we could separate schedule. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine schedule into Benefits? But they said include section ONLY when posting has real, specific content for it. Benefits section includes flexible work schedules; we could keep schedule as part of Benefits. But they also have separate Schedule section possible. Since flexible work schedules is a schedule detail, we could put under Benefits. But we could also create Schedule section with that detail. However they said prefer few substantive sections over many thin ones. So better to not create separate Schedule unless needed. Since schedule info is minimal, we could incorporate into Benefits. Pay: no info, so omit. Thus sections: About the role, Responsibilities, Requirements (Minimum Qualifications), Qualifications (Preferred Qualifications), Skills (maybe we can extract skills from preferred qualifications: ability to develop and manage major agency program, ability to estimate and budget..., developed verbal and written communication skills, ability to establish and maintain effective working relationships, etc). Could put those under Skills. But we also have knowledge, skills, abilities in Minimum Qualifications? Actually Minimum Qualifications includes knowledge, skill and mental development equivalent to completion of four years college with coursework in MIS, IT, CS or related fields. Requires prior experience equivalent to four years of progressively responsible administrative experience in IT in a public or business organization. Requires four years of professional experience supervising IT professionals in a large and complex public or business organization. That's more experience/requirements than skills. Could treat as Requirements. Preferred Qualifications list includes many abilities and experience. Thus we can have Skills section pulling out abilities: "Ability to develop and manage a major agency program. Ability to estimate and budget for future needs and cost of personnel, space, equipment, supplies, and services. Developed verbal and written communication skills to present information to internal and external stakeholders with clarity and precision. Ability to establish and maintain effective working relationships with agency leadership, stakeholders, and other key partners." Also maybe "Master’s degree in management information systems, computer systems, or related field." That's qualification. We could also put Master's degree under Qualifications. Thus sections: - About the role (intro paragraph) - Responsibilities (Essential Functions list) - Requirements (Minimum Qualifications list) - Qualifications (Preferred Qualifications list) - Skills (list of abilities) - Benefits (list) We need to ensure we don't repeat content. We'll extract each piece. Let's extract About the role: combine first paragraph(s) up to "If you possess these knowledges, skills, abilities and experience, we invite you to apply for this position to join the DoIT Team!" That's about role. Responsibilities: Essential Functions bullet points (list). We'll list each as

. Requirements: Minimum Qualifications bullet points (list). We'll list each. Qualifications: Preferred Qualifications bullet points (list). We'll list each. Skills: maybe we can extract from Preferred Qualifications the ability statements: "Ability to develop and manage a major agency program.", "Ability to estimate and budget for future needs and cost of personnel, space, equipment, supplies, and services.", "Developed verbal and written communication skills to present information to internal and external stakeholders with clarity and precision.", "Ability to establish and maintain effective working relationships with agency leadership, stakeholders, and other key partners." Also maybe "Master’s degree..." is qualification not skill. We'll keep that in Qualifications. Benefits: list as given. We need to format benefits as list items. The benefits string is a bit run-together; we need to split by items. Let's parse: "Competitive Group Insurance benefits including health, life, dental and vision plans" "Flexible work schedules (when available and dependent upon position)" "10 -25 days of paid vacation time annually (10 days for first year of state employment)" "12 days of paid sick time annually which carry over year to year" "3 paid personal business days per year" "13-14 paid holidays per year dependent on election years" "12 weeks of paid parental leave" "Pension plan through the State Employees Retirement System" "Deferred Compensation Program – voluntary supplemental retirement plan" "Optional pre-tax programs -Medical Care Assistance Plan (MCAP) & Dependent Care Assistant Plan (DCAP)" "Tuition Reimbursement Program and Federal Public Service Loan Forgiveness Program eligibility" We'll make each a

. Now produce HTML fragment with headings

and then

• for lists,

  for prose. We must not include any extra text like explanations. Let's craft. Check for any boilerplate to remove: The Conditions of Employment section we are omitting because not requested? The instruction: "Prefer a few substantive sections over many thin ones." Conditions of Employment is substantive but not among the allowed headings list? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Conditions of Employment is not in that list, so we should not create a heading for it. We could fold its content into other sections? But it's not really fitting. The instruction says: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should omit Conditions of Employment entirely? But we must preserve ALL substantive information; do NOT invent or summarize away detail. If we omit Conditions of Employment, we lose substantive info. However maybe we can incorporate those details into existing sections like Requirements or Qualifications? Conditions of Employment includes things like identity verification, employment authorization, background check, travel, overtime, on-call, lifting up to 10 pounds, revolving door restrictions, ethics statements. Those are not exactly requirements/qualifications but could be considered Requirements (conditions). Could be placed under Requirements as additional items. The heading "Requirements" could encompass both minimum qualifications and conditions of employment. But we already have Minimum Qualifications separate. Could combine? However we need to preserve all info; we can put Conditions of Employment under Requirements as a list after Minimum Qualifications? But then we would have two lists under same heading; that's okay. Similarly, we could put some of those under Skills? Not appropriate. Thus we will include Conditions of Employment items under Requirements heading (maybe as a sublist). But we need to keep the heading only once. We'll create Requirements section with two lists: Minimum Qualifications and Conditions of Employment. Or we could just make one list combining all. But to preserve clarity, we could separate with a

  heading? Not allowed. We'll just make a single list under Requirements that includes both sets. However the instruction: "Use

  • for any list of duties/requirements/benefits". So we can have multiple lists under same heading; that's fine. Thus Requirements heading will contain: - Minimum Qualifications (list) - Conditions of Employment (list) We'll need to differentiate maybe with a

    preceding each list? Could add a brief

    like "Minimum Qualifications:" then list, then another

    "Conditions of Employment:" then list. That's acceptable as prose. Now we need to ensure we don't include boilerplate like "All applicants must be able to meet the following Conditions of Employment with or without reasonable accommodation, to be considered for this position. The State of Illinois complies with federal and state disability laws and will make reasonable accommodations for applicants and employees with disabilities." That's part of Conditions of Employment; we should keep the substance but maybe drop the introductory sentence? It's substantive but could be considered boilerplate? It's part of the section; we can keep it as a

    before the list. But the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The Conditions of Employment includes legal stuff; but it's not exactly EEO; it's specific to the job. Might be considered legal but it's part of the job conditions. I'd keep it. Now we need to ensure we don't include any duplicated lines. Now craft HTML. Let's write:

    About the role

    Are you looking for a rewarding career with an organization that values their staff? The Department of Innovation & Technology (DoIT) is seeking to hire qualified candidates with the opportunity to work in a dynamic, creative thinking, problem solving environment. This position serves as the Government & Public Employees (GPE) Group Chief Information Officer (GCIO) and principal policy formulating administrator for the total management process of the GPE Group supporting the Capital Development Board, Department of Revenue, Department of Lottery, Illinois Liquor Control Commission and Governor’s Office on Management & Budget. In this role you will develop and implement policies and procedures for the long and short term strategic goals of the GPE Group consistent with DoIT’s mission. If you possess these knowledges, skills, abilities and experience, we invite you to apply for this position to join the DoIT Team!

    Responsibilities

    • Subject to management approval, serves as the Group Chief Information Officer (GCIO) and policy formulating official for the Government & Public Employees (GPE) Group for the Department of Innovation & Technology (Do