Intern - Engineering

We need to output only HTML fragment, with sections as needed. Must not repeat job title. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include only sections with real specific content. We need to parse the posting. Company Information: description of company. Could be "About the role"? Actually "Company Information" is about the company, not role. The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Job Summary: description of intern role. Could be "About the role". Use

About the role

then

with that summary. - Responsibilities And Tasks: list of duties. Use

Responsibilities

then

• each bullet. - Education, Experience, License, Or Certification: could be "Requirements" or "Qualifications". The instruction: we have both Requirements and Qualifications headings. We need to decide which to use. Probably "Requirements" for education/experience, and "Qualifications" maybe for skills? But we also have Skills And Abilities separate. So we can put education/experience under Requirements, and maybe Qualifications could be omitted if not specific. But we have "Skills And Abilities" which maps to Skills heading. - Travel/Physical Requirements: Travel not required. Could be part of Schedule? Actually schedule is about work hours. Travel not required is a note; we could include under Schedule? But schedule heading is for schedule details; we have schedule info later: "Most locations offer a 9/80 schedule, providing every other Friday off". That's schedule. So we can put Travel not required maybe under a note in Responsibilities? But better to include under Schedule? Actually schedule heading is for work schedule; travel not required is separate. Could include under a short paragraph after schedule? But we should only include sections with real specific content. Travel not required is specific; we could include under a heading? Not in list. Could fold into a

  after schedule? The instruction: "Prefer a few substantive sections over many thin ones." So we could include Travel not required as a sentence in the Responsibilities or maybe in a general paragraph after schedule? But better to include under a "Schedule" section? Not exactly. However we have schedule info: "Most locations offer a 9/80 schedule, providing every other Friday off". That's schedule. Travel not required could be a separate bullet under Responsibilities? Not really. Could be a short note in its own paragraph without heading? The instruction says output only HTML fragment, we can include

  for prose. So we can add a

  Travel not required.

  after schedule section maybe. - Benefits: list of benefits. Use

  Benefits

  then
  . - Pay: Not explicitly stated; there is mention of "Competitive compensation & 401(k) program". That's compensation but not specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive compensation & 401(k) program". That's a statement about compensation, but not a specific range. Is that enough to create a Pay section? 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')". "Competitive compensation" is vague but not placeholder like "commensurate with experience". It's still vague but maybe acceptable? It says "Competitive compensation & 401(k) program". That's somewhat specific about 401(k). Could be considered real content. However they also say "Prefer a few substantive sections over many thin ones." Might be okay to include Pay section with that statement. But we also have schedule: "Most locations offer a 9/80 schedule, providing every other Friday off". That's specific, so Schedule section. Thus sections: About the role, Responsibilities, Requirements (education/experience), Skills, Benefits, Pay, Schedule. We could also include Qualifications if we want to separate skills? But we have Skills And Abilities; we could map that to Skills. Qualifications could be omitted. Now we need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title. Must not include boilerplate like EEO, legal, application instructions, etc. Must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to strip: - Company Information paragraph (we can keep as part of About the role? Actually it's about company, not role. But we could include it as a brief intro under About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So About the role should contain role description, not company info. However we could include company info as a paragraph before the heading? The instruction says output only HTML fragment, no extra headings besides those. It didn't forbid other

  content outside sections. But we should preserve all substantive information. Company information is substantive. Where to put it? Could be a

  before the first heading, describing the company. That seems acceptable. Thus we will output:

  Company Information Twenty-Six Defense, headquartered in Fort Worth, Texas, is a leading provider of high-performance products, system solutions, and aftermarket support services focusing on the defense, homeland security, and commercial aviation markets. With facilities throughout the U.S., Twenty-Six Defense is dedicated to supporting those who contribute to the national security of the United States. Twenty-Six Defense is wholly owned by Elbit Systems Ltd. (NASDAQ: ESLT and TASE: ESLT), a global high-technology company engaged in a wide range of programs for innovative defense and commercial applications.

  Then

  About the role

  with the Job Summary paragraph. Then responsibilities list. Then Requirements: education/experience. Then Skills: skills and abilities. Then Benefits: list. Then Pay: mention competitive compensation & 401(k) program. Then Schedule: 9/80 schedule. Then Travel not required: maybe a

  after schedule. We must not include the "Travel/Physical Requirements" heading; we can just put a

  Travel not required.

  . We must not include the duplicated lines like "This job description does not list all the duties..." etc. That's boilerplate; remove. Also remove the Virginia-based positions note, compensation variation note, Dayforce upload requirements, etc. All that is application instructions/legal; remove. Also remove "Reasonable accommodations may be made..." etc. That's EEO/legal; remove. Also remove "Twenty-Six Defense is an equal opportunity employer..." etc. Also remove "For Virginia-based positions only*" etc. Also remove "Please ensure your résumé meets the Dayforce upload requirements..." etc. Also remove "NOTE: Simply emailing a resume..." etc. Also remove "The job description is not an employment contract." etc. Also remove "The employer has the right to revise this job description at any time." etc. Also remove "This job description does not list all the duties of the job. You may be asked by your supervisors or managers to perform other duties." That's boilerplate; remove. Now we need to preserve all substantive information: company info, job summary, responsibilities list, education/experience, skills, benefits, pay, schedule, travel not required. Let's extract exact text. Company Information paragraph: exactly as given: "Company Information Twenty-Six Defense, headquartered in Fort Worth, Texas, is a leading provider of high-performance products, system solutions, and aftermarket support services focusing on the defense, homeland security, and commercial aviation markets. With facilities throughout the U.S., Twenty-Six Defense is dedicated to supporting those who contribute to the national security of the United States. Twenty-Six Defense is wholly owned by Elbit Systems Ltd. (NASDAQ: ESLT and TASE: ESLT), a global high-technology company engaged in a wide range of programs for innovative defense and commercial applications." We need to keep that exactly. Job Summary: "Under the direct supervision and mentorship of members of the Engineering Staff, the Engineering Intern undertakes a variety of on-going activities and assigned projects at varying levels of professional complexity requiring knowledge within an area of specialty and/or engineering college major. The Engineering Intern works as a member of the Engineering team in support of contracted tasks including design, modeling, analysis, fabrication, and test activities. The Engineering Intern will interact directly with multidiscipline professionals in the planning and implementation of assigned projects. It is a goal of the internship program to expose the student to the technical business environment to better prepare the student to make informed continued education and career decisions." We'll put that in a

  . Responsibilities list: The bullet points after "Typical assignments may include:" and then list items separated by line breaks. Also there are additional responsibilities after that: "Collaborate with colleagues and other internal or external partners in planning assignments and completing project deliverables.Conduct research and prepare written reports that include findings, recommendations, and alternative solutions as appropriate.Participate, along with other interns, in delivering a final presentation to Executive Staff summarizing the internship experience and highlighting at least one completed project.Perform additional duties as assigned." We need to split into list items. Let's capture each bullet: - Participate in technical projects and programs designed to develop both personal and professional skills aligned with the needs of the Engineering Department. - Support day to day engineering operations through tasks related to your specific area of study. - Typical assignments may include: - System and subsystem analysis and requirements specification - System and subsystem modeling and performance analysis - Designing electrical, mechanical, and/or optical components to meet engineering requirements - Fabricating, assembling, and debugging prototype electrical, mechanical, and/or optical hardware - Performing test and measurement activities using standard equipment such as multimeters, oscilloscopes, temperature sensors, and vibration probes - Conducting component research and investigations with suppliers and subcontractors - Organizing, correlating, and documenting test data using spreadsheets, word processing, or database tools - Creating technical documentation - Supporting software development or scripting tasks - Collaborate with colleagues and other internal or external partners in planning assignments and completing project deliverables. - Conduct research and prepare written reports that include findings, recommendations, and alternative solutions as appropriate. - Participate, along with other interns, in delivering a final presentation to Executive Staff summarizing the internship experience and highlighting at least one completed project. - Perform additional duties as assigned. We need to ensure we don't lose any. Also note that "Typical assignments may include:" is a heading for sublist; we could treat it as a list item with sublist? But we must use

  • for any list of duties/requirements/benefits. We could nest lists? The instruction didn't forbid nesting. But to keep simple, we could treat each sub-item as separate
  • and maybe include a preceding
  • for the heading? Better to flatten: include all items as separate
  • . The heading "Typical assignments may include:" is not a duty itself; it's intro. We could omit it as it's not a duty. But we risk losing the phrase "Typical assignments may include:" which is not substantive? It's just intro. The substantive content is the list of assignments. So we can drop the heading phrase. Thus we will create
    with each duty as
    • . List items: - Participate in technical projects and programs designed to develop both personal and professional skills aligned with the needs of the Engineering Department. - Support day to day engineering operations through tasks related to your specific area of study. - System and subsystem analysis and requirements specification - System and subsystem modeling and performance analysis - Designing electrical, mechanical, and/or optical components to meet engineering requirements