DIRECTOR, ITS IMPLEMENTATION SUPPORT & TECHNICAL TRAINING
for each section we include.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must not repeat job title as heading. So no heading for the title.
We must not put Job ID/requisition numbers as headings; we can drop them.
We must preserve all substantive information; do not invent or summarize away detail.
Thus we need to include all substantive info: description of agencies, duties, qualifications, preferred skills, schedule, 55a note, loan forgiveness, residency requirement.
We need to decide which sections to create.
Possible sections:
- About the role: includes description of DSS, HRA, DHS, ITS mission, and maybe the 55a note, loan forgiveness, residency requirement? But those might be better as separate sections: Benefits (loan forgiveness), Schedule (hours), Requirements (maybe permanent status), Qualifications (min quals), Skills (preferred skills). However the instructions say: "Prefer a few substantive sections over many thin ones." So we should combine where appropriate.
We have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to include only those with real content.
We have content for:
- About the role: description of DSS, HRA, DHS, ITS mission. Could also include note about 55a program? Might be considered part of About the role (eligibility). Could also include residency requirement and loan forgiveness as Benefits? But Benefits heading is for benefits like loan forgiveness etc. The posting mentions Public Service Loan Forgiveness as a benefit. So we can create Benefits section with that info.
- Responsibilities: the bullet list of duties.
- Requirements: maybe the permanent status requirement? Also maybe the note about 55a program? But that is more about eligibility for disabled persons; could be Requirements? However the instructions say "Requirements" heading for any list of duties/requirements/benefits? Actually they said: Use
- for any list of duties/requirements/benefits. So Requirements could be a list of requirements (like permanent status, maybe education/experience? But those are qualifications). Usually Qualifications separate. So we can put the permanent status requirement under Requirements as a simple statement.
- Qualifications: the Minimum Qualifications detailed education/experience.
- Skills: the Preferred Skills bullet list.
- Benefits: Public Service Loan Forgiveness info.
- Schedule: Hours/Shift Monday - Friday 9:00am - 5:00pm.
- Pay: not provided, so omit.
We must not create empty sections.
Thus final HTML:
About the role
... description ...
Maybe also include note about 55a program and residency requirement within About the role? Could be separate paragraphs.
But we must preserve all substantive info; we can include them as separate paragraphs under About the role.
Let's extract the description:
"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. Information Technology Services (ITS) is DSS’s technology services organization. ITS mission is to support the daily, emergent, and long-term needs of both agencies. ITS creates and enhances the technology infrastructure and computer applications that support HRA and DHS and develops applications, including a variety of client eligibility and recertification systems, case management systems, housing systems, employment/work engagement services, revenue producing computer matches, claiming systems, and personnel systems."
That's the description.
We could also add a sentence about the role: "The Office of Information Technology Services (ITS) is recruiting for one (1) Computer Specialist (Software) IV, to function as Director, ITS Implementation Support and Technical Training, who will;" but that leads into responsibilities. Might be part of About the role or Responsibilities. Since it's about the role, we could include it in About the role as an introductory sentence before responsibilities. But we have a separate Responsibilities section for the duties list. So we could put that sentence in About the role.
Thus About the role paragraph: "The Office of Information Technology Services (ITS) is recruiting for one (1) Computer Specialist (Software) IV, to function as Director, ITS Implementation Support and Technical Training." Then follow with the description of DSS etc.
Now Responsibilities: list each duty as - . We need to break the long sentence into items. The posting uses semicolons and periods. We can split into logical items:
- Oversee the agency-wide planning, coordination, and delivery of complex software implementation, enterprise technical training, online learning systems administration, and technology-related policy development.
- Provide senior-level technical leadership for highly specialized and ongoing software functions, guide multi-disciplinary projects of extraordinary technical complexity, and supervise multiple units responsible for training operations and implementation support.
- Lead planning, coordination, and execution of extremely complex software implementation functions.
- Direct development and delivery of 25+ virtual technical courses offered year-round.
- Approve design of instructional materials including manuals and simulation videos.
- Supervise planning and maintenance of instructor schedules.
- Oversee review and approval of staff training requests.
- Lead creation and updates of technology policies and procedures.
- Oversee LMS operations including Absorb, Percipio, and ITS Video resources.
- Ensure accuracy of course data, schedules, and digital updates.
- Supervise units responsible for implementation support and training.
- Provide high-level technical guidance for complex software functions.
We must preserve all substantive information; we should not lose any detail. The original includes "Leads creation and updates of technology policies and procedures." (capital L). We'll keep.
Now Requirements: The permanent status requirement: "APPLICANTS MUST BE PERMANENT IN THE COMPUTER SPECIALIST (SOFTWARE) CIVIL SERVICE TITLE". Also maybe the note about 55a program? But that is more about eligibility for disabled persons; could be included in Requirements as a note. However the 55a program is a special note about eligibility for persons with disability; it's not a requirement but a provision. Could be placed under About the role or maybe a separate section? Since we don't have a heading for "Special Programs", we could fold into About the role as a note.
But we must preserve all substantive info; we can include it as a paragraph under About the role or Requirements. I'd put under About the role as a note: "This position is also open to qualified persons with a disability who are eligible for the 55-a Program." That's from the posting.
Also the residency requirement: "New York City Residency is not required for this position". Could be under About the role as well.
Public Service Loan Forgiveness: under Benefits.
Now Qualifications: Minimum Qualifications block. We need to preserve all detail. It's a long paragraph with multiple options. We'll put as
preserving the text exactly (maybe line breaks). We'll keep the bullet-like options as sentences.
We must not invent or summarize away detail. So we need to copy the text exactly as given, preserving the meaning. We'll need to ensure we include all the details: education, experience, substitution rules, etc.
Let's copy the Minimum Qualifications section:
"Minimum Qualifications A baccalaureate degree from an accredited college, including or supplemented by twenty-four (24) semester credits in computer science or a related computer field and two (2) years of satisfactory full-time software experience in designing, programming, debugging, maintaining, implementing, and enhancing computer software applications, systems programming, systems analysis and design, data communication software, or database design and programming, including one year in a project leader capacity or as a major contributor on a complex project; or A four-year high school diploma or its educational equivalent and six (6) years of full-time satisfactory software experience as described in “1" above, including one year in a project leader capacity or as a major contributor on a complex project; or A satisfactory combination of education and experience that is equivalent to (1) or (2) above. College education may be substituted for up to two years of the required experience in (2) above on the basis that sixty (60) semester credits from an accredited college is equated to one year of experience. A masters degree in computer science or a related computer field may be substituted for one year of the required experience in (1) or (2) above. However, all candidates must have a four year high school diploma or its educational equivalent, plus at least one (1) year of satisfactory full-time software experience in a project leader capacity or as a major contributor on a complex project. NOTE: In order to have your experience accepted as Project Leader or Major Contributor experience, you must explain in detail how your experience qualifies you as a project leader or as a major contributor. Experience in computer operations, technical support, quality assurance (QA), hardware installation, help desk, or as
for prose. We must not repeat job title as heading. So no heading for the title. We must not put Job ID/requisition numbers as headings; we can drop them. We must preserve all substantive information; do not invent or summarize away detail. Thus we need to include all substantive info: description of agencies, duties, qualifications, preferred skills, schedule, 55a note, loan forgiveness, residency requirement. We need to decide which sections to create. Possible sections: - About the role: includes description of DSS, HRA, DHS, ITS mission, and maybe the 55a note, loan forgiveness, residency requirement? But those might be better as separate sections: Benefits (loan forgiveness), Schedule (hours), Requirements (maybe permanent status), Qualifications (min quals), Skills (preferred skills). However the instructions say: "Prefer a few substantive sections over many thin ones." So we should combine where appropriate. We have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content. We have content for: - About the role: description of DSS, HRA, DHS, ITS mission. Could also include note about 55a program? Might be considered part of About the role (eligibility). Could also include residency requirement and loan forgiveness as Benefits? But Benefits heading is for benefits like loan forgiveness etc. The posting mentions Public Service Loan Forgiveness as a benefit. So we can create Benefits section with that info. - Responsibilities: the bullet list of duties. - Requirements: maybe the permanent status requirement? Also maybe the note about 55a program? But that is more about eligibility for disabled persons; could be Requirements? However the instructions say "Requirements" heading for any list of duties/requirements/benefits? Actually they said: Use
- for any list of duties/requirements/benefits. So Requirements could be a list of requirements (like permanent status, maybe education/experience? But those are qualifications). Usually Qualifications separate. So we can put the permanent status requirement under Requirements as a simple statement.
- Qualifications: the Minimum Qualifications detailed education/experience.
- Skills: the Preferred Skills bullet list.
- Benefits: Public Service Loan Forgiveness info.
- Schedule: Hours/Shift Monday - Friday 9:00am - 5:00pm.
- Pay: not provided, so omit.
We must not create empty sections.
Thus final HTML:
About the role
... description ...
Maybe also include note about 55a program and residency requirement within About the role? Could be separate paragraphs. But we must preserve all substantive info; we can include them as separate paragraphs under About the role. Let's extract the description: "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. Information Technology Services (ITS) is DSS’s technology services organization. ITS mission is to support the daily, emergent, and long-term needs of both agencies. ITS creates and enhances the technology infrastructure and computer applications that support HRA and DHS and develops applications, including a variety of client eligibility and recertification systems, case management systems, housing systems, employment/work engagement services, revenue producing computer matches, claiming systems, and personnel systems." That's the description. We could also add a sentence about the role: "The Office of Information Technology Services (ITS) is recruiting for one (1) Computer Specialist (Software) IV, to function as Director, ITS Implementation Support and Technical Training, who will;" but that leads into responsibilities. Might be part of About the role or Responsibilities. Since it's about the role, we could include it in About the role as an introductory sentence before responsibilities. But we have a separate Responsibilities section for the duties list. So we could put that sentence in About the role. Thus About the role paragraph: "The Office of Information Technology Services (ITS) is recruiting for one (1) Computer Specialist (Software) IV, to function as Director, ITS Implementation Support and Technical Training." Then follow with the description of DSS etc. Now Responsibilities: list each duty as - . We need to break the long sentence into items. The posting uses semicolons and periods. We can split into logical items:
- Oversee the agency-wide planning, coordination, and delivery of complex software implementation, enterprise technical training, online learning systems administration, and technology-related policy development.
- Provide senior-level technical leadership for highly specialized and ongoing software functions, guide multi-disciplinary projects of extraordinary technical complexity, and supervise multiple units responsible for training operations and implementation support.
- Lead planning, coordination, and execution of extremely complex software implementation functions.
- Direct development and delivery of 25+ virtual technical courses offered year-round.
- Approve design of instructional materials including manuals and simulation videos.
- Supervise planning and maintenance of instructor schedules.
- Oversee review and approval of staff training requests.
- Lead creation and updates of technology policies and procedures.
- Oversee LMS operations including Absorb, Percipio, and ITS Video resources.
- Ensure accuracy of course data, schedules, and digital updates.
- Supervise units responsible for implementation support and training.
- Provide high-level technical guidance for complex software functions.
We must preserve all substantive information; we should not lose any detail. The original includes "Leads creation and updates of technology policies and procedures." (capital L). We'll keep.
Now Requirements: The permanent status requirement: "APPLICANTS MUST BE PERMANENT IN THE COMPUTER SPECIALIST (SOFTWARE) CIVIL SERVICE TITLE". Also maybe the note about 55a program? But that is more about eligibility for disabled persons; could be included in Requirements as a note. However the 55a program is a special note about eligibility for persons with disability; it's not a requirement but a provision. Could be placed under About the role or maybe a separate section? Since we don't have a heading for "Special Programs", we could fold into About the role as a note.
But we must preserve all substantive info; we can include it as a paragraph under About the role or Requirements. I'd put under About the role as a note: "This position is also open to qualified persons with a disability who are eligible for the 55-a Program." That's from the posting.
Also the residency requirement: "New York City Residency is not required for this position". Could be under About the role as well.
Public Service Loan Forgiveness: under Benefits.
Now Qualifications: Minimum Qualifications block. We need to preserve all detail. It's a long paragraph with multiple options. We'll put as
preserving the text exactly (maybe line breaks). We'll keep the bullet-like options as sentences. We must not invent or summarize away detail. So we need to copy the text exactly as given, preserving the meaning. We'll need to ensure we include all the details: education, experience, substitution rules, etc. Let's copy the Minimum Qualifications section: "Minimum Qualifications A baccalaureate degree from an accredited college, including or supplemented by twenty-four (24) semester credits in computer science or a related computer field and two (2) years of satisfactory full-time software experience in designing, programming, debugging, maintaining, implementing, and enhancing computer software applications, systems programming, systems analysis and design, data communication software, or database design and programming, including one year in a project leader capacity or as a major contributor on a complex project; or A four-year high school diploma or its educational equivalent and six (6) years of full-time satisfactory software experience as described in “1" above, including one year in a project leader capacity or as a major contributor on a complex project; or A satisfactory combination of education and experience that is equivalent to (1) or (2) above. College education may be substituted for up to two years of the required experience in (2) above on the basis that sixty (60) semester credits from an accredited college is equated to one year of experience. A masters degree in computer science or a related computer field may be substituted for one year of the required experience in (1) or (2) above. However, all candidates must have a four year high school diploma or its educational equivalent, plus at least one (1) year of satisfactory full-time software experience in a project leader capacity or as a major contributor on a complex project. NOTE: In order to have your experience accepted as Project Leader or Major Contributor experience, you must explain in detail how your experience qualifies you as a project leader or as a major contributor. Experience in computer operations, technical support, quality assurance (QA), hardware installation, help desk, or as