Robotic Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes description of company, then "We’re growing our US robotic engineering team : The role involves designing, developping, and implementing robotic systems and algorithms, contributing to the full lifecycle of our products—from concept to deployment.." Then "What you’ll do" list, then "What you bring" list, then "Base Salary: $115 000 to $150 000/ year", "Experience Required: 5 years in a relevant field", then "Your adventure at Kickmaker" (projects description), then "We offer a benefits package..." (benefits), then "Our Culture & Spirit". Also "Your adventure at Kickmaker" includes description of projects and growth path. We need headings: Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role: maybe the paragraph describing role (designing, developing, implementing robotic systems...). That's substantive. - Responsibilities: the "What you’ll do" list. - Requirements/Qualifications/Skills: "What you bring" list includes degree, experience, programming skills, ROS, control systems, etc. Could split into Requirements (education, experience) and Skills (programming, tools). But we can combine into one section "Requirements" or "Qualifications". The instruction: prefer few substantive sections over many thin ones. So maybe combine education/experience/skills into one "Requirements" section. - Pay: Base Salary line. - Benefits: benefits package description. - Maybe "About the company" not needed as heading? Could be "About the role" only. - "Your adventure at Kickmaker" could be part of "About the role" or separate? It's more about projects and growth; could be included under "About the role" or maybe a separate section like "What you’ll experience". But headings limited to given list; we can use "About the role" to cover role description and adventure. - "Our Culture & Spirit" could be a section but not in list; we could omit or include as part of About the role? Probably better to omit if not matching headings. The instruction: include a section ONLY when posting has real, specific content for it. We have content for culture/spirit, but no heading matches exactly; we could use "About the role" to include that? Might be okay. But we must not invent sections like "Culture". So we will stick to headings from list: About the role, Responsibilities, Requirements, Pay, Benefits. Possibly Schedule if present (none). So we will output those sections. We need to preserve all substantive information, not invent or summarize away detail. Must not omit details like specific industries list, number of projects, etc. Must include all details from posting. We need to format lists with

