Senior Manager, Signal Processing

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. Must not repeat job title. Must not include Job ID etc. Must not include boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About Rocket Lab (company description) maybe not needed? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should produce sections like About the role (maybe summarizing role description). Not About Rocket Lab? The example headings include "About the role". So we should create an About the role section with description of role (the paragraph about Senior Manager, Signal Processing responsibilities overview). Then Responsibilities: list of duties (Engineering Management, Algorithms Development, Customer/Program Support, Team Building). Then Requirements: maybe the "You'll Bring These Qualifications" list? Actually they have "You'll Bring These Qualifications As Senior Manager, Signal Processing" then bullet list of qualifications. Then "These Qualifications Would Be Nice To Have" could be Skills? Or maybe separate sections: Qualifications (required) and Skills (nice-to-have). Benefits: they have benefits description. Pay: they have total compensation range and base salary range. Schedule: not mentioned; maybe not include. We must not include sections with placeholder or vague like "commensurate with experience". They gave specific ranges, so we can include Pay. We must not include boilerplate like EEO, legal, ITAR, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details: e.g., responsibilities bullet points exactly as given? We can keep them but maybe rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the content verbatim (or close) but not omit any detail. However we can format as list items. We need to avoid duplication. The posting includes repeated lines? We'll need to deduplicate. Let's extract substantive content: Company description: "About Rocket Lab Rocket Lab is the end-to-end space company building rockets, spacecraft, and critical subsystems that keep the world connected, protected, expand humanity’s reach to the Moon, Mars, and beyond. We move fast, build real hardware for meaningful missions, and make the impossible routine. Come shape the future with us. SPACE SYSTEMS At Rocket Lab, we’re not just launching rockets — we're building the future of space. Our Space Systems team builds everything from complete spacecraft, precision payloads to the components and subsystems that allow them to thrive in space, like solar panels, flight software, star trackers, optical systems, separation systems, radios, and more. Our Space Systems team has enabled more than 1,700 missions, ranging from interplanetary exploration, in-space manufacturing to national security and defense initiatives. The team has built spacecraft, payloads, and components for missions to the Moon and Mars, working with partners including NASA, the Space Development Agency, and the U.S. Space Force. Whether it’s a single high-performance spacecraft, constellation, or the vertically integrated components that help them get to space — our world class Space Systems team is empowering some of the boldest and most ambitious space missions." That's substantive but maybe not needed as a section? The instruction says use headings like About the role, Responsibilities, etc. It didn't forbid other headings, but we should follow the pattern. Probably we should include About the role (role overview) not company description. However the company description is substantive; maybe we can include it under About the role? But About the role should be about the role, not company. However we could treat About the role as including both role and company context. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also include other headings if needed? But they say "Prefer a few substantive sections over many thin ones." So we likely should stick to those headings. So we need to map content to those headings. Thus: - About the role: summary of role: "Based onsite at Rocket Lab's global headquarters in Long Beach, CA, the Senior Manager, Signal Processing is responsible for the algorithm development for new digital payload products including advanced radar payloads (Synthetic Aperture Radar and space-based radar systems), modems, processors, and network routers. The DSP Algorithms Lead will take the design from initial concept through inflight operations. The successful candidate will have a strong combination of DSP knowledge and system design, and will thrive in a fast-paced, dynamic environment." That seems appropriate. - Responsibilities: list of duties under "What You'll Get To Do" broken into subcategories: Engineering Management, Algorithms Development, Customer/Program Support, Team Building. We'll need to capture each bullet. Let's extract bullet points exactly: Engineering Management: - Define appropriate engineering processes for new algorithms development including activities, milestones and engineering reviews, ensuring general compliance with best practice systems engineering process - Support the development and maintenance of program schedules - Task, support and monitor engineers throughout the engineering process - Ensure engineering process and associated documentation products are traceable from requirements through design, implementation and verification Algorithms Development: - Set technical roadmap for the development of DSP algorithms - Design, develop, and optimize DSP algorithms for signal processing tasks such as filtering, modulation, demodulation, compression, noise reduction, and feature extraction. - Architect the digital product design - Lead the development process, ensuring key design decisions and developments are in alignment with the required product capabilities - Lead the development of test plans and procedures - Lead the design and development of GSE and production automation - Support the development of product documentation including ICDs and User Manuals - Liaise with hardware design, FPGA, and software engineers to design, build, test, and deliver a completed product - Stay updated with the latest advancements in DSP technologies and methodologies - Implement solutions to improve system performance and efficiency Customer/Program Support: - Liase with customers and program team in support of current programs and new business proposals - Review proposals and requirements specifications to assess compliance based on existing unit capabilities vs development needs - Scope and drive development activities for new requirements - Drive key design decisions in support of the product technical roadmap - Support engineering reviews such as PDRs, CDRs and TRRs - Provide technical support to internal/external customers including general questions and anomaly troubleshooting - Maintain broad awareness of product development and production schedules to ensure the needs of customers and programs are satisfied Team Building: - Grow a team of 3-4 engineers for DSP algorithms - Mentor junior engineers for career growth - Familiarize DSP algorithm concepts across teams We need to ensure we keep the exact phrasing; some have typos like "Liase" (should be Liaise) but we keep as is. - Requirements: The "You'll Bring These Qualifications As Senior Manager, Signal Processing" list: - Bachelors degree in electrical engineering (or an equivalent qualification) and 10+ years of relevant experience - Experience in space electronics with technical expertise in high speed serial interfaces (SPI, PCIe, Ethernet), system on chips, microcontrollers, and digital signal processing. - Experience in developing and delivering a digital product including assessing requirements, prototyping engineering models, and producing space worthy products. - Detailed knowledge of digital signal processing (DSP) algorithms and communication theory - A demonstrated track record of owning a technical program, product, or team end to end and carrying it across the finish line under real pressure, we hire on what you've shipped, not years logged - Evidence you've moved real hardware and software from prototype toward scalable, flight-ready production - Understanding of the nuances of transponders, SAR, or advanced communication systems - US citizenship is required due to program requirements - Ability to obtain TS / SCI We need to keep them as list items. - Qualifications: maybe we treat the above as Requirements, and Qualifications could be something else? But the instruction list includes both Requirements and Qualifications as separate headings. However the posting only has one qualifications list. Could split into Required Qualifications (Requirements) and Preferred Qualifications (Qualifications). The "These Qualifications Would Be Nice To Have" list can go under Qualifications (or Skills). But they also have Skills heading. We need to decide. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - Requirements: the mandatory qualifications list. - Qualifications: the nice-to-have list (These Qualifications Would Be Nice To Have). - Skills: maybe we could extract from nice-to-have list items that are skills: e.g., Experience designing, integrating, and testing RF communications systems for launch vehicles or satellites; Extensive experience supporting and leading complex engineering programs and developing associated documentation; Demonstrated expertise in mentoring others; Experience leading incident management and investigations; Experience in conflict resolution and dealing with difficult people; The ability to work under pressure and to tight deadlines; Effective communication skills and the ability to build strong working relationships; Willing to work extra hours and weekends as needed to meet critical business needs. Those could be considered Skills. But we need to avoid duplication; we could put all nice-to-have under Qualifications and leave Skills empty (but we shouldn't emit empty sections). So we need to decide: maybe we treat Qualifications as the nice-to-have list, and Skills as a subset? But we must not emit empty sections. So we need to allocate content to each heading such that each has substantive content. We could treat: - Requirements: mandatory qualifications. - Qualifications: nice-to-have qualifications (the list starting "These Qualifications Would Be Nice To Have"). - Skills: maybe we could extract from the nice-to-have list items that are more skill-oriented, but that would split the list and cause duplication. Better to put all nice-to-have under Qualifications and omit Skills section (since no specific skills beyond those). But the instruction says to include a section ONLY when the posting has real, specific content for it. If we don't have specific content for Skills beyond what's already in Qualifications, we could omit Skills. That seems okay. - Benefits: we have benefits description: "In addition to competitive base pay, you'll receive company stock as part of your total compensation package, giving you a direct stake in our success....Our comprehensive benefits package includes our industry-leading Employee Stock Purchase Program (with a 15% discount on company stock), top-tier medical plans (HMO, PPO, and a zero cost HDHP option with a significant HSA company contribution), dental and vision coverage, paid vacation and sick time, 11 paid holidays, flexible spending and dependent care accounts, paid parental leave, disability and life insurance, and a 401(k) retirement plan with company match.Additional perks include subsidized EV charging, onsite fitness centers (where available), discounted gym memberships, complimentary snacks and beverages, 50% employee discount on our popular merch store, and a variety of other employee discounts." We need to keep that. - Pay: they have total compensation range and base salary range. Also mention "Level and base salary will be determined on a case-by-case basis and may vary based on the following considerations: job-related knowledge and skills, education, and experience." That's substantive. Thus Pay section: include those ranges and note about determination. - Schedule: not mentioned; we should omit. Now we need to remove boilerplate: remove ITAR, EEO, equal opportunity, scam warning, application instructions, etc. Also remove the "Important Information" sections about ITAR, etc. Also remove the "What To Expect" paragraph? That is substantive? It's about mission and culture; maybe we could include under About the role? But it's more generic. The instruction says preserve ALL substantive information; do not invent or summarize away detail. The "What To Expect" paragraph is substantive but maybe could be considered part of About the role