Vulnerability Researcher

We need to produce HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also remove "Pay transparency" note? It mentions pay range but says it's estimate; we can include Pay section if posting actually states them. It says "Please note the targeted compensation range is provided as an estimate..." No actual numbers given. So we cannot create Pay section because no specific numbers. Benefits? Not mentioned. Schedule? Not mentioned. So we may have sections: About the role (Overview), Responsibilities (What You Will Do / What You'll Do), Requirements/Qualifications (What You Need To Have), Skills (maybe combine), maybe "Preferred Qualifications" (What We'd Like You To Have). Also maybe "About BigBear.ai". That could be a section like "About the Company". But headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use those headings as appropriate. We need to map content. We have: - Overview: "Do you have a passion..." etc. That's about the role. Could be "About the role". - "What You Will Do Why This Role Is Unique" then bullet list (though not bullet but sentences). Then "What You'll Do In This Role, You'll Hunt for Vulnerabilities:" etc. That's responsibilities. - "What You Need To Have" includes clearance, experience, programming expertise, technical background, reverse engineering, communication skills, education. That's requirements/qualifications. - "What We'd Like You To Have" includes proven track record, innovative mindset, collaborative spirit. That's preferred qualifications/skills. - "About BigBear.ai" description. We must not include boilerplate like "BigBear.ai is an Equal opportunity employer..." etc. Remove that. Also remove duplicated lines: there is some duplication: "Education: Bachelor's Degree in Computer Science or a related field, OR minimum of 2 years of experience in computer science, information systems, or network engineering." appears after earlier similar statements. We need to preserve all substantive info but not duplicate. We'll combine. We must not invent or summarize away detail. Must preserve all substantive info. So we need to include all details from those sections, but we can combine similar points without losing info. Must not omit any detail. That is tricky: we need to keep all specifics like years, languages, etc. We can list them in

• . Ensure we don't lose any. Let's extract details: Overview / About the role: - Passion for uncovering hidden vulnerabilities and pushing boundaries of cybersecurity research. - Sees every system as a puzzle. - Elite Vulnerability Researcher with active TS/SCI with Poly clearance. - Join cutting-edge team delivering groundbreaking engineering and vulnerability research results supporting national security missions. - Work on challenging research projects discovering initial access capabilities and developing proof-of-concept exploits that make a real difference. What You Will Do / Why This Role Is Unique: - Work on classified, mission-critical research that directly impacts national security. - Collaborate with elite teams of engineers and researchers passionate about pushing boundaries. - Freedom to explore and innovate, discovering previously unknown vulnerabilities across hardware, software, OS. - See research make a real difference in protecting national security interests. What You'll Do In This Role, You'll Hunt for Vulnerabilities: - Actively debug software, troubleshoot crashes, analyze programmatic flow to uncover hidden security flaws in hardware components, software applications, OS. - Analyze Source Code: Perform in-depth source code analysis to discover software vulnerabilities and author detailed documentation on impact and severity. - Develop Proof-of-Concept Exploits: Create and demonstrate compelling proof-of-concept exploits against research targets, prototypes, hands-on demonstrations of vulnerability analysis results. What You Need To Have: - Clearance: TS/SCI with Poly (required). - Experience: Minimum 5 years technical experience and B.S. in technical discipline. (4 additional years may be substituted in lieu of a degree.) - Programming Expertise: Minimum 4 years experience programming in Assembly, C, C#, C++, Perl, or Python in a production environment. - Technical Background: - Bachelor's Degree in Computer Science or related field plus minimum 3 years contiguous experience. - Reverse Engineering: Demonstrated experience in hardware or software reverse engineering. - Communication Skills: Demonstrated experience creating and delivering compelling technical presentations to diverse audiences. - Education: Bachelor's Degree in Computer Science or related field, OR minimum 2 years experience in computer science, information systems, or network engineering. Note: There's some overlap: The "Technical Background" includes Bachelor's plus 3 years contiguous experience, and then separate Education line says Bachelor's OR 2 years experience. We need to keep both as they are distinct statements; we shouldn't drop any. What We'd Like You To Have: - Proven Track Record: Demonstrated ability to discover multiple previously unknown vulnerabilities across multiple versions of similar technologies - the more obscure, the better! - Innovative Mindset: Relentless passion for pushing boundaries of vulnerability research and developing creative solutions to most complex challenges. - Collaborative Spirit: Desire to share knowledge and collaborate with team of like-minded researchers equally passionate about cybersecurity. About BigBear.ai: - Leading provider of AI-powered decision intelligence solutions for national security, supply chain management, digital identity. - Customers rely on predictive analytics in highly complex, distributed, mission-based operating environments. - Headquartered in McLean, Virginia. - Public company traded on NYSE under symbol BBAI. - For more info, visit https://bigbear.ai/ and follow on LinkedIn: @BigBear.ai and X: @BigBearai. We must remove EEO line. Now we need to output HTML fragment with headings

  for sections we include. Which sections have real specific content? All of the above have content. We need to decide which heading to use for each. Possible mapping: - About the role: Overview + Why This Role Is Unique? Could combine overview and uniqueness under About the role. - Responsibilities: What You Will Do / What You'll Do In This Role. - Requirements: What You Need To Have (clearance, experience, programming, technical background, education). - Qualifications: maybe same as Requirements? But we have both Requirements and Qualifications headings allowed. Could use Requirements for mandatory, Qualifications for preferred? But we also have Skills heading. Could assign: - Requirements: mandatory (clearance, experience, programming, technical background, education) - Skills: programming languages, reverse engineering, communication skills (maybe) - Qualifications: preferred (proven track record, innovative mindset, collaborative spirit) But we must not create thin sections. Let's think. We have a lot of content; we can make sections:

  About the role

  (overview + uniqueness)

  Responsibilities

  (what you'll do)

  Requirements

  (mandatory: clearance, experience, programming expertise, technical background, education)

  Skills

  (maybe programming languages, reverse engineering, communication)

  Preferred Qualifications

  (but heading list does not include Preferred Qualifications; we have Qualifications. Could use

  Qualifications

  for preferred. But we already used Requirements for mandatory; Qualifications for preferred is okay. But we also have "About BigBear.ai" maybe could be a section like "About the Company" but not in list. Could we omit? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we can use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should stick to those headings. So we need to map content to those headings only. If we have content that doesn't fit, we may need to incorporate into existing sections or omit if not fitting. But we must preserve ALL substantive information. So we need to fit all info into those headings. Thus we need to decide how to distribute content among those headings. Headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have no Benefits, Pay, Schedule specifics, so we omit those sections. We have About the role, Responsibilities, Requirements, Qualifications, Skills. We need to fit all content into these five sections. Let's allocate: - About the role: Overview + Why This Role Is Unique + About BigBear.ai? Possibly. - Responsibilities: What You Will Do / What You'll Do In This Role (hunting vulnerabilities, source code analysis, develop PoC exploits). - Requirements: Mandatory requirements: Clearance TS/SCI with Poly, Experience (5 years technical + B.S. or substitution), Programming Expertise (4 years in languages), Technical Background (B.S. + 3 years contiguous experience, reverse engineering, communication skills), Education (B.S. OR 2 years experience). Might be too much but okay. - Qualifications: Preferred qualifications: Proven track record, innovative mindset, collaborative spirit. - Skills: Could list specific technical skills: programming languages (Assembly, C, C#, C++, Perl, Python), reverse engineering, source code analysis, debugging, exploit development, technical presentation. But note some of these overlap with Requirements. We must not duplicate info. We need to preserve all substantive info without duplication. If we put programming languages under Skills, we should not also list them under Requirements (but Requirements includes programming expertise). We could keep programming expertise under Requirements as a bullet, and not repeat under Skills. Skills could include other abilities like reverse engineering, source code analysis, debugging, exploit dev, technical presentation. However reverse engineering and communication skills are already in Requirements under Technical Background. We could move them to Skills to avoid duplication, but then we would lose them from Requirements unless we keep them there as well. But we must preserve all info; duplication is not prohibited? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but we should avoid unnecessary duplication. However we can keep them in both places if needed, but better to avoid duplication. We could structure Requirements to include clearance, experience, programming expertise, education. Then Skills to include reverse engineering, source code analysis, debugging, exploit development, technical presentation, etc. That way we cover all. Let's list all specifics: From Requirements: - Clearance: TS/SCI with Poly (required). - Experience: Minimum 5 years technical experience and B.S. in technical discipline. (4 additional years may be substituted in lieu of a degree.) - Programming Expertise: Minimum 4 years experience programming in Assembly, C, C#, C++, Perl, or Python in a production environment. - Technical Background: - Bachelor's Degree in Computer Science or related field plus minimum 3 years contiguous experience. - Reverse Engineering: Demonstrated experience in hardware or software reverse engineering. - Communication Skills: Demonstrated experience creating and delivering compelling technical presentations to diverse audiences. - Education: Bachelor's Degree in Computer Science or related field, OR minimum 2 years experience in computer science, information systems, or network engineering. Note: The "Technical Background" includes Bachelor's plus 3 years contiguous experience, which overlaps with Education line. We'll keep both as separate bullets. From Responsibilities: - Work on classified, mission-critical research that directly impacts national security. - Collaborate with elite teams of engineers and researchers passionate about pushing boundaries. - Freedom to explore and innovate, discovering previously unknown vulnerabilities across hardware, software, OS. - See research make a real difference in protecting national security interests. - Actively debug software, troubleshoot crashes, analyze programmatic flow to uncover