Cybersecurity SME

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. Remove boilerplate. We need to parse the posting. Title: Cybersecurity SME Belong. Connect. Grow. with KBR! (but we don't repeat title as heading). The posting includes: - Intro 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." - "Why Join Us?" bullet list: Innovative Projects..., Collaborative Environment..., Impactful Work... - Key Responsibilities list (bulleted). - Work Environment: Location: On-site, Travel Requirements: Minimal, Working Hours: Standard - Qualifications Required: list. - Desired Experience list. - Basic Compensation: $175,800 to $214,900 (Virginia area only) plus note. - Additional Compensation: description. - "Ready to Make a Difference?" paragraph. - KBR Benefits paragraph. - "Belong, Connect and Grow at KBR" paragraph. - "We Deliver – Together." maybe. - EEO boilerplate to remove. - Job ID: R2126435 (should be folded into short p or dropped). We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. About the role: Could be the intro paragraph and maybe "Why Join Us?"? Usually "About the role" includes description of role, mission, etc. We'll put intro paragraph and maybe "Why Join Us?" as part of About the role. Responsibilities: The "Key Responsibilities" list. Requirements: Might be "Qualifications Required" and "Desired Experience"? Actually "Requirements" could be required qualifications. We'll treat "Qualifications Required" as Requirements. Qualifications: Could be "Desired Experience"? Or maybe we separate Required vs Desired? The instruction says use headings for Requirements, Qualifications, Skills. Might need to differentiate. But we can combine. Skills: Could be certifications etc. But we need to avoid thin sections. Let's think: The posting includes: - About the role: intro + Why Join Us? (maybe also Work Environment? but that could be separate? Not required heading.) - Responsibilities: list. - Requirements: Required qualifications (Active TS/SCI with Polygraph, Bachelor's degree + 10+ years, experience managing..., etc.) - Qualifications: Desired Experience (intelligence community, evaluating commercial tech, certifications, developing strategy, senior technical advisor) - Skills: maybe list of cybersecurity technologies and methodologies? Not explicit. Could be "Strong understanding of cybersecurity technologies and methodologies" etc. Could be part of Requirements. - Benefits: KBR Benefits paragraph. - Pay: Basic Compensation + Additional Compensation. - Schedule: Work Environment includes Working Hours: Standard, Travel Requirements: Minimal, Location: On-site. That could be Schedule section? Actually Schedule heading is for work schedule info. We have Working Hours: Standard, Travel Requirements: Minimal. Could put under Schedule. We need to ensure we don't create sections with filler like "not specified". We have actual content. We must not repeat job title as heading. Do not put Job ID as heading. We must output only HTML fragment, no /, no markdown. We'll produce something like:

About the role

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.

Why Join Us?

• Innovative Projects: KBR’s work is at the forefront of engineering, logistics, operations, science, program management, mission IT and cybersecurity solutions.
• Collaborative Environment: Be part of a dynamic team that thrives on collaboration and innovation, fostering a supportive and intellectually stimulating workplace.
• Impactful Work: Your contributions will be pivotal in designing, deploying, and securing mission-critical network infrastructure supporting national security operations.

But note: "Why Join Us?" is a heading? Not required; we can treat as a paragraph then list. Better:

Why Join Us:

then list. Now Responsibilities:

Responsibilities

• Lead complex cybersecurity initiatives supporting mission requirements
• Provide technical planning and strategic cybersecurity guidance
• Advise stakeholders on cybersecurity risks and solutions
• Translate mission needs into actionable technical recommendations
• Evaluate emerging technologies and commercial cybersecurity capabilities
• Coordinate efforts across multidisciplinary teams
• Support the execution of enterprise cybersecurity strategies
• Serve as a trusted advisor on cybersecurity best practices

Requirements (maybe Required Qualifications):

Requirements

• Active TS/SCI with Polygraph
• Bachelor’s degree in Cybersecurity, Computer Science, Engineering, or related field and 10+ years of experience; additional experience may be substituted for a degree
• Experience managing and executing complex cybersecurity initiatives
• Direct experience planning and executing multi-faceted technical activities
• Strong understanding of cybersecurity technologies and methodologies
• Experience working across technical and non-technical teams

Qualifications (Desired):

Qualifications

• Experience supporting intelligence community customers
• Experience evaluating commercial cybersecurity technologies
• CISSP, CISM, GIAC, or equivalent certifications
• Experience developing cybersecurity strategy
• Experience serving as a senior technical advisor

Skills: maybe we can include "Strong understanding of cybersecurity technologies and methodologies" but that's already in Requirements. Could also list "Technical planning, strategic guidance, stakeholder advising, etc." but that's responsibilities. Might be thin. Could omit Skills section if no distinct content. But we need to include only when posting has real specific content. There's no explicit skills list besides those already covered. Could we create Skills from "Strong understanding of cybersecurity technologies and methodologies" and "Experience working across technical and non-technical teams"? Those are more like qualifications. I'd say we can omit Skills to avoid thin section. Benefits:

Benefits

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.

Pay:

Pay

Basic Compensation: $175,800 to $214,900 (Virginia area only). The offered rate will be based on the selected candidate’s knowledge, skills, abilities and/or experience and in consideration of internal parity.

Additional Compensation: KBR may offer bonuses, commissions, or other forms of compensation to certain job titles or levels, per internal policy or contractual designation. Additional compensation may be in the form of sign on bonus, relocation benefits, short term incentives, long term incentives, or discretionary payments for exceptional performance.

Schedule:

Schedule

Location: On-site

Travel Requirements: Minimal

Working Hours: Standard

We should also include maybe a short paragraph for Job ID? Could fold into a short p at end:

Job ID: R2126435

but instruction says fold minor metadata into a short

or drop it. We can include a short p at end. We must not include EEO boilerplate, etc. Now ensure we didn't repeat any content unnecessarily. Also ensure we didn't include "Belong, Connect and Grow at KBR" paragraph? That's somewhat fluff but could be considered part of About the role? It's more about company culture. Could be omitted as not specific to role. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The "Belong, Connect and Grow at KBR" is substantive? It's about company values. Might be considered boilerplate but it's specific to KBR. However it's not about the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those. It's a cultural statement. Might be okay to keep but we need to place it somewhere. Could be part of About the role? Might be considered fluff but it's substantive. However we have limited sections; we could add a paragraph under About the role after the Why Join Us list. But we already have About the role with intro and Why Join Us. We could add another paragraph: "At KBR, we are passionate about our people and our Zero Harm culture. These inform all that we do and are at the heart of our commitment to, and ongoing journey toward being a People First company. That commitment is central to our team of team’s philosophy and fosters an environment where everyone can Belong, Connect and Grow. We Deliver – Together." But note that paragraph includes some repetition and maybe some fluff. It's still substantive. We'll include it. Now check for any duplicated lines: The posting had "Belong, Connect and Grow at KBR" and then later "At KBR, we are passionate about our people and our Zero Harm culture..." We'll include that. Now ensure we didn't include any "Ready to Make a Difference?" paragraph. That's basically a call to action, maybe considered application instruction? It's encouraging to apply. Might be considered application instruction. The instruction says remove application instructions. So we should drop that paragraph. Also drop "Ready to Make a Difference? If you’re excited about making a significant impact in the field of space defense and working on projects that matter, we encourage you to apply and join our team at KBR. Let's shape the future together." That's application instruction, remove. Now also drop the "KBR Benefits" heading? We already used Benefits section. Now ensure we didn't include any "We Deliver – Together." That's part of the cultural paragraph we included. Now final HTML fragment. We'll output:

About the role

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.

Why Join Us:

• Innovative Projects: KBR’s work is at the forefront of engineering, logistics, operations, science, program management, mission IT and cybersecurity solutions.
• Collaborative Environment: Be part of a dynamic team that thrives on collaboration and innovation, fostering a supportive and intellectually stimulating workplace.
• Impactful Work: Your contributions will be pivotal in designing, deploying, and securing mission-critical network infrastructure supporting national security operations.

At KBR, we are passionate about our people and our Zero Harm culture. These inform all that we do and are at the heart of our commitment to, and ongoing journey toward being a People First company. That commitment is central to our team of team’s philosophy and fosters an environment where everyone can Belong, Connect and Grow. We Deliver – Together.

Responsibilities

• Lead complex cybersecurity initiatives supporting mission requirements