Associate Signal Processing Engineer

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate. We need to parse the posting. Key content: - Intro paragraph about MITRE: "At MITRE, your passion fuels work that impacts our nation and improves lives. This is where your skills strengthen national security, cybersecurity, health, transportation, and citizen services. We’re a nonprofit engineering, applied research, and advanced technology organization working in the public interest. With objectivity and integrity at our core, we lead federally funded research and development centers for U.S. government agencies – collaborating with industry and academia to deliver integrated, high-impact solutions that advance our nation’s health, security, and prosperity. Our people tackle the toughest technical challenges, supported by competitive benefits, meaningful career development, and a culture of innovation, collaboration, and technical excellence. Choose MITRE for a career with purpose — and help shape the future." That's about the organization; could be "About the role"? Actually "About the role" is more about the job. But we could treat that as "About MITRE" but not a required heading. The instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections that have content. Likely we will have: - About the role (maybe a brief description of the position) - Responsibilities (list) - Requirements (maybe Minimum Qualifications) - Qualifications (maybe Preferred Qualifications) - Skills (maybe list of skills) - Pay (salary range) - Benefits (maybe mention competitive benefits, but not detailed; we should only include if posting actually states them. It says "supported by competitive benefits" but not specific. Might be too vague. The instruction: never create Benefits section unless posting actually states them. It does mention competitive benefits but not details. Might be considered not specific enough. Safer to omit Benefits unless we have explicit list. We'll omit. - Schedule: mentions Hybrid work location type. That's schedule? It says Annual Work Location Type: Hybrid. That's about work location, not schedule. Could treat as Schedule? Probably not. The instruction: include Schedule only if posting actually states them. It does not state schedule like full-time, part-time, hours. So omit Schedule. - Pay: Salary compensation range and midpoint: $89,200 - $111,500 - $133,800. That's specific. So include Pay. - Responsibilities: we have a block "Roles and Responsibilities:" then bullet-like sentences. We'll extract list items. - Minimum Qualifications: list. - Preferred Qualifications: list. - Skills: maybe combine technical skills from qualifications? Could create Skills section summarizing required skills like MATLAB, Python, C++, signal processing, etc. But we already have qualifications. Might be redundant. The instruction: prefer a few substantive sections over many thin ones. Could combine Minimum and Preferred into Requirements and Qualifications? Actually they differentiate Requirements (maybe minimum) and Qualifications (maybe preferred). We'll follow: Requirements = Minimum Qualifications. Qualifications = Preferred Qualifications. Skills maybe not needed if covered. But we could still include Skills if we have explicit list of skills separate. The posting includes "Strong analytical skills", "Ability to obtain and maintain a US Top Secret security clearance." etc. Those are in Minimum Qualifications. So we can put those under Requirements. Thus sections: - About the role: maybe a paragraph summarizing the role: "MITRE is seeking an Associate Signal Processing Engineer to support the development of advanced RF capabilities for our U.S. Government sponsors. At MITRE, you will apply your understanding of RF systems to model and simulate complex electromagnetic environments and leverage your signal and information processing expertise to develop resilient communications systems and mission-critical sensing capabilities." That's from posting. - Responsibilities: list items from "Typical projects include:" and "Responsibilities may include:". - Requirements: Minimum Qualifications list. - Qualifications: Preferred Qualifications list. - Pay: Salary range. We must not include boilerplate like clearance details? The posting includes clearance info: "Clearance: In addition to passing MITRE’s employment background check, you may be submitted for a U.S. Government Security clearance... This requisition requires the candidate to have a minimum of the following clearance(s): None This requisition requires the hired candidate to have or obtain, within one year from the date of hire, the following clearance(s): Secret". That's substantive info about clearance. Should we include? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include clearance info. Where to put? Could be under Requirements or a separate section like "Clearance". But headings list only includes certain ones; we can add other headings if needed? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Probably we should stick to those. Clearance could be part of Requirements (as a requirement). So include in Requirements list. Also mention "Annual Work Location Type: Hybrid". Could be under Requirements or maybe a separate "Work Location". Could add as a line in Requirements or maybe in About the role. We'll include in Requirements as a bullet: "Hybrid work location". Also mention "It is unlawful in Massachusetts..." that's boilerplate legal; remove. Also "Commitment to Non-Discrimination" etc boilerplate; remove. Also "Benefits information may be found here." boilerplate; remove. Also copyright etc; remove. Now craft HTML. Structure:

About the role

MITRE is seeking an Associate Signal Processing Engineer to support the development of advanced RF capabilities for our U.S. Government sponsors. At MITRE, you will apply your understanding of RF systems to model and simulate complex electromagnetic environments and leverage your signal and information processing expertise to develop resilient communications systems and mission-critical sensing capabilities.

