RF Phased Array Engineer II

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Rocket Lab" and "SPACE SYSTEMS" description, then "RF PHASED ARRAY ENGINEER II" role description. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should not repeat job title as heading. We need to include sections only when posting has real specific content. We need to extract content: About the role: maybe the description after role title: "Based at Rocket Lab's global headquarters in Long Beach, CA, the RF Phased Array Engineer is responsible for the development of new RF products and systems (including Rocket Lab’s phased arrays) and assessment of COTS components. The RF Phased Array Engineer will model and simulate antenna performance for current programs and proposals. The successful candidate will have a strong understanding of antennas at the component and system level and will thrive in a fast-paced, dynamic environment." That's about the role. Responsibilities: The bullet list under "What You'll Get To Do" includes two subheadings: Product Development and Customer/Program Support. We can combine into a list of responsibilities. Requirements/Qualifications: The posting has "You'll Bring These Qualifications" list: Bachelors degree..., Fundamental RF knowledge..., Basic knowledge..., Ability to obtain TS/SCI. Also "These Qualifications Would Be Nice To Have" list. Skills: maybe we can extract from qualifications: fundamental RF knowledge, link budget analysis, antenna modeling, etc. Could be separate. Benefits: The posting includes benefits description: "In addition to competitive base pay, you'll receive company stock... 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." Pay: The posting includes "Total Compensation (base and equity): $110,875 USD - $143,625 USD Base Salary: $10,800 USD - $126,000 USD". That seems odd: base salary range $10,800 - $126,000? Probably a typo but we must preserve as given. Also "Anticipated annual equity grant value is designed around function, level, experience, and other factors; realized value depends on vesting and stock-price performance." Also "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." Schedule: Not mentioned. So we should not include Schedule section. We need to remove boilerplate: ITAR, EEO, accommodation, etc. Also remove "What To Expect" maybe? It's not a standard heading; could be considered "About the role" or maybe we can include as a paragraph under About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "What To Expect" is not boilerplate but could be considered part of role description; we can keep as prose under About the role or maybe as its own section? Since we only have defined headings, we could incorporate into About the role. We must not invent sections like Skills if not explicit. However we can create Skills section if we have explicit skill list. The posting includes "Fundamental RF knowledge including link budget analysis and linearity. A solid theoretical and practical understanding of RF communications and navigation systems and components Basic knowledge of antenna and array modeling Ability to obtain TS / SCI". Those are qualifications, not necessarily skills. But we could still put them under Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not mandatory to use all. We can choose which to include based on content. We have content for About the role, Responsibilities, Qualifications (including required and nice-to-have), Benefits, Pay. Possibly also Requirements (maybe same as Qualifications). To avoid duplication, we can combine Requirements and Qualifications into one section called Qualifications. Or we could have Requirements for required qualifications and Qualifications for nice-to-have. But better to follow typical: Requirements = required qualifications; Qualifications = nice-to-have. However the posting uses "You'll Bring These Qualifications" (required) and "These Qualifications Would Be Nice To Have". So we can map: Requirements = required qualifications; Qualifications = nice-to-have. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We must not include Schedule. Now produce HTML:

About the role

then

...

. For lists:

• ...

. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all bullet points from responsibilities and qualifications. Let's extract responsibilities bullet points: Under "What You'll Get To Do": Product Development: - Support end to end efforts including architecture design, prototyping, integration, test, and flight development – Ensure key design decisions and developments are in alignment with product / system needs - Model and simulate array performance - Work alongside an interdisciplinary team of RF, digital, power, mechanical, thermal, and structural engineers - Support transition developments from new product introduction to production - Interface with vendors and customers - Develop test plans and procedures for testing active antennas – included EIRP & G/T - Design and development of GSE and production automation - Support the development of product documentation including ICDs and User Manuals Customer/Program Support: - Support proposals and requirements specifications to assess compliance based on existing unit capabilities vs development needs - Implement development activities for new requirements - 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 We need to preserve each as list items. Now Requirements (required qualifications): - Bachelors degree in electrical engineering, RF communications (or an equivalent qualification) and 2+ years of relevant experience - Fundamental RF knowledge including link budget analysis and linearity. - A solid theoretical and practical understanding of RF communications and navigation systems and components - Basic knowledge of antenna and array modeling - Ability to obtain TS / SCI Now Qualifications (nice-to-have): - Extensive experience in space grade system design - Extensive experience in analyses including worst case, reliability, FMECA, thermal, and derating analyses - Extensive experience supporting and leading complex engineering programs and developing associated documentation - Experience designing, integrating, and testing RF communications systems for launch vehicles or satellites - 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 - Project management experience Now Benefits: we need to capture all benefits listed. From text: "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. As we expand to new launch sites, groundbreaking missions, and global markets, your ownership has the opportunity to grow alongside the company.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 should keep as prose or list? It's a list of benefits; we can make

• each item. But need to preserve all detail. Could break into items: Employee Stock Purchase Program (15% discount), top-tier medical plans (HMO, PPO, zero cost HDHP with 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, 401(k) retirement plan with company match, subsidized EV charging, onsite fitness centers (where available), discounted gym memberships, complimentary snacks and beverages, 50% employee discount on merch store, variety of other employee discounts. Also mention company stock as part of total compensation package. Also mention opportunity to grow alongside company. We could keep as a paragraph plus list. Simpler: make a

  for the introductory sentences, then

  for the list of specific benefits. Now Pay: we need to include the compensation numbers and statements. From text: "Anticipated annual equity grant value is designed around function, level, experience, and other factors; realized value depends on vesting and stock-price performance.Join one of the world's fastest-growing space companies and own a piece of it. 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. As we expand to new launch sites, groundbreaking missions, and global markets, your ownership has the opportunity to grow alongside the company.Our comprehensive benefits package includes ... 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. Total Compensation (base and equity): $110,875 USD - $143,625 USD Base Salary: $10,800 USD - $126,000 USD" We need to preserve all that. Could make a

  with that info. Now About the role: we need to include the description plus maybe the "What To Expect" paragraph? The "What To Expect" is a motivational paragraph about mission etc. It's not boilerplate; we could include as part of About the role. Thus About the role content: first paragraph about role responsibilities (based at headquarters...), plus the "What To Expect" paragraph. Let's extract "What To Expect": "We’re on a mission to unlock the potential of space to improve life on Earth, but that’s not an easy task. It takes hard work, determination, relentless innovation, teamwork, grit, and an unwavering commitment to achieving what others often deem impossible. Our people out-think, out-work, and out-pace. We pride ourselves on having each other’s backs, checking our egos at the door, and rolling up our sleeves on all tasks big and small. We thrive under pressure, work to tight deadlines, and our focus is always on how we can deliver, rather than dwelling on the challenges that stand in the way." We'll include that as a

  after the role description. Now ensure we don't repeat any boilerplate like ITAR, EEO, accommodation, etc. Also remove "Important Information" sections. Now produce HTML. We must output only HTML fragment, no or , no markdown fences. Let's craft. Structure:

  About the role

  Based at Rocket Lab's global headquarters in Long Beach, CA, the RF Phased Array Engineer is responsible for the