Product Designer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate. We need to parse the posting. Key info: - Title: Product Designer at Lumion (but not used as heading) - Location: In-office, South Jordan, Utah - Comp: Salary, meaningful equity, and bonuses tied to company revenue - About Lumion: description - Why this role matters: description - The work: description (own design across entire platform, product design end to end, prototypes, design system, AI interfaces, student surfaces) - How we work: description (fluent with AI design and prototyping tools, process, in-office) - Who you are: description (shipped complex B2B software, data-dense admin tools, etc.) - Why you'll want this: Ownership, Equity, Impact, Speed - Comp and benefits: list: Salary based on what you can do, Meaningful stock options, Bonuses tied to company revenue, MacBook Pro and design and AI tooling you need, Unlimited PTO, 401(k), Health, dental, and vision reimbursement up to $537.50/mo, $200/mo tech stipend, $100/mo wellness stipend - Must be authorized to work in the US. No visa sponsorship. In-office role, relocation support available. We need sections: About the role (maybe summary of role), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. We have a lot of description that could be responsibilities: "You will own design across the entire platform. Product design end to end. You take features from PRD to shipped: user flows, interaction design, high-fidelity UI, and specs engineers can build from without guessing. You will work directly with the CEO and CTO in design sessions and own the outcome. Prototypes. Before engineering commits to a build, we want a working prototype in front of real schools. You will produce clickable, testable prototypes fast and use what you learn to sharpen the spec before a line of production code gets written. The design system. The platform spans lead management, enrollment, messaging, scheduling, payments, and reporting, and it grew fast. You will build the component library and interaction patterns that make it feel like one product, and that let engineers ship good UI without a designer in the room. AI interfaces. Schools use Lumion to configure and supervise AI agents that text, email, and call prospective students. Designing how a non-technical admissions director sets up an agent, reviews its conversations, and learns to trust it is new territory with little prior art. You will define those patterns. Student surfaces. Enrollment applications, document signing, and tuition payments, mostly on a phone. These flows handle real money and real decisions, and they have to be effortless." That's responsibilities. About the role: maybe a brief summary: "You would be Lumion's first dedicated product designer. Until now, design has been done by the founders, product managers, and engineers. That carried us a long way, and it is no longer enough. Our engineers build with AI-native workflows, so the constraint on the product is no longer how fast we can write code. It is how fast we can figure out exactly what to build and make it excellent. That is design work, and right now it is our bottleneck. The people who use our platform are admissions directors, school owners, and finance staff who live in it all day, and students making one of the bigger financial decisions of their lives. Most software in this industry was built a decade ago and looks like it. You get to set the bar for what great looks like in this market." That's about the role. Requirements/Qualifications/Skills: The posting includes "Who you are" and "How we work" and maybe "Why you'll want this". We need to separate. "Who you are": You have shipped complex B2B software. Data-dense admin tools, multi-step workflows, permissioned dashboards. You know how to make dense information feel calm and how to design for people who spend their whole workday in a product. Your craft is strong. Typography, spacing, hierarchy, color, empty states, error states. The screens you ship hold up under close inspection. You prototype. You would rather put something interactive in front of a user this week than polish a mockup for next month. You write. The words in the interface are part of the design, and you treat labels, empty states, and error messages as your job. You're sharp, not credentialed. Your degree and years of experience don't matter to us. What you have shipped and how fast you learn do. That's qualifications/skills. "How we work": You need to be fluent with AI design and prototyping tools, whether that is Figma's AI features, tools like Lovable or v0, or building prototypes in code with something like Claude Code. We care about how you work, not which tool you use. If your process ends at static mockups handed over a wall, this is not the right role. This is design inside a fast loop. Your work ships in days, you see it in front of customers, and you iterate. There are no layers between you and the decision makers, because you will be in the room with them. This is an in-office role in South Jordan, Utah, by design. Hard problems get solved faster in person, and we want the person who owns how Lumion looks and feels working directly alongside the team. That could be part of Requirements or Skills. Might be "Skills": fluency with AI design and prototyping tools, ability to work in fast loop, prototype, iterate, etc. "Why you'll want this": Ownership, Equity, Impact, Speed. That's more about benefits/motivation, but we already have Benefits and Pay sections. Comp and benefits: list as above. Pay: Salary based on what you can do, Meaningful stock options, Bonuses tied to company revenue. Could be Pay section. Benefits: MacBook Pro and design and AI tooling you need, Unlimited PTO, 401(k), Health, dental, and vision reimbursement up to $537.50/mo, $200/mo tech stipend, $100/mo wellness stipend. Schedule: In-office role in South Jordan, Utah. Relocation support available. Must be authorized to work in the US. No visa sponsorship. That's schedule/location. We must not include sections with filler like "commensurate with experience". We have actual specifics. Thus we will output sections:

