Systems Security Engineer, Lead

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: - Intro paragraph about MITRE: "At MITRE, your passion fuels work..." etc. That's about the organization, could be "About the role"? Actually "About the role" would be description of role. The intro is more about MITRE mission. Could be placed under "About the role" maybe? But we need to decide. The posting includes: "MITRE’s Mission Assured Engineering Department has a new opportunity for a strong technical candidate with systems security expertise to join an innovative team of engineers focused on developing security capabilities and ensuring resilient and secure solutions that overcome sponsor/customer needs. For this position, you will leverage your academic foundation and your work experiences to develop, hone and apply your knowledge of the latest systems security and cybersecurity engineering concepts to the next generation of trustworthy and resilient cross-domain capabilities that function anytime the sponsor/customer demands. The right candidate will have opportunities to merge work and interests with advancements from research, industry, academia, and standards groups to develop novel security capabilities. The right candidate will enjoy a fast-paced team environment, working with cutting-edge technology, and contributing to advancing security concepts. We are seeking a self-starter that assists in applying cross-domain solution principles to build security into large engineering projects and acquisition efforts. The candidate for this position will work on a wide variety of challenging problems including systems resiliency, cyber test, security, and cybersecurity activities in direct support of programs." That's description of role. So we can put that under "About the role" heading. Then "Roles & Responsibilities:" list bullet points. Those are responsibilities. Then "Basic Qualifications:" list bullet points. Then "Preferred Qualifications:" bullet points. Then "Salary compensation range and midpoint: $146,400 - $183,000 - $219,600". That's Pay. Then "Annual Work Location Type: Onsite". That's Schedule? Actually schedule maybe "Onsite" indicates work location type, not schedule. Could be "Schedule" maybe not. The instruction: Use headings for Pay, Schedule, Benefits. We have Pay info. We have no explicit Benefits info besides generic "competitive benefits" mentioned earlier but not specific. The posting says "supported by competitive benefits, meaningful career development, and a culture of innovation..." That's generic but not specific benefits list. We should not create Benefits section unless posting actually states them. It mentions competitive benefits but not details. Likely we should not create Benefits section because no specific benefits listed. Similarly Schedule: we have "Annual Work Location Type: Onsite". That's not schedule but location. Could be considered Schedule? Probably not. The instruction: include a section ONLY when posting has real, specific content for it. So we should not create Schedule unless there is explicit schedule like "full-time", "part-time", "40 hours/week". Not present. So we omit Schedule. We also have "Preferred Qualifications" which could go under Qualifications or Skills. The headings list includes Qualifications and Skills. We could put Basic Qualifications under "Qualifications". Preferred Qualifications could be under "Skills" or also under "Qualifications". But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's also "Requirements" heading. Could map Basic Qualifications to Requirements? Or Requirements could be separate from Qualifications. Usually Requirements = basic qualifications. Qualifications = preferred? But we have both basic and preferred. We could put basic under Requirements, preferred under Qualifications, and maybe Skills separate if any skill list. However we have skill-like items: "Knowledge of D3FEND, ATT&CK, Caldera, ATT&CK Evaluations, and MITRE's work for public interest", "Experience defining, developing, and validating cross-domain solutions", "Excellent written, oral, and interpersonal communication skills". Those could be Skills. Thus we can structure: - About the role: paragraph(s) describing role. - Responsibilities:

