Senior Hardware Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Need to extract content from posting. Let's parse posting. First paragraph: description of company. Not a section heading but could be "About the role"? Actually "About the role" is typical. The posting includes description of company and mission. Could be "About the role" or "About the company". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We need to avoid repeating job title as heading. Job title: senior-level Hardware Engineer. Not to repeat. We need to include sections only when posting has real specific content. Let's identify sections: - About the role / About the company: The first paragraphs describe company mission, product, etc. Could be "About the role" (though it's more about company). We'll include "About the role" with that content. - Responsibilities: The posting says: "You will work closely with other 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 directly perform circuit and PCB design and evaluation, sensor experimental design and data analysis. You will work closely with colleagues to fabricate R&D systems and implement them for field trials." That's responsibilities. - Requirements / Qualifications: "We value a self-sufficient, hands-on engineer who isn’t afraid to ask questions and learns new skills quickly." Also maybe "senior-level Hardware Engineer" implies experience. Not explicit years. Could include "Requirements" with that. - Skills: maybe list of technical skills: circuit and PCB design, sensor experimental design, data analysis, fabrication, etc. Could be under Skills. - Benefits: Many details: Competitive salary, equity, 401(k) with company match, Health, dental, vision coverage, short- and long-term disability and life insurance, Flexible time off, 12 company-paid holidays, conference and learning budget, Greentown Labs membership, transportation benefit, etc. Also mention Laminar pays 100% of individual health insurance premium for HMO medical, vision, dental, flexible PTO, $90/month transportation benefit, $65/month health and wellness benefit, FSA, 12 company-paid holidays, employer-matching 401(k), Greentown Labs membership. So we have specific benefits. - Pay: Not explicitly given a number or range. They mention "Competitive salary, equity" but no specific figure. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. For Pay, they didn't give a specific number or range, just "competitive salary". That's vague but maybe considered stating? The instruction says: 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. "Competitive salary" is somewhat vague but still states that there is a salary. However it's not a specific range. Might be considered filler? I'd lean to not include Pay section because no concrete figure. But they also mention equity. Could still be considered benefit. Safer to omit Pay section. - Schedule: Not mentioned. No schedule info. So omit. - Also maybe "Qualifications" separate from Requirements. Could combine. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from posting, but we can format as lists. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes interview process details, which might be considered application instructions? The instruction says remove application instructions. The interview process details are part of hiring process, maybe considered application instructions? It says "remove ... application instructions". The interview process details could be considered part of application instructions. However they are substantive about process. Might be considered part of the posting but likely considered instructions for candidates. The instruction says remove application instructions. So we should omit the interview process details. Also remove the LinkedIn study about women applying, diversity encouragement, domain update, safe senders list, AI tools note, data processing contact, etc. Those are boilerplate/legal. Also remove the final paragraph about pay ranges established per Pave Compensation Software etc? That is also somewhat boilerplate but includes benefit details. However we already captured benefits; the sentence about pay ranges per Pave is maybe meta. Might be considered boilerplate. We'll keep benefit details but not the meta sentence. We need to preserve all substantive information: company description, mission, responsibilities, requirements/qualifications, skills, benefits. Let's extract substantive content: Company description (first paragraph up to "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.") Also includes "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 also part of company culture. We can include that under About the role. Now responsibilities: as above. Requirements/Qualifications: "We value a self-sufficient, hands-on engineer who isn’t afraid to ask questions and learns new skills quickly." Also maybe "senior-level Hardware Engineer" implies experience; but not explicit. Could also include "You will work closely with other engineers across both the Hardware and Embedded Systems teams..." but that's responsibilities. Skills: circuit and PCB design, sensor experimental design and data analysis, fabricate R&D systems, implement for field trials. Also maybe "hands-on", "ask questions", "learn new skills quickly". Could list. Benefits: list all specifics: - Competitive salary (maybe we keep as benefit but not specific) - Equity - 401(k) with company match - Health, dental, vision coverage - Short- and long-term disability - Life insurance - Flexible time off - 12 company-paid holidays - Conference and learning budget - Greentown Labs membership - Transportation benefit ($90/month) - Health and wellness benefit ($65/month) - FSA (flexible spending account) - Laminar pays 100% of individual health insurance premium for HMO medical, vision, dental - (maybe also mention "Greentown Labs membership and a transportation benefit for your commute" already) - Also mention "We’re also proud to offer equity in our fast-growing startup and one of the most comprehensive benefits packages among startups at our stage." That's generic. We should avoid duplication. Now produce HTML. Structure:

About the role

... company description ...

Responsibilities

• ...

Requirements

• Self-sufficient, hands-on engineer
• Comfortable asking questions
• Quick learner of new skills

Skills

• Circuit and PCB design and evaluation
• Sensor experimental design and data analysis
• Fabrication of R&D systems
• Implementation of systems for field trials
• Hands‑on engineering mindset
• Ability to ask questions and learn quickly

Benefits

• Competitive salary
• Equity
• 401(k) with company match
• Health, dental, and vision coverage (100% of individual premium paid for HMO medical, vision, dental)
• Short‑ and long‑term disability
• Life insurance
• Flexible time off
• 12 company‑paid holidays
• Conference and learning budget
• Greentown Labs membership
• $90/month transportation benefit
• $65/month health and wellness benefit
• Flexible spending account (FSA)

We should not include Pay or Schedule sections. Check for any duplicated content: we included health coverage details; also we have separate line for health, dental, vision coverage and also note 100% premium. Could combine but it's fine. Now ensure we didn't include any boilerplate: we omitted interview process, LinkedIn study, domain update, AI tools note, etc. Check that we preserved all substantive info: company description includes mission, product, impact, location, team size, culture. Did we include "We run across six continents at manufacturers like Coca-Cola, Unilever, and AB InBev, backed by tier-1 investors in Physical AI." That's substantive. Should be in About the role. Also "A Laminar line uses about 20% less water and 20% fewer chemicals and runs 15% faster, with quality protected." That's substantive. Also "Productivity and sustainability improve together." Also "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." Also "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." Also "Why You'll Love it Here" section includes many bullet points; we captured benefits but also some like "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". Those are also substantive and could be part of Benefits or maybe a separate section like "Why You'll Love it Here". But we only have predefined headings; we could include them under Benefits or maybe under About the role as culture. The instruction says use those headings for sections; we can add extra sections if they have real content, but we should stick to the given examples? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive list. Could we add a section like "Why You'll Love it Here"? Might be okay but better to fit into existing sections. The "Why You'll Love it Here" includes location, recognition, team events, benefits. Some of those are benefits (Greentown Labs membership, transportation benefit) already captured. Recognition and team events could be part of Benefits or maybe a separate "Culture" section but not in list. Could incorporate into About the role or Benefits as list items. We should preserve all substantive info, so we need to include recognition, location, team events. Let's add them under Benefits as list items or maybe under About the role as a paragraph. Better to add a section "Why You'll Love it Here" but not in the list of examples; but the instruction says use those headings for section headings (e.g