Design Engineer

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Need to preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove application instructions (the "To apply..." line). Also remove EEO statements. We need to parse the posting. Let's extract content: Title: Design and Fabrication Engineer Company: Dolav USA Inc. | Grand Rapids, Michigan | On site | Full time, exempt At a glance: paragraph describing role. What the job is: bullet-like sentences. You will do well here if: bullet-like. This is probably not your role if: bullet-like. What you bring: bullet-like. Nice to have: bullet-like. The environment: paragraph. Why Dolav: paragraph. We need to map to sections: About the role (maybe the At a glance + description). Responsibilities (What the job is). Requirements (What you bring). Qualifications (maybe same as Requirements? Could combine). Skills (maybe from What you bring and Nice to have). Benefits (maybe none explicit). Pay (none). Schedule (maybe mention Full time, exempt). But we should only include sections if posting has real specific content. Pay: not mentioned. Benefits: not mentioned (no benefits listed). Schedule: we have "Full time, exempt" - that's schedule info. Could include Schedule section with that. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no markdown fences. Let's craft sections:

About the role

At Dolav USA Inc. in Grand Rapids, Michigan, you will design custom modifications to injection‑molded bins and pallets, work directly with customers and fabrication techs, program robotic equipment, and see your designs through to production.

But we need to preserve all substantive info; we can combine At a glance and description. Better: Use the At a glance paragraph: "We make heavy duty plastic bins, pallets, and bulk containers, and then we change them. A food processor needs a drain in a different place. A recycler needs a door cut where there isn’t one. A distributor calls with a rough sketch and a deadline. Someone has to turn that into a real design, price it honestly, and walk it out to the floor to make sure it gets built right. That someone is you. This is not a role where you model in isolation and email a drawing over the wall. You will be on the phone with customers, at the bench with our fabrication techs, and in SolidWorks, often in the same afternoon. If that sounds like a good day, keep reading." Then maybe a separate paragraph summarizing what the job is? But we have Responsibilities section. Let's decide sections: - About the role: At a glance paragraph. - Responsibilities: What the job is paragraph(s). Could be multiple sentences; we can put them in

