UI/UX Design Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. We have summary: Mujin is the future... then description: "We're looking for a UI/UX Design Engineer — a designer who ships." Then "What You'll Do" bullet list. Then "Position Requirements" bullet list. Then "Preferred Backgrounds". Then "Physical Demands/ Work Environment". Then "Travel Requirement: Approximnately 10%, Domestically / Internationally". Then "Prolonged periods of sitting at a desk and working on a computer Ability to work extended hours as required". Then "Great Company! Great Benefits! When working with Mujin, enjoy:" then list of benefits. We need to map to sections: About the role (summary/intro), Responsibilities (What You'll Do), Requirements (Position Requirements), Qualifications (maybe Preferred Backgrounds?), Skills (maybe AI-native workflow, MUI experience etc), Benefits (list), Pay (not mentioned), Schedule (maybe Travel requirement? Not exactly schedule; schedule could be work hours, extended hours, travel). We need to include only sections with real specific content. Pay: not mentioned, so omit. Schedule: we have travel requirement and ability to work extended hours; could be considered schedule. But we need to see if posting actually states schedule specifics: "Travel Requirement: Approximately 10%, Domestically / Internationally" and "Prolonged periods of sitting at a desk and working on a computer Ability to work extended hours as required". That's schedule-ish. We'll include a Schedule section with that content. Benefits: we have list. Qualifications: maybe combine Position Requirements and Preferred Backgrounds? The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes where. We have "Position Requirements" which is likely Requirements. Also "Preferred Backgrounds" could be Qualifications or Skills. Also there is mention of "AI-native workflow", "MUI experience is a strong plus", "Product taste and product thinking", etc. Those could be Skills. We need to preserve all substantive information, not invent or summarize away detail. So we need to include each bullet point as list items. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: EEO, accommodation request, etc. Also remove "This Position Description is intended..." and "Mujin is proud to be an Equal Employment Opportunity employer." Also remove the sponsorship eligibility line and the attention applicants accommodation request? That is boilerplate? It's about accommodation request; might be considered EEO/legal. Probably remove. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About the role: The introductory paragraphs before "What You'll Do". Let's capture: "Mujin is the future of industrial robotic systems in production and distribution environments. Our technology gives robots perception and awareness, enabling them to take on more advanced tasks. We aim to revolutionize the use of robotics within industry to free human resources from labor-intensive tasks to focus on more intellectual challenges. We're looking for a UI/UX Design Engineer — a designer who ships. In this role you'll create and build the interfaces people use to run intelligent robot systems on a live factory floor, across our operator's HMI touchscreens and PC control applications. Everything a human knows about what a robot is doing flows through the UI you design and code. Our goal is to make intelligent robots usable by anyone, with no custom development or training required." That's About the role. Responsibilities: The "What You'll Do" bullet list. Let's capture each bullet: - Own features end to end — in Figma and in code. You will design the solution and ship the production front end for it in our MUI/React codebase, rather than handing a spec to someone else to interpret. - Collaborate across teams, not just within design. Work day-to-day with product, engineering, and subject-matter experts, and directly with the operators, integrators, and field teams who live with these robots — to turn real user needs and business goals into logical and intuitive experiences. - Design human–machine interactions across multiple surfaces: PC desktop apps (data-dense job queues, dashboards, integrator tooling), operator HMI touchscreens (gloved-hand, high-contrast, real-time robot and job status) and operator scanner screens. - Design the unhappy paths as carefully as the happy one. Model complex, safety-relevant states — loading, degraded, faulted, recovering — so operators always know what the robot is doing and what is needed for continuous operations flow. - Prototype fast to learn fast. Produce multiple concepts, test them, and know when to go deeper versus when to pivot. - Contribute to and extend the MujinController design system and MUI theme so the whole team ships a cohesive, high-craft experience. - Ground your decisions in real-world user data, scenarios, and context. Partner with engineers and subject-matter experts, engage commercial and operations stakeholders, review field footage and support signals, and defend design choices with evidence, not preference. That's responsibilities. Requirements: The "Position Requirements" bullet list: - 3+ years designing complex enterprise or industrial product UI (native or web), with a portfolio showing production-released, visually refined work — and the reasoning behind each choice. - Verifiable implementations of your designs into production. - MUI experience is a strong plus. - Product taste and product thinking. Evidence you shaped what got built, not only how it looked but also how it worked — showing you prioritize ruthlessly and tie design to outcomes (adoption, error rate, task time). - Logical, systems-level thinking. You reason through state, edge cases, and data density the way an engineer does — the core of good experience design work. - Communication fluency. You speak and write confidently about your design decisions, argue them without ego, and collaborate fluently in English with a distributed engineering team. - AI-native workflow. You already use AI design/coding tools (Claude Code, Cursor, and similar) to build and prototype faster. - You take initiative. You don't wait to be handed a spec — you spot gaps, raise problems early, propose better ways of working, and push craft and process forward for the whole team. That's requirements. Qualifications: Could be "Preferred Backgrounds". Let's capture: - Design engineers from technical-product or dev-tools companies; product designers from complex B2B/enterprise or ops tooling who ship their own front-end; or UX designers from industrial, robotics, automotive, medical-device, or other real-time / safety-critical domains. That's qualifications. Skills: Might be overlapping with requirements; but we could treat "Skills" as maybe the specific technical skills: MUI/React, Figma, AI design/coding tools, etc. However we already have MUI experience in requirements, AI-native workflow in requirements. Could still have a Skills section for things like "Figma", "MUI/React", "AI design/coding tools". But we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Skills into Requirements or Qualifications. But we need to follow headings list; we can omit Skills if no distinct content beyond what's already covered. However we have "MUI experience is a strong plus" and "AI-native workflow". Those could be considered skills. But they are already in Requirements. So we can omit Skills section. Benefits: The list after "Great Company! Great Benefits! When working with Mujin, enjoy:": - 100% Company paid Medical, Dental, Vision option plus the opportunity to buy-up some benefits beginning the 1st of the month after hiring! - 100% Company Paid Life Insurance & Voluntary Benefits - 100% Company Paid Long and Short-Term Disability - 15 Paid Time Off (PTO) days beginning your 1st year! - 11 Paid Holidays, including (2) Floating Holidays! - 401(k) Plan! - Parental Leave Benefits! - Health Savings Account (HSA) option with HDHP! - Flexible Spending Account (FSA) options for Medical and Dependent Care! - Referral Bonuses! - Company Stock Options in many roles! We need to preserve all substantive information; keep exclamation marks? Probably okay. Schedule: We have travel requirement and ability to work extended hours. Also "Prolonged periods of sitting at a desk and working on a computer". That's more work environment. But schedule could include travel requirement and extended hours. Let's capture: - Travel Requirement: Approximately 10%, Domestically / Internationally - Prolonged periods of sitting at a desk and working on a computer - Ability to work extended hours as required We could also include physical demands but that's more work environment. However schedule section is about schedule; we can include travel and extended hours. The physical demands maybe not schedule. But we could include them under Schedule? Might be stretching. Better to include a Schedule section with travel and extended hours; physical demands maybe omitted as not schedule. But we need to preserve all substantive information; we cannot drop physical demands unless we put them elsewhere. Could we put them under About the role? No. Could we put them under Requirements? No. Could we create a Work Environment section? Not in allowed headings. The allowed headings list does not include Work Environment. So we need to decide where to place physical demands. Perhaps we can incorporate them into Schedule as they relate to work conditions. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to decide if Schedule section is appropriate for physical demands. The posting includes "Physical Demands/ Work Environment" heading with bullet points: "Prolonged periods of sitting at a desk and working on a computer Ability to work extended hours as required". That's basically schedule/physical demands. So we can treat that as Schedule content. Also travel requirement is separate but could be part of Schedule. So we can combine. Thus Schedule section will have: - Travel Requirement: Approximately 10%, Domestically / Internationally - Prolonged periods of sitting at a desk and working on a computer - Ability to work extended hours as required Now Pay: not mentioned, omit. Now we need to output HTML with

for each section heading, and

• for lists,

  for prose. We need to ensure we don't repeat job title as heading. Not include any boilerplate. Let's craft. About the role: prose paragraphs (maybe two paragraphs). We'll put as

  elements. Responsibilities:

  • each bullet. Requirements:
    • each bullet. Qualifications:
      • each bullet (just one bullet? Actually it's a sentence with semicolons; we can keep as one
      • ). Benefits:
        • each bullet. Schedule:
          • each bullet. Now check for any duplicated lines: we should not duplicate. Check for any boilerplate we might have inadvertently included: The "Great Company! Great Benefits!" line is introductory; we can incorporate that as a

            before the benefits list, or we can just start with benefits list. The instruction: use

            for prose. So we can include a

            "Great Company! Great Benefits! When working with Mujin, enjoy:" then the list. But that line is somewhat promotional; still substantive. We'll include as a

            . Similarly, we might include a

            for About the role. Now ensure we don't include the EEO etc. Let's write HTML. We'll need to escape any special characters? Not needed. Let's produce:

            About the role

            Mujin is the future of industrial robotic systems in