Product Designer

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate etc. We need to parse the posting. Content: - Who We Are: description of company. Could be "About the role"? Actually "Who We Are" is about company. Could be "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. We have sections: Who We Are (company overview) maybe "About the role"? But "About the role" would be description of role. We have "Who We Want" describing role. Also "What You'll Do" responsibilities. "Qualifications" list. "How We Work" maybe about work environment. "Why This Role Is Interesting" maybe about role interest. "The Perks of Working With Us" benefits. "Your Arrive Experience" culture. Also "Notice" boilerplate to remove. We need to include sections only when there is real specific content. So we can have: - About the role: maybe combine Who We Are and Who We Want? But we need to avoid duplication. Perhaps "About the role" can be a short paragraph describing the role: mid-level Product Designer, working on proprietary transportation management platform, etc. We have that in Who We Want and What You'll Do. Could put that as About the role. - Responsibilities: from What You'll Do bullet list. - Requirements: maybe from Qualifications list (3-5 years experience etc). Could be Requirements. - Qualifications: maybe separate? But we have Qualifications heading already. Could treat Qualifications as the list of qualifications (including bonus). The instruction says use headings for Qualifications, Skills, etc. We have both Qualifications and Skills maybe overlapping. We could put Qualifications as the list of required experience, and Skills as specific skills (Figma, design system, interaction design, communication, agile, AI tools). But we can also combine. We need to avoid filler like "commensurate with experience". Not present. We need Benefits: from The Perks of Working With Us list. Pay: not mentioned, so omit. Schedule: not mentioned, omit. We need to ensure we don't create empty sections. Thus output HTML with sections:

About the role

...

maybe. Then

Responsibilities

• ...

Then

Requirements

• ...

Then

Qualifications

• ...

maybe. Then

Skills

• ...

maybe. Then

Benefits

• ...

