Cybersecurity Researcher / Engineer: Secure Systems and AI (Early Career)

We need to output HTML fragment with headings

for sections: 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. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. The posting includes: - Intro paragraph about group: "The Secure Resilient Systems and Technology group advances cybersecurity research..." That's about the role? Could be "About the role" or "About the team". We'll treat as "About the role". - Then "Job Description As an Assistant Technical Staff member, you will:" followed by bullet list (actually sentences separated by periods). We'll convert to

• . - Then "Required Qualifications To thrive in this role, you should have:" then list of items. - Then "Desired Experience And Expertise We particularly value demonstrated experience in one or more of the following:" list. - Then "Recent Graduate Hiring Range: $100,200 - $120,000 Experienced Hiring Range: $100,200 - $150,000" This is Pay info. So we need a Pay section with that content. - Then "At MIT Lincoln Laboratory, our exceptional career opportunities include many outstanding benefits..." then list of benefits. So Benefits section. - No explicit Schedule info. So we should not create Schedule section. - Also there is mention of "Selected candidate will be subject to a pre-employment background investigation and must be able to obtain and maintain a Secret level DoD security clearance." That's a requirement maybe under Requirements or Qualifications. Could be part of Requirements. - Also "U.S. citizenship is required." That's also a requirement. - Also "MIT Lincoln Laboratory is an Equal Employment Opportunity (EEO) employer..." that's boilerplate to remove. - Also "Requisition ID: 43403" drop. - Also "Please visit our Benefits page for more information." maybe part of Benefits but we can keep. - Also "As an employee of MIT, you can also take advantage of other voluntary benefits, discounts and perks." part of Benefits. We need to preserve all substantive info, not invent or summarize away detail. So we need to keep the specifics: hiring ranges, benefits list, etc. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment. Structure:

  About the role

  ... intro paragraph ...

  Responsibilities

  • ... each duty ...

  Requirements

  ... maybe combine Required Qualifications and other requirements like clearance, citizenship.

  But we also have "Required Qualifications" and "Desired Experience And Expertise". Could split into Qualifications (Required) and Skills (Desired). The instruction says use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - About the role: intro paragraph. - Responsibilities: job description bullet list. - Requirements: maybe the mandatory items: Bachelor's degree, proficiency in at least one of the listed, substantial hands-on experience, problem-solving skills, plus clearance, citizenship. - Qualifications: maybe the "Required Qualifications" list? But that overlaps with Requirements. Could treat Requirements as the mandatory qualifications, and Qualifications as maybe "Desired Experience And Expertise"? But they said Skills also. Hmm. We need to decide mapping that preserves info without duplication. We have two lists: Required Qualifications (mandatory) and Desired Experience And Expertise (preferred). Also we have "Strong problem-solving and technical communication skills..." which is part of Required Qualifications. Thus we could put: - Requirements: Bachelor's degree, proficiency, substantial hands-on experience, problem-solving & communication skills, clearance, citizenship. - Qualifications: maybe the list under Required Qualifications? But that duplicates. Could treat Qualifications as the list of specific technical proficiencies (software design, secure software, etc.) and Skills as the desired experience list. But the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those headings possibly. We need to include sections only when posting has real specific content. We have content for About the role, Responsibilities, Requirements (maybe), Qualifications (maybe), Skills (maybe), Benefits, Pay. No Schedule. We need to avoid empty sections. Let's extract specifics: About the role: The first paragraph about group mission. Responsibilities: list: - Research, design, prototype, and evaluate new approaches to securing software, embedded, and communication systems against sophisticated cyber threats. - Develop high-quality software and experimental systems using Rust, C/C++, and other languages appropriate to the research. - Explore problems at the intersection of AI and cybersecurity, including applications of AI to cyber analysis and defense, as well as the security and evaluation of AI-enabled systems. - Collaborate with researchers and engineers across cybersecurity, cryptography, formal methods, AI, communications, autonomy, space, and other disciplines. - Present results to Laboratory and government stakeholders and contribute to reports, publications, prototypes, reusable software, and the transition of successful technologies to operational use. Requirements: Could be: - Bachelor’s degree in Computer Science, Computer Engineering, Cybersecurity, Software Engineering, Systems Engineering, or a related technical field. - Demonstrated proficiency in at least one of the following: Software design, development, and testing in Rust (preferred), C/C++, or another systems programming language; Secure software or systems security; Systems integration, testing, and evaluation of secure systems; Embedded systems analysis, design, and implementation. - Substantial hands-on technical experience beyond academic coursework, typically equivalent to at least six months of full-time technical experience, gained through internships, co-ops, research appointments, employment, or comparable experience. A significant portion must be directly relevant to cybersecurity, systems security, secure software, embedded systems, or AI security. - Strong problem-solving and technical communication skills, with the ability to work effectively in teams. - Must be able to obtain and maintain a Secret level DoD security clearance. - U.S. citizenship required. Qualifications: Could be the list under "Required Qualifications"? But we already used that. Maybe Qualifications could be the "Desired Experience And Expertise" list? But they also have Skills heading. Perhaps we treat Qualifications as the Required Qualifications list (the bullet items) and Skills as the Desired Experience list. However we already used Required Qualifications for Requirements. Might be okay to shift. Let's map: - Requirements: Bachelor's degree, proficiency, hands-on experience, problem-solving skills, clearance, citizenship. - Qualifications: The list of specific technical areas under Required Qualifications? Actually those are part of proficiency. Hmm. Better: Use Requirements for the mandatory qualifications (degree, experience, clearance, citizenship). Use Qualifications for the "Required Qualifications" list of technical proficiencies (software design, secure software, etc.) and Skills for the "Desired Experience And Expertise" list. But then we duplicate proficiency items. However the instruction says preserve ALL substantive information; we can repeat if needed but better not duplicate. We could split the Required Qualifications into two categories: the proficiency options (list) and the experience/skills. But we can keep them under Qualifications. Let's decide: - Requirements: Bachelor's degree, substantial hands-on experience (6 months), problem-solving & communication skills, ability to obtain Secret clearance, U.S. citizenship. - Qualifications: Demonstrated proficiency in at least one of the following: Software design, development, and testing in Rust (preferred), C/C++, or another systems programming language; Secure software or systems security; Systems integration, testing, and evaluation of secure systems; Embedded systems analysis, design, and implementation. - Skills: Desired Experience And Expertise list: Systems engineering, security requirements analysis, threat modeling; Security evaluation and assurance, including adversarial testing, experimental methods, security measurement, and evidence supporting security and assurance claims; Secure software development, operating system internals, embedded systems security, and network protocols; Applied cryptography and protocols, including industry and government standards; Static and dynamic software analysis and applied formal methods; AI and cybersecurity, including AI-enabled software analysis, vulnerability discovery, security testing, threat analysis, and cyber defense; and security of AI-enabled systems, including adversarial threats and evaluation of security, robustness, and resilience; Technical communication, including documenting designs, writing reports and research papers, and presenting technical results. That seems reasonable and preserves all info. Now Benefits: list from paragraph: Comprehensive health, dental, and vision plans; MIT-funded pension; Matching 401K; Paid leave (including vacation, sick, parental, military, etc.); Tuition reimbursement and continuing education programs; Mentorship programs; A range of work-life balance options... and much more! Also "As an employee of MIT, you can also take advantage of other voluntary benefits, discounts and perks." We'll include that as part of benefits list. Pay: Recent Graduate Hiring Range: $100,200 - $120,000; Experienced Hiring Range: $100,200 - $150,000. Also note disclaimer about base salary only. We'll include that as part of Pay section. We must not include boilerplate like EEO, disclaimer about salary? The disclaimer is part of Pay info; we can keep it as it's substantive about salary. The instruction: "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." The disclaimer about salary is not minor metadata; it's about pay. So we can include. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we remove the EEO statement, the "Apply here to learn more" maybe part of intro? Actually "If you would like to pursue cutting-edge research and work on things that truly matter at a place that combines MIT's culture of academic excellence, exceptional resources, and strong work-life balance, apply here to learn more." That's application instruction; we should remove that sentence. Also "Please visit our Benefits page for more information." maybe okay as part of benefits but could be considered application instruction? It's a reference; we can keep as it's not instruction to apply. But safer to keep? It's not an application instruction; it's just a reference. We'll keep. Also "Selected candidate will be subject to a pre-employment background investigation and must be able to obtain and maintain a Secret level DoD security clearance." That's a requirement; we keep. Now produce HTML. We need to ensure proper nesting:

  About the role

  ...

  etc. Let's craft the About the role paragraph: The first paragraph up to "We strive to bring out the best in our people and our systems, so that the Laboratory and the nation can count on them when it matters most." That's the group description. We'll include that. We should not include the sentence about "If you would like to pursue cutting-edge research..." as it's application instruction. Thus About the role paragraph: "The Secure Resilient Systems and Technology group advances cybersecurity research to address critical national security challenges. We develop and evaluate technologies that enable mission systems, from space and autonomous platforms to tactical communications and secure computing, to withstand cyberattack and continue the mission. Our goal is not simply to identify vulnerabilities, but to design security in from the start and provide rigorous evidence that these systems can be trusted under attack. Our research spans secure software and embedded systems, security architecture and threat modeling, applied cryptography, formal methods, and security evaluation, as well as the intersection of AI and cybersecurity, including both AI for cybersecurity and cybersecurity for AI. We work across the R&D lifecycle, from new concepts through prototyping