• . Use

  for prose. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes some lines about AI tools in hiring, data processing, etc. Those are likely boilerplate/legal; we should remove them. Also the line about "If you would like more information about how your data is processed, please contact us." That's legal; remove. Also the line about "We may use artificial intelligence (AI) tools..." remove. Also the line about "If you’ve ever looked at a product and thought, “I could build this better,” let’s talk!" maybe keep as part of culture? It's not boilerplate; it's a call to action but could be considered application instruction? It's encouraging to talk; might be considered application instruction. Safer to remove? The instruction: remove application instructions. That line is like a call to apply; could be considered application instruction. Safer to remove. Also the line "An image is worth a thousand words, and this one will give you the full vibe" plus video reference; that's maybe promotional; could keep? It's not essential job info; but it's about culture. Might be considered fluff but not boilerplate. However we need to preserve all substantive information; is that substantive? It's about culture/video. Might be considered fluff but still part of posting. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not those. So we could keep it as part of About the role or Culture. But we don't have a Culture heading; we could incorporate into About the role. We need to ensure we don't miss any substantive details: list of industries (medical, new mobility, electrification, agrotech, robotics, IOT and consumer devices), cross-disciplinary skills (embedded AI, high-tech manufacturing automation, eco-design, industrial design and WEB 3.0 for the economy of functionality). Also mention of maker culture, passion, excitement, kindness pillars, team and community spirit, enabling potential, autonomy, initiative. Presence in France, China, US, community over 250 passionate kickers. Looking to strengthen team in Boston, Seattle, San Fransisco. Growing US robotic engineering team: role involves designing, developping, implementing robotic systems and algorithms, contributing to full lifecycle. Then responsibilities list. Then what you bring list. Then Base Salary line. Then Experience Required line. Then Your adventure at Kickmaker: work on 5–10 projects annually, choosing from wide range of industries: robotics, medical devices, fitness tech, automotive, micro-mobility, beauty tech, sports exoskeletons, AI-driven hardware. Path evolves with curiosity: help you grow where professional ambitions and personal passions meet, always connected to latest tech breakthroughs. Then benefits: health and dental coverage, paid time off, 5 sick days, 401(k) plan. Then Culture & Spirit: innovators, for innovators, across 7 offices give tools to make ideas happen, vision: build space where innovators can explore, experiment, push boundaries together. Video reference, image worth a thousand words. Then AI tools note (remove). Then data processing note (remove). We need to include all that except removed bits. Now structure:

  About the role

  Kickmaker is a high-tech product design and industrialization agency... (include company description, maker culture, locations, team size, US robotic engineering team growth, role description).

  Then

  Responsibilities

  • Design, build, and test robotic systems and components
  ... etc. Then

  Requirements

  Bachelor’s or Master’s degree in Robotics, Mechanical Engineering, Electronic Engineering, Computer Science, or a related field

  • 5+ years of experience in robotics or automation (industry is preferred)
  • Strong programming skills in Python and/or C++
  • Experience with ROS/ROS2
  • Knowledge of control systems, computer vision, and sensor integration
  • Familiarity with simulation tools such as MATLAB
  • Strong problem-solving skills and attention to detail
  Actually need to wrap list in
  • . The degree could be a

    or

  • . Could treat as requirement bullet as well. Let's make a list: include degree as first bullet. Then

    Pay

    Base Salary: $115,000 to $150,000 per year

    Then

    Benefits

    We offer a benefits package designed to support you and your family while keeping costs low. This includes health and dental coverage, paid time off and 5 sick days for rest and renewal. You can also join our 401(k) plan to invest in your future.

    We might also include "Your adventure at Kickmaker" as part of About the role or separate section like "What you’ll experience". Since we have no heading for that, we could incorporate into About the role after role description. Thus About the role paragraph will be long, containing company description, culture, locations, team size, US team growth, role description, adventure description (projects, growth path). Ensure we keep all details. We must not repeat job title as heading. No job title present. We must not include duplicated lines. Ensure we don't repeat. Now produce HTML fragment. Check for any leftover boilerplate: lines about AI tools, data processing, contact us, image/video, "If you’ve ever looked at a product..." etc. We'll remove those. Check for any duplicated lines: maybe none. Now craft final HTML. Be careful with punctuation and formatting. Let's write:

    About the role

    Kickmaker is a high-tech product design and industrialization agency. We support our customers from prototype to production run in our main vertical markets (medical, new mobility, electrification, agrotech, robotics, IOT and consumer devices) and our cross-disciplinary skills (embedded AI, high-tech manufacturing automation, eco-design, industrial design and WEB 3.0 for the economy of functionality). We're evolving with a real maker culture! Passion, excitement and kindness are the pillars of KICKMAKER. This team and community spirit has enabled us to shape a unique corporate culture. Our approach: to enable everyone to fulfill their potential by working on exciting projects, and to encourage autonomy and initiative. Present in France, China and the United States, our community counts over 250 passionate kickers and keeps growing. It is in this context that we are looking to strengthen our team in Boston, Seattle and San Fransisco. We’re growing our US robotic engineering team: the role involves designing, developing, and implementing robotic systems and algorithms, contributing to the full lifecycle of our products—from concept to deployment. You’ll work on 5–10 projects annually, choosing from a wide range of industries: robotics, medical devices, fitness tech, automotive, micro-mobility, beauty tech, sports exoskeletons, and AI‑driven hardware. Your path evolves with your curiosity: we help you grow where your professional ambitions and personal passions meet, always connected to the latest tech breakthroughs.

    Responsibilities

    • Design, build, and test robotic systems and components
    • Develop and optimize control algorithms, perception systems, and navigation strategies
    • Integrate hardware and software components for autonomous or semi‑autonomous systems
    • Collaborate with cross‑functional teams including mechanical, electrical, and software engineers
    • Conduct simulations and real‑world testing to validate system performance
    • Troubleshoot and resolve technical issues in development and production environments
    • Stay current with emerging technologies and industry trends in robotics and AI

    Requirements

    • Bachelor’s or Master’s degree in Robotics, Mechanical Engineering, Electronic Engineering, Computer Science, or a related field
    • 5+ years of experience in robotics or automation (industry is preferred)
    • Strong programming skills in Python and/or C++
    • Experience with ROS/ROS2
    • Knowledge of control systems, computer vision, and sensor integration
    • Familiarity with simulation tools such as MATLAB
    • Strong problem‑solving skills and attention to detail

    Pay

    Base Salary: $115,000 to $150,000 per year

    Benefits

    We offer a benefits package designed to support you and your family while keeping costs low. This includes health and dental coverage, paid time off and 5 sick days for rest and renewal. You