Senior Software Engineer, Embedded Systems

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: About the role (description of job), Responsibilities (What You Will Do), Requirements/Qualifications/Skills (About You), Benefits (list). Pay and Schedule not mentioned explicitly; there is mention of competitive salary, equity, etc. Pay: they mention competitive salary and bonus opportunities, but not specific numbers. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "Competitive salary and bonus opportunities" and also later details about salary: "Laminar pays 100% of the individual health insurance premium...". That's about benefits, not pay specifics. There's no explicit salary range. Should we include Pay? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive salary and bonus opportunities" which is a statement about pay, albeit vague. It's still stating something about pay. So we could include a Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." Might combine Pay into Benefits? But they have separate headings. The instruction: "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')". "Competitive salary and bonus opportunities" is not filler? It's somewhat generic but still a statement. It's not "not specified". It's a claim. I'd include Pay section with that sentence. Schedule: no mention of schedule (e.g., full-time, remote, hours). Not present, so omit Schedule. Benefits: they have a list: Direct impact..., Comprehensive benefits package..., 401k..., Equity..., Competitive salary..., Dynamic..., Opportunities..., Access..., plus later details: health, dental, vision, life insurance, disability, transportation benefit, health and wellness benefit, FSA, 12 company-paid holidays, employer-matching 401(k), Greentown Labs membership. So we can create Benefits section with ul list. Now structure:

About the role

... (the paragraph describing role and company). Must preserve all substantive info, not invent. We'll need to condense but preserve details. Must not omit any substantive info. That's tricky: we need to keep all info but can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot omit details. We need to keep all info from the posting, but we can format into HTML. Must not lose any detail. So we need to include everything from the posting (except boilerplate). That's a lot. We need to output HTML that includes all the content, just restructured with headings. Thus we need to parse the posting and extract sections: About the role (maybe the introductory paragraphs before "We are looking for a Senior Embedded Software Engineer...")? Actually the posting starts with a description of Laminar, then "We are looking for a Senior Embedded Software Engineer...". That is the role description. Then "What You Will Do" with bullet points. Then "About You" with bullet points. Then "Benefits" with bullet points. Then later sections like "Learn How We Think", "Learn about our startup journey...", "Why You'll Love it Here", "Our Interview Process", etc. Those are also substantive info. Should we include them? The instruction: "include a section ONLY when the posting has real, specific content for it". Those sections have content. Should we create headings for them? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not include sections like "Learn How We Think", "Why You'll Love it Here", "Our Interview Process". The instruction 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? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings. Other sections like interview process, company culture, etc. might be considered part of About the role or Benefits? But they are not exactly responsibilities/requirements. However we could include them under About the role (as additional description). The instruction: "Prefer a few substantive sections over many thin ones." So we should combine extra info into About the role or Benefits. Thus we will have sections: About the role (includes company description, mission, culture, interview process, etc.), Responsibilities (What You Will Do), Requirements (About You), Benefits (Benefits list plus maybe other perks), Pay (Competitive salary and bonus opportunities). We'll omit Schedule. Now we need to ensure we preserve all substantive info. Let's extract all relevant content from posting, excluding boilerplate like cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove lines like "Learn How We Think", "Learn about our startup journey..." etc? Those are not boilerplate; they are substantive about company. We'll keep them within About the role. We must not repeat the job title as a heading. Already not. We must not put Job ID/requisition numbers as headings. Now produce HTML fragment. Let's gather content. Intro paragraph: "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." Then role: "We are looking for a Senior Embedded Software Engineer to own signal processing and firmware of Laminar’s process-aware sensors. This is a hands-on technical role at the intersection of embedded systems, digital signal processing, and sensing methodology. You will implement new detectors and sensing elements, own the signal data from end to end, and work directly with Hardware and ML teams to get the visibility into the industrial processes we need." Then "What You Will Do" with subheadings: Acquisition & Conditioning, Sensor Integration, Noise Rejection, Firmware development, Calibration, Device Connectivity. Each with description. Then "About You": bullet list of requirements. Then "Benefits": bullet list. Then later: "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 apply button if they hit 60%. Laminar (formerly H2Ok) is committed to building a diverse and inclusive team. So, to the women and nonbinary folks out there feeling unsure if you're a perfect fit, we strongly encourage you to apply! If you're ready to play a key role in scaling a game-changing company that’s transforming the industrial sector and advancing sustainability, we want to hear from you! We recently updated our domain to runlaminar.com. Please ensure you add the runlaminar.com domain to your safe senders list to ensure you receive our communications We may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses and identifying potential inconsistencies or verification signals in application materials based on available information. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us. Our pay ranges are established per Pave Compensation Software. 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. Laminar pays 100% of the individual health insurance premium for HMO medical, vision, and dental, offers flexible PTO, a $90/month transportation benefit, a $65/month health and wellness benefit, FSA, 12 company-paid holidays, an employer-matching 401(k) (unheard of at this stage!), and Greentown Labs membership, among other valuable resources. (*subject to change)" We need to strip boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The "Our Interview Process" is not boilerplate; it's substantive. We'll include that in About the role maybe. Also the lines about diversity encouragement, domain safe senders, AI tools, data processing, pay ranges per Pave, etc. Those are substantive? They are about hiring process and company policies. Could be included in About the role or Benefits