Avionics Test Engineer I- Onsite
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for any list of duties/requirements/benefits, and
for prose.
- Do NOT repeat the job title as a heading (the page already shows it)
- Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it.
- Preserve ALL substantive information; do NOT invent or summarize away detail.
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
- 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.
- Prefer a few substantive sections over many thin ones.
- Output ONLY the HTML fragment — no /, no markdown code fences.
Now, analyze the input text.
The input includes:
- Date Posted: 2026-10-22
- Country: United States of America
- Location: US-MD-ANNAPOLIS-906 ~ 2551 Riva Rd ~ BLDG 906
- Position Role Type: Onsite
- U.S. Citizen, U.S. Person, or Immigration Status Requirements: U.S. citizenship is required...
- Security Clearance Type: None/Not Required
- Security Clearance Status: Not Required
- Then a paragraph about RTX internships, co-ops, full-time careers.
- "What You Will Do" section with bullet points (duties).
- "What We Offer" (first occurrence) with bullet points (benefits/experience).
- "Qualifications You Must Have" with bullet points.
- "Qualifications We Prefer" with bullet points.
- "What We Offer" (second occurrence) with values and then relocation eligibility, etc.
- Then a bunch of boilerplate: "Learn More & Apply Now!", role type definition, salary range, benefits details, application window, EEO statement, privacy policy.
I need to extract substantive sections.
Potential sections:
- About the role (maybe a brief intro)
- Responsibilities (from "What You Will Do")
- Requirements (from "Qualifications You Must Have")
- Preferred Qualifications (from "Qualifications We Prefer")
- Benefits (from "What We Offer" first occurrence? Actually first "What We Offer" lists hands-on experience, mentorship, opportunities, collaborative environment. Second "What We Offer" lists values and then relocation eligibility, salary range, benefits, etc. But the second is more about compensation and benefits. However, the rules say: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state salary range and benefits. So we can include Pay and Benefits sections.
But note: The second "What We Offer" includes values (Safety, Trust, etc.) and then "Relocation Eligibility Learn More & Apply Now!" then role type definition, salary range, benefits details. That's a mix.
We need to structure:
- Maybe a short intro paragraph about the role (from the paragraph after security clearance).
- Responsibilities: list from "What You Will Do"
- Requirements: list from "Qualifications You Must Have"
- Preferred Qualifications: list from "Qualifications We Prefer"
- Benefits: from first "What We Offer" (hands-on experience, mentorship, etc.) and also from the second part (medical, dental, etc.) but the second part is more detailed benefits. However, the second part is under "What We Offer" but includes salary range and benefits. The rules: include a section ONLY when the posting has real, specific content for it. The posting does have specific benefits listed. So we can have a Benefits section.
- Pay: salary range is given: 57,200 USD - 108,800 USD. So we can have a Pay section.
- Schedule: The role type is Onsite, and there's a description of onsite. Could include a Schedule section? The posting says "Onsite: Employees who are working in Onsite roles will work primarily onsite." That's schedule info. But the rules say never create Schedule sections unless the posting actually states them. It does state onsite. Could include a Schedule section with that info.
- Location: The location is given. Could include a Location section? Not in the list of headings but we can include as a paragraph.
- Citizenship/Clearance: U.S. citizenship required, security clearance not required. Could include a Requirements section? But we already have Requirements for qualifications. Maybe a separate "Clearance & Citizenship" section? The rules don't specify that heading. Could fold into a short paragraph.
The rules: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings.
We need to avoid duplicating job title. The job title is not explicitly given but likely "Avionics Test Engineer". The page already shows it, so we don't include as heading.
We need to fold minor metadata (date posted, location, role type) into a short
or drop it. Probably include a short paragraph at the top with location, role type, citizenship requirement.
Now, let's structure:
1. Intro paragraph: "We are seeking a highly motivated Avionics Test Engineer to join our Systems Engineering team. In this role, you will support the testing and verification of avionics hardware using detailed test plans based on industry standards and specifications. This role is ideal for individuals with interest in avionics systems, communication protocols, and network technologies to begin building their engineering career. This candidate will become a test engineer on our Qualification testing team, collaborating with internal Engineering and Implementation teams and datalink manufacturers."
2. Responsibilities: from "What You Will Do" bullet points.
3. Requirements: from "Qualifications You Must Have" bullet points.
4. Preferred Qualifications: from "Qualifications We Prefer" bullet points.
5. Benefits: from first "What We Offer" (hands-on experience, mentorship, opportunities, collaborative environment) and also from the second part (medical, dental, vision, life insurance, etc.). But the second part is more comprehensive. However, the second part is under "What We Offer" but includes salary range and benefits. The first "What We Offer" is more about the internship/early career experience. The second "What We Offer" is about values and then benefits. Actually the second "What We Offer" starts with "Our values drive our actions..." then lists values, then "Relocation Eligibility Learn More & Apply Now!" then role type definition, salary range, benefits. That's a mix. I think we should separate: Benefits section includes the list of benefits from the second part (medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, and holidays). Also include the first "What We Offer" as maybe "What We Offer" section? But the heading "Benefits" is more appropriate.
6. Pay: salary range.
7. Schedule: onsite description.
8. Location and citizenship: maybe a short paragraph.
Also note: The posting includes "May require some travel." That could be in Responsibilities or Schedule.
Now, we must not include boilerplate: EEO statement, privacy policy, application instructions, "Learn More & Apply Now!", "Relocation Eligibility", "RTX anticipates the application window closing...", etc.
We must preserve ALL substantive information. So we need to include the details like industry standards (AEEC 618, 620, 758 and RTCA MASPS & MOPS), test equipment, etc.
Now, write HTML.
We'll start with a paragraph for metadata: location, role type, citizenship, clearance.
Then sections.
Let's draft.
Location: Annapolis, MD (2551 Riva Rd, BLDG 906). Role type: Onsite. U.S. citizenship required; security clearance not required.
About the role
We are seeking a highly motivated Avionics Test Engineer to join our Systems Engineering team. In this role, you will support the testing and verification of avionics hardware using detailed test plans based on industry standards and specifications. This role is ideal for individuals with interest in avionics systems, communication protocols, and network technologies to begin building their engineering career. This candidate will become a test engineer on our Qualification testing team, collaborating with internal Engineering and Implementation teams and datalink manufacturers.
Responsibilities
- Execute test procedures on avionics hardware in accordance with established test plans and industry specifications (e.g., AEEC 618, 620, 758 and RTCA MASPS & MOPS).
- Set up, configure, and operate test equipment, instrumentation, and simulation tools.
- Collect, analyze, and document test results with attention to accuracy and traceability.
- Collaborate with systems, hardware, and software engineers to troubleshoot issues and support avionics testing.
- Contribute to updates of test plans, procedures, and test reports.
- Maintain test environments, equipment, and lab configurations in good working order.
- Support continuous improvement efforts related to test methods, automation, and processes.
- Demonstrate strong problem‑solving skills and maintain a high level of attention to detail in all tasks and projects.
- Communicate effectively through clear, concise written documentation and professional verbal communication across various audiences.
- Work independently to complete assignments while also collaborating effectively within team environments to achieve shared goals.
- May require some travel.
Requirements
- Bachelor's degree in Electrical Engineering, Computer Engineering or related Science, Technology, Engineering or Mathematics (STEM) major obtained by start date.
- IP Communication course work or work experience.
- Experience reading and following technical documentation, schematics, and test procedures (experience may be obtained through on-the-job experience, research, coursework, or projects).
Preferred Qualifications
- Experience with test equipment such as oscilloscopes, multimeters, or protocol analyzers.
- Basic understanding of avionics systems, electronics, or embedded systems.
- Familiarity with communication and network protocols such as ACARS, ARINC 429, or similar.
- Exposure to automated test frameworks or scripting languages (Python, MATLAB, etc.).
- Understanding of requirements-based testing and verification processes.
- Internship or project experience involving avionics, embedded systems, or electronics testing.
- Experience communicating with vendors or customers through both verbal and written channels.
- Ability to deliver presentations comfortably and confidently.
Benefits
- Hands-on experience with industry-standard avionics hardware and tools.
- Mentorship from experienced engineers.
- Opportunities for technical growth and professional development.
- A collaborative environment focused
for prose. - Do NOT repeat the job title as a heading (the page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - 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. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no /, no markdown code fences. Now, analyze the input text. The input includes: - Date Posted: 2026-10-22 - Country: United States of America - Location: US-MD-ANNAPOLIS-906 ~ 2551 Riva Rd ~ BLDG 906 - Position Role Type: Onsite - U.S. Citizen, U.S. Person, or Immigration Status Requirements: U.S. citizenship is required... - Security Clearance Type: None/Not Required - Security Clearance Status: Not Required - Then a paragraph about RTX internships, co-ops, full-time careers. - "What You Will Do" section with bullet points (duties). - "What We Offer" (first occurrence) with bullet points (benefits/experience). - "Qualifications You Must Have" with bullet points. - "Qualifications We Prefer" with bullet points. - "What We Offer" (second occurrence) with values and then relocation eligibility, etc. - Then a bunch of boilerplate: "Learn More & Apply Now!", role type definition, salary range, benefits details, application window, EEO statement, privacy policy. I need to extract substantive sections. Potential sections: - About the role (maybe a brief intro) - Responsibilities (from "What You Will Do") - Requirements (from "Qualifications You Must Have") - Preferred Qualifications (from "Qualifications We Prefer") - Benefits (from "What We Offer" first occurrence? Actually first "What We Offer" lists hands-on experience, mentorship, opportunities, collaborative environment. Second "What We Offer" lists values and then relocation eligibility, salary range, benefits, etc. But the second is more about compensation and benefits. However, the rules say: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state salary range and benefits. So we can include Pay and Benefits sections. But note: The second "What We Offer" includes values (Safety, Trust, etc.) and then "Relocation Eligibility Learn More & Apply Now!" then role type definition, salary range, benefits details. That's a mix. We need to structure: - Maybe a short intro paragraph about the role (from the paragraph after security clearance). - Responsibilities: list from "What You Will Do" - Requirements: list from "Qualifications You Must Have" - Preferred Qualifications: list from "Qualifications We Prefer" - Benefits: from first "What We Offer" (hands-on experience, mentorship, etc.) and also from the second part (medical, dental, etc.) but the second part is more detailed benefits. However, the second part is under "What We Offer" but includes salary range and benefits. The rules: include a section ONLY when the posting has real, specific content for it. The posting does have specific benefits listed. So we can have a Benefits section. - Pay: salary range is given: 57,200 USD - 108,800 USD. So we can have a Pay section. - Schedule: The role type is Onsite, and there's a description of onsite. Could include a Schedule section? The posting says "Onsite: Employees who are working in Onsite roles will work primarily onsite." That's schedule info. But the rules say never create Schedule sections unless the posting actually states them. It does state onsite. Could include a Schedule section with that info. - Location: The location is given. Could include a Location section? Not in the list of headings but we can include as a paragraph. - Citizenship/Clearance: U.S. citizenship required, security clearance not required. Could include a Requirements section? But we already have Requirements for qualifications. Maybe a separate "Clearance & Citizenship" section? The rules don't specify that heading. Could fold into a short paragraph. The rules: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings. We need to avoid duplicating job title. The job title is not explicitly given but likely "Avionics Test Engineer". The page already shows it, so we don't include as heading. We need to fold minor metadata (date posted, location, role type) into a short
or drop it. Probably include a short paragraph at the top with location, role type, citizenship requirement. Now, let's structure: 1. Intro paragraph: "We are seeking a highly motivated Avionics Test Engineer to join our Systems Engineering team. In this role, you will support the testing and verification of avionics hardware using detailed test plans based on industry standards and specifications. This role is ideal for individuals with interest in avionics systems, communication protocols, and network technologies to begin building their engineering career. This candidate will become a test engineer on our Qualification testing team, collaborating with internal Engineering and Implementation teams and datalink manufacturers." 2. Responsibilities: from "What You Will Do" bullet points. 3. Requirements: from "Qualifications You Must Have" bullet points. 4. Preferred Qualifications: from "Qualifications We Prefer" bullet points. 5. Benefits: from first "What We Offer" (hands-on experience, mentorship, opportunities, collaborative environment) and also from the second part (medical, dental, vision, life insurance, etc.). But the second part is more comprehensive. However, the second part is under "What We Offer" but includes salary range and benefits. The first "What We Offer" is more about the internship/early career experience. The second "What We Offer" is about values and then benefits. Actually the second "What We Offer" starts with "Our values drive our actions..." then lists values, then "Relocation Eligibility Learn More & Apply Now!" then role type definition, salary range, benefits. That's a mix. I think we should separate: Benefits section includes the list of benefits from the second part (medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, and holidays). Also include the first "What We Offer" as maybe "What We Offer" section? But the heading "Benefits" is more appropriate. 6. Pay: salary range. 7. Schedule: onsite description. 8. Location and citizenship: maybe a short paragraph. Also note: The posting includes "May require some travel." That could be in Responsibilities or Schedule. Now, we must not include boilerplate: EEO statement, privacy policy, application instructions, "Learn More & Apply Now!", "Relocation Eligibility", "RTX anticipates the application window closing...", etc. We must preserve ALL substantive information. So we need to include the details like industry standards (AEEC 618, 620, 758 and RTCA MASPS & MOPS), test equipment, etc. Now, write HTML. We'll start with a paragraph for metadata: location, role type, citizenship, clearance. Then sections. Let's draft.
Location: Annapolis, MD (2551 Riva Rd, BLDG 906). Role type: Onsite. U.S. citizenship required; security clearance not required.
About the role
We are seeking a highly motivated Avionics Test Engineer to join our Systems Engineering team. In this role, you will support the testing and verification of avionics hardware using detailed test plans based on industry standards and specifications. This role is ideal for individuals with interest in avionics systems, communication protocols, and network technologies to begin building their engineering career. This candidate will become a test engineer on our Qualification testing team, collaborating with internal Engineering and Implementation teams and datalink manufacturers.
Responsibilities
- Execute test procedures on avionics hardware in accordance with established test plans and industry specifications (e.g., AEEC 618, 620, 758 and RTCA MASPS & MOPS).
- Set up, configure, and operate test equipment, instrumentation, and simulation tools.
- Collect, analyze, and document test results with attention to accuracy and traceability.
- Collaborate with systems, hardware, and software engineers to troubleshoot issues and support avionics testing.
- Contribute to updates of test plans, procedures, and test reports.
- Maintain test environments, equipment, and lab configurations in good working order.
- Support continuous improvement efforts related to test methods, automation, and processes.
- Demonstrate strong problem‑solving skills and maintain a high level of attention to detail in all tasks and projects.
- Communicate effectively through clear, concise written documentation and professional verbal communication across various audiences.
- Work independently to complete assignments while also collaborating effectively within team environments to achieve shared goals.
- May require some travel.
Requirements
- Bachelor's degree in Electrical Engineering, Computer Engineering or related Science, Technology, Engineering or Mathematics (STEM) major obtained by start date.
- IP Communication course work or work experience.
- Experience reading and following technical documentation, schematics, and test procedures (experience may be obtained through on-the-job experience, research, coursework, or projects).
Preferred Qualifications
- Experience with test equipment such as oscilloscopes, multimeters, or protocol analyzers.
- Basic understanding of avionics systems, electronics, or embedded systems.
- Familiarity with communication and network protocols such as ACARS, ARINC 429, or similar.
- Exposure to automated test frameworks or scripting languages (Python, MATLAB, etc.).
- Understanding of requirements-based testing and verification processes.
- Internship or project experience involving avionics, embedded systems, or electronics testing.
- Experience communicating with vendors or customers through both verbal and written channels.
- Ability to deliver presentations comfortably and confidently.
Benefits
- Hands-on experience with industry-standard avionics hardware and tools.
- Mentorship from experienced engineers.
- Opportunities for technical growth and professional development.
- A collaborative environment focused