Director, Integrated Program Management

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs before "Responsibilities". We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We have content for About the role (intro paragraphs). Responsibilities (list). Qualifications (list). Requirements? The posting has "Qualifications You Must Have" and "Qualifications We Prefer". Also there is "Essential Functions". Also "Financial, Contractual & Operational Process Support". Also "Continuous Improvement & Industry Awareness". Also "Team Leadership & Stakeholder Engagement". Also "Program Execution Excellence & EVMS Readiness". Also "Program & Business Area Leadership". Many subheadings. We need to map to required headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have those headings. We must not repeat job title as heading. We must not put Job ID etc. We need to preserve all substantive information. So we need to extract content and place under appropriate headings. We have: - About the role: initial paragraphs describing role: "As Director, Integrated Program Management, you'll be responsible for sharing your program management experience, skills, and best practices and providing business area leadership for program management processes, tools, and training in partnership with corporate program process oversight and compliance teams. This role is the accountable representative of the business area to drive program strategic plans and direction, leading change efforts, and focusing and motivating Program Managers to achieve established goals. This role will provide support, training, guidance, structure, and leadership to the business area Program Management community with the objective of influencing and improving Program Planning & Execution. The Mission Solutions and Technologies (MST) business area provides affordable, turn-key command/control, communications, integrated ISR, force protection and security solutions worldwide. The MST team has a long legacy of supporting the Department of Defense, Department of Homeland Security, commercial and international customers with years of experience in platform operations, engineering and full lifecycle management across domains – air, land, sea, space and cyber." We can put that under

About the role

with

paragraphs. - Responsibilities: The posting has a "Responsibilities" heading then bullet-like paragraphs (not bullet list but sentences). We need to convert to

