Senior UX 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. Must not include Job ID etc. Remove boilerplate like EEO, legal, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Content: - Intro: "Accruent is looking for a Senior UX Designer to lead end-to-end design across multiple B2B software products. You will research complex customer workflows, define product experiences, create and test solutions, and partner with Product and Engineering through implementation. This is a high-autonomy role for a systems thinker with strong design judgment, research experience, and interest in emerging AI-assisted and code-native design workflows." That's about the role. Could be "About the role" section. Then "What You’ll Do" list: bullet points. Then "What We’re Looking For": list of qualifications/skills. Then "Bonus Qualifications": list. Then "Why This Role": description. Then "Fortive Corporation Overview": description of Fortive. Then "About Accruent": description. Then "We Are an Equal Opportunity Employer." etc (boilerplate to remove). Then "Bonus or Equity This position is also eligible for bonus as part of the total compensation package." Then "Pay Range The salary range for this position (in local currency) is 109,700.00 - 183,200.00" Then repeated paragraphs again (duplicate). We need to preserve all substantive info, but remove duplicates. We need to decide sections: - About the role: could combine intro and maybe "Why This Role"? Actually "Why This Role" is separate. Could be its own section. - Responsibilities: from "What You’ll Do". - Requirements: maybe "What We’re Looking For" (core qualifications). Could be Requirements. - Qualifications: maybe "Bonus Qualifications"? Or we could treat "What We’re Looking For" as Requirements, and "Bonus Qualifications" as Qualifications? But spec says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have content for: - About the role: intro paragraph. - Responsibilities: bullet list under "What You’ll Do". - Requirements: bullet list under "What We’re Looking For". - Qualifications: maybe "Bonus Qualifications" (these are bonus). Could also treat as Qualifications. - Skills: maybe we could extract skills from both lists? But we already have Requirements and Qualifications; maybe we can combine skills into either. But we need to avoid thin sections. Could combine Requirements and Qualifications into one? But spec says we can have multiple sections; better to have separate if content distinct. - Benefits: we have "Bonus or Equity This position is also eligible for bonus as part of the total compensation package." Also maybe "Personal development and becoming the best you is all about growth..." that's about Accruent culture; could be Benefits? But it's more about company description. Benefits could include bonus eligibility, maybe also "Grow Without Limits" resources. However spec says only include Pay/Schedule/Benefits if posting actually states them. The posting does mention bonus eligibility, and also mentions personal development resources (Grow Without Limits). That could be considered benefits. We'll include a Benefits section with those points. - Pay: we have salary range. - Schedule: not mentioned. So we should not include Schedule section. We must not include sections with filler like "commensurate with experience". We have actual numbers for pay, so include Pay. We must not repeat duplicated content. We'll need to deduplicate. Let's extract substantive content: Intro (About the role): "Accruent is looking for a Senior UX Designer to lead end-to-end design across multiple B2B software products. You will research complex customer workflows, define product experiences, create and test solutions, and partner with Product and Engineering through implementation. This is a high-autonomy role for a systems thinker with strong design judgment, research experience, and interest in emerging AI-assisted and code-native design workflows." What You’ll Do (Responsibilities): List items: - Own UX work from discovery through post-launch iteration. - Plan and conduct user research. - Turn research and product data into clear findings and recommendations. - Design user flows, information architecture, interactions, and responsive interfaces. - Create and test AI-assisted and code-native prototypes. - Work within and contribute to Accruent’s design system and evolving UI pipeline. - Apply accessibility standards throughout the design process. - Evaluate AI-generated UI for usability, quality, responsiveness, and design-system alignment. - Partner with Product and Engineering to balance user needs, business goals, and technical constraints. - Present design decisions and facilitate productive critiques. - Review implemented work and collaborate with Engineering and QA to address gaps. - Manage work across multiple products and priorities. What We’re Looking For (Requirements): List: - A portfolio demonstrating research-informed design and strong design judgment. - Experience independently planning, conducting, and synthesizing UX research. - Strong interaction-design, information-architecture, and systems-thinking skills. - Experience designing complex B2B software workflows. - Experience designing responsive and accessible interfaces. - Experience working within and contributing to a design system. - Experience creating and testing prototypes. - Familiarity with AI-assisted or code-native prototyping. - Basic literacy with repositories and version-control concepts. - Strong communication and cross-functional collaboration skills. - High autonomy, curiosity, empathy, humility, and attention to detail. - Ability to build product, business, and domain expertise. Bonus Qualifications (Qualifications?): List: - Frontend coding experience. - Experience with AI-enabled UI pipelines, coded component libraries, design tokens, and/or Storybook. - Experience evaluating AI-generated interfaces. - Experience modernizing legacy software. - Experience in telecommunications, grocery retail, asset management, facilities, or real estate. - B2B SaaS experience. Why This Role: Paragraph: "You will help shape complex products used to manage physical assets, locations, and operational workflows. You will also help Accruent evolve its UX practice through stronger research, shared design systems, functional prototyping, and closer integration between design and implementation." Fortive Corporation Overview: Paragraph(s): "Fortive's essential technology makes the world safer and more productive. We accelerate transformation in high-impact fields like workplace safety, build environments, and healthcare. We are a global industrial technology innovator with a startup spirit. Our forward-looking companies lead the way in healthcare sterilization, industrial safety, predictive maintenance, and other mission-critical solutions. We're a force for progress, working alongside our customers and partners to solve challenges on a global scale, from workplace safety in the most demanding conditions to advanced technologies that help providers focus on exceptional patient care. We are a diverse team 10,000 strong, united by a dynamic, inclusive culture and energized by limitless learning and growth. We use the proven Fortive Business System (FBS) to accelerate our positive impact. At Fortive, we believe in you. We believe in your potential—your ability to learn, grow, and make a difference. At Fortive, we believe in us. We believe in the power of people working together to solve problems no one could solve alone. At Fortive, we believe in growth. We're honest about what's working and what isn't, and we never stop improving and innovating. Fortive: For you, for us, for growth." About Accruent: Paragraph(s): "Personal development and becoming the best you is all about growth and exploring new skills and opportunities – both in and out of the office. At Accruent, we call this Grow Without Limits, and we’re proud to offer each of our employees the resources, coaching and support necessary to achieve Growth Without Limits in their personal and professional lives. Explore where the path takes you. Accruent is a leading provider of solutions for unifying the built environment —spanning real estate, physical and digital assets, and the integrated technology systems that connect and control them. Accruent continues to set new expectations for how organizations can use data to transform how they manage their facilities and assets. With U.S. headquarters in Austin, Texas, Accruent serves over 5,000 customers in a wide range of industries in more than 100 countries worldwide." We have duplicate of that paragraph later; we need to include only once. Bonus or Equity: "This position is also eligible for bonus as part of the total compensation package." Pay Range: "The salary range for this position (in local currency) is 109,700.00 - 183,200.00" We also have duplicate of the Accruent paragraph and the Equal Opportunity boilerplate etc. We'll remove those. Now we need to decide which sections to output. Potential sections: - About the role (intro) - Responsibilities (What You’ll Do) - Requirements (What We’re Looking For) - Qualifications (Bonus Qualifications) - Benefits (Bonus or Equity + maybe Grow Without Limits? Actually Grow Without Limits is more about culture/benefits; we could include it in Benefits.) - Pay (salary range) We could also include a section "Company Overview" but not in list; but we could put Fortive Overview and About Accruent under maybe "About the company"? Not in allowed headings. The allowed headings are limited to those list. So we must fit content into those headings only. If we have content that doesn't fit, we could either omit or incorporate into existing sections if appropriate. The spec says: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exhaustive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely we should only use those headings. So we need to map all substantive content into those categories. We have content about Fortive and Accruent overview; where to put? Could be part of "About the role"? Not really. Could be part of "Benefits"? Not really. Could be part of "Qualifications"? Not. Maybe we can treat "About the role" as including company overview? But the spec says "About the role" for section headings e.g. About the role. Usually that section describes the role, not company. However we could include a brief description of the company within About the role if relevant. But we have a lot of detail about Fortive and Accruent; maybe we can put them under "About the role" as context. But that might be stretching. Alternatively, we could create a section "About the company" but not allowed. The spec 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 an exhaustive list; we could use other headings if needed? But they say "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect us to use those headings where appropriate. It doesn't forbid other headings, but to be safe we should stick to those. We have content that doesn't fit neatly: Fortive overview, Accruent overview, Why This Role (maybe could be part of About the role). Why This Role could be part of About the role as well. We could combine About the role, Why This Role, and company overview into About the role section. Responsibilities: clear. Requirements: clear. Qualifications: Bonus Qualifications. Benefits: Bonus eligibility + Grow Without Limits (personal development resources). Also maybe mention "resources, coaching and support necessary to achieve Growth Without Limits". That's a benefit. Pay: salary range. Schedule: none -> omit. Skills: we could maybe extract skills from Requirements and Qualifications