Technology Analyst 2 (Human Centered Design)

but we need to use

• for any list of duties/requirements/benefits. The qualifications are not a list but could be considered requirements. The instruction: Use
  • for any list of duties/requirements/benefits. So we should put qualifications as list items? Might be okay to break into bullet points. We can list: - Six (6) years of information technology experience, two (2) years of which must be within the discipline of human centered design. - Associate’s degree with 15 semester credit hours in computer science or a related field substitutes for one year of general information technology experience. - Candidates in a bachelor’s degree program with at least 15 semester credit hours in computer science or a related field can substitute for one year of general information technology experience. - Bachelor’s degree in any field including or supplemented by fifteen (15) semester credit hours in computer science or a related field substitutes for three (3) years of general information technology experience. - Bachelor’s degree in any field substitutes for two (2) years of general information technology experience. - Master’s degree or higher in computer science or related field substitutes for one year of general information technology experience. Preferred Qualifications: list items. - Preference for candidates holding relevant Human-Centered Design certification from recognized institutions or software providers. - Demonstrated experience with web page design, graphical user interface, and user centered design. - Technical proficiency in Human-Centered Design tools. - Fluency in a variety of programs, software, and systems such as CSS, HMI, JavaScript, and HTML. - Fluent in statistics, machine learning, and scripting. - Strong analytical skills to understand and translate business processes into technical requirements. - Problem-solving abilities to identify, troubleshoot, and resolve hardware, software, or networking issues. - Excellent communication skills to liaise effectively with both technical and non-technical staff, and to explain complex IT concepts in simple terms. - Strong leadership and project management skills. We could also have a Skills section extracting technical skills: but we already have them in Preferred Qualifications. Could create Skills heading with those technical skills. But we must not create sections with filler. If we create Skills, we need actual content. We could list technical skills: CSS, HMI, JavaScript, HTML, etc. But we already have them in Preferred Qualifications. Might be redundant. Better to keep Qualifications and maybe Skills not needed. Benefits: we have details. Benefits of Working for NYS: list items. - Generous benefits package, worth 65% of salary. - Holiday & Paid Time Off: Thirteen (13) paid holidays annually. - Up to Thirteen (13) days of paid vacation leave annually. - Up to Five (5) days of paid personal leave annually. - Up to Thirteen (13) days of paid sick leave annually for PEF. - Up to three (3) days of professional leave annually to participate in professional development. - Up to 50% telecommuting if all criteria are met according to ITS Policy. - Health Care Benefits: Eligible employees and dependents can pick from a variety of affordable health insurance programs. - Family dental and vision benefits at no additional cost. - Additional Benefits: New York State Employees’ Retirement System (ERS) Membership. - NYS Deferred Compensation. - Access to NY 529 and NY ABLE College Savings Programs, as well as U.S. Savings Bonds. - Public Service Loan Forgiveness (PSLF). - And many more. We should not include EEO etc. We also have some notes: "Please Note Appointment to this position and continued employment with the agency is contingent upon obtaining and/or maintaining New York State residency within six months of hiring. Appointment to this position is not final until all agency approvals have been granted. Additional Comments ITS will not offer permanent employment to any candidate unless the candidate provides documentation that that they are authorized to accept work in the United States on a permanent basis. It is the policy of ITS not to hire F1 or H1 visa holders for permanent employment or to sponsor non-immigrant aliens for temporary work authorization visas or for permanent residence. Some positions may require fingerprinting. Some positions may require up to 25% travel and/or lifting up to 50 lbs." These are not benefits, but could be considered "Additional Information". However we have no heading for that. Could we include a section like "Additional Information"? Not in the allowed headings list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate. Additional notes may not fit. Could we incorporate them into Qualifications or Benefits? Probably not. Might be safer to omit them as they are not core duties/requirements/benefits. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep that info. Where to put? Could create a section "Additional Information" but not in list. However the instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but suggests those are typical. Safer to include a heading like "Additional Information" maybe okay. But risk of being considered not following instruction. Perhaps we can embed those notes into a

    under Qualifications or Benefits? They are not qualifications or benefits. Could be under "Requirements"? Not really. Could be under "About the role"? Not. Maybe we can create a section "Requirements" for those notes (residency, work authorization, etc). That seems plausible: Requirements could include eligibility requirements like residency, work authorization, etc. So we can put those notes under Requirements heading. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. We'll not include Skills or Pay or Schedule. Now format. We need to output only HTML fragment, no /, no markdown. We'll produce:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    Appointment to this position and continued employment with the agency is contingent upon obtaining and/or maintaining New York State residency within six months of hiring. Appointment to this position is not final until all agency approvals have been granted. ITS will not offer permanent employment to any candidate unless the candidate provides documentation that they are authorized to accept work in the United States on a permanent basis. It is the policy of ITS not to hire F1 or H1 visa holders for permanent employment or to sponsor non-immigrant aliens for temporary work authorization visas or for permanent residence. Some positions may require fingerprinting. Some positions may require up to 25% travel and/or lifting up to 50 lbs.

    Qualifications

    Minimum Qualifications

    maybe we shouldn't use h4? Not prohibited but we could just use
    directly. But we need to keep structure. Could use

    for subheadings? The instruction only mentions using

    for section headings. It didn't forbid other headings, but to be safe we could avoid extra headings and just use

    with items, maybe preceded by a

    Minimum Qualifications. But we need to preserve the distinction between Minimum and Preferred. Could use

    Minimum Qualifications

    and

    Preferred Qualifications

    as subheadings; they are still headings, but the instruction only says use

    for section