Director, IT Systems and Governance

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. We need to preserve all substantive information. Include sections only when posting has real, specific content for it. So we need to decide which sections have content. From posting: - About the role: The first paragraph describes role: "BBCH Support Services, LLC is seeking a motivated and detail‑oriented Director, IT Systems and Governance to support technology governance, compliance, and systems coordination across BBCH and its subsidiaries. This role focuses on maintaining IT governance structures, supporting Federal Government compliance requirements, coordinating MSP activities, and assisting with IT operational initiatives." That's about the role. So we can have

About the role

with that paragraph. - Responsibilities: The "Essential Duties & Responsibilities" section includes sub-sections: IT Governance & Compliance, MSP & Vendor Coordination, IT Systems Support & Project Coordination, Steering Committee Facilitation, Security & Risk Support. We need to list duties as

• . Should we keep subheadings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings inside? Probably we should not add extra headings beyond those allowed? It says use

  for section headings (list). It doesn't say we cannot use other headings, but to be safe we can just put responsibilities as a

  directly under

  Responsibilities

  . We'll list each duty as a bullet. - Requirements: The posting has "Minimum Qualifications" and "Additional Qualifying Factors" and "Necessary Physical Requirements" and "Working Conditions". Those could be considered Requirements. We need to decide if we have enough content for a Requirements section. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can have a Requirements section that aggregates the qualifications, physical requirements, working conditions, etc. But we also have Qualifications and Skills sections possible. The instruction lists possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have qualifications: Bachelor's degree, 3-5 years experience, demonstrated experience with NIST, CMMC, MSP coordination, strong communication, etc. That's qualifications. We have skills: maybe "Strong communication, documentation, and cross‑functional collaboration skills." Could be skills. We have Benefits: described: "BBCH Support Services, LLC offers a great benefits package complete with medical, dental, and vision insurance, health savings account health reimbursement account, flexible spending account, employer paid life and disability, 401(k) matching, and paid time off along with other essential benefits." We have Pay: "Salary Range: $130,000-$165,000/annual" We have Schedule: Not explicitly mentioned. There's no schedule info (full-time, part-time, hours). So we should NOT create a Schedule section because no specific content. We also have "About Bristol Bay Construction Holdings LLC" which is company description. Could be part of About the role? Or maybe we could have an "About the company" but not in allowed headings. Since only allowed headings list, we could incorporate that into About the role or maybe omit? The instruction: "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." It doesn't forbid other headings besides the list, but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but we could still use other headings? However to be safe, we should stick to those headings. So we need to fit company description somewhere. Could be part of About the role (maybe a brief description). Or we could create an "About the role" that includes both role description and company overview. That seems okay. We must not include boilerplate like EEO, E-Verify, drug-free workplace, etc. Remove those. We must not include application instructions. We must preserve all substantive information: So we need to include all duties, qualifications, benefits, pay, etc. We need to avoid filler like "commensurate with experience", "not specified", etc. Not present. We need to output only HTML fragment, no /, no markdown fences. Thus final HTML:

  About the role

  BBCH Support Services, LLC is seeking a motivated and detail‑oriented Director, IT Systems and Governance to support technology governance, compliance, and systems coordination across BBCH and its subsidiaries. This role focuses on maintaining IT governance structures, supporting Federal Government compliance requirements, coordinating MSP activities, and assisting with IT operational initiatives. BBCH Support Services, LLC is a holding company of Bristol Bay Native Corporation, an Alaska Native Corporation. The BBCH family of companies include 8(a), small, and large businesses operating under the Aerostar, CCI, CSI, Herman, and SES brands. The vision of BBCH is to be best value companies and employers of choice, recognized for our dedication to our unity of purpose, values, employees, clients, and shareholders. For three decades, our best-value companies have provided federal and commercial clients with superior quality and cost-effective, innovative, and sustainable solutions for general construction, restoration services, civil works, fuels systems, environmental services, professional services, and facility support services.

  Responsibilities

  • Maintain and enhance IT governance frameworks, policies, and procedures across BBCH and its subsidiaries.
  • Lead compliance activities for Federal Government security requirements, including NIST SP 800‑171, CMMC Level 1, and CMMC Level 2.
  • Coordinate evidence collection, documentation updates, and readiness activities for ongoing compliance.
  • Conduct risk assessments, strengthen vendor governance practices, and monitor the organization’s security posture.
  • Serve as the primary point of coordination with Managed Service Providers (MSPs) and technology vendors.
  • Track service delivery, escalate issues, and ensure alignment with organizational needs.
  • Evaluate MSP contracts and vendor performance in collaboration with leadership.
  • Plan and coordinate IT operational projects, including system upgrades, deployments, and process improvements.
  • Work closely with MSPs and internal stakeholders to ensure smooth execution of IT initiatives.
  • Oversee IT systems activities such as asset management, access control coordination, and system documentation.
  • Facilitate the IT Steering Committee by preparing agendas, organizing materials, documenting decisions, and coordinating follow‑up actions.
  • Ensure discussions remain aligned with governance, compliance, and organizational priorities.
  • Collaborate with the executive sponsor or leadership, who will chair the committee and lead strategic decision‑making.
  • Provide governance insights and compliance updates to support informed decision‑making.
  • Implement cybersecurity controls and monitoring activities in coordination with MSPs and internal stakeholders.
  • Assist with incident response coordination and documentation.
  • Develop and maintain business continuity and disaster recovery planning materials in partnership with leadership, MSPs, and internal stakeholders.

  Qualifications

  • Bachelor’s degree in Information Technology, Cybersecurity, Business Administration, or a related field.
  • 3–5 years of experience in cybersecurity governance, risk, and compliance (GRC).
  • Demonstrated experience successfully guiding or consulting organizations through NIST SP 800‑171 and CMMC readiness, implementation, evidence collection, assessment preparation, and remediation activities.
  • Experience coordinating MSP activities or working within an MSP environment.
  • Strong communication, documentation, and cross‑functional collaboration skills.
  • Willingness to grow into broader IT operational responsibilities.

  Skills

  Strong communication, documentation, and cross‑functional collaboration skills.

  But note we already listed communication etc in qualifications; skills could be redundant. Maybe we should not duplicate. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine qualifications and skills into one Qualifications section. But we have separate headings allowed; we could keep Qualifications and maybe not Skills if it's thin. However we have skills content: "Strong communication, documentation, and cross‑functional collaboration skills." That's already in qualifications. Could be considered part of qualifications. So we could omit Skills section to avoid thin section. Benefits: we have description. Pay: we have salary range. Schedule: none, so omit. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Check if we need Requirements: we have qualifications; maybe we could rename Qualifications to Requirements? But the instruction list includes both Requirements and Qualifications as separate. We have qualifications content; we could treat that as Qualifications. Requirements could be things like physical requirements, working conditions, etc. But we have those: "Necessary Physical Requirements" and "Working Conditions". Those are substantive. Could we put them under Requirements? The instruction says include a section ONLY when posting has real, specific content for it. We have physical requirements and working conditions. So we could have a Requirements section that includes those. But we also have qualifications. So we could have both Requirements and Qualifications sections. Let's extract physical requirements and working conditions: Necessary Physical Requirements: - Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. - Essential and marginal functions may require maintaining physical condition necessary for bending, stooping, sitting, walking, or standing for prolonged periods of time; most of time is spent sitting in a comfortable position with frequent opportunity to move about. - Work is mostly performed from a sedentary posture. - The employee is regularly required to hear, talk, sit, and use hands and fingers to operate a keyboard and phone. - The employee may be occasionally required to reach with hands and arms and lift, handle, or move objects weighing up to 40 pounds. - Specific vision abilities required by this job include close vision, distance vision, peripheral vision, and the ability to adjust vision. Working Conditions: - The job is performed in an office setting with exposure to computer screens and requires extensive use of a computer, keyboard, mouse, and multi-line telephone system. - The work described herein is primarily in a modern office setting. - Occasional travel may be required. We should include these as bullet list under Requirements. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We must not include fluff like "Reasonable accommodations may be made..." that's substantive. Now ensure we removed boilerplate: EEO, E-Verify, drug-free workplace, etc. Also removed "Additional Qualifying Factors" (pre-employment drug screening, background check, clearance). Those are substantive? They are about hiring conditions. Should we include them? They are part of qualifications? The posting includes: "As a condition of employment, you will be required to pass a pre-employment drug screening (post accepted offer) and have acceptable background check results. If applicable to the contract, you must also obtain the appropriate clearance levels required and be able to obtain access to military installations." That's substantive info about requirements. Should we include that under Requirements or Qualifications? It's a condition of employment. Could be part of Requirements. We'll include it under Requirements as