Reverse Engineering/Vulnerability Research Internship (Summer 2027)

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. Must not invent or summarize away detail. Must not include sections with filler like "commensurate with experience". Must only include sections when posting has real specific content. We need to parse the posting. Key content: - Intro paragraph: "For brilliant minds in science, technology, engineering and business operations, Battelle is the place to do the greatest good..." etc. That's about the role? Could be "About the role" or "About Battelle". The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have: Job Summary: "We are currently seeking a Reverse Engineering/Vulnerability Research Intern for the Summer 2027. This position is onsite, located in Columbus, OH. Application deadline: October 23rd, 2026". Also earlier: "Do you like solving the hardest computing problems..." etc. That's more about role. Responsibilities: bullet list: "Collaborate with the Mission Focused Tools to improve reverse engineering and embedded system development capabilities, integrating hardware, software, and reverse engineering tasks", "Support the latest Mission Focused Tools Unit’s research and development programs", "Learn and improve your reverse engineering and vulnerability research skills through project and team building activities", "Conduct and / or participate in assigned technical tasks and activities with minimum supervision and within time and budget constraints. Work independently and effectively in a multi-disciplinary team environment; Effectively communicate ideas with other engineers; and work with minimal supervision". That's responsibilities. Key Qualifications: list of requirements: "Current enrollment in an Associate, Bachelor, or Master degree program in Computer Science, Computer Engineering, or any other related field of study", "Must have at least 1-year of college level coursework completed", "Experience writing or debugging software code in C or C++ or debugging microcontroller code (C or C++)", "Fundamental knowledge of computer architecture and experience working with computer assembly languages (x86, x64, ARM, MIPS)", "Familiarity with disassemblers/decompilers (IDA Pro/Free, Ghidra, Binary Ninja)", "Interest in one or more of the following areas: Computer Network Defense (CND), Computer Network Operations, Information Operations, and/or Cyber Operations; Electrical engineering, microelectronics, and embedded systems; Reverse Engineering, Vulnerability Research/Discovery", "Ability to demonstrate good organization, communication, problem-solving and teamwork skills", "Must be a sole US citizen with the ability to obtain and maintain a US government security clearance". Those are qualifications/requirements. Preferred Qualifications: list: "Ability to apply learned cyber skills to real life scenarios (internships, hack-a-thons, cyber security clubs, CTFs, etc.)", "Experience working with multi-disciplinary teams", "Experience with one or more of the following areas: High level software languages such as Java, C#, or Python; Low level debug tools such as GDB, OllyDbg, WinDbg, or Immunity Debugger; Microcontroller design and assembly languages; Traditional electronics lab equipment supporting test and debug activities; Reverse engineering embedded hardware and software; Analyzing disassembled code; Programming and using data acquisition tools". Those could be Skills or Qualifications. Compensation Data: "The salary range for this role is $20.00 – $40.00 per hour, in addition to a $2,000 housing stipend for students relocating more than 50 miles from home and university. Internship pay is benchmarked against national averages taking into consideration a student's major and year in school." That's Pay (and maybe Benefits includes housing stipend). Also "Preparing You for Career Success" paragraph about internship outcomes: could be Benefits? Not exactly. There's also "Flexible work schedules: Most teams follow a flexible, compressed work schedule that allows for every other Friday off", "Enjoy enhanced work flexibility, including a hybrid arrangement: You have options for where and when you work. Our Together with Flexibility model allows you to work 60% in-office and 40% remote, with Monday and Tuesday as common in-office days, dependent on team and position needs." That's Schedule. Also "Employee Resource Groups that help cultivate an inclusive and welcoming community", "Social and professional networking events with Battelle Senior Leadership and your colleagues", "Opportunities for philanthropic involvement to give back and make an impact in the community". Those could be Benefits. Also "Vaccinations & Safety Protocols" is boilerplate/legal; should be removed. Also "Battelle is an equal opportunity employer..." boilerplate; remove. Also "The above statements are intended to describe the nature and level of work..." boilerplate; remove. Also "For more information about our other openings, please visit www.battelle.org/careers" maybe remove as navigation. Thus we need sections: - About the role: could include the introductory paragraphs about Battelle, mission, intern impact, job summary, location, deadline, maybe the "Do you like solving..." paragraph. Should we include all that? Yes, preserve substantive info. - Responsibilities: as bullet list. - Requirements: maybe combine Key Qualifications as Requirements. Or we could have Requirements (mandatory) and Qualifications (preferred). The instruction list includes Requirements and Qualifications separate. So we can put Requirements = Key Qualifications (mandatory). Qualifications = Preferred Qualifications. - Skills: maybe we could extract skills from responsibilities? But we already have Skills section maybe for technical skills like C/C++, assembly, disassemblers, etc. However those are already in Requirements. Might be redundant. But we can still have Skills if there is distinct content. The posting includes "Experience writing or debugging software code in C or C++", "Fundamental knowledge of computer architecture and experience working with computer assembly languages", "Familiarity with disassemblers/decompilers", etc. Those could be Skills. But we already used them in Requirements. To avoid duplication, we could put them under Skills and keep Requirements as enrollment, year, citizenship, etc. However the instruction says preserve ALL substantive information; we can duplicate? It says do NOT invent or summarize away detail. Duplication is not invented, but might be redundant but still preserving. However better to follow the headings: Requirements (mandatory), Qualifications (preferred), Skills (maybe technical skills). But we need to decide. Let's map: Requirements (mandatory): - Current enrollment in an Associate, Bachelor, or Master degree program in Computer Science, Computer Engineering, or any other related field of study - Must have at least 1-year of college level coursework completed - Must be a sole US citizen with the ability to obtain and maintain a US government security clearance Qualifications (preferred): - Ability to apply learned cyber skills to real life scenarios (internships, hack-a-thons, cyber security clubs, CTFs, etc.) - Experience working with multi-disciplinary teams - Experience with one or more of the following areas: * High level software languages such as Java, C#, or Python * Low level debug tools such as GDB, OllyDbg, WinDbg, or Immunity Debugger * Microcontroller design and assembly languages * Traditional electronics lab equipment supporting test and debug activities * Reverse engineering embedded hardware and software * Analyzing disassembled code * Programming and using data acquisition tools Skills (maybe): - Experience writing or debugging software code in C or C++ or debugging microcontroller code (C or C++) - Fundamental knowledge of computer architecture and experience working with computer assembly languages (x86, x64, ARM, MIPS) - Familiarity with disassemblers/decompilers (IDA Pro/Free, Ghidra, Binary Ninja) - Interest in one or more of the following areas: Computer Network Defense (CND), Computer Network Operations, Information Operations, and/or Cyber Operations; Electrical engineering, microelectronics, and embedded systems; Reverse Engineering, Vulnerability Research/Discovery - Ability to demonstrate good organization, communication, problem-solving and teamwork skills But some of those overlap with qualifications. However we can still include. Alternatively we could combine Requirements and Qualifications into one section "Requirements" and skip Qualifications. But instruction says prefer few substantive sections over many thin ones. So we might want to avoid too many sections. Let's see what we have: - About the role (substantial) - Responsibilities (substantial) - Requirements (we could include both mandatory and preferred as one list) - Skills (maybe not needed if we put technical skills in Requirements) - Pay (substantial) - Benefits (substantial: housing stipend, flexible work schedules, hybrid arrangement, employee resource groups, networking events, philanthropic opportunities) - Schedule (maybe part of Benefits? But we have schedule info: flexible compressed work schedule every other Friday off, hybrid arrangement 60% in-office 40% remote Monday/Tuesday in-office. That's schedule.) We could combine Benefits and Schedule? But instruction says include a section only when posting has real specific content. We have both Benefits and Schedule content. So we can have both. We could omit Skills if we incorporate into Requirements. Let's see if we have enough content for Skills separate: we have technical skills like C/C++, assembly, disassemblers, etc. That's substantive. Could be a Skills section. Thus sections: About the role, Responsibilities, Requirements, Skills, Pay, Benefits, Schedule. Check each for real content: About the role: includes intro paragraphs about Battelle, mission, intern impact, job summary, location, deadline, "Do you like solving..." paragraph, description of labs, team culture, IRAD program. That's substantive. Responsibilities: bullet list. Requirements: mandatory qualifications: enrollment, 1-year coursework, US citizen/security clearance. Also maybe "Must have at least 1-year of college level coursework completed" is mandatory. Also "Current enrollment..." etc. Also maybe "Must be a sole US citizen..." That's it. Could also include "Interest in one or more of the following areas..."? That's more like qualification/skill. We'll keep it in Requirements? Might be better to put in Skills. Let's keep Requirements as those three. Skills: technical skills and interest areas: C/C++ debugging, assembly languages, disassemblers, interest areas (CND, CNO, InfoOps, CyberOps; EE, microelectronics, embedded systems; Reverse Eng, Vuln Research), organization/communication/problem-solving/teamwork. Pay: salary range $20-40 per hour + $2000 housing stipend for relocation >50 miles. Benefits: includes "Preparing You for Career Success" paragraph? That's more about outcomes; could be considered Benefits. Also includes flexible work schedules? Actually that's schedule. But we have separate schedule. Benefits could include: Employee Resource Groups, social/professional networking events, philanthropic involvement, maybe also the internship outcome stats (98% felt better prepared, 100% respected). Also "Battelle is committed to its employee’s professional growth. We encourage new ideas with our large Internal Research and Development (IRAD) program where engineers work on projects they are passionate about." That's more about role but could be benefit. We'll include in Benefits. Schedule: flexible compressed work schedule every other Friday off; hybrid arrangement 60% in-office 40% remote with Monday/Tuesday common in-office days. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include any markdown fences. We must not include any boilerplate like EEO, vaccinations, legal, etc. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must preserve all substantive info. Let's craft. First, About