Statewide Director - Regional Field Offices (Director DDSO)

The user wants me to convert this job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: 1. About the role / Duties Description - this is the main description 2. Responsibilities - broken down into Administrative, Service Access, Service Authorization, Constituent support 3. Requirements / Minimum Qualifications 4. Preferred Qualifications 5. Additional Comments - contains various info about transfers, eligibility, benefits, etc. The rules say: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists - Use

  for prose - Don't repeat job title as heading - Don't put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (EEO, scam warnings, application instructions) - Only include sections with real content - No filler/placeholder text - Output only HTML fragment Looking at the content: The "Duties Description" is essentially the "About the role" section. It has a narrative paragraph followed by core competencies and then detailed responsibilities broken into categories. The responsibilities are clearly categorized: Administrative, Service Access, Service Authorization, Constituent support. These should be a Responsibilities section with sub-lists. Minimum Qualifications and Preferred Qualifications are clear. Additional Comments contains: - Transfer eligibility info - Medicare/Medicaid eligibility requirement - PSLF info - Long term leave policy - Reasonable accommodation contact - Benefits: Savings programs, pre-tax savings, EAP, life/disability insurance, deferred compensation, paid holidays/leave, health care, paid parental leave, retirement, professional development - EEO statement (boilerplate, should remove) The benefits are quite detailed and specific, so I should include a Benefits section. No Pay or Schedule information is explicitly stated (location and telecommuting to be discussed at interview - that's not specific enough for a Schedule section). Let me structure:

  About the role

  ...narrative...

  Core competencies: ...

  Responsibilities

  Administrative

  • ...

  Service Access

  • ...

  Service Authorization

  • ...

  Constituent Support

  • ...

  Requirements

  Minimum Qualifications: ...

  Substitutions: ...

  Qualifications

  Preferred Qualifications: ...

  Benefits

  • ...
  Wait, the rules say use

  for section headings. Should I use

  for sub-sections? The rules don't mention

  , but it's semantic HTML. The example headings given are all

  . I think using

  for sub-categories within Responsibilities is fine as it's semantic. But the rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other heading levels. I'll use

  for main sections and

  for sub-sections. Now, let me extract all the content carefully. From Duties Description: - First paragraph: "The New York State Office for People With Developmental Disabilities (OPWDD) is seeking a creative, innovative leader who is capable of executing strategic decisions overseeing the daily operations of our Regional Field Offices under the Division of Service Access, Program Implementation and Constituents Supports (SPS). The position serves at the pleasure of the Commissioner of OPWDD." - Second paragraph: "The Statewide Director, under the direction of the Associate Commissioner, Division of Service Access, Program Implementation and Constituents Supports provides executive leadership, strategic direction, and operational oversight of OPWDD's regional field offices statewide. This role ensures consistent, high-quality service delivery, regulatory compliance, and system performance across all regions while advancing OPWDD's commitment to diversity, equity, inclusion, and accessibility (DEIA). The Director serves as a key liaison between Central Office leadership and regional field office operations, translating statewide policy into equitable, person-centered practice. The role requires a strong focus on systems alignment, workforce development, community partnership, and continuous improvement, with intentional integration of DEIA principles into all operational decisions." - Core competencies: "Strategic planning, oversight and coordination of key initiatives Mission focused implementation of policies and procedures Risk management approach to operations." Then Administrative responsibilities (bulleted in the text but not formatted as list): - Responsible for ensuring appropriately resourced units within existing allocations. - Supervise 5 Regional Field Office (RFO) Directors who have oversight of fidelity of program models regional office operations - Monitor staff performance activities including regular training and support, performance evaluations to ensure a competent workforce. - Monitoring of strategic initiatives to ensure alignment - Assist in the direction and management of RFO staff that include approximately 800 professionals in five regions with 21 satellite offices across the State - Oversee the authorization and system capacity with over 415 voluntary agencies statewide Service Access: - Ensure service access activities occur in an equitable and consistent manner in accordance with existing procedures - Manage engagement activities with service recipients - Oversight of implementation of the three-step process for eligibility determinations for OPWDD - Oversight of seven key process steps related to the front door - Ensure language access and plain language practices are implemented - Monitor overall compliance monitoring with regulatory and operational practices. - Manage service access and person-centered options for all New Yorker's seeking OPWDD services through OPWDDs Regional Offices. - Manage the creation of and timely access to OPWDD services for priority populations such as those aging out of residential schools both in and out of state, individuals who are dually diagnosed who remain in emergency or acute care hospital settings, and those who are moving out of institutional settings including developmental centers and skilled nursing facilities and ensure timely access to services. Service Authorization: - Ensure service authorization guidelines are applied consistently to ensure equitable access to services - Manage eligibility timelines to ensure compliance with Eligibility Service Access Legislation (ESAL) - Monitor engagement points to ensure consistent and accessible customer experience. - Implement federal regulations for Home and Community Based settings rules which will have far reaching effects on many of the providers, requiring actions by the regional offices. Constituent support: - Manage processing of provider related requests for changes to existing capacity - Manage crisis teams with complex cases and provider clinical consultations to ensure timely response and support. - Lead the regional offices efforts with various individual and family advocacy groups including local councils and county based Mental Hygiene sub committees. - Work with multiple voluntary and governmental agencies to coordinate and fund services - Manage collaborative working relationships with local mental health providers to implement and further develop crisis intervention and prevention services. - Manage auspice change and rate rationalization within the provider community Location and telecommuting to be discussed at interview - this is not specific, so no Schedule section. LinkedIn link - probably not needed, it's navigation. Minimum Qualifications: detailed text. Preferred Qualifications: detailed text. Additional Comments: - Transfer eligibility via Section 70.1 - Preference to OPWDD employees impacted by closures - Medicare/Medicaid eligibility requirement - PSLF info - Long term leave policy - Reasonable accommodation contact - Benefits list: Savings programs (U.S. Savings Bond, College Savings Plan), Voluntary pre-tax savings (Health Care Spending Account, Dependent Care Advantage Account), EAP, Life insurance and Disability insurance, NYS Deferred Compensation Plan, Paid Holidays and Leave (13 paid holidays, 13 days vacation initially, 5 days personal leave, paid sick leave), Health Care Coverage (variety of affordable health insurance, family dental and vision at no extra cost), Paid Parental Leave (up to 12 weeks at full pay), Retirement Program (NYS Employees' Retirement System), Professional Development and Education and Training (training programs, tuition assistance, PSWP) - EEO statement - remove as boilerplate I need to include the benefits in a Benefits section. The benefits are quite detailed, so I'll list them. Now, I need to decide on section headings. The rules suggest: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I have: - About the role (from Duties Description narrative) - Responsibilities (with sub-categories) - Requirements (Minimum Qualifications) - Qualifications (Preferred Qualifications) - but "Qualifications" might be confused with Requirements. The rules list both "Requirements" and "Qualifications" as example headings. I'll use "Requirements" for minimum qualifications and "Preferred qualifications" as a subsection or separate. Actually, the rules say "Qualifications" as a heading example. I'll use "Requirements" for minimum and "Preferred qualifications" as a sub-heading or separate

  . But the rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So both Requirements and Qualifications are separate top-level sections. I'll make Minimum Qualifications under Requirements, and Preferred Qualifications under Qualifications. But the content has "Minimum Qualifications" and "Preferred Qualifications". I'll do:

  Requirements

  Minimum Qualifications: ...

  Qualifications

  Preferred Qualifications: ...

  That seems appropriate. Skills - not explicitly listed separately, but core competencies could be skills. However, core competencies are mentioned in About the role. I could extract them as a Skills section, but they're part of the role description. The rules say "include a section ONLY when the posting has real, specific content for it". The core competencies are listed: Strategic planning, oversight and coordination of key initiatives; Mission focused implementation of policies and procedures; Risk management approach to operations. That's three items. Could be a Skills section. But they're labeled "Core competencies" in the description. I'll include them in About the role or as a separate Skills section. Since the rules mention Skills as an example heading, and there are specific competencies listed, I'll create a Skills section. But the core competencies are part of the Duties Description. I'll include them in About the role as a paragraph or list. Let's see: "Core competencies: Strategic planning, oversight and coordination of key initiatives Mission focused implementation of policies and procedures Risk management approach to operations." I'll make a list. Now, let's write the HTML. I'll start with

  About the role

  Then paragraphs for the narrative. Then maybe

  Core competencies

  with
  • ... but the rules say use

    for section headings. Sub-headings can be

    . That's fine. Then

    Responsibilities

    with

    for each category. Then

    Requirements

    with the minimum qualifications. Then

    Qualifications

    with preferred qualifications. Then

    Benefits

    with list. No Pay, no Schedule. Now, ensure I don't include boilerplate: EEO statement, application instructions (none really, just LinkedIn), scam warnings. The Additional Comments has a lot of info. Some is benefits, some is eligibility/transfer info. The transfer info and eligibility requirements are not benefits per se, but additional conditions. Should I include them? The rules say "Preserve ALL substantive information". The transfer eligibility, Medicare/Medicaid requirement, PSLF, long term leave, reasonable accommodation are substantive. But they don't fit neatly into Benefits. Could