Embedded System Engineer
? The instructions: 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 (the page already shows it) and 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. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to parse the posting.
Key sections:
- About Us (company description) - could be a paragraph.
- What We Do: description of company's focus.
- What You Will Do: overview.
- Responsibilities: bullet list.
- What You Need: qualifications (education, experience, skills). Could be a list.
- Salary range: "Our good faith estimate of the salary range for this role is $96,000 - $131,000. Exact compensation may vary based on skills, experience, and other factors." This is pay info, so we should include a Pay section with that content.
- Benefits: "In addition to base pay, we offer a full benefits package." That's benefits info, so include Benefits section.
- Schedule: "This position requires on-site presence at Spellman High Voltage headquarters in Hauppauge, NY." That's schedule/location info. Could be Schedule section.
- Location: Hauppauge, NY (maybe part of schedule). We'll include location in schedule.
- Embedded Systems Engineer Reports To: Director, Embedded Systems & Controls Department: Engineering Location Hauppauge, NY - we can fold minor metadata into a short
or drop it. Probably include a short paragraph with reporting line and department.
- Also "What You Will Do" includes some prose.
- "Other expectations:" bullet list? Actually it's a paragraph with multiple sentences. Could treat as part of responsibilities? But we already have Responsibilities section. The "Other expectations:" seems like additional responsibilities. We could incorporate into Responsibilities list.
We need to avoid duplication. Let's extract substantive content.
First, company description: "Spellman High Voltage Electronics Corporation, a family owned business for over 75 years, takes pride in powering progress in health, security and quality of life. We are key partners with the world’s leading medical devices, semiconductor, scientific analytics and industrial systems manufacturers. When they want to push the limits of what’s possible with high voltage applications, they turn to us to make it happen. While Spellman is not a household name, our products are used to make and often power many of the most advanced technologies that make modern life possible. With design and manufacturing sites in North America, Europe and Asia, we have become the preferred provider of high voltage power solutions for OEMs pushing the boundaries of technology around the world by designing and producing the products they need to power progress."
That's About Us.
Next, "What We Do: Spellman High Voltage Electronics Corp. is a leading and growing international company that delivers advanced products and solutions into the medical imaging, Non-Destructive Testing (NDT), Food Inspection and Transport Security markets at the global scale. As a part of our continuous focus on offering high performance and cutting-edge products and solutions to our markets, the field of advanced power conversion, power management and controls, embedded systems is of strategic and critical importance. In this context, Spellman High Voltage Electronics Corp. is seeking a highly talented, motivated, creative, and experienced engineering leader in the field of embedded systems in the field of Power Electronics, Power Management and Digital Controls, to include development, testing and validation."
That could be a section "About the role" maybe. But we have "About the role" as a possible heading. However the instructions say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role heading.
But we already have About Us separate. Could combine About Us and What We Do into About the role? Actually About the role usually describes the role, not company. But we can still have About the role heading containing the description of what we do and the seeking statement. However we also have About Us separate. The instructions say include a section ONLY when the posting has real, specific content for it. So we can have both About Us and About the role if they have content. But About Us is not one of the example headings; they gave examples but not limited to those. We can still use for any section heading. So we can have About Us
and About the Role
.
But we need to avoid thin sections. Both have substantive content.
Next, "What You Will Do: Support the design, development, implementation, testing, and documentation of firmware and software to be used in high voltage power supplies in all our markets and applications of interest, interfacing and supporting our global engineering community as needed."
That's a paragraph; could be part of Responsibilities or a separate section "What You Will Do". But we already have Responsibilities section; maybe we can incorporate this into Responsibilities as an overview bullet? However the Responsibilities section later has a list of duties. The "What You Will Do" is a summary; we could keep it as a paragraph under Responsibilities heading before the list.
But instructions: Use - for any list of duties/requirements/benefits, and
for prose. So we can have a
for the overview, then a
for the list.
Now Responsibilities list: The bullet points after "Responsibilities" heading:
- Technical Support project planning for firmware/software development needs
- Hands-on support of firmware and software design for high voltage power supplies (HVPS). Languages used (C, Verilog, VHDL, Assembly, C, C#, VB6, Java, WPF, Linux) and firmware development based on RTOS.
- Interface with peers in the Engineering team to implement features desired as described in product and application requirements.
- Support the preparation of all technical documentation, such as circuit and block diagrams, test reports, manuals, technical reports, release documentation etc.
- Support the review and interpretation of internal/external customer requirements
- Support the improvement of the FW and SW release process, to include the use of revision control systems such as Tortoise SVN
- Continuous research of latest concepts as they pertain to Embedded Systems: Development including DSP’s, MCU’s, FPGA’s, CPLD’s, SOM.
- Other expectations: As needed, interface with the company’s sales & Marketing, operations, and quality teams among others, in support of common projects and overall company strategy
- As needed, support the development of Embedded Systems Engineering plans for current and future product and technology development projects based on the company’s overall objectives
- Embrace an engineering culture of high performance and provide the corresponding behaviors and performance.
- Proactively seek guidance and mentoring to ensure a comprehensive understanding of what a hands-on approach to executing Embedded Systems projects with a focus on comprehensive requirements analysis, definition of the appropriate technical approach and solution, project planning and management, and risk assessment and mitigation, means and how it is implemented.
- Support product development design reviews and provide applicable inputs and associated documentation for design changes, specifications, and Software/Firmware releases among others per Spellman engineering product development processes.
We need to turn each into - . Some are long sentences; we keep them.
Now "What You Need:" section includes qualifications:
- Bachelor’s degree (Master’s degree preferred) in Electrical Engineering and minimum 3 years of experience in Embedded Systems tasks and projects.
- Understanding of the principles of Design and Development principles of FPGA code using Verilog or VHDL
- Understanding of the principles of digital systems that include ADC’s, DAC's, UART's, RS-485, RS-232, embedded Ethernet, USB, microcontrollers, DSP’s, RAM, SRAM, EEPROM, switching low-voltage power supplies, pulse-width modulation devices, discrete logic, and FPGA’s
- Understanding of the principles of using emulators, debuggers, JTAG, integrated development environments, and other design and verification tools
- Some experience with/ exposure to advanced engineering tools such as: Matlab-Simulink, PSIM and others.
- Basics in the development of design documentation that can be presented to the customer community
- Support for design verification testing and documentation
- Passion about collaborating with other company teams in a multidisciplinary environment (sales and marketing, operations, quality, supply chain), customers…etc. to drive a continuous and strong focus on value creation
We can treat as Requirements or Qualifications. The instructions list headings: Requirements, Qualifications, Skills. We could combine into Requirements (or Qualifications). Since it's a mix of education, experience, skills, we could have a single section "Requirements" with a list.
Now Pay: "Our good faith estimate of the salary range for this role is $96,000 - $131,000. Exact compensation may vary based on skills, experience, and other factors."
We'll put in Pay section as a
.
Benefits: "In addition to base pay, we offer a full benefits package."
We'll put in Benefits section as a
.
Schedule: "This position requires on-site presence at Spellman High Voltage headquarters in Hauppauge, NY."
We'll put in Schedule section as a
.
Also we have location earlier: "Location Hauppauge, NY". Already covered.
Now we need to remove boilerplate: EEO statement, accommodation request, note to recruiters, etc. Remove those.
Also remove duplicated lines: There's some duplication like "Understanding of the principles of Design and Development principles of FPGA code using Verilog or VHDL" appears maybe twice? Actually appears once. There's duplication of "C" in languages list: "Languages used (C, Verilog, VHDL, Assembly, C, C#, VB6, Java, WPF, Linux)". We'll keep as is but could deduplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Removing duplicate "C" might be considered summarizing away detail? It's a minor duplication; but it's likely okay to keep as is. We could keep the list as given.
Now we need to output only HTML fragment, no markdown.
Structure:
About Us
...
About the Role
...
What You Will Do
...
Responsibilities
- ...
...
Requirements
- ...
...
Pay
...
Benefits
...
Schedule
...
We need to ensure we don't create empty sections.
Now let's craft the content.
About Us paragraph: copy exactly.
About the Role paragraph: copy the "What We Do:" paragraph.
What You Will Do paragraph: copy that sentence.
Responsibilities list: we need to convert each bullet.
Let's list them precisely:
1. Technical Support project planning for firmware/software development needs
for prose. 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 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. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to parse the posting. Key sections: - About Us (company description) - could be a paragraph. - What We Do: description of company's focus. - What You Will Do: overview. - Responsibilities: bullet list. - What You Need: qualifications (education, experience, skills). Could be a list. - Salary range: "Our good faith estimate of the salary range for this role is $96,000 - $131,000. Exact compensation may vary based on skills, experience, and other factors." This is pay info, so we should include a Pay section with that content. - Benefits: "In addition to base pay, we offer a full benefits package." That's benefits info, so include Benefits section. - Schedule: "This position requires on-site presence at Spellman High Voltage headquarters in Hauppauge, NY." That's schedule/location info. Could be Schedule section. - Location: Hauppauge, NY (maybe part of schedule). We'll include location in schedule. - Embedded Systems Engineer Reports To: Director, Embedded Systems & Controls Department: Engineering Location Hauppauge, NY - we can fold minor metadata into a short
or drop it. Probably include a short paragraph with reporting line and department. - Also "What You Will Do" includes some prose. - "Other expectations:" bullet list? Actually it's a paragraph with multiple sentences. Could treat as part of responsibilities? But we already have Responsibilities section. The "Other expectations:" seems like additional responsibilities. We could incorporate into Responsibilities list. We need to avoid duplication. Let's extract substantive content. First, company description: "Spellman High Voltage Electronics Corporation, a family owned business for over 75 years, takes pride in powering progress in health, security and quality of life. We are key partners with the world’s leading medical devices, semiconductor, scientific analytics and industrial systems manufacturers. When they want to push the limits of what’s possible with high voltage applications, they turn to us to make it happen. While Spellman is not a household name, our products are used to make and often power many of the most advanced technologies that make modern life possible. With design and manufacturing sites in North America, Europe and Asia, we have become the preferred provider of high voltage power solutions for OEMs pushing the boundaries of technology around the world by designing and producing the products they need to power progress." That's About Us. Next, "What We Do: Spellman High Voltage Electronics Corp. is a leading and growing international company that delivers advanced products and solutions into the medical imaging, Non-Destructive Testing (NDT), Food Inspection and Transport Security markets at the global scale. As a part of our continuous focus on offering high performance and cutting-edge products and solutions to our markets, the field of advanced power conversion, power management and controls, embedded systems is of strategic and critical importance. In this context, Spellman High Voltage Electronics Corp. is seeking a highly talented, motivated, creative, and experienced engineering leader in the field of embedded systems in the field of Power Electronics, Power Management and Digital Controls, to include development, testing and validation." That could be a section "About the role" maybe. But we have "About the role" as a possible heading. However the instructions say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role heading.
But we already have About Us separate. Could combine About Us and What We Do into About the role? Actually About the role usually describes the role, not company. But we can still have About the role heading containing the description of what we do and the seeking statement. However we also have About Us separate. The instructions say include a section ONLY when the posting has real, specific content for it. So we can have both About Us and About the role if they have content. But About Us is not one of the example headings; they gave examples but not limited to those. We can still use for any section heading. So we can have About Us
and About the Role
.
But we need to avoid thin sections. Both have substantive content.
Next, "What You Will Do: Support the design, development, implementation, testing, and documentation of firmware and software to be used in high voltage power supplies in all our markets and applications of interest, interfacing and supporting our global engineering community as needed."
That's a paragraph; could be part of Responsibilities or a separate section "What You Will Do". But we already have Responsibilities section; maybe we can incorporate this into Responsibilities as an overview bullet? However the Responsibilities section later has a list of duties. The "What You Will Do" is a summary; we could keep it as a paragraph under Responsibilities heading before the list.
But instructions: Use - for any list of duties/requirements/benefits, and
for prose. So we can have a
for the overview, then a
for the list.
Now Responsibilities list: The bullet points after "Responsibilities" heading:
- Technical Support project planning for firmware/software development needs
- Hands-on support of firmware and software design for high voltage power supplies (HVPS). Languages used (C, Verilog, VHDL, Assembly, C, C#, VB6, Java, WPF, Linux) and firmware development based on RTOS.
- Interface with peers in the Engineering team to implement features desired as described in product and application requirements.
- Support the preparation of all technical documentation, such as circuit and block diagrams, test reports, manuals, technical reports, release documentation etc.
- Support the review and interpretation of internal/external customer requirements
- Support the improvement of the FW and SW release process, to include the use of revision control systems such as Tortoise SVN
- Continuous research of latest concepts as they pertain to Embedded Systems: Development including DSP’s, MCU’s, FPGA’s, CPLD’s, SOM.
- Other expectations: As needed, interface with the company’s sales & Marketing, operations, and quality teams among others, in support of common projects and overall company strategy
- As needed, support the development of Embedded Systems Engineering plans for current and future product and technology development projects based on the company’s overall objectives
- Embrace an engineering culture of high performance and provide the corresponding behaviors and performance.
- Proactively seek guidance and mentoring to ensure a comprehensive understanding of what a hands-on approach to executing Embedded Systems projects with a focus on comprehensive requirements analysis, definition of the appropriate technical approach and solution, project planning and management, and risk assessment and mitigation, means and how it is implemented.
- Support product development design reviews and provide applicable inputs and associated documentation for design changes, specifications, and Software/Firmware releases among others per Spellman engineering product development processes.
We need to turn each into - . Some are long sentences; we keep them.
Now "What You Need:" section includes qualifications:
- Bachelor’s degree (Master’s degree preferred) in Electrical Engineering and minimum 3 years of experience in Embedded Systems tasks and projects.
- Understanding of the principles of Design and Development principles of FPGA code using Verilog or VHDL
- Understanding of the principles of digital systems that include ADC’s, DAC's, UART's, RS-485, RS-232, embedded Ethernet, USB, microcontrollers, DSP’s, RAM, SRAM, EEPROM, switching low-voltage power supplies, pulse-width modulation devices, discrete logic, and FPGA’s
- Understanding of the principles of using emulators, debuggers, JTAG, integrated development environments, and other design and verification tools
- Some experience with/ exposure to advanced engineering tools such as: Matlab-Simulink, PSIM and others.
- Basics in the development of design documentation that can be presented to the customer community
- Support for design verification testing and documentation
- Passion about collaborating with other company teams in a multidisciplinary environment (sales and marketing, operations, quality, supply chain), customers…etc. to drive a continuous and strong focus on value creation
We can treat as Requirements or Qualifications. The instructions list headings: Requirements, Qualifications, Skills. We could combine into Requirements (or Qualifications). Since it's a mix of education, experience, skills, we could have a single section "Requirements" with a list.
Now Pay: "Our good faith estimate of the salary range for this role is $96,000 - $131,000. Exact compensation may vary based on skills, experience, and other factors."
We'll put in Pay section as a
.
Benefits: "In addition to base pay, we offer a full benefits package."
We'll put in Benefits section as a
.
Schedule: "This position requires on-site presence at Spellman High Voltage headquarters in Hauppauge, NY."
We'll put in Schedule section as a
.
Also we have location earlier: "Location Hauppauge, NY". Already covered.
Now we need to remove boilerplate: EEO statement, accommodation request, note to recruiters, etc. Remove those.
Also remove duplicated lines: There's some duplication like "Understanding of the principles of Design and Development principles of FPGA code using Verilog or VHDL" appears maybe twice? Actually appears once. There's duplication of "C" in languages list: "Languages used (C, Verilog, VHDL, Assembly, C, C#, VB6, Java, WPF, Linux)". We'll keep as is but could deduplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Removing duplicate "C" might be considered summarizing away detail? It's a minor duplication; but it's likely okay to keep as is. We could keep the list as given.
Now we need to output only HTML fragment, no markdown.
Structure:
About Us
...
About the Role
...
What You Will Do
...
Responsibilities
- ...
...
Requirements
- ...
...
Pay
...
Benefits
...
Schedule
...
We need to ensure we don't create empty sections.
Now let's craft the content.
About Us paragraph: copy exactly.
About the Role paragraph: copy the "What We Do:" paragraph.
What You Will Do paragraph: copy that sentence.
Responsibilities list: we need to convert each bullet.
Let's list them precisely:
1. Technical Support project planning for firmware/software development needs
About Us
andAbout the Role
. But we need to avoid thin sections. Both have substantive content. Next, "What You Will Do: Support the design, development, implementation, testing, and documentation of firmware and software to be used in high voltage power supplies in all our markets and applications of interest, interfacing and supporting our global engineering community as needed." That's a paragraph; could be part of Responsibilities or a separate section "What You Will Do". But we already have Responsibilities section; maybe we can incorporate this into Responsibilities as an overview bullet? However the Responsibilities section later has a list of duties. The "What You Will Do" is a summary; we could keep it as a paragraph under Responsibilities heading before the list. But instructions: Use- for any list of duties/requirements/benefits, and
for prose. So we can have a
for the overview, then a
- for the list.
Now Responsibilities list: The bullet points after "Responsibilities" heading:
- Technical Support project planning for firmware/software development needs
- Hands-on support of firmware and software design for high voltage power supplies (HVPS). Languages used (C, Verilog, VHDL, Assembly, C, C#, VB6, Java, WPF, Linux) and firmware development based on RTOS.
- Interface with peers in the Engineering team to implement features desired as described in product and application requirements.
- Support the preparation of all technical documentation, such as circuit and block diagrams, test reports, manuals, technical reports, release documentation etc.
- Support the review and interpretation of internal/external customer requirements
- Support the improvement of the FW and SW release process, to include the use of revision control systems such as Tortoise SVN
- Continuous research of latest concepts as they pertain to Embedded Systems: Development including DSP’s, MCU’s, FPGA’s, CPLD’s, SOM.
- Other expectations: As needed, interface with the company’s sales & Marketing, operations, and quality teams among others, in support of common projects and overall company strategy
- As needed, support the development of Embedded Systems Engineering plans for current and future product and technology development projects based on the company’s overall objectives
- Embrace an engineering culture of high performance and provide the corresponding behaviors and performance.
- Proactively seek guidance and mentoring to ensure a comprehensive understanding of what a hands-on approach to executing Embedded Systems projects with a focus on comprehensive requirements analysis, definition of the appropriate technical approach and solution, project planning and management, and risk assessment and mitigation, means and how it is implemented.
- Support product development design reviews and provide applicable inputs and associated documentation for design changes, specifications, and Software/Firmware releases among others per Spellman engineering product development processes.
We need to turn each into
- . Some are long sentences; we keep them.
Now "What You Need:" section includes qualifications:
- Bachelor’s degree (Master’s degree preferred) in Electrical Engineering and minimum 3 years of experience in Embedded Systems tasks and projects.
- Understanding of the principles of Design and Development principles of FPGA code using Verilog or VHDL
- Understanding of the principles of digital systems that include ADC’s, DAC's, UART's, RS-485, RS-232, embedded Ethernet, USB, microcontrollers, DSP’s, RAM, SRAM, EEPROM, switching low-voltage power supplies, pulse-width modulation devices, discrete logic, and FPGA’s
- Understanding of the principles of using emulators, debuggers, JTAG, integrated development environments, and other design and verification tools
- Some experience with/ exposure to advanced engineering tools such as: Matlab-Simulink, PSIM and others.
- Basics in the development of design documentation that can be presented to the customer community
- Support for design verification testing and documentation
- Passion about collaborating with other company teams in a multidisciplinary environment (sales and marketing, operations, quality, supply chain), customers…etc. to drive a continuous and strong focus on value creation
We can treat as Requirements or Qualifications. The instructions list headings: Requirements, Qualifications, Skills. We could combine into Requirements (or Qualifications). Since it's a mix of education, experience, skills, we could have a single section "Requirements" with a list.
Now Pay: "Our good faith estimate of the salary range for this role is $96,000 - $131,000. Exact compensation may vary based on skills, experience, and other factors."
We'll put in Pay section as a
. Benefits: "In addition to base pay, we offer a full benefits package." We'll put in Benefits section as a
. Schedule: "This position requires on-site presence at Spellman High Voltage headquarters in Hauppauge, NY." We'll put in Schedule section as a
. Also we have location earlier: "Location Hauppauge, NY". Already covered. Now we need to remove boilerplate: EEO statement, accommodation request, note to recruiters, etc. Remove those. Also remove duplicated lines: There's some duplication like "Understanding of the principles of Design and Development principles of FPGA code using Verilog or VHDL" appears maybe twice? Actually appears once. There's duplication of "C" in languages list: "Languages used (C, Verilog, VHDL, Assembly, C, C#, VB6, Java, WPF, Linux)". We'll keep as is but could deduplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Removing duplicate "C" might be considered summarizing away detail? It's a minor duplication; but it's likely okay to keep as is. We could keep the list as given. Now we need to output only HTML fragment, no markdown. Structure:
About Us
...
About the Role
...
What You Will Do
...
Responsibilities
- ... ...
Requirements
- ... ...
Pay
...
Benefits
...
Schedule
...
We need to ensure we don't create empty sections. Now let's craft the content. About Us paragraph: copy exactly. About the Role paragraph: copy the "What We Do:" paragraph. What You Will Do paragraph: copy that sentence. Responsibilities list: we need to convert each bullet. Let's list them precisely: 1. Technical Support project planning for firmware/software development needs
- . Some are long sentences; we keep them.
Now "What You Need:" section includes qualifications:
- Bachelor’s degree (Master’s degree preferred) in Electrical Engineering and minimum 3 years of experience in Embedded Systems tasks and projects.
- Understanding of the principles of Design and Development principles of FPGA code using Verilog or VHDL
- Understanding of the principles of digital systems that include ADC’s, DAC's, UART's, RS-485, RS-232, embedded Ethernet, USB, microcontrollers, DSP’s, RAM, SRAM, EEPROM, switching low-voltage power supplies, pulse-width modulation devices, discrete logic, and FPGA’s
- Understanding of the principles of using emulators, debuggers, JTAG, integrated development environments, and other design and verification tools
- Some experience with/ exposure to advanced engineering tools such as: Matlab-Simulink, PSIM and others.
- Basics in the development of design documentation that can be presented to the customer community
- Support for design verification testing and documentation
- Passion about collaborating with other company teams in a multidisciplinary environment (sales and marketing, operations, quality, supply chain), customers…etc. to drive a continuous and strong focus on value creation
We can treat as Requirements or Qualifications. The instructions list headings: Requirements, Qualifications, Skills. We could combine into Requirements (or Qualifications). Since it's a mix of education, experience, skills, we could have a single section "Requirements" with a list.
Now Pay: "Our good faith estimate of the salary range for this role is $96,000 - $131,000. Exact compensation may vary based on skills, experience, and other factors."
We'll put in Pay section as a