Senior DSP Engineer - TS/SCI

We need to output HTML fragment with sections: About the role? Not present. The posting includes a description paragraph at start: "In a world of possibilities...". That's like about the role? Could be considered "About the role" or "Job Description". The instruction: 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 repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract sections: The posting includes: - Intro paragraph: "In a world of possibilities, pursue one with endless opportunities. Imagine Next! At Parsons, you can imagine a career where you thrive, work with exceptional people, and be yourself. Guided by our leadership vision of valuing people, embracing agility, and fostering growth, we cultivate an innovative culture that empowers you to achieve your full potential. Unleash your talent and redefine what’s possible." That's like "About the role" or "Company overview". Could be "About the role". We'll put under

  About the role

  with that paragraph. - Then "Job Description" heading (but we shouldn't duplicate job title). The text after "Job Description" is the description of the role: "Seeking a Senior DSP Engineer to design, implement, and field advanced processing chains for communications signals of interest (SOIs) across terrestrial, airborne, maritime-surface, and space segments. The role centers on detection, characterization, demodulation, and exploitation of tactical and strategic data-bearing waveforms in congested, contested, and degraded electromagnetic environments. Work spans algorithm development through operational software deployed against collected I/Q from wideband receivers and software-defined radios." That's prose; could be part of About the role or separate "Job Description". Since we already used About the role for intro, we could treat this as "Job Description". But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't list Job Description as a standard heading, but we can still use About the role for overview. The "Job Description" text could be considered part of About the role. However we have a separate "Responsibilities" section later. So we could combine intro + job description into About the role. Then we have "Responsibilities" heading with a list of bullet points (each sentence). We'll output

  Responsibilities

  then
  • each bullet. Then "Required Qualifications" heading with bullet list. We'll output

    Qualifications

    (or Requirements?). The instruction includes Requirements and Qualifications as possible headings. The posting says "Required Qualifications". We'll use

    Qualifications

    (or Requirements). Since they have both "Required Qualifications" and also list items like degree, experience, citizenship, clearance, etc. That's qualifications. We'll put under Qualifications. Then there is "Security Clearance Requirement" which repeats the clearance requirement; it's duplicate of earlier. We should not duplicate. We'll ignore duplicate. Then there is a paragraph about Federal Solutions team etc. That's more about company/team; could be part of About the role or maybe a separate section like "About the team". But we only have allowed headings; we could incorporate into About the role. Then "Salary Range: $112,200.00 - $196,400.00". That's Pay info. So we need a Pay section. According to instruction, we can create Pay section only if posting actually states them. It does. So we will add

    Pay

    with

    Salary Range: $112,200.00 - $196,400.00

    . We should not include Benefits or Schedule as not present. We must remove boilerplate: equal opportunity employer, fraudulent recruitment, etc. We must preserve all substantive information: ensure we keep all bullet points from Responsibilities and Qualifications. Let's extract Responsibilities bullets exactly: From text after "Responsibilities": - Architect and implement DSP pipelines for detection, classification, parameterization, and tracking of communications signals across HF through Ka-band collections. - Develop synchronization, carrier and symbol recovery, equalization, and demodulation algorithms for both well-documented and poorly characterized waveforms, including frequency-hopped, spread-spectrum, and low-probability-of-intercept / low-probability-of-detection constructions. - Recover payload bits and reconstruct higher-layer structure from tactical and strategic data links, including line-of-sight, beyond-line-of-sight, and satellite communications carriers (protected and commercial). - Design multi-rate channelizers, polyphase filter banks, and wideband front-end processing suitable for high-occupancy spectrum and mixed narrowband / wideband collections. - Characterize and mitigate real-world impairments typical of long-range and over-water paths: Doppler from moving platforms, multipath, co-channel interference, phase noise, IQ imbalance, and low SNR. - Perform SOI development and waveform discovery against unidentified or evolving communications systems; produce reusable signal models, feature sets, and processing recipes. - Implement and optimize algorithms in C/C++ and Python on Linux, with GPU/CUDA or equivalent acceleration where throughput or latency requires it; integrate with SDR hardware and existing mission processing frameworks. - Validate processing chains against laboratory-generated and field-collected I/Q using quantitative metrics (detection probability, false-alarm rate, EVM, BER, protocol decode success). - Support end-to-end integration with RF front ends, collection systems, and downstream analytic or C2 consumers; contribute to lab, ground, and occasional field test events. - Mentor junior engineers, review designs, and translate operational collection needs into technical requirements and processing architectures. - Document algorithms, interfaces, and performance so capabilities can be sustained and transitioned. Now Qualifications bullets: From "Required Qualifications": - Bachelor’s degree in Electrical Engineering, Computer Engineering, or a closely related discipline; Master’s degree preferred. - Equivalent experience may be considered in lieu of a degree. - 8 years of experience required - U.S. citizenship - An active Top Secret / SCI clearance - Ten or more years of professional experience developing DSP algorithms for digital communications, COMINT, or closely related SIGINT applications. - Deep working knowledge of communications theory: modulation and coding, multiple access, synchronization, estimation and detection, channel models, and link-budget fundamentals. - Hands-on experience demodulating and exploiting communications waveforms used for command-and-control and data exchange among surface, airborne, and space assets—not limited to a single band or access method. - Proficiency in implementing signal processing in C/C++ and Python in Linux environments; version control with Git. - Experience with at least one mission-relevant framework or environment such as MATLAB, GNU Radio, or X-Midas. - Demonstrated ability to work from raw I/Q through bits and recoverable protocol structure under operationally realistic impairments. Note: There's also "8 years of experience required" and later "Ten or more years of professional experience". Might be contradictory but we keep both. Also there is "Security Clearance Requirement" duplicate; we ignore. Now About the role: combine intro paragraph and maybe the Federal Solutions paragraph. Intro: "In a world of possibilities, pursue one with endless opportunities. Imagine Next! At Parsons, you can imagine a career where you thrive, work with exceptional people, and be yourself. Guided by our leadership vision of valuing people, embracing agility, and fostering growth, we cultivate an innovative culture that empowers you to achieve your full potential. Unleash your talent and redefine what’s possible." Federal Solutions paragraph: "This position is part of our Federal Solutions team. The Federal Solutions segment delivers resources to our US government customers that ensure the success of missions around the globe. Our intelligent employees drive the state of the art as they provide services and solutions in the areas of defense, security, intelligence, infrastructure, and environmental. We promote a culture of excellence and close-knit teams that take pride in delivering, protecting, and sustaining our nation's most critical assets, from Earth to cyberspace. Throughout the company, our people are anticipating what’s next to deliver the solutions our customers need now." We can combine them into About the role. Now Pay: "Salary Range: $112,200.00 - $196,400.00" Now ensure we don't include any boilerplate like equal opportunity, fraudulent recruitment, etc. Now produce HTML fragment:

    About the role

    In a world of possibilities, pursue one with endless opportunities. Imagine Next! At Parsons, you can imagine a career where you thrive, work with exceptional people, and be yourself. Guided by our leadership vision of valuing people, embracing agility, and fostering growth, we cultivate an innovative culture that empowers you to achieve your full potential. Unleash your talent and redefine what’s possible. This position is part of our Federal Solutions team. The Federal Solutions segment delivers resources to our US government customers that ensure the success of missions around the globe. Our intelligent employees drive the state of the art as they provide services and solutions in the areas of defense, security, intelligence, infrastructure, and environmental. We promote a culture of excellence and close-knit teams that take pride in delivering, protecting, and sustaining our nation's most critical assets, from Earth to cyberspace. Throughout the company, our people are anticipating what’s next to deliver the solutions our customers need now.

    Responsibilities

    • Architect and implement DSP pipelines for detection, classification, parameterization, and tracking of communications signals across HF through Ka-band collections.
    • Develop synchronization, carrier and symbol recovery, equalization, and demodulation algorithms for both well-documented and poorly characterized waveforms, including frequency-hopped, spread-spectrum, and low-probability-of-intercept / low-probability-of-detection constructions.
    • Recover payload bits and reconstruct higher-layer structure from tactical and strategic data links, including line-of-sight, beyond-line-of-sight, and satellite communications carriers (protected and commercial).
    • Design multi-rate channelizers, polyphase filter banks, and wideband front-end processing suitable for high-occupancy spectrum and mixed narrowband / wideband collections.
    • Characterize and mitigate real-world impairments typical of long-range and over-water paths: Doppler from moving platforms, multipath, co-channel interference, phase noise, IQ imbalance, and low SNR.
    • Perform SOI development and waveform discovery against unidentified or evolving communications systems; produce reusable signal models, feature sets, and processing recipes.
    • Implement and optimize algorithms in C/C++ and Python on Linux, with GPU/CUDA or equivalent acceleration where throughput or latency requires it; integrate with SDR hardware and existing mission processing frameworks.
    • Validate processing chains against laboratory-generated and field-collected I/Q using quantitative metrics (detection probability, false-alarm rate, EVM, BER, protocol decode success).
    • Support end-to-end integration with RF front ends, collection systems, and downstream analytic or C2 consumers; contribute to lab, ground, and occasional field test events.
    • Mentor junior engineers, review designs, and translate operational collection needs into technical requirements and processing architectures