Senior Research and Development Program Manager

We need to output HTML fragment with sections: h3 headings for sections present: About the role? Actually we have Company Overview, Department Overview, Job Description (including THE OPPORTUNITY, Role And Responsibilities, Required Qualifications, Preferred Knowledge..., Working Conditions..., COMPENSATION, Benefits). We must not repeat job title as heading. Use

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 include boilerplate, navigation, EEO, etc. Remove duplicated lines. Include only sections with real specific content. We need to preserve all substantive information. Let's extract content. Company Overview: paragraph(s) about Motorola Solutions and Silvus. Should we include as a section? Possibly "About the role" or "Company Overview". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should use those headings where applicable. Could also use other meaningful headings but they gave examples. Safer to stick to those headings. So we need sections: About the role (maybe combine Company Overview and Department Overview?), Responsibilities, Requirements (maybe Required Qualifications), Qualifications (maybe Preferred Knowledge?), Skills, Benefits, Pay, Schedule. We have schedule: hybrid schedule, minimum 3 days onsite per week, on-site days Mondays, Wednesdays, Thursdays. Pay: $185,000 - $245,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! Responsibilities: list of duties from Role And Responsibilities. Requirements: Required Qualifications bullet list? It's a paragraph with multiple requirements. Could break into list. Qualifications: Preferred Knowledge, Skills, And Abilities. Skills: maybe combine with Preferred? But we can have Skills section for technical fluency etc. Let's extract specifics. Company Overview paragraph: "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 is dedicated to one mission: connecting those who keep us safe. We do so by delivering the most advanced Mobile Ad-hoc Network (MANET) radios powered by our custom and ever evolving Mobile-Networked MIMO waveform. Together, our radios and waveform provide vital communications for mission critical applications in the harshest environments from underground tunnels to high altitude balloons. Silvus StreamCaster™ radios are being rapidly adopted by customers all over the world ranging from the U.S. and Allied Nations Departments of Defense, to International, Federal, State and Local Law Enforcement agencies, all the way to the Superbowl, Grammys and industry-leading drone, robot, and unmanned systems manufacturers. Would you like to join an incredibly talented group of people, doing very challenging work, with the prime directive of “Keeping Our Heroes Connected”? Silvus’ rapid growth is fueled by a focus on research and innovation and a team of the most passionate, skilled and creative thinking individuals. If you are looking for a challenging experience, you owe it to yourself to learn how Silvus can be the next chapter of your career." We can combine these into About the role section (maybe two paragraphs). Ensure no boilerplate. Job Description THE OPPORTUNITY paragraph: "Silvus Technologies, the global leader in advanced MIMO mesh networking solutions for defense, industrial, and public safety applications, is seeking a Senior Research and Development (R&D) Program Manager who will report to the Vice President of Research and Development (R&D). This is a foundational role for Silvus R&D that blends technical know-how with strategic thinking and process-oriented execution. This position offers a unique opportunity to shape and deliver key new technology solutions within Silvus’ growing R&D organization. The Program Manager will partner closely with Senior R&D and Engineering leadership, as well as Silvus management, Business Development, and Product teams to define programmatic goals, both technical and strategic, drive cross-functional project execution, and deliver high-impact products to Silvus customers. This role is part of a passionate team redefining radio frequency (RF) sensing, electronic warfare and wireless connectivity in the most demanding environments, from battlefield networks and autonomous systems to public safety and industrial applications. You will work alongside world-class engineers solving real-world challenges, with opportunities to grow, innovate, and lead as our organization scales. This position is based at Silvus Technologies’ headquarters in the heart of vibrant West Los Angeles, CA, and is on a hybrid schedule, a minimum of 3 days onsite per week is expected. On-site days are Mondays, Wednesdays, and Thursdays." We can include schedule info in Schedule section, but also mention location/hybrid in About the role? Probably schedule separate. Now Role And Responsibilities list: - Lead end-to-end program execution across the full engineering lifecycle, from concept and design through implementation, integration, validation, and productization. - Own program definition, scope and objectives inside the Silvus R&D group as well as in engagements with Silvus groups outside R&D and organizations outside Silvus. - Own program schedules, milestones, and deliverables, ensuring alignment across cross-functional teams including Systems, FPGA, Software, RF, Hardware, and QA. - Facilitate cross-team collaboration to identify and resolve technical or schedule blockers, driving timely and data-driven decisions in collaboration with product, sales, and business development organizations. - Track risks, dependencies, and issues; develop mitigation strategies and communicate impacts and resource demands to R&D leadership and upper management. - Drive engineering cadence and communication, including design reviews, design syncs, and status updates with internal and external stakeholders. - Maintain project documentation and dashboards (e.g., Confluence, JIRA) for clear visibility into goals, progress, and key metrics. - Prepare executive reports and presentations, communicating program status, milestones, and risk assessments to senior management. - Hire, manage, and mentor various engineers, junior program managers, and other key personnel as needed to support the growth and success of the Silvus R&D organization. - Perform other related duties, of which the above are representative. We'll put these in

  • . Required Qualifications (list): - Master’s degree in Electrical Engineering, Computer Engineering, Computer Science, or a related technical field plus a minimum of 10 years of relevant program management and/or engineering experience in a technology-driven organization. - Proven experience managing complex hardware/software wireless communications, networking, or electronic warfare programs in a fast-paced R&D or product development environment. - Strong organizational, analytical, and problem-solving skills, with the ability to manage multiple programs and shift priorities. - Exceptional communication and presentation abilities with a track record of influencing across technical and non-technical teams. - 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. We can include as list. Preferred Knowledge, Skills, And Abilities: - Ph.D. in EE, ECE, or a related field with 15+ years of relevant industry experience. - Demonstrated success with hands-on product development, technical program management, or engineering leadership roles. - Technical fluency in multiple areas such as: wireless systems design, RF engineering, networking, electronic warfare, firmware/software integration, and test/validation. - Self-starter with a strong sense of ownership, capable of driving progress with minimal oversight. - Eligibility for U.S. Security Clearance. We can put under Skills or Qualifications. Since we have Skills section, we can put technical fluency etc there. But we also have Preferred Knowledge etc. Let's make a Skills section for technical fluency etc. And maybe a Qualifications section for Preferred Knowledge (Ph.D., experience). But the instruction says use headings like Qualifications, Skills. We'll have: - Qualifications (Preferred Knowledge, Skills, And Abilities) maybe as list. - Skills (Technical fluency areas) as list. But we risk duplication. Let's think: The posting has "Preferred Knowledge, Skills, And Abilities" with bullet points. Within that, there is "Technical fluency in multiple areas such as: wireless systems design, RF engineering, networking, electronic warfare, firmware/software integration, and test/validation." That's skills. The rest are more like qualifications/experience. We could split: Qualifications section for Ph.D., experience, hands-on product development, self-starter, eligibility for security clearance. Skills section for technical fluency list. Let's do that. Working Conditions And Physical Requirements: "Office environment. 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. Walking/Moving in the labs." We could include as a brief paragraph under maybe "Working Conditions" but not in the prescribed headings. Since not listed, maybe we omit? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It didn't restrict to only those headings; they gave examples. We could add a heading like "Working Conditions" but they didn't list it as example. Safer to omit if not in list? The instruction: "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. But to be safe, we could include Working Conditions as a heading if we want to preserve info. However, the instruction also says "Prefer a few substantive sections over many thin ones." Working Conditions is thin (just two sentences). Might be better to incorporate into About the role or Responsibilities? Not really. Could drop as it's minor. But we need to preserve ALL substantive information. If we drop it, we lose info. However, maybe it's considered boilerplate? It's specific: office environment, lift up to 20 lbs, walking/moving in labs. That's substantive. We could include as a paragraph under a heading like "Working Conditions". Since they didn't forbid other headings, we can use

    for it. Let's include. Now Benefits: list as given. Pay: $185,000 - $245,000 annually. Schedule: hybrid schedule, minimum 3 days onsite per week, on-site days Mondays, Wednesdays, Thursdays. Now we need to output only HTML fragment, no /, no markdown. We'll structure:

    About the role

    Company overview paragraph(s) + Department overview paragraph(s) + Job description opportunity paragraph (maybe exclude schedule part? We'll keep schedule info in Schedule section, but we can still mention location/hybrid? Better to keep schedule separate. So in About the role we can include company overview, department overview, and the opportunity description excluding schedule specifics. Let's extract opportunity paragraph without schedule: "Silvus Technologies, the global leader in advanced MIMO mesh networking solutions for defense, industrial, and public safety applications, is seeking a Senior Research and Development (R&D) Program Manager who will report to the Vice President of Research and Development (R&D). This is a foundational role for Silvus R&D that blends technical know-how