Responsibilities

• End-to-end modeling and simulation (M&S) of commercial cellular physical layer signals to enable spectrum coexistence innovation.
• Development of novel signal processing algorithms for improved signal detection in congested environments.
• Evaluation of different MIMO transmission schemes for throughput, reliability, interference mitigation, etc.
• Theoretical analysis for performance assessments of novel geolocation techniques.
• Waveform design and prototyping under challenging channel conditions.
• Next-generation AI-enhanced signal processing design for ISAC or spectral efficiency.
• Characterize bands under study for repurposing or coexistence with commercial and incumbent systems.
• Evaluate and advance propagation modeling based upon system operations.
• Using technical knowledge of communications and signal processing principles to help solve problems across various application areas.
• Designing models and simulations or lab tests to evaluate technical solutions.
• Define appropriate evaluation methodologies to evaluate the compatibility of communication, radar, and navigation systems operating in shared or adjacent frequency bands.
• Assess the operational impacts of interference on system performance across current and emerging technologies (e.g., commercial 6G on government systems).
• Mentoring and staff development of junior engineers and continued technical growth.
• Comprehension of standards documents to inform M&S decision-making.
• Leading the development and contributing to the develop of project proposals for sponsors and internal research and development (IR&D).
• Drive research areas, investigate novel solutions, and distill information for varying audiences across internal and external sponsors.

Requirements

• Bachelor's degree in Electrical Engineering, Computer Engineering or related discipline.
• Proficient with MATLAB, Python, or C++ or other tools or languages.
• Strong analytical skills.
• Ability to obtain and maintain a US Top Secret security clearance.
• A strong technical background in at least one of the following areas:
  • Signal processing (detection and estimation theory)
  • Digital communications
  • Receiver design, channel estimation and equalization
  • Machine learning, AI, and optimization algorithms
  • System performance analysis
  • RF system modeling
• Excellent written and oral communication skills.
• Experience delivering technical reports, presentations, and/or code, including definition, completion, and technical quality.
• Hybrid work location.
• Must obtain a Secret security clearance within one year of hire.

Qualifications

• Master’s degree in Electrical Engineering, Computer Engineering or related discipline.
• Understanding of software-defined radios, adaptive communications, electronic protection, or dynamic spectrum access concepts.
• Familiarity with modeling and simulation tools such as Sionna, MATLAB, Simulink, STK, HFSS, CST, Wireless InSite, SEAMCAT, HTZ communications, or similar.
• Experience with wireless protocols such as 5G NR, LTE, Wi-Fi, IoT, Bluetooth.
• Experience with large codebases, software engineering best practices, and/or GPU-accelerated programming.
• Familiarity with RF sensing and navigation systems (including radar, GPS/GNSS).
• Experience in sensor fusion and autonomy.

Pay

Salary compensation range: $89,200 - $111,500 - $133,800 (annual).

We need to ensure no extra sections like Benefits or Schedule. Check for any leftover boilerplate: we removed. Check that we didn't repeat job title as heading: we didn't. Check that we didn't include Job ID/requisition numbers: we didn't. Check that we preserved all substantive info: we included intro, responsibilities, requirements (including clearance, hybrid work location), qualifications, pay. Did we miss any specifics like "The ideal candidate will have strong analytical skills and experience in both classical digital signal processing/digital communications and machine learning/data science." That's covered in requirements (strong analytical skills, background in areas). Might be okay. Also "This position will require a strong grounding in RF systems; the candidate should possess a working knowledge of the fundamentals of receiver design." That's covered under receiver design. "The candidate should be familiar with wireless technologies and engineering challenges associated with employment of RF systems." Covered under wireless protocols. "Roles and Responsibilities: This position requires an ability for innovative thought, technical expertise, and interest in the development of cutting-edge resilient wireless solutions for Government Sponsors." That's somewhat covered in responsibilities bullet about innovative thought? Not explicit. Could add a bullet: "Apply innovative thought and technical expertise to develop cutting-edge resilient wireless solutions for government sponsors." But we already have many bullets; maybe we should add to capture that line. However we must preserve all substantive information; we should not omit that line. Let's add a bullet under Responsibilities: "Apply innovative thought and technical expertise to develop cutting-edge resilient wireless solutions for Government Sponsors." Also "In this position, you will apply your technical expertise towards furthering the public good by developing, applying, and evaluating state-of-the-art communications and signal processing technologies." That's similar to intro but we could add bullet. We already have intro paragraph about role; maybe that covers. But to be safe, we can add a bullet: "Apply technical expertise to develop, apply, and evaluate state-of-the-art communications and signal processing technologies for public good." We'll add. Also "Typical projects include:" we already captured list. Also "Responsibilities may include:" we captured. Now check if any other specifics: "The ideal