Wireless Communication Systems Engineer

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. Let's parse the posting. We have: - Application Close Date: "Applications will be accepted on an ongoing basis until the requisition is closed." This is minor metadata; we can fold into a short

or drop. Probably drop as it's not substantive. - At Blue Origin, we envision... (intro). This is about the role? Could be "About the role". We'll include a section About the role with that paragraph. - Job Description: "As part of a hardworking team..." This is also description; could be part of About the role or Responsibilities? The posting includes a "Responsibilities Include But Are Not Limited To" list. So we can treat the earlier description as About the role. - Special Mentions: "Relocation providedTravel expected up to 20% of the timeInterviews will include a technical assessmentThis role will be onsite in either the Bay Area, CA; San Diego, CA; Austin, TX; or Kent, WA. A temporary remote work exception may be available while specific sites are being developed." This includes location, travel, remote exception. Could be part of About the role or maybe a separate section like "Location/Travel". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could incorporate location/travel into About the role or maybe into Responsibilities? Probably About the role. - Responsibilities: list of bullet points (many). We'll output

Responsibilities

then

• each. - Minimum Qualifications: list. Could be Requirements or Qualifications. The headings we have: Requirements, Qualifications, Skills. We need to decide mapping. Typically "Minimum Qualifications" could go under Qualifications. "Preferred Qualifications" also under Qualifications or maybe Skills? But we have separate Skills heading. Could put both under Qualifications. However we need to avoid empty sections. We'll include Qualifications heading with both minimum and preferred? Or we could split: Requirements for minimum, Qualifications for preferred, Skills for technical skills list. Let's see content. Minimum Qualifications bullet list includes: Bachelor's degree, 3+ years experience, strong understanding, experience with communication technologies, experience developing models, understanding of wireless channel effects, ability to work collaboratively, must be US citizen etc. Preferred Qualifications bullet list includes: Master's degree, experience with satellite etc., experience with link-level simulations, experience developing modem PHY algorithms, familiarity with fixed-point modeling, familiarity with RF components, experience with synchronization etc., experience supporting FPGA prototyping etc. Skills: Not explicitly listed as a separate section, but many of the qualifications are skills. Could create a Skills section summarizing technical skills like MATLAB, Python, C/C++, SystemC, OFDM, QPSK/QAM, etc. But we must not invent or summarize away detail; we can extract from the qualifications. However we must not create a section if it's just filler. We could create a Skills section with bullet list of skills mentioned: MATLAB, Python, C/C++, SystemC, OFDM, QPSK/QAM, synchronization, channel estimation, equalization, forward error correction, link adaptation, fixed-point modeling, RF components, ADCs, DACs, mixers, amplifiers, phased-array, beamforming, etc. But that might be considered summarizing; but it's still preserving detail? It's extracting from the text, not inventing. It's okay as long as we don't add new info not present. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Minimum and Preferred into Qualifications, and not create Skills unless there is a distinct skills list. The posting does not have a separate "Skills" heading; but we could still create a Skills section if we have specific skill items. However risk of being considered thin. I'd rather not create Skills section; instead put all qualifications under Qualifications. Pay: The posting includes "Base Pay Range For CA applicants is $192,051.00 - $268,870.35 WA applicants is $192,051.00 - $268,870.35 Other Site Ranges May Differ". That's specific pay ranges. So we should include a Pay section with that info. Schedule: Not mentioned explicitly; there is mention of travel up to 20% of time, but not schedule like full-time, part-time, shift. No schedule info. So we should not create Schedule section. Benefits: There's a Benefits section with details. So include Benefits. About the role: we have introductory paragraphs. We'll include that. Responsibilities: we have list. Requirements: maybe we could have a Requirements section for minimum qualifications? But we already have Qualifications. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't require us to use all; we can choose. We need to avoid duplication. We could put minimum qualifications under Requirements, and preferred under Qualifications, or combine. Let's decide: Use Requirements for minimum qualifications, Qualifications for preferred qualifications. That gives two substantive sections. Then we can also have Skills maybe not needed. But we could also put technical skills under Skills if we want. However we already have details in Requirements and Qualifications; Skills may be thin. I'd skip Skills. Thus sections: About the role, Responsibilities, Requirements (minimum), Qualifications (preferred), Benefits, Pay. Check if any other sections like "Special Mentions" could be folded into About the role. Now we need to output HTML fragment only, no extra text. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all bullet points from Responsibilities, Minimum Qualifications, Preferred Qualifications, Benefits, Pay range, location/travel/relocation/remote exception, etc. We must not include boilerplate like EEO, equal opportunity, application instructions, etc. We removed those. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to ensure we don't include the "Culture Statement" paragraph about "Don’t meet all desired requirements?" That's somewhat encouraging to apply; could be considered boilerplate? It's not exactly EEO but it's a generic encouragement. Might be considered filler but it's substantive? It's a statement encouraging applicants. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The culture statement is not exactly those, but it's a generic encouragement. Might be considered not boilerplate but it's still a kind of encouragement. However it's not specific to the role; it's a generic statement. I'd consider it boilerplate-ish and could be removed. Safer to remove. Also "Export Control Regulations" paragraph about citizenship requirement is already covered in Minimum Qualifications (must be US citizen etc). That's duplicated; we can keep only one instance. We'll keep the citizenship requirement in Minimum Qualifications and drop the Export Control Regulations paragraph. Background Check Required etc: that's generic boilerplate; remove. Benefits section we keep. Now let's craft HTML. We'll start with

  About the role

  then a

  containing the introductory paragraphs: vision statement, TeraWave description, job description paragraph, special mentions (relocation, travel, interview assessment, location, remote exception). We need to ensure we keep all info. Let's extract the relevant text: From posting: "At Blue Origin, we envision millions of people living and working in space for the benefit of Earth. We’re working to develop reusable, safe, and low-cost space vehicles and systems within a culture of safety, collaboration, and inclusion. Join our team of problem solvers as we add new chapters to the history of spaceflight! Blue Origin is pioneering the future of space-based communications with TeraWave, a revolutionary satellite communications network designed to deliver symmetrical data speeds of up to 6 Tbps anywhere on Earth. This multi-orbit constellation will consist of optically interconnected satellites in low Earth orbit (LEO) and medium Earth orbit (MEO), providing enterprise-grade connectivity for critical operations worldwide." Then "Job Description As part of a hardworking team of engineers and specialists, you will develop and analyze wireless communication system algorithms and architectures for the TeraWave custom silicon platform. You will work across communication systems, modem PHY/MAC, digital signal processing, RF, ASIC, and software teams to develop algorithms and system models and support their implementation in custom silicon. You will contribute to the development of high-performance, power-efficient communication solutions for advanced space-based wireless systems, from algorithm development and system simulation through pre-silicon verification and post-silicon validation." Then "Special Mentions Relocation providedTravel expected up to 20% of the timeInterviews will include a technical assessmentThis role will be onsite in either the Bay Area, CA; San Diego, CA; Austin, TX; or Kent, WA. A temporary remote work exception may be available while specific sites are being developed." We need to format that into readable prose. We'll combine into a paragraph or multiple paragraphs. Use

  for prose. Could be multiple

  elements. We'll produce:

  At Blue Origin, we envision millions of people living and working in space for the benefit of Earth. We’re working to develop reusable, safe, and low-cost space vehicles and systems within a culture of safety, collaboration, and inclusion. Join our team of problem solvers as we add new chapters to the history of spaceflight.

  Blue Origin is pioneering the future of space-based communications with TeraWave, a revolutionary satellite communications network designed to deliver symmetrical data speeds of up to 6 Tbps anywhere on Earth. This multi-orbit constellation will consist of optically interconnected satellites in low Earth orbit (LEO) and medium Earth orbit (MEO), providing enterprise-grade connectivity for critical operations worldwide.

  As part of a hardworking team of engineers and specialists, you will develop and analyze wireless communication system algorithms and architectures for the TeraWave custom silicon platform. You will work across communication systems, modem PHY/MAC, digital signal processing, RF, ASIC, and software teams to develop algorithms and system models and support their implementation in custom silicon. You will contribute to the development of high-performance, power-efficient communication solutions for advanced space-based wireless systems, from algorithm development and system simulation through pre-silicon verification and post-silicon validation.

  Relocation provided. Travel expected up to 20% of the time. Interviews will include a technical assessment. This role will be onsite in either the Bay Area, CA; San Diego, CA; Austin, TX; or Kent, WA. A temporary remote work exception may be available while specific sites are being developed.

  That preserves all. Now Responsibilities: list each bullet. We'll extract each bullet from "Responsibilities Include But Are Not Limited To" list. Let's copy them: - Develop and model wireless communication algorithms and signal-processing functions for custom silicon, including modem PHY/MAC, radio DSP, beamforming, and packet-processing functions. - Develop end-to-end communication system and link-level models to evaluate system performance, architecture tradeoffs, and implementation requirements. - Develop and analyze channel and RF impairment models, including noise, interference, Doppler, frequency and timing offsets, phase noise, nonlinearities, and other relevant impairments. - Design and evaluate algorithms for synchronization, channel estimation, equalization, modulation/demodulation, coding, link adaptation, and other modem functions. - Analyze algorithm performance and implementation tradeoffs including performance, complexity, latency, memory, bandwidth, power, and fixed-point requirements. - Translate communication-system and algorithm requirements into specifications suitable