Sr. Systems Software Engineer
SPX Technologies · Fremont, CA · 3 wk ago
Information Technology$175k–$195k/yrFull-time
We need to output HTML fragment with sections: Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content.
We need to parse the posting.
First, there is a company description paragraph: "Building the people that build the world..." etc. That's likely "About the role"? Actually "About the role" is a heading for description of role? The posting includes "How You Will Make An Impact (Job Summary)" and "What You Can Expect In This Role (Job Responsibilities)". Also "What we are looking for (Experience, Knowledge, Skills, Abilities, Education)". Then compensation, benefits, culture, etc.
We need to decide sections.
We should not repeat job title as heading. The page already shows it.
We need to include sections only when there is real specific content.
Let's extract content:
- About the role: Could be the job summary: "How You Will Make An Impact (Job Summary)" paragraph: "SPX is a diverse team... As a Senior Systems Software Engineer at TCI, you will contribute to the design and development of advanced RF signal acquisition, processing, analysis, and direction-finding systems used for spectrum monitoring and communications intelligence applications. You will work with multidisciplinary engineering teams to develop software that transforms complex RF and signal-processing concepts into high-performance products used by customers worldwide."
That's substantive.
- Responsibilities: "What You Can Expect In This Role (Job Responsibilities)" bullet list: "Design, develop, and maintain embedded and real-time software for RF and signal-processing systems. Enhance existing products and develop new capabilities across TCI's product portfolio. Collaborate closely with systems, hardware, test, and software engineers to deliver integrated product solutions. Support system integration, performance analysis, troubleshooting, and field issue resolution. Participate in software architecture, technical trade-off analysis, and design reviews. Contribute technical expertise in signal processing, RF systems, and software implementation."
- Requirements: The "What we are looking for (Experience, Knowledge, Skills, Abilities, Education)" includes required experience and preferred knowledge etc. Could split into Requirements (required) and Qualifications (preferred) and Skills? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include.
We have required experience: 6+ years, strong foundation in DSP, RF, etc., strong C++ skills, multi-threaded, analytical, problem solving, communication.
Preferred knowledge: Windows/Linux, inter-process communication, SDR, spectrum monitoring, direction finding, geolocation, FPGA-based signal processing, Python/MATLAB, familiarity with source control CI/CD.
Education & Certifications: MS in EE, CE, CS or related with emphasis in DSP, RF, Wireless, Signal Analysis; PhD preferred; BS with substantial experience considered. Must be US citizen or Permanent Resident for ITAR.
Thus we could have:
- Requirements: required experience (maybe also education? but education could be Qualifications). The instruction says we can have both Requirements and Qualifications sections. Let's put required experience under Requirements, and preferred knowledge/skills/abilities under Qualifications? Or Skills? Actually Skills heading could be for technical skills list. But we have both required and preferred.
We could do:
Requirements: required experience (6+ years, DSP foundation, C++, multi-threaded, analytical, problem solving, communication).
Qualifications: preferred knowledge (Windows/Linux, IPC, SDR, spectrum monitoring, DF, geolocation, FPGA, Python/MATLAB, source control CI/CD) plus education (MS preferred, PhD preferred, BS considered, US citizen/PR).
Skills: maybe we could list specific skills like C++, DSP, RF, etc. But we already covered. Might be redundant.
Better to follow typical pattern: Requirements = required experience + education; Qualifications = preferred experience/skills; Skills = maybe list of technical skills (C++, DSP, etc). But we have overlapping.
Given instruction: "Prefer a few substantive sections over many thin ones." So we should not create many sections with little content. Let's combine.
We could have:
- About the role (job summary)
- Responsibilities
- Requirements (includes required experience, education, citizenship)
- Qualifications (preferred knowledge/skills)
- Benefits (health, 401k match, flexible time off, bonus plan, etc.)
- Pay (salary range $175k-$195k, bonus eligibility)
- Schedule? Not mentioned. So omit Schedule.
We should not include sections with filler like "commensurate with experience". We have actual salary range.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes a lot of culture and diversity statements, which might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The culture/values section may be considered not boilerplate but could be kept? It's not explicitly prohibited. However, we should focus on substantive job info. The culture section is generic; maybe we can omit as it's not specific to role. The instruction: "Prefer a few substantive sections over many thin ones." The culture section is not specific to role; could be considered thin. Better to omit.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Now format:
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content.
We need to parse the posting.
First, there is a company description paragraph: "Building the people that build the world..." etc. That's likely "About the role"? Actually "About the role" is a heading for description of role? The posting includes "How You Will Make An Impact (Job Summary)" and "What You Can Expect In This Role (Job Responsibilities)". Also "What we are looking for (Experience, Knowledge, Skills, Abilities, Education)". Then compensation, benefits, culture, etc.
We need to decide sections.
We should not repeat job title as heading. The page already shows it.
We need to include sections only when there is real specific content.
Let's extract content:
- About the role: Could be the job summary: "How You Will Make An Impact (Job Summary)" paragraph: "SPX is a diverse team... As a Senior Systems Software Engineer at TCI, you will contribute to the design and development of advanced RF signal acquisition, processing, analysis, and direction-finding systems used for spectrum monitoring and communications intelligence applications. You will work with multidisciplinary engineering teams to develop software that transforms complex RF and signal-processing concepts into high-performance products used by customers worldwide."
That's substantive.
- Responsibilities: "What You Can Expect In This Role (Job Responsibilities)" bullet list: "Design, develop, and maintain embedded and real-time software for RF and signal-processing systems. Enhance existing products and develop new capabilities across TCI's product portfolio. Collaborate closely with systems, hardware, test, and software engineers to deliver integrated product solutions. Support system integration, performance analysis, troubleshooting, and field issue resolution. Participate in software architecture, technical trade-off analysis, and design reviews. Contribute technical expertise in signal processing, RF systems, and software implementation."
- Requirements: The "What we are looking for (Experience, Knowledge, Skills, Abilities, Education)" includes required experience and preferred knowledge etc. Could split into Requirements (required) and Qualifications (preferred) and Skills? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include.
We have required experience: 6+ years, strong foundation in DSP, RF, etc., strong C++ skills, multi-threaded, analytical, problem solving, communication.
Preferred knowledge: Windows/Linux, inter-process communication, SDR, spectrum monitoring, direction finding, geolocation, FPGA-based signal processing, Python/MATLAB, familiarity with source control CI/CD.
Education & Certifications: MS in EE, CE, CS or related with emphasis in DSP, RF, Wireless, Signal Analysis; PhD preferred; BS with substantial experience considered. Must be US citizen or Permanent Resident for ITAR.
Thus we could have:
- Requirements: required experience (maybe also education? but education could be Qualifications). The instruction says we can have both Requirements and Qualifications sections. Let's put required experience under Requirements, and preferred knowledge/skills/abilities under Qualifications? Or Skills? Actually Skills heading could be for technical skills list. But we have both required and preferred.
We could do:
Requirements: required experience (6+ years, DSP foundation, C++, multi-threaded, analytical, problem solving, communication).
Qualifications: preferred knowledge (Windows/Linux, IPC, SDR, spectrum monitoring, DF, geolocation, FPGA, Python/MATLAB, source control CI/CD) plus education (MS preferred, PhD preferred, BS considered, US citizen/PR).
Skills: maybe we could list specific skills like C++, DSP, RF, etc. But we already covered. Might be redundant.
Better to follow typical pattern: Requirements = required experience + education; Qualifications = preferred experience/skills; Skills = maybe list of technical skills (C++, DSP, etc). But we have overlapping.
Given instruction: "Prefer a few substantive sections over many thin ones." So we should not create many sections with little content. Let's combine.
We could have:
- About the role (job summary)
- Responsibilities
- Requirements (includes required experience, education, citizenship)
- Qualifications (preferred knowledge/skills)
- Benefits (health, 401k match, flexible time off, bonus plan, etc.)
- Pay (salary range $175k-$195k, bonus eligibility)
- Schedule? Not mentioned. So omit Schedule.
We should not include sections with filler like "commensurate with experience". We have actual salary range.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes a lot of culture and diversity statements, which might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The culture/values section may be considered not boilerplate but could be kept? It's not explicitly prohibited. However, we should focus on substantive job info. The culture section is generic; maybe we can omit as it's not specific to role. The instruction: "Prefer a few substantive sections over many thin ones." The culture section is not specific to role; could be considered thin. Better to omit.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Now format:
About the role
SPX is a diverse team of unique individuals who all make an impact. As a Senior Systems Software Engineer at TCI, you will contribute to the design and development of advanced RF signal acquisition, processing, analysis, and direction-finding systems used for spectrum monitoring and communications intelligence applications. You will work with multidisciplinary engineering teams to develop software that transforms complex RF and signal-processing concepts into high-performance products used by customers worldwide.
Responsibilities
- Design, develop, and maintain embedded and real-time software for RF and signal-processing systems.
- Enhance existing products and develop new capabilities across TCI's product portfolio.
- Collaborate closely with systems, hardware, test, and software engineers to deliver integrated product solutions.
- Support system integration, performance analysis, troubleshooting, and field issue resolution.
- Participate in software architecture, technical trade-off analysis, and design reviews.
- Contribute technical expertise in signal processing, RF systems, and software implementation.
Requirements
- 6+ years of relevant product development experience.
- Strong foundation in digital signal processing (DSP), RF communications systems, receiver architecture, signal detection, and signal analysis.
- Strong C++ software development skills with experience developing complex software systems.
- Experience developing multi-threaded software.
- Strong analytical, problem-solving, and communication skills.
- Master’s degree in Electrical Engineering, Computer Engineering, Computer Science, or a related discipline with emphasis in Digital Signal Processing (DSP), RF Communications, Wireless Communications, Signal Analysis, or related fields. A PhD is preferred; a BS with substantial directly relevant experience will also be considered.
- Must be a U.S. citizen or Permanent Resident to meet ITAR compliance requirements.
Qualifications
- Experience developing software in Windows and/or Linux environments.
- Experience with inter-process and inter-core communication.
- Experience with Software Defined Radio (SDR) platforms.
- Experience with spectrum monitoring, direction finding, and geolocation.
- Experience with FPGA-based signal-processing systems.
- Experience with Python, MATLAB, or similar engineering tools.
- Familiarity with modern source-control, CI/CD, and automated test practices.
Benefits
- Health benefits.
- 401(k) retirement with a company match.
- Flexible time off.
- Discretionary bonus plan eligibility.
- Generous and flexible paid time off including paid personal time off, caregiver, parental, and volunteer leave.
- Competitive health insurance plans and 401(k) match, with benefits starting day one.
- Competitive and performance-based compensation packages and bonus plans.
- Educational assistance, leadership development programs, and recognition programs.
- ...
Pay
The estimated salary range for this position is $175,000 - $195,000. This role is eligible to participate in a discretionary bonus plan, subject to the rules governing the plan.
We should not include filler like "At SPX, it is not common for individuals to be hired at the higher end of the range". That's somewhat filler but still substantive? It's extra detail but maybe we can keep? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that sentence if it's substantive. It's about compensation decisions. It's not filler like "commensurate with experience". It's actual detail. So we can include. Thus Pay section could have two paragraphs: salary range and note about hiring at higher end and compensation decisions. We'll output:Pay
The estimated salary range for this position is $175,000 - $195,000. At SPX, it is not common for individuals to be hired at the higher end of the range, and compensation decisions depend on a variety of factors.
This role is eligible to participate in a discretionary bonus plan, subject to the rules governing the plan.
Now ensure we didn't include Schedule section. Check for any other sections: maybe "About the company" but we used About the role. The initial paragraph about SPX Technologies building innovative solutions etc. That's company overview, not role-specific. Could be considered "About the role"? Actually "About the role" is supposed to be description of role; we used job summary. The company overview could be omitted as not role-specific. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." The company overview is not metadata; it's general company description. Could be considered boilerplate? Not exactly. But we already have About the role with job summary. Might be okay to include company overview as part of About the role? But we already used that heading for job summary. Could we add another paragraph under About the role containing company overview? That would be okay: About the role can include both company description and job summary. However, the instruction says "use