Electrical Engineer II/III

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, "Who We Are" is description of company; not needed as a section? Possibly "About the role" corresponds to "About This Role". So we can have

About the role

with content from "About This Role" paragraph. Responsibilities: The bullet list after "you will be responsible for:" includes items: Perform detailed design..., Contribute to concept..., Prepare high-quality..., Support proposal activity..., Experience with radio communication..., Knowledge and experience with computer-aided design tools..., Experience with power electronic circuit design... Actually many of those are responsibilities/requirements. We need to separate responsibilities vs qualifications vs skills. The posting includes "Qualifications Engineer II Qualifications" and "Engineer III Qualifications". Those are qualifications sections. Also there is a list of skills: experience with test equipment, etc. We need to decide what goes where. We have "About This Role" paragraph: "We believe people should love what they do – in this role, you will be responsible for: ..." Actually the colon then list. So we could treat that as responsibilities. Thus

About the role

maybe not needed; but we can put that as a short paragraph. Better: Use

About the role

with the paragraph describing role purpose (first sentence). Then responsibilities list. But the instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections. We need to decide content for each. Let's extract: - About the role: maybe the first sentence: "We believe people should love what they do – in this role, you will be responsible for:" Actually that's leading to responsibilities. Could combine. But we can put About the role as a brief description: "We believe people should love what they do – in this role, you will be responsible for: ..."? Might be redundant. Maybe better: About the role: short description of the team/business area: "This role is in Textron System’s Uncrewed Land and Air Systems business area." plus "We make things that fly..." etc. That's from Who We Are. But that is company description, not role. However we can still use it as About the role? Might be okay. But we must not invent content. We can use the "Who We Are" paragraph as about the company, but the instruction says section headings like About the role, Responsibilities etc. It didn't forbid using company description under About the role. It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can include About the role with content from "Who We Are" and maybe the first sentence. But we must not repeat the job title as a heading. Not needed. We must not include Job ID etc. We must not include boilerplate like EEO, legal, etc. We must not include application instructions. We must not include duplicated lines. We need to preserve all substantive information. Let's list substantive info: Company description: "We are Textron Systems, best known for innovative defense technologies and services. We make things that fly, hover, zoom and launch. Things that move people. Protect soldiers. Power industries. We serve customers in industries spanning aerospace and defense, specialized vehicles, turf care and fuel systems. We are a part of Textron Inc, one of the world’s leading multi-industry companies, recognized for its powerful brands such as Bell, Cessna, Beechcraft, E-Z-GO and many more. This role is in Textron System’s Uncrewed Land and Air Systems business area. Visit TextronSystems.com & HoweandHowe.com to read more about who we are and the products we make!" That's substantive. About This Role: "We believe people should love what they do – in this role, you will be responsible for:" then list. Responsibilities list items: - Perform detailed design of electrical and electronic assemblies and analysis, integration, and testing - Contribute to concept development as part of internal cross-functional design teams, including prototyping and production support - Prepare high-quality formal engineering documentation such as drawings, presentations, specifications, design presentations to customers, test plans, and test reports - Support proposal activity, providing input to cost estimates and risk assessments - Experience with radio communication systems, antenna specification, and electromagnetic interference mitigation, programming for small, embedded processors, and control systems including PID control loops - Knowledge and experience with computer-aided design tools is required; LabVIEW, MATLAB, Zuken, Mentor Graphics, Altium, Microsoft Visio, Capital Harness XC - Experience with power electronic circuit design, MOSFETs, schematic capture, board layout techniques, and circuit board manufacturing, drive circuit development for brushless DC motors, and serial data communication both single-ended and balanced. Note: Some of those are actually qualifications/skills but they appear in responsibilities list. Qualifications: Engineer II Qualifications: - Master’s or bachelor’s degree in electrical or computer engineering - Minimum 2 years’ experience in industry - Experience operating test equipment such as oscilloscopes, spectrum analyzers, signal generators, and cable design including insulation and jacket materials and installation requirements for aircraft and/or ground vehicle applications - Eligible to obtain/maintain a security clearance (Secret level) Engineer III Qualifications: - Master’s or bachelor’s degree in electrical or computer engineering - Minimum 4 years’ experience in industry - Experience operating test equipment such as oscilloscopes, spectrum analyzers, signal generators, and cable design including insulation and jacket materials and installation requirements for aircraft and/or ground vehicle applications - Excellent written and oral communications. - Customer interfacing and ability to build relationships. - Ability to work in teams and independently with minimal direction. - Capable of leading a small team. - Demonstrates ability to provide solutions to a wide range of technical problems. - Eligible to obtain/maintain a security clearance (Secret level) Skills: maybe combine test equipment experience etc. But we already have those in qualifications. Benefits: list from "How We Care": Flexible Work Schedules, Education Assistance, Career Development & Training Opportunities, Wellness Program (including Fitness Reimbursement), Medical, Dental, Vision & 401(K) with Company Funding, Paid Parental Leave. Also later: "Textron’s compensation package includes competitive base pay and provides eligible employees with benefit programs. Benefits may include health insurance and prescription plan coverage, dental insurance, family building benefits, vision insurance, mental health resources, flexible spending accounts, health savings accounts, retirement savings plans, life and disability insurance programs, and programs that provide employees time away from work." Pay: "In compliance with the local pay transparency law, the pay range for this position is $88,200 - $167,900 per year." Schedule: "Schedule: Full-time" also "Shift: First Shift", "Travel: Yes, 10 % of the Time". So schedule info includes full-time, first shift, travel 10%. We need to output sections only if they have real specific content. All these have. We must not include placeholder like "commensurate with experience". Not present. We need to avoid duplication: The qualifications for Engineer II and III overlap; we could combine? But we should preserve all substantive info. Could present as two sub-sections under Qualifications? But we only allowed headings as listed; we could have a Qualifications section and inside include both Engineer II and Engineer III details maybe as paragraphs. We must not invent headings beyond those listed. So we can have

