Scrum Master

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate like EEO, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. Keep substantive info. We need to parse the posting. Title: "Scrum Master Belong. Connect. Grow. with KBR!" but we ignore title. First paragraph: "KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound impact on the country’s most critical role – protecting our national security." That's about the role. Then "Why Join Us?" with bullet-like paragraphs: Innovative Projects..., Collaborative Environment..., Impactful Work... These are about the role/benefits? Could be part of About the role. Then "Key Responsibilities" list. Then "Work Environment" with Location, Travel Requirements, Working Hours. Then "Qualifications Required:" list. Then "Desired" list. Then "Ready to Make a Difference?" paragraph (call to action) - maybe we can include as part of About the role or maybe discard as application instruction? It's encouraging to apply, but it's not application instructions; it's motivational. Could be part of About the role. Then "KBR Benefits" paragraph. Then "Belong, Connect and Grow at KBR" paragraph (culture) - could be part of About the role or Benefits? It's more about culture. Then "We Deliver – Together." etc. Then EEO boilerplate to remove. Also Job ID "R2129760" to drop. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (intro, why join us, impactful work, culture). Responsibilities (Key Responsibilities list). Requirements? There's "Qualifications Required:" and "Desired". Those could be Qualifications and Skills? The spec says we have sections Qualifications and Skills separate. We could put required qualifications under Qualifications, desired under Skills? Or combine? Better to follow typical: Qualifications (required) and Skills (desired or specific skills). But we have both required and desired lists. Could treat Qualifications as required qualifications (education, clearance, experience). Skills as desired or specific technical skills (Jira, Confluence, etc). However the spec says include a section only when posting has real specific content for it. We have content for both. We also have Pay and Schedule: Not explicitly stated. There's "Working Hours: Standard – Core hours 0800 - 1600" that's schedule info. So we can include Schedule section with that. Pay: Not mentioned; no salary. So we should NOT include Pay section. Benefits: we have KBR Benefits paragraph describing benefits. So include Benefits. Location and Travel Requirements could be part of About the role or Work Environment; but we have no specific section for Work Environment; we could fold into About the role or maybe a separate section? Not in list; we have only those headings. So we can include location/travel in About the role. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Schedule. Check if any content for Requirements separate from Qualifications? The posting has "Qualifications Required:" and "Desired". Could treat Qualifications as required, Skills as desired. Or we could have Requirements section for required qualifications and Qualifications for desired? But spec includes both Requirements and Qualifications as possible headings. We need to decide. Better: Use Requirements for mandatory qualifications (clearance, degree, experience). Use Qualifications for desired/minimum? Actually they are similar. But we have both Required and Desired. Could put Required under Requirements, Desired under Qualifications. Skills could be technical skills like Jira, Confluence, Agile, etc. However the Desired list includes things like "Minimum of 2 years' experience in Special Access and/or SCI programs." That's still experience, not skill. Also "Demonstrated ability to work well independently or as a team member." etc. Those are more like skills/competencies. We could treat Skills as the technical tools: Jira, Confluence, GitLab, Agile techniques, etc. But the posting also includes "Ability to analyze and think quickly..." etc under Required. That's skill-like. Given the ambiguity, we can combine: Requirements = required qualifications (clearance, degree, years experience). Qualifications = desired qualifications (special access, TS/SCI, etc). Skills = specific technical skills (Jira, Confluence, Agile, etc). But we need to avoid duplication. Let's extract: Required: - Secret clearance with Top Secret, SCI Eligibility - Bachelor’s or Master’s degree in Engineering or a related technical field - 5+ years of experience as Scrum Master with a specific focus on Air Force acquisition programs or similar DoD systems - Prior experience on a Scrum team - Ability to analyze and think quickly and to resolve conflict - Knowledgeable in techniques to fill in gaps in the Scrum - Ability to determine what is Scrum and what is not - Experience with successful Agile techniques - Ability to work with and lead a team - Strong communication, interpersonal and mentoring skills - Ability to adapt to a changing environment - Self-motivation and ability to stay focused in the middle of distraction - 3+ years of experience with Jira and or GitLab - 3+ years of experience with Confluence Desired: - Minimum of 2 years' experience in Special Access and/or SCI programs. - Demonstrated ability to work well independently or as a team member. - Demonstrated ability to communicate with technical and non-technical project teams - Active TS/SCI clearance Also note that "Active TS/SCI clearance" is a clearance, but it's desired; we already have Secret clearance with TS/SCI eligibility required. So desired adds active TS/SCI. Now Skills: Could be Jira, Confluence, GitLab, Agile techniques, Scrum practices, conflict resolution, communication, mentoring, adaptability, etc. But many overlap. Given the instruction to prefer a few substantive sections over many thin ones, maybe we combine Qualifications and Skills into one section? But we have separate headings allowed. However we should only include sections that have real specific content. We have content for both Qualifications (desired) and Skills (technical). Could we treat Skills as the list of specific tools/experience (Jira, Confluence, GitLab, Agile)? That is present in required (3+ years Jira/GitLab, 3+ years Confluence). So we could put those under Skills. Thus: - About the role: includes intro, why join us, impactful work, culture, location/travel, working hours? Actually working hours goes to Schedule. - Responsibilities: list of Key Responsibilities. - Qualifications: required qualifications (clearance, degree, experience, etc). Could also include desired? But we have separate Skills. - Skills: desired qualifications (special access, TS/SCI, ability to work independently, communication) plus technical tools (Jira, Confluence, GitLab, Agile). But we already have Jira/Confluence in required; maybe we keep them under Skills as they are technical skills. - Benefits: KBR Benefits paragraph. - Schedule: Working Hours: Standard – Core hours 0800 - 1600. Also Location and Travel Requirements could be included here? But schedule section is for schedule; location/travel could be in About the role. We must not fabricate content. Ensure we preserve all substantive info. Let's draft HTML. We'll start with

