Summer 2027 Embedded Software Engineering Intern
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content.
We have:
- About the role/company: first paragraph describing Leonardo DRS. That's substantive.
- Responsibilities: list of duties (multiple bullet-like sentences). We'll put under Responsibilities
with - items.
- Qualifications: includes "High school diploma or GED", "Engineering student; some progress towards engineering degree", "Must have good interpersonal skills...", "Must be diligent...", "Good understanding of software development using C/C++ and Python on Linux...", "Good understanding of multi-threading...". Also "Preferred Qualifications:" list.
We could combine Qualifications and Preferred Qualifications under Qualifications section, maybe separate sub-sections? But instruction: prefer few substantive sections over many thin ones. So we can have Qualifications section containing both required and preferred.
- Skills: maybe not separate; we could include skills within Qualifications. But we could also have a Skills section for technical skills: C/C++, Python, Linux, Windows, multi-threading, multi-processing, embedded drivers, Git, Jira, Agile. However we already have them in Qualifications. To avoid duplication, we could keep Qualifications and maybe Skills not needed. But we need to decide.
- Benefits: The posting mentions "competitive salaries and comprehensive benefits, including medical, dental, and vision coverage, a company contribution to a health savings account, telemedicine, life and disability insurance, legal insurance, and a 401(k) savings plan. We champion wellness programs... flexible work schedules with our 9/80 program, competitive vacation, health/emergency leave, paid parental leave, and community service hours. Some employees are eligible for limited benefits only". That's substantive benefits. So we need Benefits section.
- Pay: Not explicitly stated; only "competitive salaries" but no numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "competitive salaries" but not specific pay. Is that enough? It says "competitive salaries" is a statement about pay but not specific. The instruction: 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. "competitive salaries" is vague but still a statement about pay. However it's not a specific number or range. Might be considered filler? The examples given are generic placeholders. "competitive salaries" is somewhat generic but still a statement. I'd lean to not create Pay section because it's not specific. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "competitive salaries". That's a statement about pay, albeit vague. But to be safe, maybe we include Pay section with that statement? However they said avoid filler like "commensurate with experience". "competitive salaries" is similar. I'd omit Pay section.
- Schedule: mentions "flexible work schedules with our 9/80 program". That's a schedule detail. So we could have Schedule section. It's specific: 9/80 program. So we can include Schedule.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Schedule.
We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. No Job ID.
We need to format lists with
- . For prose use
.
We need to include all responsibilities items as list items.
Responsibilities list from posting:
- Work closely with and assist engineers in the conduct of various engineering assignments
- Carry out basic work instructions that will help in understanding the fundamentals of the Company and also learn new things
- Conduct limited scope testing under the supervision of engineers
- Complete assigned tasks on time
- Gather and assemble data for engineers
- May be required to help in research in a particular field
- Conduct design analysis and/or calculations under the supervision of engineers
- Assist engineers with appropriate design details
- Must have good interpersonal skills and have the ability to build a good network (this appears also in qualifications; but it's listed under responsibilities; we should keep it as responsibility? It's duplicated; we should preserve all substantive information but not duplicate lines? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines: we should remove duplicated lines. The line "Must have good interpersonal skills and have the ability to build a good network" appears both in responsibilities and qualifications. We should keep only one instance? The instruction says remove duplicated lines. So we should keep it only once, perhaps under Qualifications (makes more sense). We'll remove from responsibilities.
- Perform a wide variety of tasks to gain familiarity with the engineering staff, methods, programs and practices
- Support, communicate, reinforce and defend the mission, values and culture of the organization
- Other duties as assigned
Thus responsibilities list items (excluding duplicated interpersonal skills). We'll keep others.
Qualifications list:
- High school diploma or GED
- Engineering student; some progress towards engineering degree
- Must be diligent, hardworking, and quick to learn
- Good understanding of software development using C/C++ and Python on Linux operating systems, with some experience on Windows as well.
- Good understanding of multi-threading and multi-processing concepts.
- Preferred Qualifications:
- Experienced in developing embedded drivers on Linux for interfaces such as TCP/IP, UART, I²C, PCIe, and others.
- Experienced in modern software development practices, including version control systems (Git), defect tracking tools (preferably Jira), peer code reviews, and Agile methodologies.
Also we had "Must have good interpersonal skills and have the ability to build a good network" (we kept). Also maybe "Must have good interpersonal skills..." we need to include.
Thus qualifications list includes interpersonal skills.
We should also include "Taking care of our people is a top priority..." but that's part of benefits intro; we already have benefits.
Now Benefits list:
- competitive salaries (maybe we keep as part of benefits? Actually it's pay; but we omitted Pay section. Could include as part of benefits? It says "competitive salaries and comprehensive benefits, including ...". So we can mention competitive salaries in benefits section as part of compensation. But we decided not to create Pay section; we can include "competitive salaries" within Benefits section as a bullet.
- medical, dental, and vision coverage
- a company contribution to a health savings account
- telemedicine
- life and disability insurance
- legal insurance
- a 401(k) savings plan
- wellness programs that focus on physical, emotional, and financial well-being
- flexible work schedules with our 9/80 program
- competitive vacation
- health/emergency leave
- paid parental leave
- community service hours
- Some employees are eligible for limited benefits only
We need to preserve all substantive information; we should not drop "Some employees are eligible for limited benefits only". Include as bullet.
Schedule: we have "flexible work schedules with our 9/80 program". Already covered in benefits; but schedule section could mention that. However we might avoid duplication. Since schedule is mentioned under benefits, we could still have a Schedule section referencing the 9/80 program. But to avoid duplication, we could keep schedule section and mention the 9/80 program; benefits section can still mention other benefits but not repeat schedule. However the instruction says preserve ALL substantive information; we can include it in both sections? That would be duplication. Better to include schedule only once. Since schedule is a specific detail, we could put it under Schedule section and not repeat in benefits. But benefits also mentions flexible work schedules with our 9/80 program; if we remove from benefits we lose that detail. However we could keep it in benefits and not have schedule section. The instruction says create Schedule section only if posting actually states them. It does state flexible work schedules with 9/80 program. So we could have Schedule section with that detail, and benefits section can still mention other benefits but not repeat the schedule line. However we would be omitting that line from benefits, which is part of the benefits description. But we could keep benefits section without that line, but then we lose that specific benefit mention. However the schedule section captures it. The instruction: preserve ALL substantive information; we can distribute it across sections; as long as each piece appears somewhere. So we can put the 9/80 program under Schedule, and not repeat under Benefits. That's fine.
Thus Benefits section will exclude the flexible work schedule line.
Now we need to format.
We'll output:
About the role
The Leonardo DRS Airborne and Intelligence Systems business is a global leader and strategic partner committed to delivering world-class, full life-cycle defense and intelligence products that protect the security of our nation and our allies. From air combat training to state-of-the-art electronic warfare systems, our technology is deployed by virtually all U.S. military and government agencies around the world.
Responsibilities
- Work closely with and assist engineers in the conduct of various engineering assignments
- Carry out basic work instructions that will help in understanding the fundamentals of the Company and also learn new things
- Conduct limited scope testing under the supervision of engineers
- Complete assigned tasks on time
- Gather and assemble data for engineers
- May be required to help in research in a particular field
- Conduct design analysis and/or calculations under the supervision of engineers
- Assist engineers with appropriate design details
- Perform a wide variety of tasks to gain familiarity with the engineering staff, methods, programs and practices
- Support, communicate, reinforce and defend the mission, values and culture of the organization
- Other duties as assigned
Qualifications
- High school diploma or GED
- Engineering student; some progress towards engineering degree
- Must be diligent, hardworking, and quick to learn
- Good understanding of software development using C/C++ and Python on Linux operating systems, with some experience on Windows as well.
- Good understanding of multi-threading and multi-processing concepts.
- Must have good interpersonal skills and have the ability to build a good network
- Preferred Qualifications:
- Experienced in developing embedded drivers on Linux for interfaces such as TCP/IP, UART, I²C, PCIe, and others.
- Experienced in modern software development practices, including version control systems (Git), defect tracking tools (preferably Jira), peer code reviews, and Agile methodologies.
But note: we have nested ul inside li for Preferred Qualifications. That's okay.
Alternatively we could have a separate subheading but we avoid many sections.
Now Benefits:
Benefits
- competitive salaries
- medical, dental, and vision coverage
- a company contribution to a health savings account
- telemedicine
- life and disability insurance
- legal insurance
- a 401(k) savings plan
- wellness programs that focus on physical, emotional, and financial well-being
- competitive vacation
- . For prose use
. We need to include all responsibilities items as list items. Responsibilities list from posting: - Work closely with and assist engineers in the conduct of various engineering assignments - Carry out basic work instructions that will help in understanding the fundamentals of the Company and also learn new things - Conduct limited scope testing under the supervision of engineers - Complete assigned tasks on time - Gather and assemble data for engineers - May be required to help in research in a particular field - Conduct design analysis and/or calculations under the supervision of engineers - Assist engineers with appropriate design details - Must have good interpersonal skills and have the ability to build a good network (this appears also in qualifications; but it's listed under responsibilities; we should keep it as responsibility? It's duplicated; we should preserve all substantive information but not duplicate lines? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines: we should remove duplicated lines. The line "Must have good interpersonal skills and have the ability to build a good network" appears both in responsibilities and qualifications. We should keep only one instance? The instruction says remove duplicated lines. So we should keep it only once, perhaps under Qualifications (makes more sense). We'll remove from responsibilities. - Perform a wide variety of tasks to gain familiarity with the engineering staff, methods, programs and practices - Support, communicate, reinforce and defend the mission, values and culture of the organization - Other duties as assigned Thus responsibilities list items (excluding duplicated interpersonal skills). We'll keep others. Qualifications list: - High school diploma or GED - Engineering student; some progress towards engineering degree - Must be diligent, hardworking, and quick to learn - Good understanding of software development using C/C++ and Python on Linux operating systems, with some experience on Windows as well. - Good understanding of multi-threading and multi-processing concepts. - Preferred Qualifications: - Experienced in developing embedded drivers on Linux for interfaces such as TCP/IP, UART, I²C, PCIe, and others. - Experienced in modern software development practices, including version control systems (Git), defect tracking tools (preferably Jira), peer code reviews, and Agile methodologies. Also we had "Must have good interpersonal skills and have the ability to build a good network" (we kept). Also maybe "Must have good interpersonal skills..." we need to include. Thus qualifications list includes interpersonal skills. We should also include "Taking care of our people is a top priority..." but that's part of benefits intro; we already have benefits. Now Benefits list: - competitive salaries (maybe we keep as part of benefits? Actually it's pay; but we omitted Pay section. Could include as part of benefits? It says "competitive salaries and comprehensive benefits, including ...". So we can mention competitive salaries in benefits section as part of compensation. But we decided not to create Pay section; we can include "competitive salaries" within Benefits section as a bullet. - medical, dental, and vision coverage - a company contribution to a health savings account - telemedicine - life and disability insurance - legal insurance - a 401(k) savings plan - wellness programs that focus on physical, emotional, and financial well-being - flexible work schedules with our 9/80 program - competitive vacation - health/emergency leave - paid parental leave - community service hours - Some employees are eligible for limited benefits only We need to preserve all substantive information; we should not drop "Some employees are eligible for limited benefits only". Include as bullet. Schedule: we have "flexible work schedules with our 9/80 program". Already covered in benefits; but schedule section could mention that. However we might avoid duplication. Since schedule is mentioned under benefits, we could still have a Schedule section referencing the 9/80 program. But to avoid duplication, we could keep schedule section and mention the 9/80 program; benefits section can still mention other benefits but not repeat schedule. However the instruction says preserve ALL substantive information; we can include it in both sections? That would be duplication. Better to include schedule only once. Since schedule is a specific detail, we could put it under Schedule section and not repeat in benefits. But benefits also mentions flexible work schedules with our 9/80 program; if we remove from benefits we lose that detail. However we could keep it in benefits and not have schedule section. The instruction says create Schedule section only if posting actually states them. It does state flexible work schedules with 9/80 program. So we could have Schedule section with that detail, and benefits section can still mention other benefits but not repeat the schedule line. However we would be omitting that line from benefits, which is part of the benefits description. But we could keep benefits section without that line, but then we lose that specific benefit mention. However the schedule section captures it. The instruction: preserve ALL substantive information; we can distribute it across sections; as long as each piece appears somewhere. So we can put the 9/80 program under Schedule, and not repeat under Benefits. That's fine. Thus Benefits section will exclude the flexible work schedule line. Now we need to format. We'll output:
About the role
The Leonardo DRS Airborne and Intelligence Systems business is a global leader and strategic partner committed to delivering world-class, full life-cycle defense and intelligence products that protect the security of our nation and our allies. From air combat training to state-of-the-art electronic warfare systems, our technology is deployed by virtually all U.S. military and government agencies around the world.
Responsibilities
- Work closely with and assist engineers in the conduct of various engineering assignments
- Carry out basic work instructions that will help in understanding the fundamentals of the Company and also learn new things
- Conduct limited scope testing under the supervision of engineers
- Complete assigned tasks on time
- Gather and assemble data for engineers
- May be required to help in research in a particular field
- Conduct design analysis and/or calculations under the supervision of engineers
- Assist engineers with appropriate design details
- Perform a wide variety of tasks to gain familiarity with the engineering staff, methods, programs and practices
- Support, communicate, reinforce and defend the mission, values and culture of the organization
- Other duties as assigned
Qualifications
- High school diploma or GED
- Engineering student; some progress towards engineering degree
- Must be diligent, hardworking, and quick to learn
- Good understanding of software development using C/C++ and Python on Linux operating systems, with some experience on Windows as well.
- Good understanding of multi-threading and multi-processing concepts.
- Must have good interpersonal skills and have the ability to build a good network
- Preferred Qualifications:
- Experienced in developing embedded drivers on Linux for interfaces such as TCP/IP, UART, I²C, PCIe, and others.
- Experienced in modern software development practices, including version control systems (Git), defect tracking tools (preferably Jira), peer code reviews, and Agile methodologies.
Benefits
- competitive salaries
- medical, dental, and vision coverage
- a company contribution to a health savings account
- telemedicine
- life and disability insurance
- legal insurance
- a 401(k) savings plan
- wellness programs that focus on physical, emotional, and financial well-being
- competitive vacation