Qualifications

and then include paragraphs with the details. Similarly Skills: maybe we can extract skills like experience with test equipment, radio communication, etc. But those already appear in qualifications and responsibilities. To avoid duplication, we could still list them under Skills if they are distinct. But risk of duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include all info, but we can group them logically; duplication is okay if it's present in multiple places? The posting has overlapping content; we should not lose any. If we put test equipment experience only under Qualifications, we still have it. If we also list under Skills, we would be duplicating but that's okay as long as we preserve. However duplication might be considered unnecessary but not prohibited. Safer to include each piece once, but ensure we didn't drop any. Let's map: Company description -> About the role (maybe). Could also be a separate section like "About the company" but not in allowed headings. So we put under About the role. About This Role paragraph -> maybe also under About the role. Responsibilities: the list after "you will be responsible for:" (including the first 4 items? Actually the list includes also experience with radio communication etc. Those might be considered responsibilities but also skills. We'll put them under Responsibilities. Qualifications: Engineer II and Engineer III bullet points. Skills: maybe we can extract any remaining skill-specific items not covered: "Experience with radio communication systems, antenna specification, and electromagnetic interference mitigation, programming for small, embedded processors, and control systems including PID control loops" (already in responsibilities). "Knowledge and experience with computer-aided design tools is required; LabVIEW, MATLAB, Zuken, Mentor Graphics, Altium, Microsoft Visio, Capital Harness XC" (also in responsibilities). "Experience with power electronic circuit design, MOSFETs, schematic capture, board layout techniques, and circuit board manufacturing, drive circuit development for brushless DC motors, and serial data communication both single-ended and balanced." (also responsibilities). So all skill items are already in responsibilities. So we could omit Skills section to avoid duplication, but we must preserve all substantive info; they are already preserved under Responsibilities. That's fine. Benefits: list from How We Care plus later paragraph. Pay: the range. Schedule: Full-time, First Shift, Travel 10%. We also have "AI Readiness" paragraph: "Textron expects employees to use AI-enabled tools responsibly and effectively..." That's substantive; we need to include it somewhere. Where fits? Could be under Qualifications or maybe a separate section like "Additional Information". But not in allowed headings. Could incorporate under Qualifications as a note? Or maybe under About the role? The instruction says we can use those headings; we could also add other headings if needed? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we need to fit AI readiness somewhere, maybe under Qualifications or Responsibilities? It's about expectations; could be under Qualifications as a bullet. Also "EEO Statement" must be removed (boilerplate). So we drop that. Also "Recruiting Company: Textron Systems Primary Location: US-Maryland-Hunt Valley Job Function: Engineering Schedule: Full-time Job Level: Individual Contributor Job Type: Experienced Shift: First Shift Travel: Yes, 10 % of the Time Job Posting: 09/23/2026, 12:00:00 AM Job Number: 345212" Some of this is metadata; we should not put Job ID/requisition numbers as headings; we can fold minor metadata into a short

or drop it. So we could include location, job function, etc. in a short paragraph maybe under About the role or separate? But we have Schedule section already; we can include shift and travel there. Location maybe not needed but could be included in About the role paragraph. We must not include duplicated