Senior Research and Development (R&D) Networked Electronic Warfare Test Engineer

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must include sections only when posting has real specific content. We have content: Company Overview, Department Overview, Job Description (THE OPPORTUNITY), Role And Responsibilities (list), Travel Requirements, Required Qualifications, Preferred Knowledge, Skills, And Abilities, Working Conditions And Physical Requirements, COMPENSATION, Benefits list, etc. Also there is some repeated sections like Basic Requirements duplicate of Required Qualifications. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove repeated EEO statement etc. Also remove "NOTE - As a US Federal Contractor..." maybe that's legal boilerplate? It's about citizenship requirement; but citizenship is already in Required Qualifications. Might be considered boilerplate? It's specific to the job? It says "NOTE - As a US Federal Contractor, Silvus Technologies requires that ALL candidates being considered for employment for any position (regardless of level) MUST be a U.S. Person (permanent resident or citizen). Stricter U.S. Citizen ONLY requirements (needed for some Engineering or R&D roles) will be included in the Required Qualifications section of the posted position. This does NOT apply to international positions; only job postings for positions located in the US." This is somewhat legal but also informs about citizenship requirement. Since citizenship is already in Required Qualifications, maybe we can drop this note as boilerplate. Also "Consistent with Motorola Solutions values and applicable law, we provide the following information to promote pay transparency and equity." That's boilerplate about pay transparency; we have actual pay range, we can keep the pay range but drop the surrounding sentence. Also "Our U.S. Benefits Include ..." is benefits section; we keep that. We need to structure: maybe sections: About the role (could combine Company Overview and Department Overview? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when we have content. We need to decide which sections to include. We have content for: - About the role: could be the job description overview (THE OPPORTUNITY) plus maybe company overview? The "About the role" heading is generic; we can put the job description summary there. - Responsibilities: list from Role And Responsibilities. - Requirements: maybe combine Required Qualifications and Basic Requirements (they are same). We'll put under Requirements. - Qualifications: maybe separate? Actually Requirements and Qualifications often overlap. But we have both Required Qualifications and Preferred Knowledge, Skills, And Abilities. Could treat Required Qualifications as Qualifications, and Preferred as Skills. Or we could have Requirements (mandatory) and Skills (preferred). The instruction list includes Requirements, Qualifications, Skills. We need to decide. We have: - Required Qualifications (mandatory): Bachelor's degree, 10 years experience, etc. - Preferred Knowledge, Skills, And Abilities: advanced degree, TCP/IP networking, ability to work independently, etc. Thus we can map: - Qualifications: Required Qualifications (mandatory) - Skills: Preferred Knowledge, Skills, And Abilities - Requirements: maybe we could also include Travel Requirements? But Travel Requirements is separate; maybe we could put under Schedule? Actually Travel Requirements is about occasional travel. Could be part of Schedule? Not exactly. There's also Working Conditions And Physical Requirements. Could be under Requirements? Might be better to have a separate section for Working Conditions? Not in list. Could incorporate into Requirements or Skills? Probably better to create a section "Requirements" for mandatory qualifications, and "Skills" for preferred. Then we can have "Pay" section for compensation. "Benefits" for benefits. "Schedule" maybe we have schedule: "This position is fully onsite, Monday through Friday". That's schedule info. Also travel requirements occasional travel. Could be part of Schedule? We'll put schedule info under Schedule heading. We also have Working Conditions And Physical Requirements: could be part of Requirements? Might be better to include under Requirements as additional details. But we have no specific heading for Working Conditions; we could embed within Requirements or maybe under a separate heading like "Working Conditions" but not in allowed list. Since we must only use headings from the list, we should not create other headings. So we need to fit that info into one of the allowed headings. Perhaps we can put Working Conditions under Requirements (as part of job requirements). Or we could put under Skills? Not ideal. We'll put under Requirements. Also we have Travel Requirements: occasional travel away from office, including overnight. Could be under Schedule (as travel schedule). We'll include under Schedule. Now we need to avoid duplicating lines. We'll consolidate. Let's extract substantive content: Company Overview: At Motorola Solutions, we believe that everything starts with our people. We’re a global close-knit community, united by the relentless pursuit to help keep people safer everywhere. We build and connect technologies to help protect people, property and places. Our solutions foster the collaboration that’s critical for safer communities, safer schools, safer hospitals, safer businesses, and ultimately, safer nations. Connect with a career that matters, and help us build a safer future. Department Overview: Silvus Technologies, a leading provider of advanced MANET and MIMO communications systems, is reshaping mesh network technology for mission-critical applications – on the ground, in the air and at sea. Its battle-proven StreamCaster family of MANET radios and proprietary MN-MIMO waveform provides the vital communications link for defense, law enforcement and public safety agencies around the world, and in the toughest operational environments. Silvus Technologies is a wholly owned subsidiary of Motorola Solutions, Inc. Would you like to join an incredibly talented group of people, doing very challenging work, with the prime directive of “Keeping Our Heroes Connected”? Job Description THE OPPORTUNITY: Silvus is seeking a Senior Research and Development (R&D) Networked Electronic Warfare Test Engineer who will report to the Senior R&D Director, Electronic Warfare. The successful individual in this role will understand performance requirements, develop test plans, implement test infrastructure and perform demonstrations of Silvus’ Networked Electronic Warfare capabilities and other wireless products and technologies under development in the Research and Development (R&D) department. This position is fully onsite, Monday through Friday, at Silvus Technologies’ headquarters in the heart of vibrant West Los Angeles. Role And Responsibilities list: - Own the complete design and execution of full coverage test procedures for novel Radio Frequency (RF) sensing and other effects using Silvus hardware and software products. - Work closely with R&D and Engineering teams to understand performance requirements and expected system behaviors. - Define test plans, implement test automation, perform troubleshooting and qualification of new designs. - Work closely with the Software Development teams to augment test systems to support rollout of new features and product configurations. - Design and implement logging and analysis tools to capture performance of both the systems under test and the test infrastructure itself. - Perform other related duties of which the above are representative. Travel Requirements: Occasional travel away from the office, including overnight, to support experimentation and demonstration of cutting-edge technology under development. Required Qualifications (list): - Bachelor’s degree in Electrical Engineering, Engineering Technology, Computer Engineering, Computer Science, or other relevant technical fields. - A minimum of 10 years of relevant industry experience, specifically in Electronic Warfare system testing. - Demonstrated experience in embedded software/firmware testing, scripting, C/C++, and python. - Proven experience with lab instruments such as signal generators, spectrum analyzers, and wireless environment emulation equipment. - Proven experience with wireless and radio communication systems, radio frequency signal propagation principles, and digital communication technologies. - Strong verbal and written communications skills to effectively communicate with internal stakeholders. - Excellent organizational skills and attentiveness to details. - Must be a U.S. Citizen due to clients under U.S. government contracts. - All employment is contingent upon the successful clearance of a background check and drug test. Preferred Knowledge, Skills, And Abilities: - Advanced degree in Electrical or Electronic Engineering. - Demonstrated experience with TCP/IP networking. - Ability to work independently, take initiative, and effectively interact with cross-functional teams and customers. Working Conditions And Physical Requirements: - Office and laboratory environments. - While performing the duties of this job, the employee is required to do the following: - Lift equipment up to 20 lbs. for the set-up of demonstrations and testing. - Perform bending and reaching movements to place items on lower and higher shelves. - Kneeling or squatting to access lower shelves. - Walking/Moving in the labs. COMPENSATION: $140,000 - $195,000 / annually Benefits list: - Incentive Bonus Plans - Medical, Dental, Vision benefits - 401K with Company Match - 10 Paid Holidays - Generous Paid Time Off Packages - Employee Stock Purchase Plan - Paid Parental & Family Leave - and more! Schedule: This position is fully onsite, Monday through Friday, at Silvus Technologies’ headquarters in the heart of vibrant West Los Angeles. (plus travel occasional) We need to avoid repeating the same info. We'll combine schedule and travel. Now produce HTML:

About the role

... combine company overview, department overview, and the opportunity description.

Responsibilities

• ... each responsibility

Requirements

maybe combine mandatory qualifications and working conditions? But we have separate Qualifications and Skills headings. Let's follow list: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Thus: - Requirements: maybe include mandatory qualifications? But we also have Qualifications heading. Could treat Requirements as mandatory qualifications, Qualifications as something else? Actually typical: Requirements = mandatory, Qualifications = education/experience, Skills = preferred. But we have both. To avoid confusion, we can assign: Requirements: Mandatory qualifications (the list under Required Qualifications). Qualifications: maybe education? But that's already in mandatory. Hmm. Better to follow the example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - Requirements: Mandatory qualifications (Required Qualifications) - Qualifications: Education requirement? But that's part of mandatory. Could be duplicate. Maybe we can put the degree requirement under Qualifications and the experience under Requirements? But that splits. Given the instruction: "Prefer a few substantive sections over many thin ones." So we might combine Requirements and Qualifications into one section? But they said use those headings for section headings. It doesn't say we must use all; we can use only those that have content. So we could choose to use Requirements for mandatory qualifications, and Skills for preferred. Then we can omit Qualifications heading if we don't have distinct content. But we have education/experience etc which could go under Requirements. That's fine. Thus sections: - About the role - Responsibilities - Requirements (mandatory qualifications + maybe working conditions) - Skills (preferred) - Benefits - Pay - Schedule We need to ensure we don't create empty headings. Now craft HTML. We'll need to escape any HTML special characters? Not needed. Let's write:

About the role

At Motorola Solutions, we believe that everything starts with our people. We’re a global close-knit community, united by the relentless pursuit to help keep people safer everywhere. We build and connect technologies to help protect people, property and places. Our solutions foster the collaboration that’s critical for safer communities, safer schools, safer hospitals, safer businesses, and ultimately, safer nations. Connect with a career that matters, and help us build a safer future.

Silvus Technologies, a leading provider