• . The content includes multiple responsibilities grouped under subheadings: Program & Business Area Leadership, Program Execution Excellence & EVMS Readiness, Team Leadership & Stakeholder Engagement, Continuous Improvement & Industry Awareness, Financial, Contractual & Operational Process Support. We need to capture all responsibilities as list items. Probably each bullet point is a sentence. We'll extract each distinct responsibility. Let's parse responsibilities section: "Responsibilities Program & Business Area Leadership Own BA program management processes: standardized PMO templates, gate reviews, and program tiering aligned with enterprise policy. Own BA program management tools, analytics, and automated reporting, including agentic workflow automation, that complement Corporate certified business systems; ensure program data integrity and readiness for CFO-owned EVMS and Pricing & Estimating. Oversee BA risk and opportunity management: review program risk and opportunity registers as required, ensure programs apply risk management in accordance with company policies and procedures, and ensure risks and opportunities are integrated with schedule and cost baselines. Serve as the two-way link between Corporate IPM, BA executive leadership, and BA programs: translate enterprise policy and priorities into BA practice, escalate program and BA needs, barriers, and improvement ideas to Corporate. Align BA program management priorities with corporate strategy and ensure timely, value‑added outcomes. Maintain a strong communication cadence across the BA, ensuring decisions and initiatives reflect senior leadership direction. Program Execution Excellence & EVMS Readiness Enable BA program execution by providing standard processes, tools, templates, and training programs that need to plan and execute costs, schedule, and technical objectives. Ensure BA programs have the processes, tools, and training needed to meet EVMS system description and DFARS/CAS requirements (baselining, variance analysis, EAC/ETC), in partnership with the CFO-owned EVMS organization. Support program readiness for EVMS reviews (IBRs, JSRs, surveillances) and track resulting corrective actions to timely closure. Conduct periodic program compliance and health assessments against corporate policy, BA standards, and DFARS/EVMS system description requirements, covering PMPs, IMS health, risk and opportunity registers, gate-review adherence, and EVMS readiness; set the BA surveillance cadence, report findings to BA leadership, and track corrective actions to closure. Team Leadership & Stakeholder Engagement Lead and mentor Program Managers, CAMs, and IPM staff to elevate program planning rigor, execution maturity, and EVMS discipline. Build strong relationships with BA executives, program managers, functional leaders, and Corporate IPM as the go-to resource for program management process, tool, and training needs. Partner with functional leaders to ensure programs have the processes, tools, and training needed for effective resource planning, allocation, and staffing, and support PM capability development and career pathing across the BA. Continuous Improvement & Industry Awareness Identify and integrate best practices, industry trends, and innovative approaches to strengthen program execution. Lead change management initiatives tied to corporate priorities; coordinate BA training requirements and schedules with Corporate IPM and support Corporate IPM in developing training. Represent the BA in corporate forums, quarterly reviews, and project meetings (Pricing & Estimating, PMPs, Tools/Training, EVMS compliance). Financial, Contractual & Operational Process Support Ensure programs have the processes and tools to manage budgets, forecasts, and financial performance; develop proposals; and manage contract and subcontract requirements. Own BA standards and templates for program management plans (PMPs), schedules, and reporting." We'll turn each line into
• . Might need to keep subheadings? Not required but we could keep them as plain text inside li? Probably better to keep as separate li items; subheadings could be omitted but we risk losing info. However we can include subheading as part of li text (e.g., "Program & Business Area Leadership: Own BA program management processes..."). We'll produce a
  with each responsibility as
  • . - Requirements: The posting has "Qualifications You Must Have" with sub-sections: Experience & Tenure Requirements, Execution Excellence & Leadership Requirements, Business Area (BA) Accountability Requirements, Technical & Cross‑Functional Competency Requirements, Financial Capability Requirements. Also there is "Essential Functions". Also there is "Qualifications We Prefer". The instruction says we have sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We have "Qualifications You Must Have" which likely goes under Requirements (mandatory). "Qualifications We Prefer" could go under Qualifications (preferred). Skills maybe from preferred? Could also be under Skills. Benefits from benefits paragraph. Pay from salary range. Schedule maybe not present (no schedule info). So we may omit Schedule if no specific content. We need to avoid placeholder like "commensurate with experience" etc. The posting includes "Compensation varies depending on a wide array of factors..." and "SNC offers annual incentive pay based upon performance that is commensurate with the level of the position." That's placeholder? It says "commensurate with the level of the position." That's somewhat vague but still specific? It's not a number. The instruction: 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. For Pay, we have actual salary range: $210,124.21 - $288,920.79. That's specific. So we can include Pay section with that range. Also mention incentive pay etc. That's okay. Benefits: posting says "SNC offers a generous benefit package, including medical, dental, and vision plans, 401(k) with 150% match up to 6%, life insurance, 3 weeks paid time off, tuition reimbursement, and more." That's specific enough. So Benefits section. Schedule: No mention of schedule (like full-time, part-time, shift). There's "Work predominantly in an office environment, with flexibility for hybrid work arrangements as needed." That's about work arrangement, not schedule. Could be considered schedule? But likely not. The instruction: only include section if posting has real specific content. There's no explicit schedule like "Monday-Friday, 9-5". So we omit Schedule. Now Requirements: Should contain mandatory qualifications (You Must Have). We'll put that under

    Requirements

    . We'll need to preserve all details. We'll convert each bullet into
  • . The sub-sections can be included as part of li text. Qualifications: Should contain preferred qualifications (Qualifications We Prefer). Also maybe skills? But we also have Skills section. We could put preferred qualifications under Qualifications, and maybe skills under Skills (like specific tools: Microsoft Project, Deltek Cobra, Power Bi, etc). However the preferred qualifications list includes certification, experience with tools, prior IBRs, practical EVMS experience, experience driving standardization, advanced skills in assessing external competition, previous management ability, demonstrated passion, ability to grasp technical concepts, strategic mindset, understanding of FAR/DFARS/CAS, background in aerospace/defense. Those are qualifications/skills. We could split: Qualifications for certifications and experience; Skills for technical skills like Microsoft Project, Deltek Cobra, Power Bi, etc. But the instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide distribution. We have "Qualifications We Prefer" which includes certifications, experience with tools, prior IBRs, practical EVMS experience, experience driving standardization, advanced skills in assessing external competition, previous management ability, demonstrated passion, ability to grasp technical concepts, strategic mindset, understanding of FAR/DFARS/CAS, background in aerospace/defense. We also have "Skills" maybe from the "Technical & Cross‑Functional Competency Requirements" under Requirements? Actually that is under Requirements (must have). That includes "Proven expertise preparing proposals, BOEs, business cases, specifications, ROMs, and coordinating engineering, production, and support resources to meet schedule and cost objectives. Strong capability in conflict resolution, strategic thinking, communication, briefing, cross‑functional collaboration, and stakeholder alignment at the executive level. Demonstrated success in customer relationship management, including resolving complex issues, identifying requirements, and shaping new business opportunities." That's more like skills. Also "Financial Capability Requirements" under Requirements: "Financial acumen sufficient to interpret program performance data and advise BA leadership on execution decisions." Thus we could treat Requirements as mandatory qualifications (including experience, leadership, technical, financial). Qualifications as preferred qualifications (certifications, tools, etc). Skills maybe we could extract specific technical skills like Microsoft Project, Deltek Cobra, Power Bi, etc. But those are also in preferred qualifications. Could also put them under Skills. Given the instruction to prefer few substantive sections over many thin ones, we might combine Qualifications and Skills into one section? But we have to follow the headings list; we can omit sections if no content. We could put all preferred qualifications under Qualifications, and maybe not have a separate Skills section if content overlaps. However we have distinct skill statements in Requirements (Technical & Cross‑Functional Competency Requirements, Financial Capability). Those are mandatory skills. Could we move them to Skills section? But then Requirements would lose some content. Better to keep Requirements as mandatory qualifications (including experience, leadership, technical, financial). Qualifications as preferred qualifications (certifications, tools, etc). Skills maybe we could omit if no distinct