RF Systems Engineer, Senior

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Job title: RF Systems Engineer, Senior (but we don't repeat as heading). Job Number: R0243334 (metadata, we can fold into short p or drop). We'll include maybe a short p with Job ID. Now sections: - About the role: The Opportunity paragraph(s). That is descriptive prose about role. We'll put in

About the role

then

...

. - Responsibilities: The bullet points? The posting includes "You will work with a varied group..." etc. Also "As a Systems Engineer on our team, you have the chance to shape a critical Air Force program by leading RF design and engineering efforts." etc. Also "Your ability to translate real-world needs into technical specifications..." etc. Also "On our team, you’ll be able to broaden your skillset into areas like digital signal processing, radio frequencies, satellite communications, space systems, and spectrum management." Also "Grow your skills by merging your expertise and qualifications to deliver cutting-edge solutions and range environments for defensive and offensive cyberspace operators." Also "Join our team and create the future of systems for the Air Force and Space Force." These are more like responsibilities/duties. We can extract bullet list. Let's list responsibilities: - Work with a varied group of professionals to satisfy mission partner requirements. - Translate real-world needs into technical specifications. - Shape a critical Air Force program by leading RF design and engineering efforts. - Design and develop RF systems, and evolve them with advanced technology solutions. - Broaden skillset into areas like digital signal processing, radio frequencies, satellite communications, space systems, and spectrum management. - Grow skills by merging expertise and qualifications to deliver cutting-edge solutions and range environments for defensive and offensive cyberspace operators. - Create the future of systems for the Air Force and Space Force. We can put as

• ...

. - Requirements: The "You Have:" bullet list. That includes: 5+ years of experience supporting RF, communications, cyber, networking, test, or systems engineering efforts Experience integrating hardware, software, and networked systems into operational or test environments Experience troubleshooting complex technical systems involving RF, networking, computing, or communications components Experience operating or supporting RF test equipment, communications systems, or spectrum-dependent systems Experience documenting engineering designs, test procedures, and technical findings Knowledge of RF fundamentals including modulation techniques, frequency planning, bandwidth management, link analysis, and signal propagation Top Secret clearance Bachelor’s degree in Electrical Engineering, Computer Engineering, Computer Science, Software Engineering, Physics, or STEM field We'll put as list. - Qualifications: The "Nice If You Have:" list. That includes: Experience supporting Department of War, Intelligence Community, or developmental test organizations Experience supporting SATCOM, tactical communications, wireless communications, or spectrum operations Experience with Software Defined Radios (SDRs) Experience conducting RF testing, analysis, or troubleshooting activities Experience integrating RF capabilities into cyber, modeling and simulation, or training environments Experience supporting DT&E, OT&E, experimentation, or mission rehearsal activities Experience with signal processing tools, waveform analysis, or RF modeling and simulation We'll put as list. - Skills: Not explicitly listed separate; maybe we can combine knowledge of RF fundamentals etc. But we already have knowledge in Requirements. Could create Skills section for technical skills: RF fundamentals, modulation techniques, frequency planning, bandwidth management, link analysis, signal propagation, hardware/software integration, troubleshooting, test equipment operation, documentation, etc. But we must not invent detail; we can extract from the posting. The posting includes "Knowledge of RF fundamentals including modulation techniques, frequency planning, bandwidth management, link analysis, and signal propagation". Also "Experience integrating hardware, software, and networked systems". Also "Experience troubleshooting complex technical systems". Also "Experience operating or supporting RF test equipment". Also "Experience documenting engineering designs". Also "Experience with Software Defined Radios (SDRs)". Also "Experience conducting RF testing, analysis, or troubleshooting activities". Also "Experience integrating RF capabilities into cyber, modeling and simulation, or training environments". Also "Experience with signal processing tools, waveform analysis, or RF modeling and simulation". So we could make a Skills section summarizing these. However we must not create a section if it's just placeholder; we have real content. So we can include Skills. But we already have Requirements and Qualifications; Skills could be overlapping. The instruction: Prefer a few substantive sections over many thin ones. Might be better to combine Requirements and Qualifications into one? But they ask to use headings for those categories if content exists. We have content for Requirements and Qualifications. Skills could be derived but might be thin. However we have explicit list of skills: knowledge of RF fundamentals, experience integrating hardware/software, troubleshooting, operating test equipment, documenting designs, experience with SDRs, conducting RF testing, integrating RF capabilities into cyber/modeling/simulation, experience with signal processing tools. That's substantive enough. We'll include Skills. - Benefits: The posting includes compensation and benefits paragraph: "Compensation At Booz Allen, we celebrate your contributions..." includes health, life, disability, financial, retirement benefits, paid leave, professional development, tuition assistance, work-life programs, dependent care. Also recognition awards program. Also full-time/part-time eligibility. Also salary range. So we can make Benefits section with list of benefits. - Pay: The posting includes salary range: "$86,800.00 to $198,000.00 (annualized USD)". Also note that salary determined by factors. We'll include Pay section with that range. - Schedule: Not explicitly mentioned. There's work model section describing remote/hybrid/onsite expectations but not a specific schedule. The posting includes "Work Model" describing remote/hybrid/onsite expectations. That could be considered Schedule? But they said only create Schedule section if posting actually states them. It does mention expectations about cameras, remote/hybrid/onsite. That's about work arrangement, not schedule (hours). Might be considered Schedule? The instruction: "Prefer a few substantive sections over many thin ones." Probably we should not create Schedule if no explicit schedule like "full-time", "part-time", "shift". There's mention of full-time and part-time employees eligibility for benefits, but not schedule. I'd skip Schedule. Now we need to output only HTML fragment, no markdown fences. We'll include a short p for Job Number maybe. Let's craft:

Job ID: R0243334

Then sections. Make sure to use

for each heading. Now produce final HTML. Check for any boilerplate removal: We removed Identity Statement, Commitment to Non-Discrimination, etc. Also removed "This posting will close within 90 days from the Posting Date." That's boilerplate? It's specific but maybe considered metadata; but we could keep as short p? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The closing date is not exactly those; but it's not a major substantive content; could be considered metadata. I'd drop it. Also removed "Identity Statement", "Candidate AI Usage Policy", "Work Model" (though we might incorporate some of that into Benefits? Actually work model is about remote/hybrid/onsite; not benefits. Could be considered Schedule? Not exactly. Might be considered "Work Model" but we don't have a heading for that. Could we include it under Benefits? Not appropriate. Could we include under "About the role"? Not really. Might be better to include a short p about work model? But instruction says only include sections when posting has real specific content for it. We could include a

for Work Model after About the role? But they'd want headings only for those categories. However we could include a

without heading? The instruction says output only HTML fragment; we can include

elements anywhere. It didn't forbid extra paragraphs outside sections. It said 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. So we can have prose paragraphs not under headings. So we could include a short paragraph for Work Model after About the role. But we need to preserve all substantive information. The Work Model section includes details about remote/hybrid/onsite expectations and camera usage. That's substantive. We should preserve it. We could put it under a heading? There's no predefined heading for Work Model; we could maybe treat it as part of About the role? But it's separate. Perhaps we can create a heading "Work Model"? Not in the list but instruction 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 should not create other headings. So we need to fit Work Model content somewhere else, maybe as a paragraph under About the role or Benefits? It's not about benefits. Could be under About the role as additional prose. That would preserve info. Similarly, Identity Statement and Commitment to Non-Discrimination are boilerplate EEO etc; we should remove. Candidate AI Usage Policy is also boilerplate? It's about AI usage in interviews; could be considered relevant but maybe considered boilerplate? It's specific to hiring process. Might be considered substantive? It's about policy; but it's not about the job. Likely we should remove as it's not about role. Thus we will keep About the role (Opportunity), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also a short paragraph for Work Model inserted after About the role. Now craft content. About the role prose: combine the Opportunity paragraphs into a cohesive paragraph. Let's extract: "Are you looking for an opportunity to combine your technical skills with big picture thinking to make an impact in national security? You understand your customer’s environment and how to develop the right systems for their mission. You will work with a varied group of professionals to satisfy mission partner requirements. Your ability to translate real-world needs into technical specifications makes you an integral part of delivering a customer focused engineering solution. As a Systems Engineer on our team, you have the chance to shape a critical Air Force program by leading RF design and engineering efforts. Your customer will trust you to not only design and develop these systems, but also evolve them with advanced technology solutions. On our team, you’ll be able to broaden your skillset into areas like digital signal processing, radio frequencies, satellite communications, space systems, and spectrum management. Grow your skills by merging your expertise and qualifications to deliver cutting-edge solutions and range environments for defensive and offensive cyberspace operators. Join our team and create the future of systems for the Air Force and Space Force." We'll put that in

  . Then maybe a short paragraph for Work Model: "Our people-first culture prioritizes the benefits of collaboration, whether it occurs in person or virtually. To support engagement and effective communication, employees working virtually are generally expected to have their cameras on during meetings. Remote: If this position is listed as remote, there may still be occasions when you are required to work in person at a Booz Allen or customer facility. Hybrid: If this position is listed as hybrid, you will be expected to work from a Booz Allen facility frequently, in alignment with leadership expectations and the needs of the role. You may also be required to work from or visit a customer facility. Onsite: If this position is listed as onsite, work will primarily be performed at a Booz Allen office or