Junior R&D Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting: It's a job ad for entry level Hardware Engineer. Contains description, responsibilities (What You Will Do), requirements (About You), preferred, benefits, etc.
We need to decide sections: Likely "About the role" (intro paragraph), "Responsibilities" (What You Will Do), "Requirements" (About You required), "Preferred Qualifications" (Preferred), "Benefits" (Benefits). Possibly "Skills" could be combined but we can include if there is specific skill list. The posting includes "Required About You" list and "Preferred". Also there is a paragraph about "What You Will Do". Also there is a paragraph about "About the role" maybe the initial description before responsibilities.
We must not include sections with filler like "Pay" or "Schedule" if not specified. The posting does not mention pay or schedule specifics. So we omit those.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive info; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format them.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes some EEO-like statements: "Laminar (formerly H2Ok) is committed to building a diverse and inclusive team..." and "We may use artificial intelligence (AI) tools..." and "Our pay ranges are established per Pave Compensation Software." Also "If you would like more information about how your data is processed..." etc. Those are boilerplate; we should remove them. Also the lines about "Learn How We Think", "Learn about our startup journey", etc. Those might be considered marketing but still substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn How We Think" sections are not exactly boilerplate but could be considered marketing; but they are not explicitly prohibited. However they might be considered part of the job posting content; but we need to preserve ALL substantive information. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to remove marketing sections like "Learn How We Think". So we should keep them if they contain substantive info about company. However we need to decide sections: maybe we can include an "About the company" section? But the allowed headings list does not include "About the company". Only the listed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those headings. The "About the role" could encompass the introductory description about the company and role. The "Responsibilities" is the "What You Will Do". The "Requirements" is the "About You" required. The "Qualifications" could be the "Preferred". The "Skills" could be maybe a combined list of skills from required and preferred? But we already have required and preferred; we could put skills under Requirements or Qualifications. The instruction says use headings only when posting has real specific content for it. So we can include About the role, Responsibilities, Requirements, Qualifications, Benefits. Possibly Skills if we have a distinct list separate from requirements. But we can embed skills within Requirements and Qualifications.
We must not repeat the job title as a heading. So no heading for "Hardware Engineer". Good.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract substantive content:
Intro paragraph before responsibilities: "For a century, the answer to “what’s in the pipe right now” was a grab sample to a lab with results back hours later. We answer it every second. Laminar is building human-centric self-driving factories: the ones made of stainless steel pipes and reactors, that make what the world eats, uses, and wears. Proprietary inline sensors read the chemistry in the pipe. Foundation models grounded in physics and chemistry reason about how close the process is to its target. Process control software acts on the answer through the plant’s automation system in real time. Laminar Insights shows what happened, why, and what it saved. A Laminar line uses about 20% less water and 20% fewer chemicals and runs 15% faster, with quality protected. Productivity and sustainability improve together. We run across six continents at manufacturers like Coca-Cola, Unilever, and AB InBev, backed by tier-1 investors in Physical AI. We’re a polymathic team of 50 in Somerville: hardware and software engineers, chemists, AI researchers, factory operators, and go-to-market wizards under one roof. Nobody here is waiting to be asked what to do. You’ll see the problem, propose the fix, and own the outcome. We believe in autonomy, ownership, and demanding excellence, and we hold each other to it. If that’s how you want to spend your time, come build the self-driving factory with us."
That's about the role/company. We'll put under
About the role
with containing that paragraph.
Next: "We’re seeking an entry level Hardware Engineer whose work will focus on new system Research and Development. You will work closely with Senior Engineers across both the Hardware and Embedded Systems teams to rapidly evaluate new technologies, test performance of sensing systems, and integrate them into field prototypes. This role will perform PCB design, assembly and testing along with mechanical housing design and cable harnessing. We value a self-sufficient, hands-on engineer who isn’t afraid to ask questions and learns new skills quickly. Your work will directly impact our hardware product design, improve prototype iteration speed, and help Laminar to save more resources every day."
That could also be part of About the role or Responsibilities. But we have a separate "What You Will Do" list. We could put the paragraph under About the role as well, but maybe better to put under Responsibilities? However the "What You Will Do" is a list of duties. The preceding paragraph is more about the role. I'd keep it in About the role.
Then "What You Will Do" list:
- Design protype PCBs from commercially available and custom sensors using KiCAD, Solidworks, and simulation softwares such as PSPICE
- Develop and implement test strategies alongside the Laminar Data Analysis team. Collect and present this data in informal and formal reviews to allow for rapid analysis and sensor comparisons
- Assemble complex PCBAs using reflow soldering techniques. Rework non-functional units and perform modifications as needed during board bringup
- Design mechanical housings for sensors and edge compute. Conduct thermal, vibrational and ingress progression tests with guidance from senior engineers
- Integrate sensors to established testing platform using Zephyr RTOS
- Bring new ideas and creatively pursue new approaches to product sensing to solve critical problems for our clients
- Contribute to the overall hardware team by providing design, assembly, and debug assistance on multiple projects. Own your own projects early in career and drive direct impact on hardware shipping to our customers
We need to preserve the exact wording? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the text as is, maybe fix minor typos? "Design protype PCBs" maybe it's a typo but we should keep as is? It's part of the posting; we should not change it. We'll keep exactly.
We'll put under
Responsibilities
with a - for each.
Next: "Required About You" list:
- 1-3 years (entry level) experience in electronics design, mechanical design, and data analysis
- Electronics experience: PCB SMD and THT soldering, rework, troubleshooting, oscilloscope use, digital signal analysis. Ability to read and debug electrical schematics
- Basic coding experience: Python, C, C++ and comfortable with the core concepts of embedded programming and data analysis
- Generalist mindset: comfortable working with all parts of electromechanical assemblies, experiment design, and documentation
- Wants to learn new things rapidly and apply them. Comfortable with ambiguity and desires rapid growth in early career
- Clear, efficient, and respectful communicator, good at balancing multiple projects and shifting priorities
- Previous project experience. Clubs, research, internships, volunteering, or personal projects. Be prepared to discuss projects and your contribution to them
We'll put under
Requirements
with - .
Next: "Preferred" list:
- Extensive project or work experience in electronics design, chemical process engineering or manufacturing
- Experience working with PCB contract manufacturers, machine shops both domestic and international
- PCB design experience with microcontrollers, industrial communications protocols and analog electronics combined
- Significant prior experience navigating the balance between “move fast and break things, but not the important things”
- Experience with Zephyr RTOS
- Design experience in sanitary or hazardous environments. ATEX and ASME BPE or similar
We'll put under
Qualifications
(or maybe "Preferred Qualifications").
Next: Benefits section: The posting includes a Benefits paragraph: "Benefits Direct impact on product and cultureComprehensive benefits package including Medical, Dental, Vision, Life Insurance, Disability, Transportation benefit, Health and Wellness benefit, and more401k plan with employer matchingEquityCompetitive salary and bonus opportunitiesDynamic and inclusive work environmentOpportunities for growth and professional developmentAccess to Greentown Labs' extensive network of cleantech startups Learn How We Think Learn about our startup journey: Our Journey How we're combating climate change: AI-Powered Climate Tech A customer story: Ben & Jerry's uses H2Ok's precision automation to cut time & water usage Why You'll Love it Here A front-row seat at Greentown Labs, North America's largest cleantech innovation hub, in a Somerville neighborhood ranked one of the coolest in the world Real recognition: 2026 World Economic Forum Technology Pioneer, Gold 2026 Edison Award, Unilever Startup of the Year, Innovator Awards by both Coca-Cola and ABInBev, and more A team that celebrates together from rooftop lunches, ping pong matches, Lunch & Learns, and regular team events Competitive salary, equity, and a 401(k) with company match Health, dental, and vision coverage, plus short- and long-term disability and life insurance Flexible time off and 12 company-paid holidays A conference and learning budget to keep growing your craft Greentown Labs membership and a transportation benefit for your commute Our Interview Process Phone screen with Laminar Head of Ops or Recruiter (15-20 minutes) Intro call with Hiring Manager (30 minutes) On-site interview, including short tour of GTL, overview of tech, and interview/presentation with the Hiring Manager and a few team members. Depending on the role, a skills exercise that should take no longer than an hour to prep, would be sent ahead of time. We record your skills exercise to share with any team members who could not join the interview and/or with Founder's ahead of their Founder's Interview. If you are not local, we can conduct this virtually Finalists for Full-Time positions will have a Founder’s Interview in-person Final steps: Two professional references are requested, ideally one from your current organization and one who served as your Manager If an Offer Letter is extended, a Background check is conducted A recent study from LinkedIn showed that most women apply to jobs only when they meet 100% of the requirements, whereas men will hit the
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive info; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format them. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes some EEO-like statements: "Laminar (formerly H2Ok) is committed to building a diverse and inclusive team..." and "We may use artificial intelligence (AI) tools..." and "Our pay ranges are established per Pave Compensation Software." Also "If you would like more information about how your data is processed..." etc. Those are boilerplate; we should remove them. Also the lines about "Learn How We Think", "Learn about our startup journey", etc. Those might be considered marketing but still substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn How We Think" sections are not exactly boilerplate but could be considered marketing; but they are not explicitly prohibited. However they might be considered part of the job posting content; but we need to preserve ALL substantive information. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to remove marketing sections like "Learn How We Think". So we should keep them if they contain substantive info about company. However we need to decide sections: maybe we can include an "About the company" section? But the allowed headings list does not include "About the company". Only the listed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those headings. The "About the role" could encompass the introductory description about the company and role. The "Responsibilities" is the "What You Will Do". The "Requirements" is the "About You" required. The "Qualifications" could be the "Preferred". The "Skills" could be maybe a combined list of skills from required and preferred? But we already have required and preferred; we could put skills under Requirements or Qualifications. The instruction says use headings only when posting has real specific content for it. So we can include About the role, Responsibilities, Requirements, Qualifications, Benefits. Possibly Skills if we have a distinct list separate from requirements. But we can embed skills within Requirements and Qualifications. We must not repeat the job title as a heading. So no heading for "Hardware Engineer". Good. We need to output only HTML fragment, no /, no markdown fences. Let's extract substantive content: Intro paragraph before responsibilities: "For a century, the answer to “what’s in the pipe right now” was a grab sample to a lab with results back hours later. We answer it every second. Laminar is building human-centric self-driving factories: the ones made of stainless steel pipes and reactors, that make what the world eats, uses, and wears. Proprietary inline sensors read the chemistry in the pipe. Foundation models grounded in physics and chemistry reason about how close the process is to its target. Process control software acts on the answer through the plant’s automation system in real time. Laminar Insights shows what happened, why, and what it saved. A Laminar line uses about 20% less water and 20% fewer chemicals and runs 15% faster, with quality protected. Productivity and sustainability improve together. We run across six continents at manufacturers like Coca-Cola, Unilever, and AB InBev, backed by tier-1 investors in Physical AI. We’re a polymathic team of 50 in Somerville: hardware and software engineers, chemists, AI researchers, factory operators, and go-to-market wizards under one roof. Nobody here is waiting to be asked what to do. You’ll see the problem, propose the fix, and own the outcome. We believe in autonomy, ownership, and demanding excellence, and we hold each other to it. If that’s how you want to spend your time, come build the self-driving factory with us." That's about the role/company. We'll put under
About the role
withcontaining that paragraph. Next: "We’re seeking an entry level Hardware Engineer whose work will focus on new system Research and Development. You will work closely with Senior Engineers across both the Hardware and Embedded Systems teams to rapidly evaluate new technologies, test performance of sensing systems, and integrate them into field prototypes. This role will perform PCB design, assembly and testing along with mechanical housing design and cable harnessing. We value a self-sufficient, hands-on engineer who isn’t afraid to ask questions and learns new skills quickly. Your work will directly impact our hardware product design, improve prototype iteration speed, and help Laminar to save more resources every day." That could also be part of About the role or Responsibilities. But we have a separate "What You Will Do" list. We could put the paragraph under About the role as well, but maybe better to put under Responsibilities? However the "What You Will Do" is a list of duties. The preceding paragraph is more about the role. I'd keep it in About the role. Then "What You Will Do" list: - Design protype PCBs from commercially available and custom sensors using KiCAD, Solidworks, and simulation softwares such as PSPICE - Develop and implement test strategies alongside the Laminar Data Analysis team. Collect and present this data in informal and formal reviews to allow for rapid analysis and sensor comparisons - Assemble complex PCBAs using reflow soldering techniques. Rework non-functional units and perform modifications as needed during board bringup - Design mechanical housings for sensors and edge compute. Conduct thermal, vibrational and ingress progression tests with guidance from senior engineers - Integrate sensors to established testing platform using Zephyr RTOS - Bring new ideas and creatively pursue new approaches to product sensing to solve critical problems for our clients - Contribute to the overall hardware team by providing design, assembly, and debug assistance on multiple projects. Own your own projects early in career and drive direct impact on hardware shipping to our customers We need to preserve the exact wording? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the text as is, maybe fix minor typos? "Design protype PCBs" maybe it's a typo but we should keep as is? It's part of the posting; we should not change it. We'll keep exactly. We'll put under
Responsibilities
with a- for each.
Next: "Required About You" list:
- 1-3 years (entry level) experience in electronics design, mechanical design, and data analysis
- Electronics experience: PCB SMD and THT soldering, rework, troubleshooting, oscilloscope use, digital signal analysis. Ability to read and debug electrical schematics
- Basic coding experience: Python, C, C++ and comfortable with the core concepts of embedded programming and data analysis
- Generalist mindset: comfortable working with all parts of electromechanical assemblies, experiment design, and documentation
- Wants to learn new things rapidly and apply them. Comfortable with ambiguity and desires rapid growth in early career
- Clear, efficient, and respectful communicator, good at balancing multiple projects and shifting priorities
- Previous project experience. Clubs, research, internships, volunteering, or personal projects. Be prepared to discuss projects and your contribution to them
We'll put under
Requirements
with- .
Next: "Preferred" list:
- Extensive project or work experience in electronics design, chemical process engineering or manufacturing
- Experience working with PCB contract manufacturers, machine shops both domestic and international
- PCB design experience with microcontrollers, industrial communications protocols and analog electronics combined
- Significant prior experience navigating the balance between “move fast and break things, but not the important things”
- Experience with Zephyr RTOS
- Design experience in sanitary or hazardous environments. ATEX and ASME BPE or similar
We'll put under
Qualifications
(or maybe "Preferred Qualifications"). Next: Benefits section: The posting includes a Benefits paragraph: "Benefits Direct impact on product and cultureComprehensive benefits package including Medical, Dental, Vision, Life Insurance, Disability, Transportation benefit, Health and Wellness benefit, and more401k plan with employer matchingEquityCompetitive salary and bonus opportunitiesDynamic and inclusive work environmentOpportunities for growth and professional developmentAccess to Greentown Labs' extensive network of cleantech startups Learn How We Think Learn about our startup journey: Our Journey How we're combating climate change: AI-Powered Climate Tech A customer story: Ben & Jerry's uses H2Ok's precision automation to cut time & water usage Why You'll Love it Here A front-row seat at Greentown Labs, North America's largest cleantech innovation hub, in a Somerville neighborhood ranked one of the coolest in the world Real recognition: 2026 World Economic Forum Technology Pioneer, Gold 2026 Edison Award, Unilever Startup of the Year, Innovator Awards by both Coca-Cola and ABInBev, and more A team that celebrates together from rooftop lunches, ping pong matches, Lunch & Learns, and regular team events Competitive salary, equity, and a 401(k) with company match Health, dental, and vision coverage, plus short- and long-term disability and life insurance Flexible time off and 12 company-paid holidays A conference and learning budget to keep growing your craft Greentown Labs membership and a transportation benefit for your commute Our Interview Process Phone screen with Laminar Head of Ops or Recruiter (15-20 minutes) Intro call with Hiring Manager (30 minutes) On-site interview, including short tour of GTL, overview of tech, and interview/presentation with the Hiring Manager and a few team members. Depending on the role, a skills exercise that should take no longer than an hour to prep, would be sent ahead of time. We record your skills exercise to share with any team members who could not join the interview and/or with Founder's ahead of their Founder's Interview. If you are not local, we can conduct this virtually Finalists for Full-Time positions will have a Founder’s Interview in-person Final steps: Two professional references are requested, ideally one from your current organization and one who served as your Manager If an Offer Letter is extended, a Background check is conducted A recent study from LinkedIn showed that most women apply to jobs only when they meet 100% of the requirements, whereas men will hit the
- .
Next: "Preferred" list:
- Extensive project or work experience in electronics design, chemical process engineering or manufacturing
- Experience working with PCB contract manufacturers, machine shops both domestic and international
- PCB design experience with microcontrollers, industrial communications protocols and analog electronics combined
- Significant prior experience navigating the balance between “move fast and break things, but not the important things”
- Experience with Zephyr RTOS
- Design experience in sanitary or hazardous environments. ATEX and ASME BPE or similar
We'll put under
- for each.
Next: "Required About You" list:
- 1-3 years (entry level) experience in electronics design, mechanical design, and data analysis
- Electronics experience: PCB SMD and THT soldering, rework, troubleshooting, oscilloscope use, digital signal analysis. Ability to read and debug electrical schematics
- Basic coding experience: Python, C, C++ and comfortable with the core concepts of embedded programming and data analysis
- Generalist mindset: comfortable working with all parts of electromechanical assemblies, experiment design, and documentation
- Wants to learn new things rapidly and apply them. Comfortable with ambiguity and desires rapid growth in early career
- Clear, efficient, and respectful communicator, good at balancing multiple projects and shifting priorities
- Previous project experience. Clubs, research, internships, volunteering, or personal projects. Be prepared to discuss projects and your contribution to them
We'll put under