About the role

then

paragraphs combining the relevant prose. We need to avoid duplication: The "Why Join Us?" includes three paragraphs: Innovative Projects, Collaborative Environment, Impactful Work. We'll combine them into prose. Also the "Belong, Connect and Grow at KBR" paragraph about culture. Also location/travel: "Location: On-siteTravel Requirements: Less than 10% Working Hours: Standard – Core hours 0800 - 1600". We'll separate location/travel into About the role, and Working Hours into Schedule. Now Responsibilities: list each responsibility as

. We need to ensure we don't include boilerplate like "Ready to Make a Difference? If you’re excited about making a significant impact..." That's motivational but could be considered part of About the role. It's not boilerplate; it's substantive encouraging. We'll include it as part of About the role. Now Qualifications: list required qualifications as

. We'll include all required bullet points. Skills: list desired qualifications and technical skills as

. But we need to avoid duplication: Jira/Confluence already in required; but we could still list them under Skills if we want, but that would duplicate. Better to list under Skills only the desired items not already covered: Special Access/SCI programs experience, Active TS/SCI clearance, ability to work independently/team, communicate with technical/non-technical teams. Also maybe "Demonstrated ability to work well independently or as a team member." and "Demonstrated ability to communicate with technical and non-technical project teams". Also maybe "Minimum of 2 years' experience in Special Access and/or SCI programs." That's desired. We could also include "Ability to analyze and think quickly..." under Skills? But it's already in required. We'll keep required under Qualifications. Thus Skills section will contain: - Minimum of 2 years' experience in Special Access and/or SCI programs. - Active TS/SCI clearance. - Demonstrated ability to work well independently or as a team member. - Demonstrated ability to communicate with technical and non-technical project teams. We could also include "Ability to work with and lead a team" but that's already in required. Now Benefits: KBR Benefits paragraph: "KBR offers a selection of competitive lifestyle benefits which could include 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule. We support career advancement through professional training and development." We'll put that in

. Schedule: "Working Hours: Standard – Core hours 0800 - 1600". We'll put in

. Now ensure we didn't include Pay section. Now check for any duplicated lines: We need to avoid repeating same content. Let's craft HTML. We'll need to escape any special characters? Not needed. We'll output:

About the role

KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to customers in the intelligence and national security communities. In this position, your work will have a profound impact on protecting national security. Why Join Us? Innovative Projects: At KBR, you'll work on prototype projects supporting the U.S. Air Force Research Laboratory’s most mission-critical objectives. The Air Force Research Laboratory is the primary scientific research and development center for the Department of the Air Force, leading the discovery, development, and integration of affordable warfighting technologies for air, space, and cyberspace forces. Collaborative Environment: KBR fosters a dynamic and collaborative atmosphere where cross-functional teams of product managers, engineers, developers, and defense experts work in unison using Agile and DevOps principles for rapid iteration, continuous feedback, and integration. The team is passionate, forward-thinking, and united by a mission‑first mindset that encourages knowledge sharing, innovation, and problem‑solving. Impactful Work: Your work will directly support the Air Force in expanding current national capabilities, collaborating with experts across the Intelligence Community, Department of Defense, National Laboratories, industry, inter‑agency, academia, and partner nations. Belong, Connect and Grow at KBR: We are passionate about our people and our Zero Harm culture, fostering an environment where everyone can