Project Assistant - Artificial Intelligence Enablement Specialist - 7377
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (EEO, scam warnings, application instructions)
- Include section ONLY when real specific content exists
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits unless posting actually states them
- Output ONLY HTML fragment
I need to decide on section headings. The suggested headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
I'll map:
- "About the role" for the introductory paragraph about reporting line and general description.
- "Responsibilities" for the duties list.
- "Qualifications" for minimum qualifications (could split into Minimum Qualifications and Preferred Qualifications, but maybe keep as one section with sub-lists? The rule says use
for section headings. Could have "Qualifications" as h3 and then sub-headings? But only h3 allowed? The rule says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those. I'll use h3 for main sections. For minimum vs preferred, I could use h4? But the instruction says use for section headings. Might be okay to use h3 for each. However, "Qualifications" is one section. I'll do "Qualifications" as h3, then within it, maybe use for Minimum and Preferred? But the instruction says use for section headings. It doesn't say not to use h4. But to be safe, I'll keep it as one Qualifications section with two sub-lists labeled in prose or using ? Better to use for subsections? The example headings include "Requirements" and "Qualifications" as separate. Actually, "Requirements" and "Qualifications" are listed as examples. Could treat Minimum Qualifications as Requirements and Preferred as Qualifications? But they are both qualifications. I'll do "Minimum Qualifications" and "Preferred Qualifications" as separate h3 sections? That might be too many. The rule: "Prefer a few substantive sections over many thin ones." So maybe combine into one "Qualifications" section with two lists.
I'll structure:
About the role
The incumbent will report to Data & Artificial Intelligence Specialist within the Office of Digital Strategy.
Responsibilities
- ... each duty ...
Qualifications
Minimum Qualifications
Seven (7) years of experience in artificial intelligence, computer science, data engineering, data analytics, information technology, or a related field demonstrating a comprehensive understanding of various IT disciplines and how they intersect within large-scale organizations. At least two (2) years of experience must be within the discipline of artificial intelligence.
Substitutions: Earned college degrees in computer science, data science, mathematics, information technology or a related field of study may substitute for the specified years of broad IT experience as follows:
- Bachelor’s degree substitutes for 4 years of experience.
- Master’s degree substitutes for an additional 1 year of experience.
- Doctoral degree substitutes for an additional 2 years of experience.
Preferred Qualifications
- Working knowledge of AI/ML fundamentals, including model types, training data, ethics, bias detection, and fairness.
- Familiarity with AI risk and governance frameworks (such as NIST AI RMF, ISO/IEC 42001, or EU AI Act) and healthcare regulations like HIPAA and HITECH.
- Strong written communication skills to author policies, standard operating procedures, and risk assessments, with the ability to translate complex technical jargon for non-technical users.
- Experience designing and delivering engaging training courses, manuals, and e-learning modules using webinar software and standard office suites.
- Strong organizational and project management skills to handle multiple tasks concurrently, with experience using GRC, workflow, and document management platforms like SharePoint.
But the rule says use for section headings. Using h4 might be okay, but to be safe, I could make "Minimum Qualifications" and "Preferred Qualifications" as h3 sections. However, that would create many sections. The rule says prefer a few substantive sections. I'll keep Qualifications as one h3 and use h4 for subsections. The instruction doesn't forbid h4. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other heading levels. I think it's fine.
Now Benefits: explicit list. I'll create a Benefits section.
Pay: specific statement about salary. I'll create a Pay section.
Schedule: not explicitly stated, but travel requirements. Could include in Additional Comments or a separate section? The posting says "This position may require travel throughout New York State including overnights to areas not served by public transportation." That's a schedule/travel requirement. Could be under "Schedule" or "Additional Information". The example headings include Schedule. I'll create a Schedule section for travel requirements.
Additional Comments: includes location, accommodation, E-Verify, visa, etc. Some of that is boilerplate (EEO, accommodation, visa). The rule says remove EEO/equal-opportunity/scam-warning boilerplate. The accommodation request info might be considered boilerplate? It says "If you require reasonable accommodation... please contact..." That's standard boilerplate. Also "The NYS Department of Health does not participate in E-Verify and does not sponsor visa applications." That's also standard. The rule says remove EEO/equal-opportunity/scam-warning boilerplate. This includes accommodation and visa statements. Also "For more information on the NYS Department of Health’s Mission..." is boilerplate. So I should remove those.
But the location info: "This position is being recruited in both New York City and Albany; the position may be filled at either location." That's substantive. Also "When reviewing qualifications, omissions and vagueness cannot be interpreted in the candidate’s favor. Candidates are responsible for providing accurate and clear descriptions of their experience demonstrating how they meet the minimum qualifications." That's instructional but maybe keep? It's about application process. The rule says remove application instructions. That's an instruction. So drop.
Travel requirement: keep.
Benefits list: keep.
Pay statement: keep.
Now, the "Additional Comments" section includes benefits, pay, travel, location, and boilerplate. I'll split: location and travel into Schedule or a separate "Additional Information" section? The example headings don't include "Additional Information". But we can create a section for "Location" or "Schedule". Since travel is schedule-related, I'll put travel under Schedule. Location could be under "About the role" or a separate "Location" section? Not in example headings. I'll include location in About the role or a separate paragraph.
Better to have a "Location" section? Not in examples. I'll include location in About the role.
Let's outline final HTML:
About the role
The incumbent will report to Data & Artificial Intelligence Specialist within the Office of Digital Strategy. This position is being recruited in both New York City and Albany; the position may be filled at either location.
Responsibilities
- Serve as reviewer for AI tool requests submitted by staff; evaluate against architecture, security, data privacy, and interoperability standards
- Assess vendor AI/ML solutions for model transparency, explainability, training data provenance, and bias/fairness risk
- Partner with Security, Privacy, Legal, and Procurement on a consistent intake and risk-scoring process
- Research, design and deliver role-based training on responsible AI use, approved tools, prompt literacy, and common risk patterns
- Track the AI vendor and regulatory landscape; brief leadership on emerging capability and risk
- Maintain the AI tool registry/inventory, for NYS DOH
- Administer the intake workflow and generate periodic compliance reporting for leadership
- Coordinate governance committee scheduling, agendas, minutes, and action-item follow-through
- Serve as point of contact for staff checking status on submitted requests
- Author and maintain SOPs, acceptable-use policies, process documentation etc.
- Maintain the documentation repository
Qualifications
Minimum Qualifications
Seven (7) years of experience in artificial intelligence, computer science, data engineering, data analytics, information technology, or a related field demonstrating a comprehensive understanding of various IT disciplines and how they intersect within large-scale organizations. At least two (2) years of experience must be within the discipline of artificial intelligence.
Substitutions: Earned college degrees in computer science, data science, mathematics, information technology or a related field of study may substitute for the specified years of broad IT experience as follows:
- Bachelor’s degree substitutes for 4 years of experience.
- Master’s degree substitutes for an additional 1 year of experience.
- Doctoral degree substitutes for an additional 2 years of experience.
Preferred Qualifications
- Working knowledge of AI/ML fundamentals, including model types, training data, ethics, bias detection, and fairness.
- Familiarity with AI risk and governance frameworks (such as NIST AI RMF, ISO/IEC 42001, or EU AI Act) and healthcare regulations like HIPAA and HITECH.
- Strong written communication skills to author policies, standard operating procedures, and risk assessments, with the ability to translate complex technical jargon for non-technical users.
- Experience designing and delivering engaging training courses, manuals, and e-learning modules using webinar software and standard office suites.
for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (EEO, scam warnings, application instructions) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits unless posting actually states them - Output ONLY HTML fragment I need to decide on section headings. The suggested headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I'll map: - "About the role" for the introductory paragraph about reporting line and general description. - "Responsibilities" for the duties list. - "Qualifications" for minimum qualifications (could split into Minimum Qualifications and Preferred Qualifications, but maybe keep as one section with sub-lists? The rule says use