Mobile Malware Engineer

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. No job title heading. No Job ID. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Preserve all substantive info. We need to parse the job description. Key parts: - Job#: 3043746 (drop) - Job Description: (maybe drop) - Candidates must be U.S. citizens able to obtain and/or maintain a Department of Defense security clearance as a condition and continuation of employment. (This is a requirement/clearance) - Mobile Malware Engineer Location: Linthicum, MD (On-site) (Location and on-site) - Role Overview paragraph: "We are seeking a Mobile Malware Engineer to analyze, reverse engineer, and characterize malicious software targeting Android and iOS platforms. This role supports a federal government customer by evaluating complex malicious code and delivering actionable intelligence. The engineer will investigate instances of malicious code to determine attack vectors, payloads, and the extent of damage and data exfiltration, directly supporting national security missions. This position will support multiple branches within the organization, with a primary focus on iOS and MacOS experience." - Key Responsibilities list: bullet points. - Required Qualifications: Education, Clearance, Experience, Technical Skills, Certifications. - Preferred Qualifications: list. - Work Environment: "This position requires work to be performed fully on-site." - Everforth Apex description: company overview, benefits, etc. - Benefits Overview: details. - Then more boilerplate EEO etc. We need sections: About the role (role overview), Responsibilities (key responsibilities), Requirements (maybe required qualifications?), Qualifications (maybe education?), Skills (technical skills?), Benefits (benefits overview), Pay (if any), Schedule (if any). The posting does not mention Pay or Schedule explicitly besides on-site (schedule maybe not). No pay info. So we should not include Pay or Schedule sections because they have no specific content. Also we should not include sections with filler like "commensurate with experience". So we will include sections that have content: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also "Work Environment" but not in list; we could incorporate into Requirements or maybe as part of About the role? The instruction says use headings for those specific section names; we should not create other headings. So we need to map content to those headings. We have: - About the role: Role Overview paragraph. - Responsibilities: Key Responsibilities list. - Requirements: maybe the mandatory requirements: U.S. citizenship, clearance eligibility, education/experience, certifications (CompTIA Security+ required). Also maybe "Must be eligible to obtain and maintain a DOW TS/SCI Clearance." (typo DOW? but keep). Also "Experience with iOS, MacOS, and Android platforms. Experience in R&D and with Bluetooth technology is also required." That seems like required experience. - Qualifications: maybe education specifics? But we already used education in Requirements. Could separate: Requirements = mandatory (clearance, citizenship, experience, certifications). Qualifications = preferred qualifications? But the instruction says we can have both Requirements and Qualifications sections. We need to decide what goes where. The posting has "Required Qualifications" and "Preferred Qualifications". So we can map Required Qualifications to Requirements section, and Preferred Qualifications to Qualifications section. However we also have Technical Skills under Required Qualifications. Could also have Skills section for technical skills. But we already have Skills heading allowed. Let's think. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to avoid duplication and ensure we preserve all substantive info. Potential mapping: - About the role: Role Overview paragraph. - Responsibilities: Key Responsibilities list. - Requirements: Mandatory items: U.S. citizenship, clearance eligibility, education/experience (Bachelor's + 8 years or Master's + 6 years, or 4 years experience in lieu of Bachelor's), CompTIA Security+ certification required, experience with iOS, MacOS, Android, R&D, Bluetooth technology. - Qualifications: Preferred Qualifications list (experience with CNO toolchains, nation-state APT, MDM/EMM, forensics tools, published research, CVEs, open-source contributions, additional certifications, development experience with C, C++, .NET). - Skills: Technical Skills: Proficiency in ARM/ARM64 assembly, low-level binary analysis, strong knowledge of Android/iOS internals, hands-on experience with Ghidra, IDA Pro, Jadx, Frida, MobSF, Corellium, scripting in Python, familiarity with Java, Kotlin, or Swift. - Benefits: Benefits Overview paragraph. - Pay: none -> omit. - Schedule: maybe mention on-site work schedule? The posting says "This position requires work to be performed fully on-site." That's about work environment, not schedule. Could we put that under Requirements? Or maybe under About the role? But we have no Schedule heading content; we should omit Schedule. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to use

for each section heading, then content:

for prose,

