Scrum Master - Senior

We need to output HTML fragment with sections: headings

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting and decide which sections to include. We have content: - Purpose and Impact: description about role, mission, etc. Could be "About the role" or "Purpose and Impact". According to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map "Purpose and Impact" to "About the role". Provide prose. - Work Schedule: "8 Hours per day, Monday thru Friday". That's schedule. So we need a Schedule section. - Essential Responsibilities: list of duties. So Responsibilities section with

  • . - Work Environment, Physical Demands, and Mental Demands: maybe part of Responsibilities? Could be separate but not in allowed headings. Could be part of About the role or Responsibilities. Probably include as part of Responsibilities or About the role. Since we prefer few substantive sections, we can incorporate into Responsibilities as additional bullet? But it's not a duty; it's environment. Could be part of About the role. We'll decide later. - Minimum Requirements (Knowledge, Skills, And Abilities): list of requirements. That's Requirements section. - Minimum Education: duplicate of Minimum Requirements? Actually there is a separate Minimum Education line after Minimum Requirements. It repeats Bachelor's degree etc. Also Minimum Years of Experience repeats. So we need to deduplicate. - Preferred Certifications and Qualifications: could be Qualifications section. - Benefits Overview: list of benefits. So Benefits section. - Compensation Details: Pay range $160,000 - $190,000. So Pay section. - Other Responsibilities: Safety, Quality, Procedure Compliance: these are generic boilerplate; might be considered EEO/legal boilerplate? They are about company policies. Might be considered boilerplate; we should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. These are internal policies but could be considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Other Responsibilities" includes Safety, Quality, Procedure Compliance. This seems like generic company policy, not specific to the role. Likely should be removed as boilerplate. - Qualified applicants will receive consideration... EEO statement: remove. - Compensation Details: we have Pay. - Benefits Overview: Benefits. - Original Posting date etc: minor metadata; we can drop or put in short p. - Amentum anticipates this job requisition will remain open... timeline: minor metadata; drop. - Amentum is proud to be an Equal Opportunity Employer...: EEO boilerplate; remove. Thus sections: About the role (Purpose and Impact), Responsibilities (Essential Responsibilities + Work Environment etc?), Requirements (Minimum Requirements), Qualifications (Preferred Certifications and Qualifications), Benefits, Pay, Schedule. We need to ensure we don't create sections with filler. All have real content. We must not repeat job title as heading. Not include Job ID. We must use

    for section headings. Use

    • for any list of duties/requirements/benefits, and

      for prose. Thus:

      About the role

      ... purpose and impact text ... maybe also include work environment? We'll decide. Better to keep About the role as purpose and impact paragraph. Then Responsibilities: list of essential responsibilities (the bullet list). Also include Work Environment etc as maybe a bullet? But it's not a duty; it's environment. Could be included as a paragraph under Responsibilities? But we need to use

      • for any list of duties/requirements/benefits. Work environment is not a list; could be a

        . We'll add a

        after the list. Requirements: list of minimum requirements (knowledge, skills, abilities). Use

        • . Qualifications: list of preferred certifications and qualifications. Use
          • . Benefits: list of benefits. Use
            • . Pay:

              with salary range. Schedule:

              with work schedule. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the sections. Let's extract the purpose and impact text: "Purpose and Impact: Are you ready to apply your leadership to shape the Cyber, Security, & Intel landscape? Amentum is seeking a Senior Scrum Master to join our team of mission-driven professionals at Fort Meade, MD. In this role, you will lead challenging, high-visibility projects that directly impact the Nation’s defense and intelligence missions. Supporting DISA, Amentum’s Intel and Cyber Division is expanding a proven team of highly skilled engineers and architects to design, deploy, and sustain an innovative IT enterprise solution. As the Scrum Master, you will serve as the critical catalyst for this team, removing obstacles, driving agile delivery, and ensuring seamless execution across complex project lifecycles. Our team delivers secure, mission-critical capabilities where system integrity and rapid deployment are paramount. We are seeking a Senior Scrum Master who combines meticulous organizational discipline with strategic foresight. In this role, you will lead efforts to establish and maintain highly efficient agile execution in a rapidly evolving operational environment. Success requires the ability to navigate complex, cross-functional dependencies independently while fostering collaborative solutions across integrated engineering teams. To excel, you must possess a proactive leadership mindset and the agility to rapidly master and govern the delivery of next-generation systems and services." That's the purpose and impact. We'll put that in

              . Now Responsibilities: The "Essential Responsibilities:" list includes many items. Let's capture them exactly as bullet points. List: - Drive end-to-end project execution using a hybrid project management methodology, leveraging predictive processes for high-level planning and iterative Agile processes for technical execution. - Facilitate Scaled Agile Framework (SAFe) ceremonies at the team and program levels, including Daily Scrums, Sprint Planning, Backlog Refinement, Sprint Reviews, Retrospectives, and Program Increment (PI) Planning. - Partner directly with the Government PMO and Amentum leadership to deliver formal status reports, manage the Integrated Master Schedule (IMS), and present project performance metrics. - Establish and maintain project governance artifacts, including comprehensive risk, action item, issues, and decisions (RAID) logs, and actively brief mitigation strategies to stakeholders. - Serve as the primary shield for the engineering team, proactively identifying, tracking, and removing technical and administrative impediments to maintain high team velocity and focus. - Performance management - Track, analyze, and report team performance metrics (such as velocity, burn-up/burn-down charts, cumulative flow, and SLA compliance) to drive continuous improvement. - Translate complex engineering milestones into structured, trackable sprint epics, features, and user stories within Jira/Confluence. - Collaborate with Product Owners, System Engineers, and Site Leads to manage and prioritize the team's backlog, ensuring clear acceptance criteria and definition of "Done." - Coordinate cross-functional project schedules and dependencies with external contractors, site teams (such as Fort Meade operations), and third-party independent test agencies (e.g., JITC). - Conduct post-project reviews and lessons-learned sessions to identify process bottlenecks. - Implement continuous process improvements to optimize delivery speed and quality. - Establish team operating agreements and responsibility matrices (RACI), coaching team members on SAFe principles, hybrid delivery expectations, and program-level standards. - Lead project readiness reviews, manage authorized service interruptions (ASIs) scheduling, and assist in the creation of site deployment schedules and project checklists. We need to preserve all. Also there is a line "Work Environment, Physical Demands, and Mental Demands: Employee will work in a SCIF on a daily basis. Employee may also be required to work in a datacenter environment for specified periods of time." This is not under Essential Responsibilities but separate. We could add as a paragraph after the list. Now Requirements: Minimum Requirements (Knowledge, Skills, And Abilities) list: - Fifteen (15) years of experience in IT project management, systems engineering, or technical program execution supporting large-scale enterprise deployments - Seven (7) years of dedicated experience managing projects/programs using hybrid methodologies (predictive planning paired with iterative execution), with at least three (3) years in a senior Scrum Master or Project Manager leadership role. - Bachelor’s degree in Business Administration, Information Technology (IT), Project Management, Systems Engineering, or a related field. - Proven experience implementing Scaled Agile Framework (SAFe) principles, facilitating Program Increment (PI) Planning, and managing Agile Release Trains (ARTs). - Demonstrated experience directly interfacing with Government stakeholders (e.g., DISA PMs, Product Owner, Lead Engineer, ISSM, etc.) to deliver status reports, manage expectations, and coordinate program reviews. - Extensive background in predictive project scheduling, including developing and maintaining an Integrated Master Schedule (IMS), tracking milestones, and utilizing project management tools (such as MS Project). - Expert-level proficiency in Jira and Confluence for managing Agile backlogs, creating custom workflows, and tracking team velocity, burn-down metrics, and sprint health. - Strong expertise in risk management, with proven experience establishing and maintaining RAID logs (Risks, Action Items, Issues, and Decisions) for high-visibility IT programs. - Excellent communication, facilitation, and leadership skills, with a track record of resolving cross-team conflicts, removing organizational impediments, and driving collaborative solutions. - Ability to support non-standard hours, including scheduled maintenance windows, deployment surges, and emergency planning sessions. - Ability to travel up to 10%. - Security Clearance Required: Must have active Top Secret clearance with SCI eligibility Also there is Minimum Education line: "Minimum Education: Bachelor’s degree in Computer Science, Information Technology (IT), Systems Engineering, or related technical field. Additional years of experience can substitute for degree." This duplicates some but adds Computer Science focus. We need to preserve all substantive info, not duplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to deduplicate overlapping content. The Minimum Requirements list includes Bachelor’s degree in Business Administration, IT, Project Management, Systems Engineering, or a related field. Minimum Education says Bachelor’s degree in Computer Science, IT, Systems Engineering, or related technical field. Additional years of experience can substitute for degree. So we need to combine? We could keep both but note they are similar; but they are not identical; one includes Business Administration, Project Management; the other includes Computer Science and says experience can substitute. Both are substantive. We should not remove either unless they are exact duplicates. They are not exact duplicates, so we keep both. However we need to avoid duplication of same sentence. We'll keep both as separate bullet points? But they are both education requirements. Could combine into one bullet that mentions both? But that would