Training/Dev Specialist II

We need to output HTML fragment with sections: About the role? The posting includes Overview, Responsibilities, Qualifications, Required Documents, Advertised Salary Minimum, ADA, College/Department Highlights, Mission, Values, Funding Statement, College Highlights, University Highlights. However we must only include sections when posting has real specific content. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instructions: 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. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have Overview (which could be About the role). Responsibilities section present. Qualifications (minimum and preferred) present. Knowledge, Skills, And Abilities present (could be Skills). Benefits: they mention "Exempt positions are eligible for excellent benefits including: 13 paid holidays, earn 22 days of paid vacation leave and 12 days of sick leave per year, 50% tuition reduction for employees and dependents, competitive health benefits packages and a generous contribution into your retirement." That's specific benefits. So we can include Benefits section. Pay: "Advertised Salary Minimum $63,000; Commensurate with experience, plus excellent benefits". This includes a specific minimum salary $63,000. The phrase "Commensurate with experience" is placeholder but we have a specific minimum. According to rule: never create Pay section unless posting actually states them. It does state Advertised Salary Minimum $63,000; so we can include Pay with that info. However we must avoid filler like "Commencement with experience". We can include the minimum and note that it's commensurate with experience? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not include that phrase if it's just filler. We could include just the minimum salary: "$63,000". But we must preserve ALL substantive information; do not invent or summarize away detail. The posting says "Advertised Salary Minimum $63,000; Commensurate with experience, plus excellent benefits". The substantive info is the minimum $63,000 and that it's commensurate with experience (which is somewhat filler). But we could keep the phrase as part of the sentence? The instruction says never emit a heading followed by filler/placeholder text. It doesn't say we cannot include that phrase inside the paragraph; just that we shouldn't have a heading with only filler. So we can include a Pay section with a paragraph that includes the minimum salary and mention commensurate with experience (maybe okay). But to be safe, we could phrase: "Advertised salary minimum: $63,000 (commensurate with experience)." That includes the filler but it's part of the sentence. Might be okay. Schedule: The posting mentions hybrid telework, expected to work at least three days per week at the USU Salt Lake Campus. Also mentions variable schedules, weather, road conditions associated with field work. So we have some schedule info: hybrid telework, at least three days onsite, variable schedule due to field work. That's specific enough to include a Schedule section. We also have Required Documents (application instructions) which we must remove per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop Required Documents section. College/Department Highlights, Mission, Values, Funding Statement, College Highlights, University Highlights: These are likely boilerplate or extra info not requested as sections. We should keep substantive information? The instruction says preserve ALL substantive information; do not invent or summarize away detail. However we are limited to using only the specified section headings. If we include extra headings not in the list, that would violate the rule (they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't explicitly forbid other headings, but they gave examples. Likely they want us to only use those headings. So we should incorporate that info into appropriate sections (maybe About the role includes overview, mission, values?). But we must not invent or summarize away detail. We could embed the college/department highlights etc within About the role paragraph. That would preserve the info without extra headings. That seems acceptable. Thus final HTML: sections: About the role (overview), Responsibilities, Qualifications (maybe split into Minimum Qualifications and Preferred Qualifications? Could combine), Skills (Knowledge, Skills, And Abilities), Benefits, Pay, Schedule. We need to use

  • for any list of duties/requirements/benefits. So for Responsibilities we should list each duty as
  • . For Qualifications we could list minimum and preferred as separate lists? Could do two lists: Minimum Qualifications and Preferred Qualifications each as
    . For Skills we could list each bullet as
    • . For Benefits we list each benefit as
    • . For Pay we just a paragraph. For Schedule we paragraph. We must not repeat the job title as heading. So no heading for Training/Development Specialist II. We need to ensure we don't include boilerplate like EEO etc. We removed. Now craft content. About the role: combine Overview paragraph plus maybe mission/values? We'll keep overview as is, maybe add mission/values as part of About the role? But we need to preserve all substantive information; we can include mission and values in About the role as extra paragraphs. That's okay. Let's extract Overview text: "Overview The Training/Development Specialist II provides training and technical assistance to community rehabilitation and Home and Community Based Waiver providers to advance competitive integrated employment, meaningful community inclusion, and quality of life for people with disabilities. The individual will develop and deliver training, provide hands-on mentoring and technical assistance, and help people with disabilities, families, professionals, and service-provider organizations translate evidence, policy, and person-centered values into sustained daily practice. This is a proactive field-building role. The individual seeks out opportunities and develops relationships throughout Utah. Success requires initiative, consistent follow-up, and a relentless commitment to improving services and outcomes rather than waiting for work to arrive. The Training/Development Specialist II must possess the knowledge and experience required to independently perform complex training, mentoring, technical assistance, evaluation, and project-development work. Responsibilities may affect provider practices and disability-service systems at local and state levels. The individual must be able to navigate complex service systems, navigate resistance to change, and support partners through initial engagement, measurable implementation, and sustained improvement. This position reports to the Principal Investigator of the Project in the IDRPP Research and Training Division. This classification has no supervisory responsibilities. Project assignments, reporting relationships, and coordination responsibilities may be refined based on final program structure and negotiated project requirements. This position is eligible for hybrid telework in the state of Utah. The successful applicant will be expected to work at least three days per week at the USU Salt Lake Campus." We can keep that as About the role. Responsibilities list: many sentences. We'll break into bullet points. Responsibilities text: "Provides training and technical assistance to director support professionals, people with disabilities and their families on disability employment, community inclusion, person-centered practices, provider transformation, training, mentoring, and related assigned areas. Proactively identifies, contacts, and cultivates relationships with providers, communities, employers, families, professionals, and system partners throughout Utah, including stakeholders who may be hesitant, difficult to reach, or early in readiness for change. Develops, adapts, and delivers accessible, evidence informed training for people with disabilities, families, direct support professionals, provider leaders, educators, support coordinators, and public partners. Provides statewide mentoring and technical assistance that helps participants apply learning in actual service, employment, workplace, and community settings. Delivers one-on-one, onsite, virtual, and group training through workshops, communities of practice, coaching sessions, and other formats for both small groups and large audiences. Uses a systematic improvement process through training and technical assistance data to make data-based decisions to assess strengths and needs, establish jointly owned goals, develop action plans, coach implementation, identify barriers, measure progress and fidelity, and refine supports until practices are sustained. Incorporates person-centered planning and thinking tools, including Charting the LifeCourse and other tools selected with DHHS/DSPD and project stakeholders, into training and technical assistance as appropriate. Develops curricula, facilitator and participant materials, implementation toolkits, case studies, activities, assessments, online modules, and other digital learning content using Microsoft Office and Articulate, among other computer-based tools. Aligns training and technical assistance with applicable evidence, federal and state policy, and project guidance, including WIOA, the HCBS Settings Rule, Employment First, and DHHS/DSPD requirements. Collects and analyzes qualitative and quantitative information to document participation, learning, implementation progress, practice change, and organizational outcomes. Develops reports, presentations, proposals, publications, briefs, tip sheets, and other media for partners, funders, and professional audiences. Attends meetings, trainings, and conferences and serves on advisory boards, councils, and workgroups as requested. Performs miscellaneous job-related duties as assigned." We'll make each a
    • . Qualifications: Minimum Qualifications bullet list: - Bachelor's degree in rehabilitation counseling, special education, social work, psychology, public health, education, disability studies, or a closely related field, plus at least two years of relevant experience. - Professional experience in training, technical assistance, employment services, disability services, provider support, program implementation, or a closely related area. - Experience with people with disabilities and families, competitive integrated employment, provider transformation, person-centered planning, assistive technology, online course development, learning-management systems, evaluation, or statewide service delivery. - Knowledge of the HCBS support systems in Utah. Preferred Qualifications: - A master's degree in a relevant field is preferred. - Ability to write technical papers and reports. We could combine into one list with headings? But we need to use
      • for any list. Could have two separate
        each preceded by a

        heading? But we cannot add extra headings besides the allowed ones. However we could embed a or something inside

        . Probably okay to have a

        preceding each list. The instruction: Use

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

          for prose. So we can have a

          intro then

          . That's fine. Skills (Knowledge, Skills, And Abilities) list: - Knowledge of competitive integrated employment supported and customized employment, community inclusion, person-centered practices, and service delivery in home and community-based settings. - Possess the ability to present in small and large group settings. - Knowledge of evidence-based training, mentoring, coaching, implementation, adult-learning, and continuous-improvement practices. -