Firmware Engineering Co-op
OnLogic · South Burlington, VT · 3 wk ago
On-site$22/hrTemporary
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications?, Skills?, Benefits, Pay, Schedule. According to rules: Use for section headings. Only include sections when posting has real specific content. We have:
- About the role: description at start: "As a member of the Firmware Engineering Team at OnLogic, you will learn some of the rigors and unique design methodologies...". That's about the role. So we can have
for section headings. Only include sections when posting has real specific content. We have:
- About the role: description at start: "As a member of the Firmware Engineering Team at OnLogic, you will learn some of the rigors and unique design methodologies...". That's about the role. So we can have About the role
with paragraph(s).
- Responsibilities: list after "In this role, you'll be responsible for:" then bullet list. So Responsibilities
with - ...
.
- Requirements: after "Requirements" heading in source. So Requirements
with list.
- Qualifications: maybe not separate; but we have "Who we're looking for:" which could be considered Qualifications or Skills. The instruction says we can have sections like Qualifications, Skills. We need to decide if we should create a Qualifications section for that content. The content: "Who we're looking for: A hands-on engineer ...". That's more like desired attributes/qualifications. Could be placed under Qualifications. Also "The team you will be joining:" etc is more about team description, maybe not needed. "Who we are:" also company description, maybe not needed. But we must preserve ALL substantive information; do not invent or summarize away detail. However we can omit boilerplate like navigation, legal, EEO, duplicated lines. The "Who we are:" includes diversity statement etc. That's substantive? It's about company values, maybe considered boilerplate? It's not cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, but it's still company description. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The diversity statement is not exactly those categories, but could be considered EEO? It mentions diversity, harassment-free workplace. That is EEO/equal-opportunity content. Likely should be removed as it's EEO boilerplate. Similarly "We are committed to providing a safe, inclusive, and harassment-free workplace..." is EEO. So we should drop that.
Also "Learn more about Life at OnLogic: www.onlogic.com/life-at-onlogic." and "To learn more about our values, our mission and what it's like to work at OnLogic, visit www.onlogic.com/careers." Those are links, maybe considered navigation? Probably drop.
We need to preserve all substantive information: role description, responsibilities, requirements, who we're looking for (qualifications/skills), team description maybe not essential but could be considered substantive? It's about the team; could be kept under a section like "Team". But we only have predefined headings list; we could add a custom heading? The instruction says use 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. Safer to stick to those. The team description could be placed under About the role or maybe omitted? It's substantive but not covered by those headings. Could incorporate into About the role paragraph.
Similarly "Who we are:" could be omitted as EEO/boilerplate.
Thus sections: About the role (includes initial paragraph and maybe team description), Responsibilities, Requirements, Qualifications (or Skills), Benefits, Pay, Schedule.
We have Pay and Schedule info in Benefits paragraph: "The pay for this co-op is $22/hour, with an up to 40 hour per week commitment, January to June, 2027." That includes pay and schedule. According to rules, we should not create Pay/Schedule sections unless posting actually states them. It does state pay and schedule. So we could either have a Benefits section that includes pay and schedule, or separate Pay and Schedule sections. The instruction: "Prefer a few substantive sections over many thin ones." So better to combine pay and schedule into Benefits section, or have Benefits section with pay and schedule details. But they also said: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we could have Benefits, Pay, Schedule as separate if we want, but they'd be thin. Better to have Benefits section that includes pay and schedule. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay and schedule, so we could create them but they'd be thin. Prefer few substantive sections, so combine into Benefits.
Thus sections: About the role, Responsibilities, Requirements, Qualifications (or Skills), Benefits.
Now we need to extract content.
About the role: combine first paragraph and maybe team description.
First paragraph: "As a member of the Firmware Engineering Team at OnLogic, you will learn some of the rigors and unique design methodologies OnLogic uses to create the world's most reliable Industrial PCs during this 6-month Co-op (January 2027 - June 2027). You will work alongside Firmware engineers to develop firmware and software infrastructure targeting various CPU, SoCs, and microcontroller architectures, specifically targeting a range of motherboards and expansion cards. In this role, you will be involved in the complete product lifecycle—from initial concept and development to prototype build, validation, and through to volume production. We believe in the power of in-person collaboration and the benefits of a strong workplace community. Therefore, this Co-op will take place onsite in Cary, North Carolina, or South Burlington Vermont."
Team description: "The team you will be joining: Our Engineering team creates our cutting edge industrial computers by finding innovative solutions on a daily basis. The Engineering team's success relies on collaboration, creative thinking and a commitment to being at the forefront of technology. Roles on our Engineering team include, Electrical, Mechanical, Applications and Regulatory."
We could incorporate that into About the role.
Thus About the role paragraph(s) could be two
elements.
Responsibilities: list items:
- Working with the product definition and product design team to identify and document the microcontroller firmware requirements.
- Performing bare metal firmware development.
- Performing RTOS porting and development of the device drivers.
- Developing infrastructure to support firmware build, test and release.
- Participating in continuous improvement of the company's development processes.
- Supporting product certification process including document and issue fixing.
- Supporting product sustainability and customer requirements for SW/FW related issues.
- Tracking issues and assisting with severity assessments, facilitating resolutions and/or appropriate documentation.
Make each
- .
Requirements: list:
- An undergraduate student currently pursuing a bachelor's degree majoring in Computer Science, Computer Engineering, Electrical Engineering, or a related technical field, who will return for 1+ semester at their institution following completion of the Co-op.
- Understanding of software/firmware design with C, Assembly.
- Experience using basic development tools to troubleshoot software and interactions at the software/hardware boundary.
- Familiarity with software/firmware design and implementation within a Linux or Windows environment.
- Available full-time (up to 40 hours per week) from January 2027 through June 2027
- Ability to work in the U.S. without visa sponsorship.
- Satisfactory completion of a background check.
Make each
- .
Qualifications/Skills: "Who we're looking for:" bullet-ish sentences:
- A hands-on engineer who enjoys digging in and working at the low level where accounting for interactions, behaviors, and unknowns that span the software stack and underlying hardware.
- A detail-oriented developer who understands that precision in firmware/software design constraints is vital for industrial reliability.
- A self-motivated individual with an ability to solve complex software/firmware problems strategically.
- Someone with excellent written and verbal communication skills for collaborating and documenting, design reasoning, decisions and implementation details.
We could put under Qualifications.
Benefits: includes pay and schedule: "The pay for this co-op is $22/hour, with an up to 40 hour per week commitment, January to June, 2027."
We could also mention that it's a co-op, 6-month, etc but that's already in About the role. Benefits section could just be that sentence.
We should not include duplicated lines, boilerplate, etc.
Now produce HTML fragment:
About the role
As a member of the Firmware Engineering Team at OnLogic, you will learn some of the rigors and unique design methodologies OnLogic uses to create the world's most reliable Industrial PCs during this 6-month Co-op (January 2027 - June 2027). You will work alongside Firmware engineers to develop firmware and software infrastructure targeting various CPU, SoCs, and microcontroller architectures, specifically targeting a range of motherboards and expansion cards. In this role, you will be involved in the complete product lifecycle—from initial concept and development to prototype build, validation, and through to volume production. We believe in the power of in-person collaboration and the benefits of a strong workplace community. Therefore, this Co-op will take place onsite in Cary, North Carolina, or South Burlington Vermont.
The team you will be joining: Our Engineering team creates our cutting edge industrial computers by finding innovative solutions on a daily basis. The Engineering team's success relies on collaboration, creative thinking and a commitment to being at the forefront of technology. Roles on our Engineering team include, Electrical, Mechanical, Applications and Regulatory.
Responsibilities
- Working with the product definition and product design team to identify and document the microcontroller firmware requirements.
- Performing bare metal firmware development.
- Performing RTOS porting and development of the device drivers.
- Developing infrastructure to support firmware build, test and release.
- Participating in continuous improvement of the company's development processes.
- Supporting product certification process including document and issue fixing.
- Supporting product sustainability and customer requirements for SW/FW related issues.
- Tracking issues and assisting with severity assessments, facilitating resolutions and/or appropriate documentation.
Requirements
- An undergraduate student currently pursuing a bachelor's degree majoring in Computer Science, Computer Engineering, Electrical Engineering, or a related technical field, who will return for 1+ semester at their institution following completion of the Co-op.
- Understanding of software/firmware design with C, Assembly.
- Experience using basic development tools to troubleshoot software and interactions at the software/hardware boundary.
- Familiarity with software/firmware design and implementation within a Linux or Windows environment.
- Available full-time (up to 40 hours per week) from January 2027 through June 2027
- Ability to work in the U.S. without visa sponsorship.
- Satisfactory completion of a background check.
Qualifications
- A hands-on engineer who enjoys digging in and working at the low level where accounting for interactions, behaviors, and unknowns that span the software stack and underlying hardware.
- A detail-oriented developer who understands that precision in firmware/software design constraints is vital for industrial reliability.
- A self-motivated individual with an ability to solve complex software/firmware problems strategically.
- Someone with excellent written and verbal communication skills for collaborating and documenting, design reasoning, decisions and implementation details.
Benefits
The pay for this co-op is $22/hour, with an up to 40 hour per week commitment, January to June, 2027.
Check for any leftover boilerplate: removed EEO, links, etc. All good.
Now output only HTML fragment.
Requirements
with list. - Qualifications: maybe not separate; but we have "Who we're looking for:" which could be considered Qualifications or Skills. The instruction says we can have sections like Qualifications, Skills. We need to decide if we should create a Qualifications section for that content. The content: "Who we're looking for: A hands-on engineer ...". That's more like desired attributes/qualifications. Could be placed under Qualifications. Also "The team you will be joining:" etc is more about team description, maybe not needed. "Who we are:" also company description, maybe not needed. But we must preserve ALL substantive information; do not invent or summarize away detail. However we can omit boilerplate like navigation, legal, EEO, duplicated lines. The "Who we are:" includes diversity statement etc. That's substantive? It's about company values, maybe considered boilerplate? It's not cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, but it's still company description. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The diversity statement is not exactly those categories, but could be considered EEO? It mentions diversity, harassment-free workplace. That is EEO/equal-opportunity content. Likely should be removed as it's EEO boilerplate. Similarly "We are committed to providing a safe, inclusive, and harassment-free workplace..." is EEO. So we should drop that. Also "Learn more about Life at OnLogic: www.onlogic.com/life-at-onlogic." and "To learn more about our values, our mission and what it's like to work at OnLogic, visit www.onlogic.com/careers." Those are links, maybe considered navigation? Probably drop. We need to preserve all substantive information: role description, responsibilities, requirements, who we're looking for (qualifications/skills), team description maybe not essential but could be considered substantive? It's about the team; could be kept under a section like "Team". But we only have predefined headings list; we could add a custom heading? The instruction says use 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. Safer to stick to those. The team description could be placed under About the role or maybe omitted? It's substantive but not covered by those headings. Could incorporate into About the role paragraph.
Similarly "Who we are:" could be omitted as EEO/boilerplate.
Thus sections: About the role (includes initial paragraph and maybe team description), Responsibilities, Requirements, Qualifications (or Skills), Benefits, Pay, Schedule.
We have Pay and Schedule info in Benefits paragraph: "The pay for this co-op is $22/hour, with an up to 40 hour per week commitment, January to June, 2027." That includes pay and schedule. According to rules, we should not create Pay/Schedule sections unless posting actually states them. It does state pay and schedule. So we could either have a Benefits section that includes pay and schedule, or separate Pay and Schedule sections. The instruction: "Prefer a few substantive sections over many thin ones." So better to combine pay and schedule into Benefits section, or have Benefits section with pay and schedule details. But they also said: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we could have Benefits, Pay, Schedule as separate if we want, but they'd be thin. Better to have Benefits section that includes pay and schedule. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay and schedule, so we could create them but they'd be thin. Prefer few substantive sections, so combine into Benefits.
Thus sections: About the role, Responsibilities, Requirements, Qualifications (or Skills), Benefits.
Now we need to extract content.
About the role: combine first paragraph and maybe team description.
First paragraph: "As a member of the Firmware Engineering Team at OnLogic, you will learn some of the rigors and unique design methodologies OnLogic uses to create the world's most reliable Industrial PCs during this 6-month Co-op (January 2027 - June 2027). You will work alongside Firmware engineers to develop firmware and software infrastructure targeting various CPU, SoCs, and microcontroller architectures, specifically targeting a range of motherboards and expansion cards. In this role, you will be involved in the complete product lifecycle—from initial concept and development to prototype build, validation, and through to volume production. We believe in the power of in-person collaboration and the benefits of a strong workplace community. Therefore, this Co-op will take place onsite in Cary, North Carolina, or South Burlington Vermont."
Team description: "The team you will be joining: Our Engineering team creates our cutting edge industrial computers by finding innovative solutions on a daily basis. The Engineering team's success relies on collaboration, creative thinking and a commitment to being at the forefront of technology. Roles on our Engineering team include, Electrical, Mechanical, Applications and Regulatory."
We could incorporate that into About the role.
Thus About the role paragraph(s) could be two
elements. Responsibilities: list items: - Working with the product definition and product design team to identify and document the microcontroller firmware requirements. - Performing bare metal firmware development. - Performing RTOS porting and development of the device drivers. - Developing infrastructure to support firmware build, test and release. - Participating in continuous improvement of the company's development processes. - Supporting product certification process including document and issue fixing. - Supporting product sustainability and customer requirements for SW/FW related issues. - Tracking issues and assisting with severity assessments, facilitating resolutions and/or appropriate documentation. Make each
About the role
As a member of the Firmware Engineering Team at OnLogic, you will learn some of the rigors and unique design methodologies OnLogic uses to create the world's most reliable Industrial PCs during this 6-month Co-op (January 2027 - June 2027). You will work alongside Firmware engineers to develop firmware and software infrastructure targeting various CPU, SoCs, and microcontroller architectures, specifically targeting a range of motherboards and expansion cards. In this role, you will be involved in the complete product lifecycle—from initial concept and development to prototype build, validation, and through to volume production. We believe in the power of in-person collaboration and the benefits of a strong workplace community. Therefore, this Co-op will take place onsite in Cary, North Carolina, or South Burlington Vermont.
The team you will be joining: Our Engineering team creates our cutting edge industrial computers by finding innovative solutions on a daily basis. The Engineering team's success relies on collaboration, creative thinking and a commitment to being at the forefront of technology. Roles on our Engineering team include, Electrical, Mechanical, Applications and Regulatory.
Responsibilities
- Working with the product definition and product design team to identify and document the microcontroller firmware requirements.
- Performing bare metal firmware development.
- Performing RTOS porting and development of the device drivers.
- Developing infrastructure to support firmware build, test and release.
- Participating in continuous improvement of the company's development processes.
- Supporting product certification process including document and issue fixing.
- Supporting product sustainability and customer requirements for SW/FW related issues.
- Tracking issues and assisting with severity assessments, facilitating resolutions and/or appropriate documentation.
Requirements
- An undergraduate student currently pursuing a bachelor's degree majoring in Computer Science, Computer Engineering, Electrical Engineering, or a related technical field, who will return for 1+ semester at their institution following completion of the Co-op.
- Understanding of software/firmware design with C, Assembly.
- Experience using basic development tools to troubleshoot software and interactions at the software/hardware boundary.
- Familiarity with software/firmware design and implementation within a Linux or Windows environment.
- Available full-time (up to 40 hours per week) from January 2027 through June 2027
- Ability to work in the U.S. without visa sponsorship.
- Satisfactory completion of a background check.
Qualifications
- A hands-on engineer who enjoys digging in and working at the low level where accounting for interactions, behaviors, and unknowns that span the software stack and underlying hardware.
- A detail-oriented developer who understands that precision in firmware/software design constraints is vital for industrial reliability.
- A self-motivated individual with an ability to solve complex software/firmware problems strategically.
- Someone with excellent written and verbal communication skills for collaborating and documenting, design reasoning, decisions and implementation details.
Benefits
The pay for this co-op is $22/hour, with an up to 40 hour per week commitment, January to June, 2027.
Check for any leftover boilerplate: removed EEO, links, etc. All good. Now output only HTML fragment.