Lead UX Designer
Applied Systems · United States · 1 mo ago
RemoteRemoteArt & Creative$120k–$175k/yrFull-time
We need to output HTML fragment with sections: h3 headings for sections present with content. Must not repeat job title. Must not include Job ID etc. Must include only sections with real specific content. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Why You’ll Like Working on Team Applied", "How We’ll Support You", "Compensation Transparency", "Your Security Matters", "AI Utilization", "EEO Statement". Those are boilerplate. Keep substantive info: Team, Salary Range, Location, Opportunity for Impact (maybe a paragraph), What You’ll Do (list of duties), What We’re Looking For (requirements), Benefits (Medical, Dental, Vision Coverage, Holiday and Vacation Time, Health & Wellness Days, A Bonus Day for Your Birthday). Also maybe "Opportunity for Impact" is a paragraph.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. Salary range is given: $120,000-$175,000 USD. That's pay info, so we can include a Pay section. Benefits are listed. Schedule? Not mentioned. So no Schedule.
We need to use for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can choose headings that match content. The instruction: "use
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can choose headings that match content. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those exact headings or similar. Probably we should use those headings where appropriate. For this posting, we have sections: About the role (maybe "Opportunity for Impact" or team description). Responsibilities (What You’ll Do). Requirements/Qualifications/Skills (What We’re Looking For). Benefits. Pay.
We should not repeat job title. Use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all bullet points from "What You’ll Do" and "What We’re Looking For". Also include the paragraph about team and impact.
We need to remove duplicated lines. There's some duplication: "Experience working across multiple product domains or platforms." and later "Experience working across multiple product domains and stakeholder groups." Both are separate but similar; we keep both as they are distinct.
Also "Bonus points if you also have: Visionary thinking..." keep as bullet? It's a sentence; we can include as a list item under Requirements maybe.
We need to format lists.
Let's extract content.
First, header: "Job Description Team: Ivans UX Salary Range: $120,000-$175,000 USD Location: Remote US and Canada Opportunity for Impact Ivans, a division of Applied Systems, is where insurance technology gets reinvented, and we build it fast. Our cloud software and AI-powered solutions reach thousands of agencies and brokers worldwide, setting the pace for what modern insurance can do. We’re looking for a Lead UX Designer to join our UX team. This person will be designing complex, multi-step, high-volume workflows that insurance agents will use over and over. Success will result in removing time, friction, and errors. The Lead UX Designer will shape strategic direction for this major initiative, providing product vision and leadership to this critical initiative."
We can turn that into a paragraph under About the role or maybe "Opportunity for Impact". We'll create a section "About the role" with that paragraph.
Next, "What You’ll Do" with subheadings: Planning and Process, UX Research, Information Architecture, Interaction Design, Visual Design, Deploying, Facilitation, Storytelling. Each has bullet-like sentences. We need to output as list items under Responsibilities. Probably we can combine them into a single
with each bullet being the description under each subheading. Could also keep subheadings as but instruction only mentions for section headings; we can still use inside? Not prohibited but better to keep simple: just list each duty as
- . We'll preserve the content exactly.
Let's list each duty:
- Planning and Process: Defines UX strategies and frameworks for multi‑team initiatives. Leads planning sessions to align scope, timeline, and success metrics across disciplines. Ensures UX activities connect seamlessly to product and business roadmaps.
- UX Research: Shapes research agendas and ensures insights and tangible success metrics drive cross‑product decisions. Integrates data from multiple sources to inform strategic design direction. Guides research prioritization and alignment across teams or product lines.
- Information Architecture: Creates scalable IA frameworks and models that span multiple workflows and systems. Aligns content structures and naming conventions across teams for consistency. Validates navigation frameworks through iterative testing and stakeholder review.
- Interaction Design: Designs system‑level interaction models that unify patterns across products. Leads development of design frameworks that support reusable experiences. Mentors peers in designing for scalability, accessibility, and maintainability.
- Visual Design: Defines visual direction for complex experiences and ensures system alignment. Shapes evolution of visual standards within the design system. Drives collaboration with engineering and marketing to maintain brand coherence.
- Deploying: Oversees design delivery and implementation planning across product teams. Defines and enforces standards for QA, design fidelity, and usability validation. Collaborates with engineering leads to improve handoff tools and processes.
- Facilitation: Facilitates high‑impact design workshops and cross‑disciplinary planning sessions. Navigates competing priorities and builds alignment through structured discussion. Mentors others in effective facilitation and decision‑making practices.
- Storytelling: Delivers compelling design narratives that shape vision and inspire action. Translates design strategy into clear, audience‑specific communication. Coaches teams in developing storytelling skills for stakeholder alignment.
Next, "Key Performance Outcomes" maybe could be part of Responsibilities or separate section? It lists Execution, Insights, Impact. Could be considered as outcomes; but we could incorporate into Responsibilities or a separate section "Performance Outcomes". However instruction says prefer few substantive sections over many thin ones. Could merge into Responsibilities as additional bullet points. But they are outcomes not duties. Might be okay to include as a separate section "Key Performance Outcomes". But we need to decide if it's substantive enough. It has three bullet points each with a sentence. Could be included as a list under a heading "Key Performance Outcomes". That seems reasonable.
But we must not create sections with filler. This is real content.
Next, "What We’re Looking For" includes many bullet-like sentences. We'll list them as items under Requirements (or Qualifications). We'll need to preserve all.
Let's extract each line:
- B2B complex interaction design experience, crafting multi-step, high-volume workflows.
- 7+ years of experience in UX/product design, with at least 2 years in a leadership or strategic role.
- Bachelor’s or advanced degree in Design, HCI, or a related discipline — or equivalent senior experience.
- Proven success leading large-scale design efforts with measurable business and user impact.
- Strong portfolio demonstrating design leadership across complex, shipped digital products.
- Deep experience with user research, design systems, and interaction models.
- Expert-level skills in design and collaboration tools (Figma, Miro, etc.).
- Comfortable navigating ambiguity and leading in environments with shifting priorities.
- Mastery of UX design principles, systems thinking, interaction models, and product strategy alignment.
- Exceptional facilitation and communication skills; able to influence senior stakeholders and guide decision-making.
- Deep understanding of research methodologies and their strategic application.
- Ability to coach designers through complex problem spaces and grow team capability.
- Experience working across multiple product domains or platforms.
- Knowledge of technical constraints and development workflows; collaborates effectively with engineering.
- Experience working across multiple product domains and stakeholder groups.
- Bonus points if you also have: Visionary thinking with the ability to drive long-term design impact while delivering in the short term.
- Talent shows up in a lot of different ways, and we mean that. We welcome candidates from all backgrounds and experience levels, including military members and their spouses and those without a traditional degree or tech background.
- If this role speaks to you, apply.
The last two are more like encouragement; we may keep them as prose not list.
But we need to preserve ALL substantive information. So we should include those sentences as well, maybe as a paragraph after the list.
Now Benefits: "Medical, Dental, and Vision Coverage Holiday and Vacation Time Health & Wellness Days A Bonus Day for Your Birthday". We'll format as list.
Pay: Salary Range: $120,000-$175,000 USD. We'll put under Pay section as a paragraph.
Location: Remote US and Canada. Could be included in About the role paragraph or separate section Location. But we have no heading for Location in the list of allowed headings; but we could include it in About the role paragraph. The instruction says use those headings for sections; we can still include location in the About the role paragraph.
We must not include Job ID etc.
Now produce HTML fragment.
Structure:
About the role
...
Responsibilities
- ...
...
Key Performance Outcomes
- ...
...
Requirements
- ...
...
Talent shows up in a lot of different ways, and we mean that. We welcome candidates from all backgrounds and experience levels, including military members and their spouses and those without a traditional degree or tech background.
If this role speaks to you, apply.
Benefits
- Medical, Dental, and Vision Coverage
- Holiday and Vacation Time
- Health & Wellness Days
- A Bonus Day for Your Birthday
Pay
$120,000-$175,000 USD
We need to ensure we didn't miss any substantive info: The paragraph about "Opportunity for Impact" includes the description of Ivans etc. We'll include that in About the role paragraph.
Also we need to include the sentence "We’re looking for a Lead UX Designer to join our UX team." etc. Already in About the role.
Check for duplication: The "What You’ll Do" list includes each subheading with multiple sentences. We'll combine each subheading's sentences into one list item? Might lose some nuance but still preserve all info. Could also break each sentence into separate list items, but that may be too granular. The instruction: "Use - for any list of duties/requirements/benefits". It doesn't forbid having multiple sentences inside a li. So we can keep each subheading as a li with its sentences.
Now check for any other substantive content: "Opportunity for Impact" heading we turned into About the role. Good.
Now ensure we didn't include boilerplate: removed sections like "Why You’ll Like Working on Team Applied", "How We’ll Support You", "Compensation Transparency", "Your Security Matters", "AI Utilization", "EEO Statement". Good.
Now output only HTML fragment.
Let's craft the About the role paragraph:
"Team: Ivans UX. Salary Range: $120,000-$175,000 USD. Location: Remote US and Canada. Opportunity for Impact: Ivans, a division of Applied Systems, is where insurance technology gets reinvented, and we build it fast. Our cloud software and AI-powered solutions reach thousands of agencies and brokers worldwide, setting the pace for what modern insurance can do. We’re looking for
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all bullet points from "What You’ll Do" and "What We’re Looking For". Also include the paragraph about team and impact.
We need to remove duplicated lines. There's some duplication: "Experience working across multiple product domains or platforms." and later "Experience working across multiple product domains and stakeholder groups." Both are separate but similar; we keep both as they are distinct.
Also "Bonus points if you also have: Visionary thinking..." keep as bullet? It's a sentence; we can include as a list item under Requirements maybe.
We need to format lists.
Let's extract content.
First, header: "Job Description Team: Ivans UX Salary Range: $120,000-$175,000 USD Location: Remote US and Canada Opportunity for Impact Ivans, a division of Applied Systems, is where insurance technology gets reinvented, and we build it fast. Our cloud software and AI-powered solutions reach thousands of agencies and brokers worldwide, setting the pace for what modern insurance can do. We’re looking for a Lead UX Designer to join our UX team. This person will be designing complex, multi-step, high-volume workflows that insurance agents will use over and over. Success will result in removing time, friction, and errors. The Lead UX Designer will shape strategic direction for this major initiative, providing product vision and leadership to this critical initiative."
We can turn that into a paragraph under About the role or maybe "Opportunity for Impact". We'll create a section "About the role" with that paragraph.
Next, "What You’ll Do" with subheadings: Planning and Process, UX Research, Information Architecture, Interaction Design, Visual Design, Deploying, Facilitation, Storytelling. Each has bullet-like sentences. We need to output as list items under Responsibilities. Probably we can combine them into a single
with each bullet being the description under each subheading. Could also keep subheadings as but instruction only mentions for section headings; we can still use inside? Not prohibited but better to keep simple: just list each duty as
- . We'll preserve the content exactly.
Let's list each duty:
- Planning and Process: Defines UX strategies and frameworks for multi‑team initiatives. Leads planning sessions to align scope, timeline, and success metrics across disciplines. Ensures UX activities connect seamlessly to product and business roadmaps.
- UX Research: Shapes research agendas and ensures insights and tangible success metrics drive cross‑product decisions. Integrates data from multiple sources to inform strategic design direction. Guides research prioritization and alignment across teams or product lines.
- Information Architecture: Creates scalable IA frameworks and models that span multiple workflows and systems. Aligns content structures and naming conventions across teams for consistency. Validates navigation frameworks through iterative testing and stakeholder review.
- Interaction Design: Designs system‑level interaction models that unify patterns across products. Leads development of design frameworks that support reusable experiences. Mentors peers in designing for scalability, accessibility, and maintainability.
- Visual Design: Defines visual direction for complex experiences and ensures system alignment. Shapes evolution of visual standards within the design system. Drives collaboration with engineering and marketing to maintain brand coherence.
- Deploying: Oversees design delivery and implementation planning across product teams. Defines and enforces standards for QA, design fidelity, and usability validation. Collaborates with engineering leads to improve handoff tools and processes.
- Facilitation: Facilitates high‑impact design workshops and cross‑disciplinary planning sessions. Navigates competing priorities and builds alignment through structured discussion. Mentors others in effective facilitation and decision‑making practices.
- Storytelling: Delivers compelling design narratives that shape vision and inspire action. Translates design strategy into clear, audience‑specific communication. Coaches teams in developing storytelling skills for stakeholder alignment.
Next, "Key Performance Outcomes" maybe could be part of Responsibilities or separate section? It lists Execution, Insights, Impact. Could be considered as outcomes; but we could incorporate into Responsibilities or a separate section "Performance Outcomes". However instruction says prefer few substantive sections over many thin ones. Could merge into Responsibilities as additional bullet points. But they are outcomes not duties. Might be okay to include as a separate section "Key Performance Outcomes". But we need to decide if it's substantive enough. It has three bullet points each with a sentence. Could be included as a list under a heading "Key Performance Outcomes". That seems reasonable.
But we must not create sections with filler. This is real content.
Next, "What We’re Looking For" includes many bullet-like sentences. We'll list them as items under Requirements (or Qualifications). We'll need to preserve all.
Let's extract each line:
- B2B complex interaction design experience, crafting multi-step, high-volume workflows.
- 7+ years of experience in UX/product design, with at least 2 years in a leadership or strategic role.
- Bachelor’s or advanced degree in Design, HCI, or a related discipline — or equivalent senior experience.
- Proven success leading large-scale design efforts with measurable business and user impact.
- Strong portfolio demonstrating design leadership across complex, shipped digital products.
- Deep experience with user research, design systems, and interaction models.
- Expert-level skills in design and collaboration tools (Figma, Miro, etc.).
- Comfortable navigating ambiguity and leading in environments with shifting priorities.
- Mastery of UX design principles, systems thinking, interaction models, and product strategy alignment.
- Exceptional facilitation and communication skills; able to influence senior stakeholders and guide decision-making.
- Deep understanding of research methodologies and their strategic application.
- Ability to coach designers through complex problem spaces and grow team capability.
- Experience working across multiple product domains or platforms.
- Knowledge of technical constraints and development workflows; collaborates effectively with engineering.
- Experience working across multiple product domains and stakeholder groups.
- Bonus points if you also have: Visionary thinking with the ability to drive long-term design impact while delivering in the short term.
- Talent shows up in a lot of different ways, and we mean that. We welcome candidates from all backgrounds and experience levels, including military members and their spouses and those without a traditional degree or tech background.
- If this role speaks to you, apply.
The last two are more like encouragement; we may keep them as prose not list.
But we need to preserve ALL substantive information. So we should include those sentences as well, maybe as a paragraph after the list.
Now Benefits: "Medical, Dental, and Vision Coverage Holiday and Vacation Time Health & Wellness Days A Bonus Day for Your Birthday". We'll format as list.
Pay: Salary Range: $120,000-$175,000 USD. We'll put under Pay section as a paragraph.
Location: Remote US and Canada. Could be included in About the role paragraph or separate section Location. But we have no heading for Location in the list of allowed headings; but we could include it in About the role paragraph. The instruction says use those headings for sections; we can still include location in the About the role paragraph.
We must not include Job ID etc.
Now produce HTML fragment.
Structure:
About the role
...
Responsibilities
- ...
...
Key Performance Outcomes
- ...
...
Requirements
- ...
...
Talent shows up in a lot of different ways, and we mean that. We welcome candidates from all backgrounds and experience levels, including military members and their spouses and those without a traditional degree or tech background.
If this role speaks to you, apply.
Benefits
- Medical, Dental, and Vision Coverage
- Holiday and Vacation Time
- Health & Wellness Days
- A Bonus Day for Your Birthday
Pay
$120,000-$175,000 USD
We need to ensure we didn't miss any substantive info: The paragraph about "Opportunity for Impact" includes the description of Ivans etc. We'll include that in About the role paragraph.
Also we need to include the sentence "We’re looking for a Lead UX Designer to join our UX team." etc. Already in About the role.
Check for duplication: The "What You’ll Do" list includes each subheading with multiple sentences. We'll combine each subheading's sentences into one list item? Might lose some nuance but still preserve all info. Could also break each sentence into separate list items, but that may be too granular. The instruction: "Use - for any list of duties/requirements/benefits". It doesn't forbid having multiple sentences inside a li. So we can keep each subheading as a li with its sentences.
Now check for any other substantive content: "Opportunity for Impact" heading we turned into About the role. Good.
Now ensure we didn't include boilerplate: removed sections like "Why You’ll Like Working on Team Applied", "How We’ll Support You", "Compensation Transparency", "Your Security Matters", "AI Utilization", "EEO Statement". Good.
Now output only HTML fragment.
Let's craft the About the role paragraph:
"Team: Ivans UX. Salary Range: $120,000-$175,000 USD. Location: Remote US and Canada. Opportunity for Impact: Ivans, a division of Applied Systems, is where insurance technology gets reinvented, and we build it fast. Our cloud software and AI-powered solutions reach thousands of agencies and brokers worldwide, setting the pace for what modern insurance can do. We’re looking for
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all bullet points from "What You’ll Do" and "What We’re Looking For". Also include the paragraph about team and impact. We need to remove duplicated lines. There's some duplication: "Experience working across multiple product domains or platforms." and later "Experience working across multiple product domains and stakeholder groups." Both are separate but similar; we keep both as they are distinct. Also "Bonus points if you also have: Visionary thinking..." keep as bullet? It's a sentence; we can include as a list item under Requirements maybe. We need to format lists. Let's extract content. First, header: "Job Description Team: Ivans UX Salary Range: $120,000-$175,000 USD Location: Remote US and Canada Opportunity for Impact Ivans, a division of Applied Systems, is where insurance technology gets reinvented, and we build it fast. Our cloud software and AI-powered solutions reach thousands of agencies and brokers worldwide, setting the pace for what modern insurance can do. We’re looking for a Lead UX Designer to join our UX team. This person will be designing complex, multi-step, high-volume workflows that insurance agents will use over and over. Success will result in removing time, friction, and errors. The Lead UX Designer will shape strategic direction for this major initiative, providing product vision and leadership to this critical initiative." We can turn that into a paragraph under About the role or maybe "Opportunity for Impact". We'll create a section "About the role" with that paragraph. Next, "What You’ll Do" with subheadings: Planning and Process, UX Research, Information Architecture, Interaction Design, Visual Design, Deploying, Facilitation, Storytelling. Each has bullet-like sentences. We need to output as list items under Responsibilities. Probably we can combine them into a single
- with each bullet being the description under each subheading. Could also keep subheadings as
- . We'll preserve the content exactly.
Let's list each duty:
- Planning and Process: Defines UX strategies and frameworks for multi‑team initiatives. Leads planning sessions to align scope, timeline, and success metrics across disciplines. Ensures UX activities connect seamlessly to product and business roadmaps.
- UX Research: Shapes research agendas and ensures insights and tangible success metrics drive cross‑product decisions. Integrates data from multiple sources to inform strategic design direction. Guides research prioritization and alignment across teams or product lines.
- Information Architecture: Creates scalable IA frameworks and models that span multiple workflows and systems. Aligns content structures and naming conventions across teams for consistency. Validates navigation frameworks through iterative testing and stakeholder review.
- Interaction Design: Designs system‑level interaction models that unify patterns across products. Leads development of design frameworks that support reusable experiences. Mentors peers in designing for scalability, accessibility, and maintainability.
- Visual Design: Defines visual direction for complex experiences and ensures system alignment. Shapes evolution of visual standards within the design system. Drives collaboration with engineering and marketing to maintain brand coherence.
- Deploying: Oversees design delivery and implementation planning across product teams. Defines and enforces standards for QA, design fidelity, and usability validation. Collaborates with engineering leads to improve handoff tools and processes.
- Facilitation: Facilitates high‑impact design workshops and cross‑disciplinary planning sessions. Navigates competing priorities and builds alignment through structured discussion. Mentors others in effective facilitation and decision‑making practices.
- Storytelling: Delivers compelling design narratives that shape vision and inspire action. Translates design strategy into clear, audience‑specific communication. Coaches teams in developing storytelling skills for stakeholder alignment.
Next, "Key Performance Outcomes" maybe could be part of Responsibilities or separate section? It lists Execution, Insights, Impact. Could be considered as outcomes; but we could incorporate into Responsibilities or a separate section "Performance Outcomes". However instruction says prefer few substantive sections over many thin ones. Could merge into Responsibilities as additional bullet points. But they are outcomes not duties. Might be okay to include as a separate section "Key Performance Outcomes". But we need to decide if it's substantive enough. It has three bullet points each with a sentence. Could be included as a list under a heading "Key Performance Outcomes". That seems reasonable.
But we must not create sections with filler. This is real content.
Next, "What We’re Looking For" includes many bullet-like sentences. We'll list them as items under Requirements (or Qualifications). We'll need to preserve all.
Let's extract each line:
- B2B complex interaction design experience, crafting multi-step, high-volume workflows.
- 7+ years of experience in UX/product design, with at least 2 years in a leadership or strategic role.
- Bachelor’s or advanced degree in Design, HCI, or a related discipline — or equivalent senior experience.
- Proven success leading large-scale design efforts with measurable business and user impact.
- Strong portfolio demonstrating design leadership across complex, shipped digital products.
- Deep experience with user research, design systems, and interaction models.
- Expert-level skills in design and collaboration tools (Figma, Miro, etc.).
- Comfortable navigating ambiguity and leading in environments with shifting priorities.
- Mastery of UX design principles, systems thinking, interaction models, and product strategy alignment.
- Exceptional facilitation and communication skills; able to influence senior stakeholders and guide decision-making.
- Deep understanding of research methodologies and their strategic application.
- Ability to coach designers through complex problem spaces and grow team capability.
- Experience working across multiple product domains or platforms.
- Knowledge of technical constraints and development workflows; collaborates effectively with engineering.
- Experience working across multiple product domains and stakeholder groups.
- Bonus points if you also have: Visionary thinking with the ability to drive long-term design impact while delivering in the short term.
- Talent shows up in a lot of different ways, and we mean that. We welcome candidates from all backgrounds and experience levels, including military members and their spouses and those without a traditional degree or tech background.
- If this role speaks to you, apply.
The last two are more like encouragement; we may keep them as prose not list.
But we need to preserve ALL substantive information. So we should include those sentences as well, maybe as a paragraph after the list.
Now Benefits: "Medical, Dental, and Vision Coverage Holiday and Vacation Time Health & Wellness Days A Bonus Day for Your Birthday". We'll format as list.
Pay: Salary Range: $120,000-$175,000 USD. We'll put under Pay section as a paragraph.
Location: Remote US and Canada. Could be included in About the role paragraph or separate section Location. But we have no heading for Location in the list of allowed headings; but we could include it in About the role paragraph. The instruction says use those headings for sections; we can still include location in the About the role paragraph.
We must not include Job ID etc.
Now produce HTML fragment.
Structure:
About the role
...
Responsibilities
- ... ...
Key Performance Outcomes
- ... ...
Requirements
- ... ...
Talent shows up in a lot of different ways, and we mean that. We welcome candidates from all backgrounds and experience levels, including military members and their spouses and those without a traditional degree or tech background.
If this role speaks to you, apply.
Benefits
- Medical, Dental, and Vision Coverage
- Holiday and Vacation Time
- Health & Wellness Days
- A Bonus Day for Your Birthday
Pay
$120,000-$175,000 USD
We need to ensure we didn't miss any substantive info: The paragraph about "Opportunity for Impact" includes the description of Ivans etc. We'll include that in About the role paragraph. Also we need to include the sentence "We’re looking for a Lead UX Designer to join our UX team." etc. Already in About the role. Check for duplication: The "What You’ll Do" list includes each subheading with multiple sentences. We'll combine each subheading's sentences into one list item? Might lose some nuance but still preserve all info. Could also break each sentence into separate list items, but that may be too granular. The instruction: "Use- for any list of duties/requirements/benefits". It doesn't forbid having multiple sentences inside a li. So we can keep each subheading as a li with its sentences. Now check for any other substantive content: "Opportunity for Impact" heading we turned into About the role. Good. Now ensure we didn't include boilerplate: removed sections like "Why You’ll Like Working on Team Applied", "How We’ll Support You", "Compensation Transparency", "Your Security Matters", "AI Utilization", "EEO Statement". Good. Now output only HTML fragment. Let's craft the About the role paragraph: "Team: Ivans UX. Salary Range: $120,000-$175,000 USD. Location: Remote US and Canada. Opportunity for Impact: Ivans, a division of Applied Systems, is where insurance technology gets reinvented, and we build it fast. Our cloud software and AI-powered solutions reach thousands of agencies and brokers worldwide, setting the pace for what modern insurance can do. We’re looking for