DSP SW Engineer
E-Space · Santa Clara, CA · 3 wk ago
On-siteEngineering$100k–$200k/yrFull-time
We need to output HTML fragment with sections using 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 posting.
First, there is an intro: "Ready to make connectivity from space universally accessible..." etc. That's likely "About the role" or maybe "About the role" is a heading. The posting includes "What you will do:" which is responsibilities. Then "What you bring to this role:" which is qualifications/requirements. Then "Bonus points for the following:" which could be Skills or additional qualifications. Then "Additional Requirements" includes flexibility to work extended hours etc. Then pay info: "$100,000 - $200,000 a year" and "This is a full time, exempt position, based out of our Santa Clara office." Also "The target base pay for this position is $100,000 - $200,000 annually." So we have Pay section.
Then "Why E-Space is right for you:" and bullet list of benefits: "An opportunity to really make a difference", "Sustainability at our core", etc. Also "We want you to make the most of your journey at E-Space. That’s why we support and invest in the physical, emotional and financial well-being of our team members and their families. Some of what you can expect when working at E-Space: ..." So Benefits section.
Schedule: Not explicitly mentioned besides "flexibility to occasionally work extended hours or weekends during critical periods is expected." That's more about schedule expectations. Could be Schedule section.
We need to avoid boilerplate like EEO, legal, etc. Also remove duplicated lines.
We must preserve all substantive information; do not invent or summarize away detail.
We need to use
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 posting.
First, there is an intro: "Ready to make connectivity from space universally accessible..." etc. That's likely "About the role" or maybe "About the role" is a heading. The posting includes "What you will do:" which is responsibilities. Then "What you bring to this role:" which is qualifications/requirements. Then "Bonus points for the following:" which could be Skills or additional qualifications. Then "Additional Requirements" includes flexibility to work extended hours etc. Then pay info: "$100,000 - $200,000 a year" and "This is a full time, exempt position, based out of our Santa Clara office." Also "The target base pay for this position is $100,000 - $200,000 annually." So we have Pay section.
Then "Why E-Space is right for you:" and bullet list of benefits: "An opportunity to really make a difference", "Sustainability at our core", etc. Also "We want you to make the most of your journey at E-Space. That’s why we support and invest in the physical, emotional and financial well-being of our team members and their families. Some of what you can expect when working at E-Space: ..." So Benefits section.
Schedule: Not explicitly mentioned besides "flexibility to occasionally work extended hours or weekends during critical periods is expected." That's more about schedule expectations. Could be Schedule section.
We need to avoid boilerplate like EEO, legal, etc. Also remove duplicated lines.
We must preserve all substantive information; do not invent or summarize away detail.
We need to use for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
First, maybe an "About the role" section: The introductory paragraph(s) before "What you will do:" could be considered about the role/mission. Let's capture:
"Ready to make connectivity from space universally accessible, secure and actionable? Then you’ve come to the right place! E-Space is bridging Earth and space to enable hyper-scaled deployments of Internet of Things (IoT) solutions and services. We are building a highly-advanced low Earth orbit (LEO) space system that will fundamentally change the design, economics, manufacturing and service delivery associated with traditional satellite and terrestrial IoT systems. We’re intentional, we’re unapologetically curious and we’re 100% committed to innovate space-based communications and deliver actionable intelligence that will expand global economies, protect space and our planet and enhance our overall quality of life."
That's substantive. We'll put that in
under
About the role
.
Next Responsibilities: Under "What you will do:" list bullet points (each sentence separated by period?). Let's list each duty as separate - .
The text:
"Implement and evaluate defined DSP and 5G NR physical-layer (PHY) functions for satellite communications over non-terrestrial networks (NTN), working from agreed specifications and technical guidance.Develop and run PHY/link-level simulations to measure error rates, throughput, and acquisition and tracking performance under representative satellite channel conditions, including propagation delay, Doppler, noise, and RF impairments.Develop, test, and optimize C/C++ DSP firmware for 5G NR PHY processing, meeting defined execution-time, memory, power, and numerical-accuracy requirements.Create floating-point and fixed-point reference models, reproducible test vectors, and expected results for ASIC designers and verification engineers. Document interfaces, scaling, rounding, saturation, and other assumptions needed to compare implementations.Contribute to SystemC transaction-level modeling (TLM) and high-level synthesis (HLS) development, including synthesizable implementations, with guidance from engineers experienced in these flows.Support pre-silicon verification and new-chip bring-up by running regressions, comparing model, firmware, and hardware results, investigating discrepancies, and documenting fixes with ASIC, verification, and software engineers."
We need to split into separate items. Each sentence ends with a period. We'll create
- for each.
Now Requirements/Qualifications: "What you bring to this role:" list bullet points.
Text:
"Demonstrated DSP and digital-communications fundamentals, including sampling, filtering, modulation, OFDM, synchronization, channel estimation, and error-correction concepts. Evidence may come from academic, research, personal, or professional projects.Ability to implement and debug numerical algorithms in C/C++, and to use Python or MATLAB for simulation, analysis, and test automation.Working knowledge of wireless PHY processing and the ability to translate technical specifications into implementation and test cases; familiarity with the basic structure of a 5G NR PHY.Understanding of fixed-point arithmetic, quantization, overflow, and numerical precision, with the ability to compare an implementation against a reference model.Understanding of embedded software constraints, including execution time, memory use, and hardware/software interfaces, supported by practical implementation or debugging work.Ability to build reproducible tests, use version control, document technical assumptions and results, and explain discrepancies during code and design reviews."
We'll make each as
- .
Now Bonus points: "Bonus points for the following:" list.
Text:
"Experience with SystemC TLM, or with HLS tools to develop and verify synthesizable C/C++ or SystemC implementations.Experience with 5G NR or NTN algorithms and specifications, satellite channel modeling, or compensation for Doppler and timing effects.Experience with FPGA/ASIC verification, emulation, SDR platforms, chip bring-up, or laboratory validation of communication systems.Experience with 5G NR MAC, PHY/MAC interfaces, scheduling interactions, or HARQ procedures.Experience implementing and optimizing algorithms on vector DSPs, including SIMD intrinsics, vectorization, and efficient memory access.Experience with low-power ASIC or firmware design, including reducing computation and data movement, managing idle states, or measuring power consumption."
We could treat these as Skills or Additional Qualifications. The spec allows Skills section. We'll put under
Skills
maybe. Or we could incorporate into Requirements. But better to have Skills section for bonus points.
Now Additional Requirements: "This is a fast-paced, high-impact environment - flexibility to occasionally work extended hours or weekends during critical periods is expected." That's schedule expectation. Also maybe "We are redefining how satellites are designed, manufactured and used—so we’re looking for candidates with passion, deep knowledge and direct experience on LEO satellite component development, design and in-orbit activities. If that’s your experience – then we’ll be immediately wow-ed." That's more like a statement about desired experience; could be part of Requirements. Also "E-Space is not currently able to provide employment sponsorship for candidates who do not hold work authorization for the location of this role." That's a requirement (work authorization). We'll include that in Requirements or maybe a separate section like "Additional Requirements". But we have limited headings; we could put under Requirements as extra items.
We need to avoid boilerplate like "EEO", etc. The "Additional Requirements" paragraph includes flexibility to work extended hours etc. We'll treat that as Schedule maybe.
Now Pay: "$100,000 - $200,000 a year" and "This is a full time, exempt position, based out of our Santa Clara office." Also "The target base pay for this position is $100,000 - $200,000 annually." We'll put Pay section with that info.
Now Benefits: Under "Why E-Space is right for you:" and following bullet list.
Paragraph: "As a member of our team, you will play a crucial role in driving our success. Our team members have a strong sense of dedication and responsibility; this includes a strong commitment to our mission to create an entirely new suite of global capabilities to improve lives, business efficiencies and build a smarter planet. This means that there will be times when extra hours, including nights and weekends, may be needed to meet critical deadlines and mission goals. In return, we offer a dynamic work environment with opportunities for professional growth and development and the chance to make a meaningful impact in a high-growth industry. We want you to make the most of your journey at E-Space. That’s why we support and invest in the physical, emotional and financial well-being of our team members and their families. Some of what you can expect when working at E-Space:"
Then bullet list:
- An opportunity to really make a difference
- Sustainability at our core
- Fair and honest workplace
- Innovative thinking is encouraged
- Competitive salaries
- Continuous learning and development
- Health and wellness care options
- Financial solutions for the future
- Optional legal services (US only)
- Paid holidays
- Paid time off
We'll put those as - .
Now Schedule: We have flexibility to occasionally work extended hours or weekends during critical periods is expected. Also maybe mention full-time exempt position based out of Santa Clara office (location). That could be Schedule? Actually location is not schedule. But we could include location under Schedule or maybe under About the role? The spec says Schedule section only if posting actually states them. The posting mentions "This is a full time, exempt position, based out of our Santa Clara office." That's about employment type and location, not schedule. However schedule could be inferred from "flexibility to occasionally work extended hours or weekends during critical periods is expected." That's schedule expectation. We'll create Schedule section with that sentence.
Now we need to ensure we don't create sections with filler like "commensurate with experience". We have actual content.
Now we need to avoid duplication: The pay appears twice; we can include once.
Now we need to avoid including "We may use artificial intelligence (AI) tools..." that's boilerplate; remove.
Also remove "If you would like more information about how your data is processed, please contact us." That's boilerplate.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Maybe also include "Additional Requirements" like work authorization and fast-paced environment; we could add to Requirements.
Skills
- ...
...
Benefits
- ...
...
Pay
$100,000 - $200,000 a year. This is a full-time, exempt position based out of our Santa Clara office.
Schedule
Flexibility to occasionally work extended hours or weekends during critical periods is expected.
Check if any other sections like Qualifications vs Requirements; we have Requirements covering qualifications. Could also have Qualifications separate but not needed.
Now ensure we preserve all substantive information: Did we miss any? Let's review original text for any other details not captured.
Original includes: "We are redefining how satellites are designed, manufactured and used—so we’re looking for candidates with passion, deep knowledge and direct experience on LEO satellite component development, design and in-orbit activities. If that’s your experience – then we’ll be immediately wow-ed." This is a statement about desired experience; we haven't included that. Should we include it? It's substantive. Could be added to Requirements as an item.
Also: "E-Space is not currently able to provide employment sponsorship for candidates who do not hold work authorization for the location of this role." That's a requirement; we should include.
Also: "We may use artificial intelligence (AI) tools..." we removed as boilerplate.
Also: "Final hiring decisions are ultimately made by humans." That's boilerplate
- for any list of duties/requirements/benefits, and
for prose. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. First, maybe an "About the role" section: The introductory paragraph(s) before "What you will do:" could be considered about the role/mission. Let's capture: "Ready to make connectivity from space universally accessible, secure and actionable? Then you’ve come to the right place! E-Space is bridging Earth and space to enable hyper-scaled deployments of Internet of Things (IoT) solutions and services. We are building a highly-advanced low Earth orbit (LEO) space system that will fundamentally change the design, economics, manufacturing and service delivery associated with traditional satellite and terrestrial IoT systems. We’re intentional, we’re unapologetically curious and we’re 100% committed to innovate space-based communications and deliver actionable intelligence that will expand global economies, protect space and our planet and enhance our overall quality of life." That's substantive. We'll put that in
under
About the role
. Next Responsibilities: Under "What you will do:" list bullet points (each sentence separated by period?). Let's list each duty as separate - . The text: "Implement and evaluate defined DSP and 5G NR physical-layer (PHY) functions for satellite communications over non-terrestrial networks (NTN), working from agreed specifications and technical guidance.Develop and run PHY/link-level simulations to measure error rates, throughput, and acquisition and tracking performance under representative satellite channel conditions, including propagation delay, Doppler, noise, and RF impairments.Develop, test, and optimize C/C++ DSP firmware for 5G NR PHY processing, meeting defined execution-time, memory, power, and numerical-accuracy requirements.Create floating-point and fixed-point reference models, reproducible test vectors, and expected results for ASIC designers and verification engineers. Document interfaces, scaling, rounding, saturation, and other assumptions needed to compare implementations.Contribute to SystemC transaction-level modeling (TLM) and high-level synthesis (HLS) development, including synthesizable implementations, with guidance from engineers experienced in these flows.Support pre-silicon verification and new-chip bring-up by running regressions, comparing model, firmware, and hardware results, investigating discrepancies, and documenting fixes with ASIC, verification, and software engineers." We need to split into separate items. Each sentence ends with a period. We'll create
- for each. Now Requirements/Qualifications: "What you bring to this role:" list bullet points. Text: "Demonstrated DSP and digital-communications fundamentals, including sampling, filtering, modulation, OFDM, synchronization, channel estimation, and error-correction concepts. Evidence may come from academic, research, personal, or professional projects.Ability to implement and debug numerical algorithms in C/C++, and to use Python or MATLAB for simulation, analysis, and test automation.Working knowledge of wireless PHY processing and the ability to translate technical specifications into implementation and test cases; familiarity with the basic structure of a 5G NR PHY.Understanding of fixed-point arithmetic, quantization, overflow, and numerical precision, with the ability to compare an implementation against a reference model.Understanding of embedded software constraints, including execution time, memory use, and hardware/software interfaces, supported by practical implementation or debugging work.Ability to build reproducible tests, use version control, document technical assumptions and results, and explain discrepancies during code and design reviews." We'll make each as
- .
Now Bonus points: "Bonus points for the following:" list.
Text:
"Experience with SystemC TLM, or with HLS tools to develop and verify synthesizable C/C++ or SystemC implementations.Experience with 5G NR or NTN algorithms and specifications, satellite channel modeling, or compensation for Doppler and timing effects.Experience with FPGA/ASIC verification, emulation, SDR platforms, chip bring-up, or laboratory validation of communication systems.Experience with 5G NR MAC, PHY/MAC interfaces, scheduling interactions, or HARQ procedures.Experience implementing and optimizing algorithms on vector DSPs, including SIMD intrinsics, vectorization, and efficient memory access.Experience with low-power ASIC or firmware design, including reducing computation and data movement, managing idle states, or measuring power consumption."
We could treat these as Skills or Additional Qualifications. The spec allows Skills section. We'll put under
Skills
maybe. Or we could incorporate into Requirements. But better to have Skills section for bonus points. Now Additional Requirements: "This is a fast-paced, high-impact environment - flexibility to occasionally work extended hours or weekends during critical periods is expected." That's schedule expectation. Also maybe "We are redefining how satellites are designed, manufactured and used—so we’re looking for candidates with passion, deep knowledge and direct experience on LEO satellite component development, design and in-orbit activities. If that’s your experience – then we’ll be immediately wow-ed." That's more like a statement about desired experience; could be part of Requirements. Also "E-Space is not currently able to provide employment sponsorship for candidates who do not hold work authorization for the location of this role." That's a requirement (work authorization). We'll include that in Requirements or maybe a separate section like "Additional Requirements". But we have limited headings; we could put under Requirements as extra items. We need to avoid boilerplate like "EEO", etc. The "Additional Requirements" paragraph includes flexibility to work extended hours etc. We'll treat that as Schedule maybe. Now Pay: "$100,000 - $200,000 a year" and "This is a full time, exempt position, based out of our Santa Clara office." Also "The target base pay for this position is $100,000 - $200,000 annually." We'll put Pay section with that info. Now Benefits: Under "Why E-Space is right for you:" and following bullet list. Paragraph: "As a member of our team, you will play a crucial role in driving our success. Our team members have a strong sense of dedication and responsibility; this includes a strong commitment to our mission to create an entirely new suite of global capabilities to improve lives, business efficiencies and build a smarter planet. This means that there will be times when extra hours, including nights and weekends, may be needed to meet critical deadlines and mission goals. In return, we offer a dynamic work environment with opportunities for professional growth and development and the chance to make a meaningful impact in a high-growth industry. We want you to make the most of your journey at E-Space. That’s why we support and invest in the physical, emotional and financial well-being of our team members and their families. Some of what you can expect when working at E-Space:" Then bullet list: - An opportunity to really make a difference - Sustainability at our core - Fair and honest workplace - Innovative thinking is encouraged - Competitive salaries - Continuous learning and development - Health and wellness care options - Financial solutions for the future - Optional legal services (US only) - Paid holidays - Paid time off We'll put those as- .
Now Schedule: We have flexibility to occasionally work extended hours or weekends during critical periods is expected. Also maybe mention full-time exempt position based out of Santa Clara office (location). That could be Schedule? Actually location is not schedule. But we could include location under Schedule or maybe under About the role? The spec says Schedule section only if posting actually states them. The posting mentions "This is a full time, exempt position, based out of our Santa Clara office." That's about employment type and location, not schedule. However schedule could be inferred from "flexibility to occasionally work extended hours or weekends during critical periods is expected." That's schedule expectation. We'll create Schedule section with that sentence.
Now we need to ensure we don't create sections with filler like "commensurate with experience". We have actual content.
Now we need to avoid duplication: The pay appears twice; we can include once.
Now we need to avoid including "We may use artificial intelligence (AI) tools..." that's boilerplate; remove.
Also remove "If you would like more information about how your data is processed, please contact us." That's boilerplate.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
$100,000 - $200,000 a year. This is a full-time, exempt position based out of our Santa Clara office.
Schedule
Flexibility to occasionally work extended hours or weekends during critical periods is expected.
Check if any other sections like Qualifications vs Requirements; we have Requirements covering qualifications. Could also have Qualifications separate but not needed. Now ensure we preserve all substantive information: Did we miss any? Let's review original text for any other details not captured. Original includes: "We are redefining how satellites are designed, manufactured and used—so we’re looking for candidates with passion, deep knowledge and direct experience on LEO satellite component development, design and in-orbit activities. If that’s your experience – then we’ll be immediately wow-ed." This is a statement about desired experience; we haven't included that. Should we include it? It's substantive. Could be added to Requirements as an item. Also: "E-Space is not currently able to provide employment sponsorship for candidates who do not hold work authorization for the location of this role." That's a requirement; we should include. Also: "We may use artificial intelligence (AI) tools..." we removed as boilerplate. Also: "Final hiring decisions are ultimately made by humans." That's boilerplate
- .
Now Schedule: We have flexibility to occasionally work extended hours or weekends during critical periods is expected. Also maybe mention full-time exempt position based out of Santa Clara office (location). That could be Schedule? Actually location is not schedule. But we could include location under Schedule or maybe under About the role? The spec says Schedule section only if posting actually states them. The posting mentions "This is a full time, exempt position, based out of our Santa Clara office." That's about employment type and location, not schedule. However schedule could be inferred from "flexibility to occasionally work extended hours or weekends during critical periods is expected." That's schedule expectation. We'll create Schedule section with that sentence.
Now we need to ensure we don't create sections with filler like "commensurate with experience". We have actual content.
Now we need to avoid duplication: The pay appears twice; we can include once.
Now we need to avoid including "We may use artificial intelligence (AI) tools..." that's boilerplate; remove.
Also remove "If you would like more information about how your data is processed, please contact us." That's boilerplate.
Now produce HTML.
Structure: