Associate Vulnerability Researcher Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include if content present. We need to parse the job posting. First, remove boilerplate: "In a world of possibilities..." etc. Also remove equal opportunity, fraudulent recruitment, etc. We need to keep substantive info. Let's extract sections: - About the role: The introductory paragraph about Parsons, mission, etc. Could be considered About the role. The posting starts with "In a world of possibilities..." then "At Parsons, you can imagine a career..." then "Guided by our leadership vision..." then "Unleash your talent..." then "Job Description: Parsons is seeking an Associate Vulnerability Research Engineer..." That's about the role. So we can put that in

About the role

with paragraphs. - Responsibilities: The "What You'll Be Doing:" bullet list. So we create

Responsibilities

with

• items. - Qualifications: The "What Qualifications You'll Bring:" bullet list. So

  Qualifications

  with list. - Desired Skills: "What Desired Skills You'll Bring:" bullet list. Could be Skills section. So

  Skills

  with list. - Security Clearance Requirement: There's duplicate lines: "Must be able to obtain and maintain a Top Secret clearance Must be able to obtain and maintain SCI and/or SAP accesses U.S. Citizenship is required Security Clearance Requirement: None". This is contradictory. Probably we need to include security clearance as part of Qualifications? But we have no specific heading for clearance. Could be part of Requirements? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no explicit "Requirements" heading but we could use Requirements for clearance and citizenship. However we already used Qualifications for qualifications list. Could treat Requirements as separate from Qualifications? Usually Requirements are mandatory qualifications. But we have both Qualifications and Desired Skills. The posting includes "What Qualifications You'll Bring:" (mandatory) and "What Desired Skills You'll Bring:" (desired). So we can map Qualifications to Requirements? Actually they said use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have both Requirements and Qualifications. We need to decide what goes where. Likely Requirements = mandatory qualifications (clearance, citizenship, degree, etc). Qualifications = maybe the list of qualifications? But they already have a list labeled "What Qualifications You'll Bring:" which seems like mandatory qualifications. So we could put that under Requirements. Then we could have Qualifications section for something else? But there is no other qualifications list. Could combine? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to use all. We should include a section only when posting has real, specific content for it. So we need to decide which headings have content. We have content for About the role, Responsibilities, (maybe Requirements), Qualifications (the list), Skills (desired), Pay (salary range), maybe Schedule? Not mentioned. Benefits? Not mentioned besides generic "endless growth opportunities" but that's vague. Not specific benefits like health insurance, etc. So we should not create Benefits section unless specific content. So we skip Benefits. Schedule: not mentioned. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. But we have both Requirements and Qualifications; we need to allocate content. We could treat Requirements as the security clearance and citizenship requirement (mandatory). Qualifications as the degree, programming experience, etc list. Skills as desired skills. Let's extract: Requirements content: - Must be able to obtain and maintain a Top Secret clearance - Must be able to obtain and maintain SCI and/or SAP accesses - U.S. Citizenship is required Also maybe "Work will be performed in both classified and unclassified environments." That's more about work environment, could be part of About the role or Responsibilities? Could be part of About the role. We'll include Requirements as a list. Qualifications content: - Bachelor's degree in Computer Science, Computer Engineering, Electrical Engineering, Cybersecurity, or a related technical field - Programming experience in languages such as C, C++, and Python through academic projects, internships, research, or professional experience - Familiarity with low-level software concepts including memory management, processes, threads, and operating system fundamentals - Familiarity with a decompiler/disassembler such as Ghidra, IDA Pro, or Binary Ninja - Familiarity with at least one instruction set architecture, such as x86/x86-64, ARM/AArch64, or MIPS - Strong analytical and problem-solving skills and an interest in understanding how complex systems work at a low level - Demonstrated interest in vulnerability research, reverse engineering, exploit development, embedded systems, or related technical security disciplines - Familiarity with common exploitation concepts and mitigations such as memory corruption, DEP/NX, ASLR, and stack protections Skills content (desired): - Internship, academic research, independent research, Capture the Flag (CTF), or other hands-on experience involving reverse engineering, vulnerability research, or exploit development - Experience reverse engineering embedded and Internet of Things (IoT) systems - Experience with Ghidra, IDA Pro, Binary Ninja, or similar reverse engineering tools - Experience using debuggers such as GDB, WinDbg, or LLDB - Experience with emulation or virtualization technologies such as QEMU - Knowledge of networking protocols and network protocol analysis - Experience with embedded software development, firmware analysis, microcontrollers, or hardware debugging - Participation in cybersecurity competitions, vulnerability research projects, open-source projects, or publication of independent technical research Pay: Salary Range: $63,600.00 - $111,300.00 Now About the role content: We need to capture the introductory paragraphs before "Job Description:" and maybe the job description sentence. Let's extract: "In a world of possibilities, pursue one with endless opportunities. Imagine Next! At Parsons, you can imagine a career where you thrive, work with exceptional people, and be yourself. Guided by our leadership vision of valuing people, embracing agility, and fostering growth, we cultivate an innovative culture that empowers you to achieve your full potential. Unleash your talent and redefine what’s possible." Then "Job Description: Parsons is seeking an Associate Vulnerability Research Engineer to join our team in support of advanced research and development contracts for the U.S. Government. You'll work alongside experienced vulnerability researchers on a small, highly technical team performing vulnerability research and reverse engineering against complex embedded and cyber-physical systems. This position provides an opportunity to develop hands-on expertise across the vulnerability research lifecycle, from initial target analysis and reverse engineering through vulnerability discovery, exploit development, and integration into operational cyber capabilities. This is an onsite position based at the Cromulence - Parsons office in the historic downtown of Melbourne, Florida, on Florida's Space Coast. Work will be performed in both classified and unclassified environments." We should keep all that as About the role. Now we need to output HTML fragment with

  headings and

  for prose,

  • for lists. We must not repeat job title as heading. Already not. We must not include Job ID/requisition numbers. We must remove boilerplate: equal opportunity, fraudulent recruitment, etc. Also remove "Parsons is an equal opportunity employer..." and the fraudulent recruitment link. Also remove "Throughout the company, our people are anticipating what’s next to deliver the solutions our customers need now." That's maybe part of About the role? It's after Federal Solutions description. Might be considered boilerplate but it's still about culture. Could keep but it's somewhat generic. However it's not explicitly boilerplate like EEO. It's still part of the description. Might keep as part of About the role. But we also have a paragraph about Federal Solutions segment: "This position is part of our Federal Solutions team. The Federal Solutions segment delivers resources to our US government customers that ensure the success of missions around the globe. Our intelligent employees drive the state of the art as they provide services and solutions in the areas of defense, security, intelligence, infrastructure, and environmental. We promote a culture of excellence and close-knit teams that take pride in delivering, protecting, and sustaining our nation's most critical assets, from Earth to cyberspace. Throughout the company, our people are anticipating what’s next to deliver the solutions our customers need now." That is substantive about the team. Could include in About the role as well. Thus About the role will be multiple paragraphs. Now we need to ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML. We'll structure:

    About the role

    ... first paragraph ...

    ... job description paragraph ...

    ... Federal Solutions paragraph(s) ...

    Then

    Responsibilities

    • ... each bullet ...
    Then

    Requirements

    • ... clearance etc ...
    Then

    Qualifications

    • ... qualifications list ...
    Then

    Skills

    • ... desired skills ...
    Then

    Pay

    Salary Range: $63,600.00 - $111,300.00

    We should not include Schedule or Benefits. Now ensure we preserve all substantive information. Let's list each bullet exactly. Responsibilities bullets from "What You'll Be Doing:": - Perform vulnerability research / reverse engineering (VR/RE) against embedded systems, including both hardware and software targets, under the guidance of senior researchers - Analyze software, firmware, binaries, protocols, and system behavior to identify potential vulnerabilities - Develop, test, debug, and document cyber tools, proof-of-concept exploits, and supporting research software - Use debuggers, decompilers, disassemblers, emulators, and other low-level analysis tools to understand target behavior - Collaborate with senior researchers to develop new vulnerability research techniques and solve challenging technical problems - Build expertise in reverse engineering, exploit development, operating system internals, embedded systems, and computer architecture Check if any missing: The original had line breaks; we captured. Qualifications bullets from "What Qualifications You'll Bring:": - Bachelor's degree in Computer Science, Computer Engineering, Electrical Engineering, Cybersecurity, or a related technical field - Programming experience in languages such as C, C++, and Python through academic projects, internships, research, or professional experience - Familiarity with low-level software concepts including memory management, processes, threads, and operating system fundamentals - Familiarity with a decompiler/disassembler such as Ghidra, IDA Pro, or Binary Ninja - Familiarity with at least one instruction set architecture, such as x86/x86-64, ARM/AArch64, or MIPS - Strong analytical and problem-solving skills and an interest in understanding how complex systems work at a low level - Demonstrated interest in vulnerability research, reverse engineering, exploit development, embedded systems, or related technical security disciplines - Familiarity with common exploitation concepts and mitigations such as memory corruption, DEP/NX, ASLR, and stack protections Skills bullets from "What Desired Skills You'll Bring:": - Internship, academic research, independent research, Capture the Flag (CTF), or other hands-on experience involving reverse engineering, vulnerability research, or exploit development - Experience reverse engineering embedded and Internet of Things (IoT)