Senior 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. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Key sections: - Intro about company: maybe "About the role" or "About FloQast"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. The posting includes: - Intro paragraph about FloQast (company description). Could be "About the role"? Actually "About the role" would describe the role. The posting includes "What You'll Do" (responsibilities), "What You'll Bring" (requirements/qualifications/skills), "Why You'll Love Working With Us" (benefits/culture), "About FloQast" (company info), "Our Values", etc. We need to map to headings: About the role (maybe a brief summary of role?), Responsibilities (What You'll Do), Requirements (maybe "What You'll Bring" includes experience, etc.), Qualifications (maybe similar), Skills (maybe tools), Benefits (Benefits Package), Pay (base pay range), Schedule (maybe not present). There's no explicit schedule info. So we should not include Schedule unless present. We must not include sections with filler like "commensurate with experience". The pay range is given: $170,000-$230,000. Benefits described: Medical, Dental, Vision, Family Forming benefits, Life & Disability Insurance, Unlimited Vacation. Also mention "Compensation is not limited to base salary. FloQast values our Total Rewards, and offers a competitive and elaborate Benefits Package including, but not limited to, ...". So we can include Benefits and Pay sections. We need to preserve all substantive info; do not invent or summarize away detail. So we need to list responsibilities as bullet points from "What You'll Do". Requirements/Qualifications/Skills from "What You'll Bring". Possibly separate Requirements (experience) and Qualifications (education? not given) and Skills (tools). But we can combine if needed. However instruction: prefer a few substantive sections over many thin ones. So we could have sections: About the role (maybe a brief summary from intro?), Responsibilities, Requirements (covering experience, qualifications, skills), Benefits, Pay. Or separate Qualifications and Skills if content distinct. Let's extract: About the role: Could be a short paragraph summarizing the role: "As a Senior Product Designer, you will collaborate closely with Product, Engineering, and Design partners and own the end-to-end design and execution for major features and new offerings." That's from responsibilities. But maybe better to have About the role as a brief overview: The role is Senior Product Designer at FloQast, focusing on AI-powered Accounting Transformation Platform, designing human-centered tools, etc. We can craft from intro: "FloQast is at the forefront... Our vision is to create human-centered tools...". But that's more about company. However we can still include About the role as a short description: "Senior Product Designer responsible for end-to-end design of major features, collaborating with product, engineering, and design partners, driving design vision, ensuring quality, championing user empathy, executing with velocity, leading and mentoring." That's basically responsibilities. But we need to avoid duplication. Perhaps we can put About the role as a brief summary from the first paragraph before "What You'll Do". The posting starts with company description, then "At FloQast, design is a driving force...". Then "Come join us! Visa sponsorship is not available at this time". Then "What You'll Do". So we could treat the intro as About the role? Not exactly. But we can still include About the role as a short paragraph describing the role's purpose: "As a Senior Product Designer at FloQast, you will help shape the AI-powered Accounting Transformation Platform, designing human-centered tools that automate repetitive work, detect anomalies, and surface insights for accounting teams." That is derived from content. We must not invent details; we can paraphrase but must preserve substance. Paraphrasing is okay as long as we don't lose detail. We'll try to keep close to original. Responsibilities: list bullet points from "What You'll Do". Let's extract each bullet: - Define strategy: Own the end-to-end design strategy for mission-critical feature areas within the FloQast platform from conception through launch and post-launch iteration. - Design for AI: Translate complex AI capabilities and requirements into intuitive, trustworthy experiences that remove adoption barriers and help accounting teams realize value quickly. - Drive design vision and roadmap: Partner closely with Product Management, Engineering, and Leadership to define product strategy, contributing a deep, user-centered perspective that defines feature opportunities with exceptional attention to detail. - Elevate quality and consistency: Ensure your surfaces are polished, easy to use, visually delightful, and maintain a high standard of quality and consistency across our enterprise platform and design system. - Champion user empathy: Conduct and leverage qualitative and quantitative data (including user research, testing, and analytics) to ground design decisions, evaluate success, and advocate for the needs of accounting and finance professionals. - Execute with velocity: Confidently own design execution in Figma, delivering concept designs, high-fidelity prototypes, and clear specifications to engineering partners, while finding creative ways to ship high-quality work in a fast-paced environment. - Lead and mentor: Act as a design leader within the team, bringing clarity and alignment across projects, and offering mentorship to junior designers to foster a culture of design excellence. - You turn problems into opportunities and project that mindset to your peers. We'll put each as

. Requirements/Qualifications/Skills: from "What You'll Bring". Let's parse: - You've designed and delivered sophisticated software at scale. You have 5+ years of professional experience designing and shipping high-quality, complex SaaS or enterprise products. - You've proven your ability to lead the end-to-end design lifecycle for major initiatives, including the definition and execution of new features and products from 0-1. - You transform complexity into intuitive clarity. Your robust portfolio showcases exceptional visual design, interaction design, and strategic thinking, specifically demonstrating work on data-heavy applications, workflows, or sophisticated tooling. - You are an expert with modern design tools and AI-accelerated workflows. You have expert-level proficiency with design and prototyping tools, particularly Figma, experience contributing to robust design systems, and you use AI-powered tools (like Figma Make, ChatGPT/Gemini/Claude, and others) to accelerate knowledge, quality, collaboration, and delivery. - You are eager to design for the future of AI. You're familiar with the challenges and opportunities of designing AI-driven features, including defining appropriate user controls, managing trust, and translating complex models into clear user value. - You are an effective collaborator and advocate for your users. You possess strong strategic collaboration skills and can articulate your design rationale clearly and persuasively to product managers, engineers, and executive stakeholders. You ground and validate your design decisions by utilizing both qualitative user research (e.g., interviews, testing) and quantitative data (e.g., analytics). - You approach ambiguity with a growth mindset. You have the ability to thrive in a fast-paced, evolving environment and an aptitude for tackling ambiguous problem spaces while framing difficult challenges as opportunities. We could split into Requirements (experience, years, leading lifecycle), Qualifications (portfolio, visual/interaction design, strategic thinking), Skills (tools, Figma, AI-powered tools, collaboration, research, growth mindset). But to avoid many thin sections, we could combine into one "Requirements" section covering all. However instruction: prefer a few substantive sections over many thin ones. So maybe we have sections: About the role, Responsibilities, Requirements (covering experience, qualifications, skills), Benefits, Pay. We need to ensure we don't omit any substantive info. Let's list all points and include them in Requirements as bullet points. Benefits: from "Why You'll Love Working With Us" and later: "Compensation is not limited to base salary. FloQast values our Total Rewards, and offers a competitive and elaborate Benefits Package including, but not limited to, Medical, Dental, Vision, Family Forming benefits, Life & Disability Insurance, and Unlimited Vacation." Also mention "FloQast Product Design is a place where curious, thoughtful people come together to solve meaningful problems and grow through their work. You’ll have the freedom to explore ideas, take ownership, and create real impact with the support of teammates and managers who genuinely want you to succeed. We’re a collaborative team that values openness and initiative. Here, you can be scrappy, think boldly, and know that your voice truly matters." That's more culture but could be part of Benefits or maybe a separate section like "About the team". But we only have allowed headings; we could include that in Benefits as part of culture, but Benefits heading is for benefits. However we could still include that as part of Benefits? Might be stretching. Better to include a separate section? Not allowed headings besides those listed. Could we include a section like "About the team"? Not in list. So we might incorporate that into Benefits or maybe into About the role? But Benefits is for benefits; we could still include culture under Benefits? Might be okay but not ideal. However we could also add a section "Why You'll Love Working With Us" as a subsection under Benefits? But heading must be exactly one of the listed. Could we add a section "Benefits" and include both tangible benefits and culture points? The instruction: "Prefer a few substantive sections over many thin ones." So we can combine culture into Benefits. Pay: base pay range $170,000-$230,000. Also note "Compensation is not limited to base salary." We'll include that. Schedule: not present, so omit. Now we need to remove boilerplate: Visa sponsorship not available, EEO statements, legal, AI usage policy, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "Link to FloQast Recruiting AI Usage Policy". Also remove "FloQast reserves the right to amend, change, alter, and revise pay ranges and benefits offerings at any time." That's maybe boilerplate but it's substantive? It's a disclaimer; maybe we can drop as it's not essential detail? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. That line is a legal disclaimer about pay ranges; could be considered legal boilerplate. Safer to remove. Also remove "All applicants acknowledge that by applying to this position you understand that this specific pay range is contingent upon meeting the qualifications and requirements of the role, and for the successful completion of the interview selection and process. It is at the Company's discretion to determine what pay is provided to a candidate within the range associated with the role." That's also legal; remove. Remove "FloQast is regularly rated as a Best Place to Work! ..." That's maybe marketing but could be considered boilerplate? It's not legal but maybe still fluff. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Not explicitly to remove marketing fluff. But we might keep it as it's substantive about company reputation. However it's somewhat promotional; but we can keep if we want. However to be safe, maybe we can keep a brief mention of "FloQast is regularly rated as a Best Place to Work!" as part of Benefits or About the role? It's not essential but could be kept. However we need to preserve ALL substantive information; does that include marketing fluff? Probably yes, as it's substantive about company. But we can decide to keep it under Benefits or About the role. But we also have "About FloQast" paragraph later describing company mission, values, etc. That's substantive about company; we could include under About the