We must preserve all substantive information. Let's extract. From Who We Are: "Arrive Logistics is a leading transportation and technology company in North America with plans to grow significantly year over year. Our success is a testament to our remarkable team and what we’re building together. We’re committed to providing employees with a meaningful work experience and have established an award-winning culture that supports personal and career development in a fun, casual, and collaborative environment." From Who We Want: "Arrive Logistics is looking for a mid-level Product Designer to join our product design team. You’ll work on our proprietary transportation management platform, the software our reps and operations teams use to move freight every day. Our users live in this tool for eight hours a day under real time pressure. Screens are dense, workflows are complex, and a confusing state costs real money, both for our business and the user. The design problems here are about speed to completion, information hierarchy in high-density interfaces, and reducing friction from tasks people repeat thousands of times a week." From What You'll Do: bullet list: - Contribute to and own designs for features and flows within your sprint team’s area, from early framing through shipped UI - Partner closely with your product manager and engineers to define requirements, explore solutions, and rapidly iterate based on feedback - Leverage problem discovery and user research to help sharpen problems before jumping to solutions - Spend real time with our users, who are onsite, generous with their opinions, and turn what you learn into design decisions you can act on and share - Conduct and synthesize lightweight research (interviews, usability tests, feedback sessions, problem discovery) - Design wireframes, prototypes, and high-fidelity mockups in Figma, Miro and similar tools - Contribute components and patterns to our design system and keep your work consistent with it - Present work and rationale clearly to your team and to the stakeholders - Take part in critique with the wider design team, both giving and receiving Qualifications list: - 3-5 years of experience as a product or UX designer, ideally on a B2B or SaaS product - A portfolio that shows how you think, not just final screens. We want to see the options you considered and why you landed where you did - Strong Figma skills - Comfort working within an established design system and contributing back to it - Solid interaction design and usability fundamentals, especially in data-dense or workflow-heavy interfaces - Ability to communicate design decisions clearly to both technical and non-technical audiences - Experience in an agile-like, sprint-based product development environment - Experience using AI tools in your process, whether that's Figma Make, Claude, or something you've found on your own - Bonus: experience designing for logistics, supply chain, or other complex operational tools How We Work: "We’re a hybrid team, working alongside designers and partners in our other offices. You’ll own your work, with regular critique and support from the wider design team. We’d rather you bring a rough idea early than a polished one late." Why This Role Is Interesting: paragraph about freight, expert users, platform built in-house, design system mature but expanding. The Perks of Working With Us: list: - Take advantage of our comprehensive benefits package, including medical, dental, vision, life, disability, and supplemental coverage. - Invest in your future with our matching 401(k) program. - Build relationships and find your home at Arrive through our Employee Resource Groups. - Enjoy office wide engagement activities, team events, happy hours and more! - Leave the suit and tie at home; our dress code is casual. - Work in the booming city of Austin, TX – we are in a convenient location close to the airport and downtown. - Park your car for free on site! - Start your morning with a specialty drink from our fully stocked coffee bar, Broker’s Brew. - Sweat it out with the team at our onsite gym. - Maximize your wellness with free counseling sessions through our Employee Assistance Program - Take time to manage your physical and mental health - we offer company paid holidays, paid vacation time and wellness days. - Receive 100% paid parental leave when you become a new parent. - Get paid to work with your friends through our Referral Program! - Get relocation assistance! If you are not local to the area, we offer relocation packages. Your Arrive Experience: paragraph about award-winning culture, recognitions, employee-founded resource groups. Notice boilerplate to remove. We need to map to headings. About the role: Could combine Who We Are and Who We Want? But maybe better: About the role: description of role and team. Use paragraph(s) from Who We Want and maybe How We Work? But How We Work is about work style. Responsibilities: What You'll Do list. Requirements: maybe the Qualifications list (the required experience). But we also have Qualifications heading; maybe Requirements = the bullet list of qualifications (3-5 years experience etc). Qualifications could be the same? Might be redundant. Could treat Requirements as the list of mandatory qualifications, and Qualifications as the list of desired/bonus? But we have both headings; we need to avoid filler. Could put Requirements as the list of required qualifications (3-5 years experience, portfolio, Figma skills, design system comfort, interaction design, communication, agile experience, AI tools). Qualifications could be the bonus: experience designing for logistics, supply chain, or other complex operational tools. But that seems thin. Alternatively, we could omit Qualifications heading and just have Requirements and Skills. But instruction says we can include sections only when posting has real specific content. We have content for Skills: strong Figma skills, comfort with design system, interaction design fundamentals, communication ability, agile experience, AI tools experience. That's basically same as qualifications. Might be overlapping. Better to follow typical structure: About the role (description), Responsibilities (What You'll Do), Requirements (Qualifications list), Benefits (Perks). Possibly also Skills (maybe separate list of technical skills). But we can combine Requirements and Skills into one section? But headings are prescribed; we can still include Skills if we have content. Let's extract Skills: from Qualifications list we have: Strong Figma skills, Comfort working within an established design system and contributing back to it, Solid interaction design and usability fundamentals, Ability to communicate design decisions clearly, Experience in an agile-like sprint-based product development environment, Experience using AI tools in your process. Those are skills. Requirements could be the years of experience and portfolio etc. But those are also qualifications. Maybe we treat Requirements as the mandatory experience (3-5 years, portfolio) and Qualifications as the skillset list. But the instruction says use headings for Requirements, Qualifications, Skills. So we can have three sections: Requirements (years experience, portfolio), Qualifications (maybe the list of competencies like Figma, design system, interaction design, communication, agile, AI), Skills (maybe the bonus? Or we could put bonus under Qualifications). However we need to avoid filler. Let's decide: - About the role: paragraph describing role and company (combine Who We Are and Who We Want maybe). We'll write a concise paragraph. - Responsibilities: ul list from What You'll Do. - Requirements: li list for "3-5 years of experience as a product or UX designer, ideally on a B2B or SaaS product" and "A portfolio that shows how you think, not just final screens. We want to see the options you considered and why you landed where you did". Could also include "Experience in an agile-like, sprint-based product development environment" and "Experience using AI tools in your process" but those are more skills. We'll keep them in Skills. - Qualifications: maybe list of "Strong Figma skills", "Comfort working within an established design system and contributing back to it", "Solid interaction design and usability fundamentals, especially in data-dense or workflow-heavy interfaces", "Ability to communicate design decisions clearly to both technical and non-technical audiences". That seems like qualifications. - Skills: maybe list of "Experience in an agile-like, sprint-based product development environment", "Experience using AI tools in your process", "Bonus: experience designing for logistics, supply chain, or other complex operational tools". But bonus is not a skill per se but could be under Skills. - Benefits: ul list from The Perks of Working With Us. We must not include sections with filler like "commensurate with experience". Not present. Check each section for substantive content. About the role: we need to avoid repeating job title. We'll write a paragraph: "Arrive Logistics is a leading transportation and technology company in North America with plans to grow significantly year over year. They are seeking a mid-level Product Designer to join their product design team, working on a proprietary transportation management platform used by reps and operations teams to move freight. The role involves tackling dense screens, complex workflows, and real-time pressure to improve speed, information hierarchy, and reduce repetitive task friction." That captures Who We Are and Who We Want. Responsibilities: list each bullet.