Director of Operations

We need to output HTML fragment with sections: About the role? The posting includes Position Summary, Key Responsibilities, Qualifications (Required, Preferred), Core Competencies, Working Conditions & Physical Demands, Success Measures maybe. Also includes Delegation Map, etc. We must use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should only include sections when posting has real specific content. No Pay, Schedule, Benefits mentioned. So we can include sections: About the role (maybe Position Summary), Responsibilities (Key Responsibilities), Qualifications (Required and Preferred), Skills (Core Competencies), Working Conditions (Working Conditions & Physical Demands). Also maybe Success Measures could be part of Responsibilities or separate? Could be a section like "Success Measures". But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. But we can also include other headings if needed? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can use those headings. It also says "include a section ONLY when the posting has real, specific content for it". So we need to map content to those headings. We have Position Summary -> About the role. Key Responsibilities -> Responsibilities. Qualifications -> Qualifications (we can split Required and Preferred maybe as subpoints but still under Qualifications). Core Competencies -> Skills. Working Conditions & Physical Demands -> maybe we could put under Requirements? But Requirements is a heading example. Could use Requirements for qualifications? Actually they separate Qualifications and Requirements. Usually Requirements = qualifications. But we already have Qualifications. Could use Requirements for something else like "Experience" etc. But we have no separate Requirements section besides qualifications. Could combine Qualifications and Requirements? But we need to follow instruction: use those headings; we can omit headings if no content. So we can have About the role, Responsibilities, Qualifications, Skills, Working Conditions (maybe not in list but we could treat as Requirements? Not sure). The list includes Benefits, Pay, Schedule which we don't have. So we omit those. We could also include a section "Success Measures" but not in the list; maybe we can incorporate into Responsibilities or About the role. Better to add as a separate section with heading "Success Measures" but that's not in the examples; but instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Likely they expect only those headings. So we should not create Success Measures heading. We can embed success measures within Responsibilities or About the role. Thus sections: About the role (Position Summary), Responsibilities (Key Responsibilities + Success Measures maybe), Qualifications (Required and Preferred), Skills (Core Competencies), Working Conditions (Working Conditions & Physical Demands). Also maybe Requirements? Could treat Qualifications as Requirements? But we already have Qualifications. Could omit Requirements. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we need to break into bullet points. The responsibilities are long paragraphs; we can split into logical bullet points: Scope of Responsibility (four pillars), Operating Rhythm and Execution, Logistics and Supply Chain, Site Operations, Health, Safety, Security, and Compliance, IT and Information Security, Leadership and Organizational Build, Delegation Map (maybe not needed). We'll produce bullet points. For Qualifications: Required Qualifications bullet list, Preferred Qualifications bullet list. For Skills: Core Competencies bullet list. For Working Conditions: maybe a paragraph. We must preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting didn't have those at end except maybe "This job description reflects the general nature..." that's boilerplate but maybe we should keep? It's generic but not EEO. It's part of job description; we can keep as it's substantive? It's a disclaimer; maybe we can drop as boilerplate? It's not EEO but it's a generic statement. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This line is not those; it's a generic disclaimer about job description. Might be okay to keep. But we can keep as a paragraph under Working Conditions maybe. We must output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

  About the role

  Position Summary ...

  Responsibilities

  • Scope of Responsibility: direct ownership of four functional pillars: Logistics/Supply Chain, Site Operations, Health, Safety, and Security, IT/InfoSec (coordination-only). Finance/Accounting adjacent but not owned; maintain interface.
  • Operating Rhythm and Execution: own daily, weekly, monthly operating cadence; decision-maker for day-to-day trade-offs; translate 1‑year plan into weekly/monthly objectives with owners, dates, measurable criteria; maintain current operational picture and report to Head of Operations; ensure consistency of process and standards across departments.
  • Logistics and Supply Chain: order management and customer service; direct purchasing, buying, procurement (vendor qualification, negotiation, performance); oversee inbound/outbound shipping; ensure customs, trade, import/export compliance; own inventory control end‑to‑end (receiving, storage, cycle counting, accuracy); direct production planning and scheduling aligning material availability to demand.
  • Site Operations: manage physical campus, coordinate/oversee contractors and trades; oversee capital improvements and construction with site/development managers; own condition/availability of roads, bridges, buildings, grounds, systems, equipment; ensure land compliance per Legal guidance; direct site maintenance programs (preventive, corrective, emergent); provide operational support to Production; maintain qualified on‑site/near‑site presence for DCMA response.
  • Health, Safety, Security, and Compliance: own physical/site security posture (access control, gate ops, cameras, comms, incident response); direct general site safety (medical/emergency readiness); own process and facilities safety programs; ensure and evidence regulatory compliance across ATF, OSHA, DCMA, DSCA, ESSP, SSP and successors; own safety/compliance training, records, audit readiness; serve as campus point of accountability during regulatory inspections/audits.
  • IT and Information Security: own campus IT operations and business systems (ERP/MRP selection, implementation, optimization); direct technology infrastructure supporting site operations (cameras, comms, networking) in coordination with Physical Security; own CMMC compliance posture (assessment readiness, evidence collection, POA&M management, certification maintenance); direct information security across IT and OT (access mgmt, incident response, OT/ICS cyber protections); ensure IT/InfoSec requirements from DoD contracts (DFARS 252.204-7012, NIST SP 800-171) are met and evidenced; manage IT vendors, service providers, licensing; build IT/InfoSec function from current unsettled state (finalizing staffing model for IT/Compliance Manager and CISSP/OT Cyber Specialist).
  • Leadership and Organizational Build: develop and retain Phase 1 functional team and scale through later phases; establish clear roles, responsibilities, decision rights; set and hold culture standard per CMG’s Vision, Mission, Core Values; build bench strength and succession depth to avoid single points of failure.
  • Delegation Map – what transfers from Head of Operations: daily/weekly/monthly Ops execution and cadence; procurement, inventory, logistics execution; contractor management and site maintenance; safety/security program execution and audit readiness; IT/InfoSec operations, CMMC posture, OT cyber; day‑to‑day vendor/contractor relationships – all transferred and fully supported by Head of Operations. 1/3/10‑year operational planning, RMSL integration, external B2B/B2G partnership development, cross‑site consistency, Vision/Mission/Core Values standard‑setting remain with Head of Operations (Director contributes input, executes campus‑side tasks, enforces at campus level).
  • Success Measures: First 30 Days – complete assessment of four pillars, assume ownership of campus operating cadence, meet every direct report, key contractor, critical vendor. First 90 Days – operating rhythm runs independently of Head of Operations; compliance gaps (ATF, OSHA, DCMA, DSCA, ESSP, SSP, CMMC) documented with remediation plans and owners. First 12 Months – Phase 1 headcount hired and productive across all pillars; documented repeatable processes for each pillar; zero material compliance findings; safety program operating to standard; CMMC certification path on track; ERP/MRP implemented or under active implementation; inventory accuracy, on‑time shipping, site availability metrics established and trending to target; Head of Operations time allocation shifted toward strategic work.

  Qualifications

  Required Qualifications

  • Bachelor’s degree in Operations Management, Engineering, Business, Supply Chain, or related field; equivalent experience considered.
  • Minimum 8–10 years of progressive operations leadership, including at least 3 years with direct P&L or multi‑function operational ownership.
  • Demonstrated experience leading multiple dissimilar functions simultaneously (e.g., supply chain, facilities, safety), not deep expertise in a single vertical.
  • Proven track record in a regulated manufacturing or industrial environment with substantive compliance obligations.
  • Direct experience with inventory control, procurement, and production scheduling.
  • Experience hiring and building teams from a small base.
  • Ability to obtain and maintain a U.S. security clearance; U.S. person status as required by ITAR/EAR.
  • Willingness to reside within commuting distance of the Ballinger Campus.

  Preferred Qualifications

  • Experience in defense manufacturing or as a DoD supplier, with working familiarity with DCMA, DSCA, and DFARS requirements.
  • Experience with ATF‑regulated operations and explosives or energetics safety frameworks (ESSP, SSP).
  • Greenfield or brownfield site buildout experience – standing up operations where processes do not yet exist.
  • ERP/MRP implementation or optimization experience.
  • Familiarity with CMMC, NIST SP 800‑171, and DFARS cybersecurity flow‑down requirements.
  • Exposure to OT/ICS cybersecurity in a production environment.
  • Formal continuous improvement credentials (Lean, Six Sigma, or equivalent).
  • Prior military logistics, engineering, or installation‑management leadership.
  • Experience supporting an acquisition integration.

  Skills

  • Bias for execution; closes loops; distinguishes activity from progress.
  • Comfort with ambiguity; builds the process rather than waiting to be handed one.
  • Range over depth; credible across supply chain, facilities, safety, and IT without needing to be the technical expert in any one discipline.
  • Safety/Compliance discipline;