Staff Product Designer
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting.
We have sections: "The Impact You Will Have" (responsibilities). "What We Look For" (requirements/qualifications/skills). "About Ridgeline" (company info maybe not needed). "Compensation And Benefits" includes Pay and Benefits. No explicit schedule. There's no schedule info. So we should not include Schedule section.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, privacy statements, etc. Also remove application instructions, etc.
We need to preserve all substantive information. So we need to extract responsibilities list, requirements list, benefits list, pay info.
Let's parse.
From posting:
Intro paragraph: "Are you energized by designing complex, data-rich workflows...". That's marketing fluff; maybe part of About the role? Could be considered "About the role" prose.
Then: "As a Product Designer at Ridgeline, you’ll help modernize one of the most complex and fast-moving areas of investment management software: trading. You’ll partner closely with product managers, engineers, and customers to design experiences that help traders manage complex activity with greater clarity, speed, and accuracy. You’ll work across order management and electronic trading, from configurable trading workspaces and exception management to automated and AI-assisted workflows, while helping define how Ridgeline’s broader platform patterns come to life for traders. You’ll leverage modern AI tools like Claude, Cursor, and Claude Code to accelerate exploration, prototype experiences, evaluate edge cases, and improve product quality and design velocity across the entire design process. At Ridgeline, how we work matters as much as what we build. Ridgeliners act like owners, choose growth over comfort, and communicate with transparency. We assume positive intent, bias toward action, and bring solutions, not just problems. We celebrate wins, learn from setbacks, and thrive in a resilient, collaborative, high-performing culture. If this excites you, we’d love to meet you! You must be work authorized in the United States without the need for employer sponsorship."
That's a lot of prose; could be part of About the role.
Then "The Impact You Will Have" bullet list (actually lines). Let's extract each bullet:
- Reimagine workflows across order management and electronic trading, helping investment teams manage increasingly complex trading activity with clarity and efficiency
- Design intuitive workflows that help traders navigate complex decisions, surface actionable information, and manage exceptions and alerts with speed and accuracy
- Extend existing patterns and frameworks like Ridgeline’s configurable dashboards into trading, creating flexible workspaces that users can tailor to their workflows and priorities
- Build intelligent trading experiences that incorporate automated and deterministic workflows, AI-assisted guidance, and emerging AI capabilities
- Prototype and iterate quickly using tools like Claude, Cursor, and Claude Code to explore workflows, edge cases, and interaction patterns
- Translate concepts into polished, production-ready experiences in Figma with strong systems thinking and visual craft
- Collaborate closely with engineering to ensure designs are feasible, scalable, and thoughtfully implemented
- Contribute to Ridgeline’s design systems, interaction patterns, prompt libraries, and AI design practices
- Conduct customer conversations, lightweight research, and usability testing to rapidly validate ideas and improve workflows
- Mentor designers through feedback, collaboration, and thoughtful design critique
- Think creatively, own problems, seek solutions, and communicate clearly along the way
- Contribute to a collaborative environment deeply rooted in learning, teaching, and transparency
That's responsibilities.
Then "What We Look For" bullet list:
- 6+ years of experience designing and shipping successful digital product experiences
- Strong interaction design, systems thinking, visual design, and prototyping skills
- Experience designing complex workflows, data-intensive applications, or enterprise software platforms
- Active AI-native workflow experience using tools like Claude, Cursor, or Claude Code as part of daily product and design practice
- Ability to simplify technically complex systems into intuitive user experiences
- Experience collaborating closely with engineering teams to deliver thoughtful, scalable solutions
- Strong storytelling, communication, and presentation skills
- Ability to mentor and coach other designers while raising quality across a broader organization
- Experience gathering customer insights and translating findings into actionable product improvements
- Ability to manage ambiguity, prioritize effectively, and drive clarity across cross-functional teams
- Strong problem-solving skills and a high level of product ownership
- Willingness to learn about cutting-edge technologies while cultivating expertise in investment management workflows and order management systems
- Ability to communicate effectively with colleagues at all levels
- A shareable portfolio (attachment or online)
Then "Bonus Experience" bullet list:
- Experience in financial services, investment management, trading platforms, or other complex financial products
- Experience conducting user research and usability testing
- Proficiency with modern front-end technologies including React, JavaScript/TypeScript, and CSS
- Experience contributing to design systems and design-to-code workflows
- Experience designing AI-native product experiences including agentic behavior, transparency patterns, confidence cues, and user controls
We could combine "What We Look For" and "Bonus Experience" into Requirements/Qualifications/Skills sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which headings to use based on content.
We have About the role (intro). Responsibilities (Impact). Requirements (maybe "What We Look For" core). Qualifications could be similar; but we could split: Requirements (mandatory), Qualifications (maybe bonus?), Skills (maybe specific skills). However we must not create sections with filler. We need to include only sections with real specific content.
We could do:
- About the role (intro paragraph)
- Responsibilities (list)
- Requirements (list of mandatory qualifications)
- Skills (list of skills like interaction design, systems thinking, etc.) but that overlaps.
Better: Use Requirements for the "What We Look For" list (mandatory). Use Skills for the "Bonus Experience" list (optional/bonus). Or we could combine both into Requirements and not have Skills. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements (including both mandatory and bonus), Benefits, Pay. That's four sections.
But we need to use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can omit those not needed. So we can have About the role, Responsibilities, Requirements, Benefits, Pay. That's fine.
Now we need to extract Benefits and Pay.
From "Compensation And Benefits":
- typical starting salary range for new hires in this role: $168,000-$210,000. For select locations (SF Bay Area, CA, and NYC Metro Area): $184,500-$231,000.
- Final compensation amounts determined by multiple factors.
- As an employee at Ridgeline, you’ll have many opportunities for advancement...
- In addition to base salary, Ridgeline employees can participate in our Company Stock Plan subject to applicable Stock Option Agreement.
- We also offer rich benefits: unlimited vacation, educational and wellness reimbursements, and $0 cost employee insurance plans.
- Please check out our Careers page for a more comprehensive overview of our perks and benefits.
Thus Benefits: unlimited vacation, educational and wellness reimbursements, $0 cost employee insurance plans. Also Company Stock Plan (maybe considered benefit). We'll list those.
Pay: salary ranges as above.
Now we need to format.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce:
About the role
... intro paragraph(s) ...
Then Responsibilities
- ... each responsibility ...
Then Requirements
- ... each requirement (mandatory) ...
Then Benefits
- ... each benefit ...
Then Pay
... salary ranges ...
We must not include schedule.
We need to ensure we preserve all substantive information: include the note about work authorized in US without sponsorship? That is in intro paragraph after "If this excites you, we’d love to meet you! You must be work authorized in the United States without the need for employer sponsorship." That's substantive; we should keep it in About the role paragraph.
Also include note about "At Ridgeline, how we work matters as much as what we build..." etc. That's part of About the role.
Also include "As an employee at Ridgeline, you’ll have many opportunities for advancement in your career and can make a true impact on the product." That's part of Benefits? Actually it's more about career advancement; could be included in Benefits or About the role. But we already have Benefits section for tangible benefits; we could include career advancement as a benefit? Might be okay to keep in About the role or Benefits. Since it's not a typical benefit like vacation, but still substantive. We could include it in Benefits as a bullet: "Opportunities for career advancement and impact". However the instruction says preserve ALL substantive information; we can include it in Benefits list.
Also include "In addition to the base salary, Ridgeline employees can participate in our Company Stock Plan subject to the applicable Stock Option Agreement." That's a benefit.
Also include "We also offer rich benefits that reflect the kind of organization we want to be: one in which our employees feel valued and are inspired to bring their best selves to work." That's fluff; we can keep as part of Benefits intro paragraph.
Now we need to ensure we don't include boilerplate: EEO, privacy statements, etc. Remove lines about Ridgeline Candidate Privacy Policy, Applicant Privacy Statement, etc. Also remove "This posting is for an existing vacancy." Also remove "Please check out our Careers page for a more comprehensive overview of our perks and benefits." That's maybe okay to keep? It's a reference; but it's not substantive detail; could be considered boilerplate. Safer to remove.
Also remove "Ridgeline is proud to be a community-minded, discrimination-free equal opportunity workplace." That's EEO boilerplate; remove.
Also remove "Ridgeline processes the information you submit..." etc. Remove.
Now craft the HTML.
We need to be careful with escaping any HTML special characters; but plain text is fine.
Let's compose About the role paragraph(s). Could be multiple paragraphs but we can combine into one with line breaks? Better to keep as one
with sentences.
Intro: "Are you energized by designing complex, data-rich workflows that help investment firms make faster, smarter decisions? Do you enjoy simplifying deeply technical systems into intuitive, elegant experiences that customers trust every day? Are you excited to shape how AI, automation, and intelligent workflows transform modern investment management? If so, we invite you to be a part of our innovative team."
Then the role description: "As a Product Designer at Ridgeline, you’ll help modernize one of the most complex and fast-moving areas of investment management software: trading. You’ll partner closely with product managers, engineers, and customers to design experiences that help traders manage complex activity with greater clarity, speed, and accuracy. You’ll work across order management and electronic trading, from configurable trading workspaces and exception management to automated and AI-assisted workflows, while helping define how Ridgeline’s broader platform patterns come to life for traders. You’ll leverage modern AI tools like Claude, Cursor, and Claude Code to accelerate exploration, prototype experiences, evaluate edge cases, and improve product quality and design velocity across the
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, privacy statements, etc. Also remove application instructions, etc. We need to preserve all substantive information. So we need to extract responsibilities list, requirements list, benefits list, pay info. Let's parse. From posting: Intro paragraph: "Are you energized by designing complex, data-rich workflows...". That's marketing fluff; maybe part of About the role? Could be considered "About the role" prose. Then: "As a Product Designer at Ridgeline, you’ll help modernize one of the most complex and fast-moving areas of investment management software: trading. You’ll partner closely with product managers, engineers, and customers to design experiences that help traders manage complex activity with greater clarity, speed, and accuracy. You’ll work across order management and electronic trading, from configurable trading workspaces and exception management to automated and AI-assisted workflows, while helping define how Ridgeline’s broader platform patterns come to life for traders. You’ll leverage modern AI tools like Claude, Cursor, and Claude Code to accelerate exploration, prototype experiences, evaluate edge cases, and improve product quality and design velocity across the entire design process. At Ridgeline, how we work matters as much as what we build. Ridgeliners act like owners, choose growth over comfort, and communicate with transparency. We assume positive intent, bias toward action, and bring solutions, not just problems. We celebrate wins, learn from setbacks, and thrive in a resilient, collaborative, high-performing culture. If this excites you, we’d love to meet you! You must be work authorized in the United States without the need for employer sponsorship." That's a lot of prose; could be part of About the role. Then "The Impact You Will Have" bullet list (actually lines). Let's extract each bullet: - Reimagine workflows across order management and electronic trading, helping investment teams manage increasingly complex trading activity with clarity and efficiency - Design intuitive workflows that help traders navigate complex decisions, surface actionable information, and manage exceptions and alerts with speed and accuracy - Extend existing patterns and frameworks like Ridgeline’s configurable dashboards into trading, creating flexible workspaces that users can tailor to their workflows and priorities - Build intelligent trading experiences that incorporate automated and deterministic workflows, AI-assisted guidance, and emerging AI capabilities - Prototype and iterate quickly using tools like Claude, Cursor, and Claude Code to explore workflows, edge cases, and interaction patterns - Translate concepts into polished, production-ready experiences in Figma with strong systems thinking and visual craft - Collaborate closely with engineering to ensure designs are feasible, scalable, and thoughtfully implemented - Contribute to Ridgeline’s design systems, interaction patterns, prompt libraries, and AI design practices - Conduct customer conversations, lightweight research, and usability testing to rapidly validate ideas and improve workflows - Mentor designers through feedback, collaboration, and thoughtful design critique - Think creatively, own problems, seek solutions, and communicate clearly along the way - Contribute to a collaborative environment deeply rooted in learning, teaching, and transparency That's responsibilities. Then "What We Look For" bullet list: - 6+ years of experience designing and shipping successful digital product experiences - Strong interaction design, systems thinking, visual design, and prototyping skills - Experience designing complex workflows, data-intensive applications, or enterprise software platforms - Active AI-native workflow experience using tools like Claude, Cursor, or Claude Code as part of daily product and design practice - Ability to simplify technically complex systems into intuitive user experiences - Experience collaborating closely with engineering teams to deliver thoughtful, scalable solutions - Strong storytelling, communication, and presentation skills - Ability to mentor and coach other designers while raising quality across a broader organization - Experience gathering customer insights and translating findings into actionable product improvements - Ability to manage ambiguity, prioritize effectively, and drive clarity across cross-functional teams - Strong problem-solving skills and a high level of product ownership - Willingness to learn about cutting-edge technologies while cultivating expertise in investment management workflows and order management systems - Ability to communicate effectively with colleagues at all levels - A shareable portfolio (attachment or online) Then "Bonus Experience" bullet list: - Experience in financial services, investment management, trading platforms, or other complex financial products - Experience conducting user research and usability testing - Proficiency with modern front-end technologies including React, JavaScript/TypeScript, and CSS - Experience contributing to design systems and design-to-code workflows - Experience designing AI-native product experiences including agentic behavior, transparency patterns, confidence cues, and user controls We could combine "What We Look For" and "Bonus Experience" into Requirements/Qualifications/Skills sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which headings to use based on content. We have About the role (intro). Responsibilities (Impact). Requirements (maybe "What We Look For" core). Qualifications could be similar; but we could split: Requirements (mandatory), Qualifications (maybe bonus?), Skills (maybe specific skills). However we must not create sections with filler. We need to include only sections with real specific content. We could do: - About the role (intro paragraph) - Responsibilities (list) - Requirements (list of mandatory qualifications) - Skills (list of skills like interaction design, systems thinking, etc.) but that overlaps. Better: Use Requirements for the "What We Look For" list (mandatory). Use Skills for the "Bonus Experience" list (optional/bonus). Or we could combine both into Requirements and not have Skills. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements (including both mandatory and bonus), Benefits, Pay. That's four sections. But we need to use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can omit those not needed. So we can have About the role, Responsibilities, Requirements, Benefits, Pay. That's fine. Now we need to extract Benefits and Pay. From "Compensation And Benefits": - typical starting salary range for new hires in this role: $168,000-$210,000. For select locations (SF Bay Area, CA, and NYC Metro Area): $184,500-$231,000. - Final compensation amounts determined by multiple factors. - As an employee at Ridgeline, you’ll have many opportunities for advancement... - In addition to base salary, Ridgeline employees can participate in our Company Stock Plan subject to applicable Stock Option Agreement. - We also offer rich benefits: unlimited vacation, educational and wellness reimbursements, and $0 cost employee insurance plans. - Please check out our Careers page for a more comprehensive overview of our perks and benefits. Thus Benefits: unlimited vacation, educational and wellness reimbursements, $0 cost employee insurance plans. Also Company Stock Plan (maybe considered benefit). We'll list those. Pay: salary ranges as above. Now we need to format. We need to output only HTML fragment, no /, no markdown fences. We'll produce:
About the role
... intro paragraph(s) ...
ThenResponsibilities
- ... each responsibility ...
Requirements
- ... each requirement (mandatory) ...
Benefits
- ... each benefit ...
Pay
... salary ranges ...
We must not include schedule. We need to ensure we preserve all substantive information: include the note about work authorized in US without sponsorship? That is in intro paragraph after "If this excites you, we’d love to meet you! You must be work authorized in the United States without the need for employer sponsorship." That's substantive; we should keep it in About the role paragraph. Also include note about "At Ridgeline, how we work matters as much as what we build..." etc. That's part of About the role. Also include "As an employee at Ridgeline, you’ll have many opportunities for advancement in your career and can make a true impact on the product." That's part of Benefits? Actually it's more about career advancement; could be included in Benefits or About the role. But we already have Benefits section for tangible benefits; we could include career advancement as a benefit? Might be okay to keep in About the role or Benefits. Since it's not a typical benefit like vacation, but still substantive. We could include it in Benefits as a bullet: "Opportunities for career advancement and impact". However the instruction says preserve ALL substantive information; we can include it in Benefits list. Also include "In addition to the base salary, Ridgeline employees can participate in our Company Stock Plan subject to the applicable Stock Option Agreement." That's a benefit. Also include "We also offer rich benefits that reflect the kind of organization we want to be: one in which our employees feel valued and are inspired to bring their best selves to work." That's fluff; we can keep as part of Benefits intro paragraph. Now we need to ensure we don't include boilerplate: EEO, privacy statements, etc. Remove lines about Ridgeline Candidate Privacy Policy, Applicant Privacy Statement, etc. Also remove "This posting is for an existing vacancy." Also remove "Please check out our Careers page for a more comprehensive overview of our perks and benefits." That's maybe okay to keep? It's a reference; but it's not substantive detail; could be considered boilerplate. Safer to remove. Also remove "Ridgeline is proud to be a community-minded, discrimination-free equal opportunity workplace." That's EEO boilerplate; remove. Also remove "Ridgeline processes the information you submit..." etc. Remove. Now craft the HTML. We need to be careful with escaping any HTML special characters; but plain text is fine. Let's compose About the role paragraph(s). Could be multiple paragraphs but we can combine into onewith line breaks? Better to keep as one
with sentences. Intro: "Are you energized by designing complex, data-rich workflows that help investment firms make faster, smarter decisions? Do you enjoy simplifying deeply technical systems into intuitive, elegant experiences that customers trust every day? Are you excited to shape how AI, automation, and intelligent workflows transform modern investment management? If so, we invite you to be a part of our innovative team." Then the role description: "As a Product Designer at Ridgeline, you’ll help modernize one of the most complex and fast-moving areas of investment management software: trading. You’ll partner closely with product managers, engineers, and customers to design experiences that help traders manage complex activity with greater clarity, speed, and accuracy. You’ll work across order management and electronic trading, from configurable trading workspaces and exception management to automated and AI-assisted workflows, while helping define how Ridgeline’s broader platform patterns come to life for traders. You’ll leverage modern AI tools like Claude, Cursor, and Claude Code to accelerate exploration, prototype experiences, evaluate edge cases, and improve product quality and design velocity across the