• list from Roles & Responsibilities. - Requirements:
  • list from Basic Qualifications. - Qualifications:
    • list from Preferred Qualifications. - Skills:
      • list of skill items (knowledge of frameworks, communication skills, etc.) - Pay:

        Salary compensation range and midpoint: $146,400 - $183,000 - $219,600 We must not include Benefits or Schedule. We must not include boilerplate like EEO, accommodation, copyright, etc. We must preserve all substantive information. Ensure we don't lose any details. Let's extract details precisely. About the role paragraph(s): From posting: "MITRE’s Mission Assured Engineering Department has a new opportunity for a strong technical candidate with systems security expertise to join an innovative team of engineers focused on developing security capabilities and ensuring resilient and secure solutions that overcome sponsor/customer needs. For this position, you will leverage your academic foundation and your work experiences to develop, hone and apply your knowledge of the latest systems security and cybersecurity engineering concepts to the next generation of trustworthy and resilient cross-domain capabilities that function anytime the sponsor/customer demands. The right candidate will have opportunities to merge work and interests with advancements from research, industry, academia, and standards groups to develop novel security capabilities. The right candidate will enjoy a fast-paced team environment, working with cutting-edge technology, and contributing to advancing security concepts. We are seeking a self-starter that assists in applying cross-domain solution principles to build security into large engineering projects and acquisition efforts. The candidate for this position will work on a wide variety of challenging problems including systems resiliency, cyber test, security, and cybersecurity activities in direct support of programs." We can keep as one or multiple

        . Probably one

        is fine. Responsibilities bullet list: From "Roles & Responsibilities:" then list: - The engineer will be a core member of the technical team and serve as systems security and cybersecurity subject matter expert (SME) to stakeholders and collaborators. - The position will also serve as primary, trusted independent advisor to DoD sponsors on the security design of national security systems and requires direct in-person contributions to our government customers. - Advise sponsors in developing and acquiring secure, resilient cyber-physical systems with a focus on protecting mission systems, strengthening defenses, and resolving security weaknesses - Apply knowledge of Systems Security Engineering and Cybersecurity to define and implement cross-domain solutions that strengthen security of information exchanges in developing and fielded systems - Provide recommendations on ensuring systems are specified, designed, developed, implemented, integrated, tested and sustained to meet security, resiliency, and safety requirements - Collaborate closely with sponsors and DoD customers to define priorities, support planning and execution of security assessments, and deliver clear, actionable findings - Assist in development of systems security and cybersecurity strategy development, system testing and evaluation, and verification and validation efforts - Collaborate effectively with MITRE, government, and contractors; to effectively communicate in writing, presentations, and collaborative discussions; able to interface with peers, managers, and government sponsors - Promote collaboration and integration with other organizational elements within the Mission Assured Engineering department and across MITRE - Research and develop unique, cutting-edge technical capabilities and processes for understanding, assessing, and analyzing system and technology resilience and security - Contribute to projects or small teams to solve complex cybersecurity problems for our sponsors - Keep pace with the rapidly advancing lifecycle of emerging technologies to maintain cutting edge support of sponsor programs We need to ensure each bullet is a

      • . Requirements (Basic Qualifications): - Typically requires a minimum of 8 years of related experience with a Bachelor’s degree; or 6 years and a Master’s degree; or a PhD with 3 years’ experience; or equivalent combination of related education and work experience. - Demonstrated technical depth in the field of Systems Security Engineering, Cybersecurity, Software Engineering, or Systems Engineering - Experience developing or evaluating Systems Security Engineering solutions and capabilities - The ability to think critically and be proactive in pursuing research and problem-solving with minimal supervision - Understanding of the missions, domains, and challenges of cybersecurity work with MITRE sponsors - Excellent written, oral, and interpersonal communication skills and a keen desire to learn. An open attitude to promoting the work of others - Knowledge of D3FEND, ATT&CK, Caldera, ATT&CK Evaluations, and MITRE's work for public interest - Experience defining, developing, and validating cross-domain solutions - Must have an active Top Secret U.S Government issued Security Clearance and must be eligible to obtain and maintain a Top Secret/SCI U.S Government issued Security Clearance. Per the U.S. Government’s eligibility requirements, you must be a U.S Citizen to be considered for a security clearance - This position requires a minimum of 3 days on-site Note: The last bullet about 3 days on-site is also a requirement; could be placed under Requirements. Qualifications (Preferred Qualifications): - Demonstrated track record building strong internal and external partnerships - Active Top Secret/SCI clearance. This requisition requires the candidate to have a minimum of the following clearance(s): Top Secret - This requisition requires the hired candidate to have or obtain, within one year from the date of hire, the following clearance(s): Top Secret/SCI We could combine these but keep as separate bullets. Skills: we need to extract skill-specific items not already covered. Could include: - Knowledge of D3FEND, ATT&CK, Caldera, ATT&CK Evaluations, and MITRE's work for public interest (already in Requirements but could also be skill) - Experience defining, developing, and validating cross-domain solutions (also in Requirements) - Excellent written, oral, and interpersonal communication skills (also in Requirements) - Ability to think critically and be proactive (maybe skill) - Understanding of missions, domains, challenges (maybe skill) But we risk duplication. However instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's present in multiple sections? But we should not duplicate content unnecessarily? It didn't forbid duplication, but better to avoid repeating same bullet in multiple sections. We can assign each piece to appropriate section: Basic Qualifications (Requirements) includes education/experience, technical depth, experience developing/evaluating SSE solutions, critical thinking, understanding missions, communication skills, knowledge of frameworks, experience defining cross-domain solutions, clearance, on-site days. Preferred Qualifications (Qualifications) includes partnership building, clearance details. Skills could include: knowledge of frameworks, communication skills, critical thinking, etc. But those already in Requirements. Perhaps we can treat Skills as a separate section for items like "Knowledge of D3FEND, ATT&CK, Caldera, ATT&CK Evaluations, and MITRE's work for public interest", "Experience defining, developing, and validating cross-domain solutions", "Excellent written, oral, and interpersonal communication skills". However that duplicates. Maybe better to not create Skills section if it would just repeat. But we need to decide if we should include Skills heading. The instruction: Prefer a few substantive sections over many thin ones. If Skills would be thin (just a few items) maybe we can omit Skills and put those items under Qualifications or Requirements. However we already have Qualifications for preferred qualifications. We could merge skill items into Qualifications. But we already have Qualifications for preferred qualifications (partnership building, clearance). Could add skill items there. Thus we could have sections: About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications + skill items), Pay. We must not create Benefits or Schedule. Let's compile. Requirements (basic) bullets: - Typically requires a minimum of 8 years of related experience with a Bachelor’s degree; or 6 years and a Master’s degree; or a PhD with 3 years’ experience; or equivalent combination of related education and work