Principal Electrical Engineer- Computing Products (Onsite)
or drop it." So we can include location maybe as a short paragraph? The posting includes location: US-IA-CEDAR RAPIDS-193 ~ 1120 Collins Rd NE ~ BLDG193. That's location metadata; we can fold into a short
maybe under About the role? But we need to preserve all substantive information. The location is substantive? It's location of job. Could include a short paragraph after heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have sections with those headings. We need to decide which sections have content. Let's extract content: About the role: The description about role: "We are seeking a highly motivated Principal Electrical Engineer to join the Computing Products Department within the Displays, Computing & Networking Directorate. This department is responsible for the development and sustainment of state-of-the-art avionics hardware products including ruggedized mission computers, video processing modules, and network products used in commercial and military aircraft platforms. This role is onsite, in Cedar Rapids, Iowa. This role supports all phases of the hardware development lifecycle—program pursuit, design, integration, verification, and factory transition. The selected candidate will collaborate closely with cross-functional partners, including Systems, Software, Mechanical, Environmental Effects, Manufacturing/Operations, and Design-to-Cost teams, to ensure all product requirements are successfully achieved. Strong expertise in high-speed digital circuit board design, EMI control, manufacturability, testability, and thermal management is essential. This role is specifically to lead on KC-46 VRCU and VPU Integration activities followed by other Boeing computer efforts with the DPC product line. The principal engineer will have responsibilities that include lead P1, P2, and P3's in integration and qual preparation and testing, collaborating with three other team leads (project engineering, over design lead, and cert lead), support platform and equipment systems request for trouble-shooting support and root causing failures that occur during testing. Once the KC-46 program HW is completed, this team also works on DPC-2120/7000 programs for commercial aircraft." That's a lot; we can put under About the role. Responsibilities: The "What You Will Do:" list: Designing Circuit Cards for Avionics Computers. Attend review or planning meetings to collaborate with other engineers on designs. Trouble-shooting circuit cards or full computers design hardware in a lab environment. Designing test solutions to prove design is compliant. Oversee qualification testing and root cause any failures to this testing. Mentoring and delegating tasks to less experienced engineers working the integration part of the KC-46 program.
or drop. The requirement about U.S. Person is substantive. Also security clearance not required is maybe not needed but could be included. We'll include a Requirements section with that info. Qualifications: "Qualifications You Must Have:" and "Qualifications We Prefer:" We'll combine into Qualifications section. Skills: Could be extracted from preferences: Hardware requirements development, experience with lab equipment, ability to work collaboratively, schematic capture, PWB layout, interfacing with complex embedded devices, digital logic device development (FPGA/ASIC), formal qualification experience (DO-160 or MIL-STD-810/461), understanding of DTC+, DFM, DFT. Also from must-have: degree STEM + 8 years experience or advanced degree +5 years, experience in EE role, hands-on troubleshooting. Those could be qualifications rather than skills. But we can still have Skills section for specific technical skills: schematic capture, PWB layout, etc. However we need to avoid thin sections. Perhaps combine Qualifications and Skills? But instruction says we can have sections for each if they have real content. We'll have Qualifications (must have + preferred) and Skills (technical skills). Might be okay. Benefits: The "What We Offer" list includes many benefits. We'll include Benefits section. Pay: Salary range: "The salary range for this role is 107,500 USD - 204,500 USD." Also mention that it's a good faith estimate. We'll include Pay section. Schedule: There's mention of onsite, or , no markdown fences. Let's craft. Structure:
About the role
...
Maybe include location as part of About the role paragraph.Responsibilities
- ... ...
Requirements
U.S. Person requirement ... Security clearance not required.
Qualifications
Must have: ...
Preferred: ...
Alternatively we could use- for must-have and preferred.
But we need to preserve details: Must have: Typically requires a degree in STEM and minimum 8 years prior relevant experience or an Advanced Degree in a related field and minimum 5 years of experience. Experience in an Electrical Engineering role. Hands-on troubleshooting experience.
Preferred: Hardware requirements development including working with systems and subsystems teams to determine meaningful and testable requirements for the design. Experience working with standard lab equipment for integration testing of hardware designs. Ability to work collaboratively with team members and independently on assigned tasks. Schematic capture of digital/analog mixed signal electrical circuit designs. Printed board (PWB) layout expertise. Interfacing with complex embedded devices (microprocessors, graphics processors, memory). Digital logic device development (including FPGA and ASIC development). Formal qualification experience (preferred DO-160 or MIL-STD-810/MIL-STD-461 standards). Understanding of Design to Cost (DTC+), Design for Manufacturing (DFM), Design for Test (DFT).
We could put these as
- under Qualifications.
Skills: maybe we could extract from preferred list as skills; but we already have them in Qualifications. Might be redundant. Could skip Skills section.
But instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications and Skills into one Qualifications section. We'll not create Skills.
Benefits: list many items. We'll put as
- .
Pay:
The salary range for this role is 107,500 USD - 204,500 USD.
Schedule:Onsite role located in Cedar Rapids, Iowa; We also need to include location maybe in About the role or Schedule. We'll put location in About the role paragraph. Now ensure we don't include boilerplate: Remove "Date Posted", "Country", "Location", "Position Role Type", "U.S. Citizen, U.S. Person, or Immigration Status Requirements:" we keep the substance but not the heading. Also remove "Security Clearance Type: None/Not Required Security Clearance Status: Not Required" we keep substance. Remove "Learn More & Apply Now!" and subsequent promotional paragraphs about Collins Aerospace etc. That's boilerplate? It's promotional but maybe substantive? It's about company description; could be considered boilerplate but it's part of posting. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The promotional paragraphs about Collins Aerospace might be considered boilerplate but they are not legal/EEO. However they are generic marketing. Might be considered boilerplate? The instruction says to remove duplicated lines and application instructions. It doesn't explicitly say to remove company overview. But to be safe, we might keep the initial paragraph about RTX and Collins Aerospace as part of About the role? It's somewhat generic but still substantive about the company. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." The company overview is substantive? It's describing the company; could be considered part of job posting. I'd keep it in About the role maybe as a brief intro. But we already have a lot in About the role; we can include that as a preceding paragraph. Let's craft About the role paragraph: Combine the company overview and role specifics. Company overview: "At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Collins Aerospace is a leader in technologically advanced, intelligent solutions that help redefine the aerospace and defense industry. With a comprehensive portfolio and deep technical expertise, we help customers meet the demands of the global market." Then role specifics: "We are seeking a highly motivated Principal Electrical Engineer to join the Computing Products Department within the Displays, Computing & Networking Directorate. This department is responsible for the development and sustainment of state-of-the-art avionics hardware products including ruggedized mission computers, video processing modules, and network products used in commercial and military aircraft platforms. This role is onsite, in Cedar Rapids, Iowa. This role supports all phases of the hardware development lifecycle—program pursuit, design, integration, verification, and factory transition. The selected candidate will collaborate closely with cross-functional partners, including Systems, Software, Mechanical, Environmental Effects, Manufacturing/Operations, and Design-to-Cost teams, to ensure all product requirements are successfully achieved. Strong expertise in high-speed digital circuit board design, EMI control, manufacturability, testability, and thermal management is essential. This role is specifically to lead on KC-46 VRCU and VPU Integration activities followed by other Boeing computer efforts with the DPC product line. The principal engineer will have responsibilities that include lead P1, P2, and P3's in integration and qual preparation and testing, collaborating with three other team leads (project engineering, over design lead, and cert lead), support platform and equipment systems request for trouble-shooting support and root causing failures that occur during testing. Once the KC-46 program HW is completed, this team also works on DPC-2120/7000 programs for commercial aircraft." We'll put that in
maybe multiple paragraphs but we can combine. Now Responsibilities: list from "What You Will Do:" plus maybe the <10% travel as needed? Actually travel is mentioned there; we can include in Responsibilities as a bullet. Responsibilities bullets: - Designing Circuit Cards for Avionics Computers. - Attend review or planning meetings