• each duty. List duties: - Design custom modifications to injection molded bins and pallets in SolidWorks, from the first conversation through the last production drawing. - Take a vague request from a customer or distributor and turn it into something buildable, which usually means asking better questions than they knew to answer. - Build the full package behind a quote: bill of material, routings, item numbers, and a cost estimate that holds up on labor, setups, and hardware. - Program, run, and troubleshoot our robotic fabrication equipment, and keep the saws and welders running. - Walk your own designs out to the floor, watch the first one get built, and fix what does not fit. - Own custom projects start to finish alongside Sales and Production, and tell people where things stand before they have to ask. - Work with counterparts in the United States, Europe, and Israel on products and problems that cross all three. That seems comprehensive. - Requirements: What you bring (mandatory). List: - Bachelor of Science in Mechanical Engineering or in Product Design and Manufacturing. - Three or more years in mechanical engineering or in product design and manufacturing. Five or more is preferred. - SolidWorks as a daily tool, including 3D modeling, 2D production drawings, geometric dimensioning and tolerancing, and disciplined version control. - Robot control and programming experience. ABB is preferred. - Real time on a production floor, not just near one. - Communication skills you can demonstrate, because we will ask you to demonstrate them. We could also include "Nice to have" as Skills or maybe separate Skills section. - Skills: Could combine Nice to have items: - SAP Business One or a comparable ERP. - Plastic welding. - Machine maintenance and troubleshooting. - Product testing to ASTM or ISO standards. - Experience with plastics, injection molded products, or material handling equipment. - Project leadership with real milestones, timelines, and budgets. We could also include communication skills etc but already in Requirements. - Schedule: Full time, exempt. We could also mention occasional travel, coordination outside standard Eastern Time hours. That's schedule-related. Thus Schedule section:

  Full‑time, exempt position with occasional travel for customer visits, job walks, and trade shows; some coordination with Europe and Israel occurs outside standard Eastern Time hours.

  - Benefits: none specific, so omit. - Pay: none, omit. - Qualifications: Could be same as Requirements; but we already have Requirements. The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include Qualifications if we have distinct content; but we could merge Requirements and Qualifications. However we need to avoid thin sections. Perhaps we combine Requirements and Qualifications into one section called Requirements (or Qualifications). Since we have both "What you bring" (requirements) and maybe "Nice to have" (skills). Qualifications could be the education/experience requirements. Let's treat Requirements as education/experience, and Skills as technical/soft skills. That seems okay. Thus:

  About the role

  ...At a glance paragraph...

  Responsibilities

  • ... each duty...

  Requirements

  • Bachelor of Science in Mechanical Engineering or in Product Design and Manufacturing.
  • Three or more years in mechanical engineering or in product design and manufacturing (five or more preferred).
  • SolidWorks as a daily tool, including 3D modeling, 2D production drawings, geometric dimensioning and tolerancing, and disciplined version control.
  • Robot control and programming experience (ABB preferred).
  • Real‑time experience on a production floor, not just near one.
  • Demonstrable communication skills.

  Skills

  • SAP Business One or comparable ERP.
  • Plastic welding.
  • Machine maintenance and troubleshooting.
  • Product testing to ASTM or ISO standards.
  • Experience with plastics, injection molded products, or material handling equipment.
  • Project leadership with real milestones, timelines, and budgets.

  Schedule

  Full‑time, exempt position with occasional travel for customer visits, job walks, and trade shows; some coordination with Europe and Israel occurs outside standard Eastern Time hours.

  We should not include any boilerplate like EEO, apply link, etc. Check that we preserved all substantive info: At a glance paragraph included; responsibilities list covered all points; requirements covered education, years, SolidWorks, robot experience, floor time, communication; skills covered nice-to-have; schedule covered full time, exempt, travel, coordination. We omitted "Why Dolav" paragraph and "The environment" paragraph. Those are substantive; we need to preserve all substantive information. So we must include them somewhere. Could add a section "About the company" or "Environment". But headings list only includes specific ones; we could add a section like "About the company" but not in list; but instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we can use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings; but we need to preserve all substantive info, so we must fit "Why Dolav" and "The environment" into existing sections. Could add them to About the role or maybe a new section "Company overview". But if we add a heading not in the list, might be considered not following instruction. However instruction says use

  for section headings (e.g. ...). It doesn't forbid other headings, but suggests those are typical. Safer to include them within existing sections: maybe add a paragraph under About the role about company and environment. Thus About the role can include At a glance plus Why Dolav and The environment. Let's craft About the role paragraph(s) that combine: - At a glance description. - Why Dolav: Dolav Plastic Products has been building industrial packaging since 1976 and sells in more than 60 countries. Dolav USA is the North American arm, based in Grand Rapids, small enough that your work is visible to everyone and large enough to be backed by a global company. You will not be one of forty engineers on a roadmap. You will be the person who makes custom work happen here. - The environment: Half office, half active fabrication floor. Saws, welders, robotics, moving equipment, and noise. Hearing protection and other personal protective equipment are required in posted areas. You will sit at a workstation for long stretches and you will be on your feet for long stretches, and you will occasionally lift up to 50 pounds. Travel is occasional, mostly customer visits, job walks, and trade shows. Some coordination with Europe and Israel happens outside standard Eastern Time hours. We already put travel/coordination in Schedule; but we could keep it there and not duplicate. However environment includes travel/coordination; we could keep schedule just about full time/exempt and mention travel/coordination there; but we might duplicate. Better to keep schedule as just full time/exempt; environment includes travel/coordination. But schedule section we already added travel/coordination; we could remove duplication and keep schedule just full time/exempt. Let's decide. We need to preserve all substantive info; we can include travel/coverage in either section but not duplicate. Let's put travel/coverage in Schedule section (makes sense). Then environment section can omit travel/coverage. Thus About the role will include At a glance, Why Dolav, and The environment (excluding travel/coverage). Let's extract environment details without travel/coverage: "The environmentHalf office, half active fabrication floor. Saws, welders, robotics, moving equipment, and noise. Hearing protection and other personal protective equipment are required in posted areas. You will sit at a workstation for long stretches and you will be on your feet for long stretches, and you will occasionally lift up to 50 pounds." We'll incorporate that. Now schedule section: Full‑time, exempt position with occasional travel for customer visits, job walks, and trade shows; some coordination with Europe and Israel occurs outside standard Eastern Time hours. Now we have all info. Let's craft final HTML. Be careful to escape any HTML special characters? Not needed. We'll output:

  About the role

  We make heavy duty plastic bins, pallets, and bulk containers, and then we change them. A food processor needs a drain in a different place. A recycler needs a door cut where there isn’t one. A distributor calls with a rough sketch and a deadline. Someone has to turn that into a real design, price it honestly, and walk it out to the floor to make sure it