Data Security Engineering Intern

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Content: - Intro: "Join our Oak Creek, WI team as a Data Security Engineering Intern! Our internships are hands on, highly technical, and designed to let you see what it's like to work at Astronautics. This is a paid undergraduate intern opportunity. As an engineering intern, you will work closely with our engineering staff on actual customer projects. Our summer intern program consists of at least 10 weeks of real-world experience in an engineering development environment. In addition to data security engineering, we have open opportunities in mechanical, process, software and systems engineering this summer. Mentors are assigned to assist interns in achieving engineering related career development that is of mutual benefit to you and Astronautics. Our internship program includes events and opportunities to meet other interns and employees across the organization." That's about the role / description. Could be "About the role" or maybe "Responsibilities"? The responsibilities are later. - Then "Requirements As a Data Security Engineering Intern, you will develop and maintain cybersecurity posture in Primary Flight, Engine, and Multi-function displays as well as in-flight computing devices including Network Servers, Mission and Display Processors, Data Concentrator Units, and Flight Controls. You will engage in all phases of avionics development including requirements gathering and verification, architecture creation and review, detailed design and analysis, peer technical reviews, compliance to industry and company design standards, and compliance to program cost and schedule targets. You will work under the supervision of engineering managers and other experienced engineers to engage in all phases of software development including the following activities: Participate in cybersecurity risk/safety assessments on aviation related systems, including analytical assessment, supplemental testing, and risk mitigation assessments Support development of cyber security lifecycle documentation in support of formal certification of avionics cybersecurity with the FAA and foreign certification authorities. Support development and execution of refutation and penetration testing" That's responsibilities/duties. - Then "Desired Skills Strong communication, analytical, organizational and problem-solving skills Ability to work effectively in a team environment based on Agile Scrum principles Capability of working independently with limited oversight from senior engineers" That's skills. - Then "Education And Experience Required Qualifications: Current accredited college or university enrollment with sophomore, junior or senior standing; making progress towards an undergraduate degree in Biomedical, Computer, Electrical, Software, Systems Engineering, Cybersecurity or Computer Science Minimum cumulative grade point average of 2.75 Demonstrate systems thinking skills (i.e., ability to recognize how to changes at a component level can impact the overall system and vice versa) Proficient in Microsoft Office tools Able to work full-time onsite during the summer of 2027 Eligible to work in the United States without sponsorship" That's qualifications. - Then "Desired Qualifications Cumulative grade point average of 3.0 or above Experience with software languages, including C, C++, Java, and Python Familiar with the concept of Risk Management Frameworks (RMF) Ability to work part-time during the school year" That's also qualifications/desired. - Then "Who We Are Join a team that designs computers, displays, and electronic systems for aircraft of the future! At Astronautics, you will be part of a creative group of professionals who work on the cutting-edge of technology. We offer competitive pay and the opportunity for professional growth in a friendly environment. Astronautics’ key product areas include electronic primary flight and engine displays, connected aircraft and cyber solutions, electronic flight bags, and certified servers for airborne applications. Services include avionics system integration and custom software for critical applications. Since its founding in 1959, Astronautics has been providing trusted, reliable, and tailored solutions to help customers achieve mission success. Astronautics is the parent company of Kearfott Corporation, headquartered in Pine Brook, New Jersey. We are proud to be an equal-opportunity workplace. All qualified applicants will receive consideration for employment without regard of race, color, ancestry, religion, sex, national origin, sexual orientation, age, citizenship, marital status, disability, gender, gender identity or expression, or veteran status." That's about the company; could be "About the role"? Actually "About the role" maybe not; but we have "About the role" heading for description of role. Could also have "About the company" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: intro paragraph(s) describing internship, location, paid, etc. - Responsibilities: the bullet list of duties (the long paragraph after "Requirements As a Data Security Engineering Intern...") Actually that section is titled "Requirements" but content is responsibilities. However we have separate headings for Requirements and Qualifications. The posting uses "Requirements" heading then describes responsibilities. Then later "Education And Experience Required Qualifications:" then "Desired Qualifications". So we need to follow the posting's headings? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if content exists. So we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections if posting has real specific content for them. Let's see what content maps: - About the role: we have introductory paragraph(s) describing internship, location, paid, etc. Yes. - Responsibilities: we have the duties list after "Requirements As a Data Security Engineering Intern..." That is responsibilities. So we can put that under Responsibilities. - Requirements: The posting has a heading "Requirements" but then the content is responsibilities. However there is also "Education And Experience Required Qualifications:" and "Desired Qualifications". The posting may consider "Requirements" as the responsibilities, and "Qualifications" as education/experience. But we need to decide what to put under Requirements heading. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should follow typical job posting structure: Requirements often list required qualifications (education, experience). But the posting uses "Requirements" heading for duties. However we must preserve ALL substantive information; we cannot misrepresent. If we put duties under Requirements, that would be inaccurate relative to typical meaning but we are just following the posting's headings? The instruction says use those headings for section headings; it doesn't say we must map content to those headings exactly as typical; we just need to output sections with those headings if the posting has real specific content for it. So we need to decide if the posting has content for "Requirements". It does have a section labeled "Requirements" (the heading). The content under that heading is the duties list. So we should output a