About the role

with paragraph(s) summarizing.

Responsibilities

with

• items for each bullet. We need to preserve all substantive info; we should not lose details. Let's extract bullet points for responsibilities: - Own design across the entire platform. Product design end to end. - Take features from PRD to shipped: user flows, interaction design, high-fidelity UI, and specs engineers can build from without guessing. - Work directly with the CEO and CTO in design sessions and own the outcome. - Produce clickable, testable prototypes fast and use what you learn to sharpen the spec before a line of production code gets written. - Build the component library and interaction patterns that make the platform feel like one product, enabling engineers to ship good UI without a designer in the room. - Design AI interfaces: how a non-technical admissions director sets up an agent, reviews its conversations, and learns to trust it. - Design student surfaces: enrollment applications, document signing, and tuition payments, mostly on a phone, handling real money and real decisions, effortless. We could combine some. Now Requirements/Qualifications/Skills: We need to decide which sections to include. The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements, Qualifications, Skills into one section maybe "Requirements" or "Qualifications". But we need to follow the rule: use headings for those specific names if we include them. We could include "Qualifications" and "Skills" as separate if we have content. But we might combine to avoid thin sections. We have content for "Who you are" (qualifications/skills) and "How we work" (skills/process). Could be merged into "Qualifications". Let's think. We could have:

  Qualifications

  with
  • items covering shipped complex B2B software, data-dense admin tools, multi-step workflows, permissioned dashboards, ability to make dense information feel calm, typography, spacing, hierarchy, color, empty states, error states, prototyping, writing copy, not credentialed, focus on shipped work and learning speed, fluency with AI design and prototyping tools (Figma AI, Lovable, v0, Claude Code), ability to work in fast loop, iterate, collaborate directly with decision makers, in-office. That seems comprehensive. We could also have a separate "Skills" for tools, but we can include in Qualifications. Now Benefits and Pay sections. Benefits: list items. Pay: Salary based on what you can do, Meaningful stock options, Bonuses tied to company revenue. Schedule: In-office role in South Jordan, Utah. Relocation support available. Must be authorized to work in the US. No visa sponsorship. We need to ensure we don't include boilerplate like "Must be authorized to work in the US. We do not sponsor work visas." That's okay to include as schedule/location. Now we must not repeat job title as heading. Already not. We must not include Job ID/requisition numbers. We must not include application instructions (like "How to apply"). We must not include cookie/navigation/legal/EEO etc. Now produce HTML fragment. Let's craft. We'll need to wrap sections in appropriate tags. We'll output something like:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Qualifications

    • ...
    ...

    Benefits

    • ...
    ...

    Pay

    • ...
    ...

    Schedule

    ...

    Check if any section might be empty: we have content for all. Now ensure we preserve all substantive info: Did we miss anything? Let's verify. From posting: - Lumion description: "Lumion is the all-in-one operating system for trade and technical schools. We power the entire institution: AI-driven lead generation and conversion, enrollment, financial aid, student lifecycle management, and tuition payments. Most schools are still stitching together five or six disconnected tools to do what our platform handles. America has a massive skilled trades shortage and the schools that train electricians, welders, and nurses are the bottleneck. We're backed by TTV Capital and Tusk Venture Partners." This is part of About the role? Could be included there. We included a paragraph about role but didn't include Lumion description. We should include that in About the role maybe as context. The About the role section could include both role and company description. Let's incorporate. Thus About the role paragraph(s) could include: Lumion description, why role matters, etc. We need to preserve all substantive info; we can't omit Lumion description. Let's craft About the role:

    Lumion is the all-in-one operating system for trade and technical schools. We power the entire institution: AI-driven lead generation and conversion, enrollment, financial aid, student lifecycle management, and tuition payments. Most schools are still stitching together five or six disconnected tools to do what our platform handles. America has a massive skilled trades shortage and the schools that train electricians, welders, and nurses are the bottleneck. We're backed by TTV Capital and