Software Delivery Lead

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the job posting. Key sections: - About the role: description of role: "The Director of Software Delivery is a critical member of Guidehouse’s senior program leadership team and reports to Program Management. Guidehouse is looking for a Director of Software Delivery to join our team. Guidehouse is responsible for building and expanding a shared service platform of over 1500 federal grant programs demonstrating a new model of how agencies and departments across the Federal Government work together to eliminate duplication of services and leverage resources and technology." We can put that under About the role. - Responsibilities: "What You Will Do" list: bullet points. - Requirements: "What You Will Need" list. - Qualifications: maybe same as Requirements? But we need to decide. The posting includes "What You Will Need" which includes many items. Could treat as Requirements. Also there is "What Would Be Nice To Have" which could be Skills or Qualifications? Usually "Nice to have" could be Skills. But we have separate sections: Skills, Qualifications. We need to decide mapping. We have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if content exists. We have: - About the role: yes. - Responsibilities: yes (What You Will Do). - Requirements: yes (What You Will Need). Could be Requirements. - Qualifications: maybe we could put education or certifications? Not explicit. There's mention of PMP Certification under nice to have. Could treat that as Qualifications? But we have Skills also. - Skills: maybe we can put technical skills: Agile, CMMI, etc. But those are in Requirements. Could separate: Requirements = experience, Qualifications = education/certifications, Skills = technical competencies. But we must not invent content. We must only include sections if posting has real specific content for them. If we split content arbitrarily, we might be creating sections with content that is indeed present but we need to ensure we don't misrepresent. Better approach: Use the headings that match the sections in the posting: About the role (intro), Responsibilities (What You Will Do), Requirements (What You Will Need), Skills (What Would Be Nice To Have), Benefits (What We Offer), Pay (salary range). Schedule: not mentioned (travel up to 10% maybe schedule? Travel required up to 10% could be considered travel requirement, not schedule. No explicit schedule like full-time, part-time, etc. So we should not create Schedule section because no specific content. Qualifications: maybe we can treat "Must be able to obtain and maintain a Federal or DoD 'public trust'" as a qualification. Also "Mastered the range of full life cycle project management" etc. But those are in Requirements. Could still put under Qualifications. But we need to avoid duplication. Perhaps we can map: - About the role: intro paragraph. - Responsibilities: bullet list from "What You Will Do". - Requirements: bullet list from "What You Will Need" (the mandatory requirements). - Qualifications: bullet list from "Must be able to obtain and maintain a Federal or DoD 'public trust'" plus maybe "PMP Certification" (nice to have) but that's nice to have. Actually PMP is nice to have, not required. Could still be qualification but it's nice to have. Might be better to put under Skills. - Skills: bullet list from "What Would Be Nice To Have". - Benefits: bullet list from "What We Offer" (benefits list). - Pay: paragraph with salary range. - Schedule: not present, so omit. We must not include sections with filler like "commensurate with experience". We have salary range specific. Now we need to output HTML fragment: use

for each section heading, then content:

for prose,

• for lists. We must not include any extra markup like or . Just the fragment. We must preserve all substantive information: ensure we don't lose any details. Let's extract content precisely. Intro (About the role): "The Director of Software Delivery is a critical member of Guidehouse’s senior program leadership team and reports to Program Management. Guidehouse is looking for a Director of Software Delivery to join our team. Guidehouse is responsible for building and expanding a shared service platform of over 1500 federal grant programs demonstrating a new model of how agencies and departments across the Federal Government work together to eliminate duplication of services and leverage resources and technology." That's the prose. Responsibilities (What You Will Do) list: - Technical and project leadership to the software development and Government customer teams, including multiple scrum teams and subcontractors. - Plans and oversees the execution of multiple simultaneous software development projects from requirements gathering to production release. - Collaborates cross organizationally (e.g. operations, customer care) to ensure the successful launch and user adoption of software releases. - Collaborates with key customer and user community representatives including Government teams to prioritize work and establish release plans. - Oversees the sustainment of software products in production. - Assumes key role in the reporting of software development status to executive management and Government customer. - Utilize metrics (e.g. defect rate, cost/schedule vs plan (EVM)) to report performance and drive process improvements in a CMMI Level 3 assessed organization. - Leads employee development and performance management through subordinate managers and direct reports, including setting clear expectations, providing timely coaching and feedback, recognizing strong performance, addressing performance issues, and supporting individualized development plans. - Partners with program and functional leaders on workforce planning, staffing, succession planning, retention, and skills development to ensure teams have the capacity and capabilities needed to meet current and future delivery commitments. - Develops subordinate managers and team leads by delegating decision-making authority, strengthening leadership capabilities, promoting collaboration across teams, and holding leaders accountable for employee engagement and delivery outcomes. - Works cross functionality to assess business requirements in support of future technology needs and requirements. Check punctuation: some start with verb, some not. We'll keep as is. Requirements (What You Will Need) list: - Delivered and supported large-scale Enterprise-wide software-based systems including a full range of support services (account management, consulting, help desk, analysis). - Understanding and applied knowledge of Agile software development on large scale project deliveries. - Experience leading and applying process improvement and change through quality management frameworks such as CMMI. - Worked extensively in the Federal contracting space – at least 12 years of experience with 5 years of progressively responsible management positions. - Demonstrated a strong understanding of Government contracts and business operations – having had budget management with profit/loss responsibility. - Managed integrated teams of employees and subcontractors involving more than 50+ individuals in multiple geographic locations. This includes multiple, simultaneous scrum teams. - Displayed a collaborative leadership style while directing multiple team leaders? Actually original: "Displayed a collaborative leadership style while directing multiple team leaders/managers on a complex and dynamic program with broad scope." - Demonstrated strong people management skills, including coaching and mentoring, career development, performance management, succession planning, employee engagement, and building an inclusive, accountable, and high-performing culture. - Mastered the range of full life cycle project management from developing plans through successful execution to closeout. - Worked effectively with customer leadership in an ‘embedded’ setting. - Demonstrated exceptional written and verbal communication skills. - Executed programs with mission critical information security policies and regulations. - Must be able to obtain and maintain a Federal or DoD "public trust"; candidates must obtain approved adjudication of their public trust prior to onboarding with Guidehouse. Candidates with an active public trust or suitability are preferred. Note: The last bullet includes the public trust requirement. Might be better to put under Qualifications. But we can keep it in Requirements; it's still a requirement. Qualifications: maybe we can separate out education? Not present. Could put "Must be able to obtain and maintain a Federal or DoD 'public trust'" as qualification. But we already have it in Requirements. To avoid duplication, maybe we move it to Qualifications and keep Requirements without that line. However the instruction: preserve ALL substantive information; do not invent or summarize away detail. If we move it, we still preserve it, just in a different section. That's okay as long as we don't lose it. But we need to ensure we don't duplicate. Let's think: The posting has a section "What You Will Need" which includes many items, ending with the public trust requirement. There's no separate "Qualifications" heading. But we are allowed to create a Qualifications section if we have substantive content. The public trust requirement is substantive. So we could put it there. However we also have other items like "Mastered the range of full life cycle project management" etc. Those are also qualifications. But they are already in Requirements. If we split, we risk losing some content if we don't duplicate. Better to keep Requirements as the full list, and not create Qualifications unless we have distinct content not covered elsewhere. Since we don't have separate qualifications like degree, certification, etc., we could omit Qualifications section. But we have PMP Certification under nice to have, which could be Skills. So we may omit Qualifications. But the instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role, Responsibilities, Requirements, Skills, Benefits, Pay. That's six sections. That's fine. Now Skills: from "What Would Be Nice To Have" list: - Prior experience serving as a senior technical leader on a large Federal IT contract ($100M+) - Experience supporting Federal grants systems or large transactional government platforms - Experience with Earned value management - PMP Certification - Local to Washington DC metro-area - Experience supporting mission‑critical systems in a highly regulated environment - Experience operating in matrixed organizations and partnering across internal practices and corporate functions We should keep as bullet list. Benefits: from "What We Offer" list: - Medical, Rx, Dental & Vision Insurance - Personal and Family Sick Time & Company Paid Holidays - Parental Leave - 401(k) Retirement Plan - Group Term Life and Travel Assistance - Voluntary Life and AD&D Insurance - Health Savings Account, Health Care & Dependent Care Flexible Spending Accounts - Transit and Parking Commuter Benefits - Short-Term & Long-Term Disability - Tuition Reimbursement, Personal Development, Certifications & Learning Opportunities - Employee Referral Program - Corporate Sponsored Events & Community Outreach - Care.com annual membership - Employee Assistance Program - Supplemental Benefits via Corestream (Critical Care, Hospital Indemnity, Accident Insurance, Legal Assistance and ID theft protection, etc.) - Position may be eligible for a discretionary variable incentive bonus We need to preserve all. Also note the sentence: "Guidehouse offers a comprehensive, total rewards package that includes competitive compensation and a flexible benefits package that reflects our commitment to creating a diverse and supportive workplace." That's prose before the list. Could include as

  before the

  . Pay: The annual salary range: "$155,000.00-$259,000.00." plus sentence: "Compensation decisions depend on a wide range of factors, including but not limited to skill sets, experience and training, security clearances, licensure and certifications, and other business and organizational needs." We'll include as

  . Schedule: Not present, omit. Now we need to output HTML fragment with

  headings. We must not include markdown code fences. Let's craft. Structure:

  About the role

  ...intro...

  Responsibilities

  • ...