• for lists. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO statements, legal, application instructions, virtual recruiter details, privacy policy links, etc. Also remove duplicated lines (EEO repeated). Remove "Everforth Apex is an equal opportunity employer..." etc. Remove "UnitedHealthcare creates..." etc. Remove "Everforth Apex Benefits Overview:" maybe we keep the benefits description but not the heading? We'll keep benefits description. We need to preserve all substantive information: location, on-site, citizenship, clearance, role overview, responsibilities, required qualifications (education, experience, certifications, etc.), preferred qualifications, technical skills, benefits. We need to ensure we don't lose any detail like "Mobile Malware Engineer Location: Linthicum, MD (On-site)". We'll include location in About the role maybe? Could add a short paragraph after role overview: "Location: Linthicum, MD (On-site)". Or we could incorporate into About the role as a sentence. Since we must preserve all substantive info, we need to include location and on-site. Also we need to preserve the statement about U.S. citizens and clearance: "Candidates must be U.S. citizens able to obtain and/or maintain a Department of Defense security clearance as a condition and continuation of employment." We'll include that in Requirements. Also "Clearance: Must be eligible to obtain and maintain a DOW TS/SCI Clearance." (maybe typo DOW but keep). We'll include. Also "Experience: Experience with iOS, MacOS, and Android platforms. Experience in R&D and with Bluetooth technology is also required." We'll include. Also "Technical Skills: Proficiency in ARM/ARM64 assembly and low-level binary analysis. Strong knowledge of Android and iOS internals. Hands-on experience with tools such as Ghidra, IDA Pro, Jadx, Frida, MobSF, or Corellium. Scripting in Python and familiarity with Java, Kotlin, or Swift." We'll put under Skills. Also "Certifications: A CompTIA Security+ certification is required." We'll put under Requirements. Also "Preferred Qualifications" list. Also "Development experience with C, C++, or .NET." under Preferred Qualifications. Also "Work Environment This position requires work to be performed fully on-site." We'll incorporate maybe in About the role or Requirements? Since we have no Work Environment heading, we can add a sentence in About the role: "This position is fully on-site in Linthicum, MD." Also "Everforth Apex is a world-class IT services company..." that's company description; is that substantive? It's about the employer, maybe we can include in About the role or maybe omit as boilerplate? It's not required but could be considered substantive. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description might be considered boilerplate but it's not explicitly listed. However it's generic marketing. Might be okay to keep? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive? It's about the employer, not the job. Might be considered not essential to the job posting but still part of description. However many such descriptions are considered boilerplate. The instruction didn't explicitly say to remove company overview. But to be safe, we could keep a brief sentence about the company being a world-class IT services company that values innovation etc. But that might be considered fluff. I'd lean to omit it because it's not directly about the role and could be considered boilerplate. However the instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It does not say to remove company overview. So we could keep it. But we need to avoid too many thin sections. We could incorporate a short sentence in About the role: "Everforth Apex is a world-class IT services company serving thousands of clients globally." That's okay. But we also have benefits overview: we need to include that. We must not include the repeated EEO paragraphs. We must not include the virtual recruiter details, privacy policy links, etc. We must not include the "Everforth Apex Systems is an equal opportunity employer..." repeated. We must not include the "If you require an accommodation..." etc. We must not include the "UnitedHealthcare creates..." etc. We must not include the address and NYSE ticker etc. Thus final HTML:

  About the role

  We are seeking a Mobile Malware Engineer to analyze, reverse engineer, and characterize malicious software targeting Android and iOS platforms. This role supports a federal government customer by evaluating complex malicious code and delivering actionable intelligence. The engineer will investigate instances of malicious code to determine attack vectors, payloads, and the extent of damage and data exfiltration, directly supporting national security missions. This position will support multiple branches within the organization, with a primary focus on iOS and MacOS experience. The position is fully on-site in Linthicum, MD.

  Responsibilities

  • Perform static and dynamic analysis of mobile malware on Android and iOS platforms.
  • Reverse engineer ARM/ARM64 binaries, unpack APK/IPA files, and bypass runtime protections.
  • Identify C2 infrastructure, persistence mechanisms, and indicators of compromise (IOCs).
  • Identify vulnerabilities in binaries, analyze shellcode, and recommend preventative or defensive actions.
  • Develop custom tooling, automation scripts, and YARA detection signatures.
  • Produce technical reports with MITRE ATT&CK for Mobile mappings and remediation recommendations.
  • Perform ongoing research into malicious software, emerging vulnerabilities, and exploitation tactics.
  • Collaborate with forensics, vulnerability research, and cyber operations teams.

  Requirements

  Candidates must be U.S. citizens able to obtain and/or maintain a Department of Defense security clearance as a condition and continuation of employment. Must be eligible to obtain and maintain a DOW TS/SCI Clearance. Education: A Bachelor's degree and 8 years of experience, or a Master's degree and 6 years of experience. A degree in Cybersecurity, Computer Science, Software Engineering, Information Technology, Information Systems, or a related field is desired. An additional four years of experience may be considered in lieu of a Bachelor's degree. Experience with iOS, MacOS, and Android platforms. Experience in R&D and with Bluetooth technology is also required. Certifications: A CompTIA Security+ certification is required.

  Qualifications