Requirements

with that content (the duties). Then we also have "Education And Experience Required Qualifications:" and "Desired Qualifications". That could be under Qualifications heading. So we will have Qualifications section containing both required and desired qualifications. - Skills: we have "Desired Skills" heading with bullet list. So we can put that under Skills. - Benefits, Pay, Schedule: The posting mentions "This is a paid undergraduate intern opportunity." and "We offer competitive pay". No specific pay amount, schedule, or benefits details. It mentions "Our summer intern program consists of at least 10 weeks of real-world experience". That's schedule (duration). It also mentions "Mentors are assigned", "events and opportunities to meet other interns". Those could be benefits but not explicit benefits like health insurance, etc. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "paid undergraduate intern opportunity" and "competitive pay". That's mention of pay but not specific amount. Is that enough to create a Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that it's paid and competitive pay. That is a statement about pay, albeit not specific. Should we include Pay section? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that it's paid and competitive pay, so we could include a Pay section with that statement. However also note: "Prefer a few substantive sections over many thin ones." If we include Pay with just a vague statement, maybe it's thin. But we could combine Pay into About the role? But the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The phrase "competitive pay" is not filler like "commensurate with experience"? It's somewhat vague but still a statement. It's not "not specified". It's stating that pay is competitive. I'd argue it's specific enough to include a Pay section. Similarly schedule: "Our summer intern program consists of at least 10 weeks of real-world experience in an engineering development environment." That's a specific schedule (duration). So we can include Schedule section with that statement. Benefits: The posting mentions "Mentors are assigned to assist interns in achieving engineering related career development that is of mutual benefit to you and Astronautics. Our internship program includes events and opportunities to meet other interns and employees across the organization." Also "We offer competitive pay and the opportunity for professional growth in a friendly environment." Those could be considered benefits. However the instruction says never create Benefits section unless posting actually states them. It does mention benefits like mentorship, events, professional growth. So we could include Benefits section with those statements. But we need to avoid too many thin sections. Perhaps we can combine Benefits and Pay and Schedule into one "Benefits" section? But headings are fixed; we cannot create custom headings. We could choose to include only those sections that have substantive content. Let's evaluate each: - About the role: substantive (intro). Yes. - Responsibilities: substantive (duties). Yes. - Requirements: we have content (duties) but that's actually responsibilities; but we have a heading "Requirements" in posting. We'll treat that as Requirements section with duties. - Qualifications: we have required and desired qualifications. Substantive. - Skills: we have desired skills. Substantive. - Benefits: we have mentorship, events, professional growth, friendly environment. That's substantive enough. - Pay: we have "paid undergraduate intern opportunity" and "competitive pay". That's somewhat substantive but could be considered thin. However we could include it. - Schedule: we have "at least 10 weeks of real-world experience". That's substantive. If we include all, we get many sections. The instruction: "Prefer a few substantive sections over many thin ones." So we might want to combine Pay and Schedule into Benefits? But we cannot change headings. However we could decide not to include Pay or Schedule if they are too thin. Let's see if the posting actually states them: Yes, it states paid and competitive pay (Pay). It states at least 10 weeks (Schedule). So they are stated. But are they "specific"? Pay: "competitive pay" is vague but still a statement about pay. Schedule: "at least 10 weeks" is specific. So Schedule is definitely specific. Pay is less specific but still a statement. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state them, so we can include. However we also need to avoid filler like "commensurate with experience". "competitive pay" is not filler like that. So I'd include