Senior UX/ Experience Designer
Prudential Financial · Fort Washington, PA · 3 wk ago
Art & Creative$89k–$147k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Skills), Benefits, Pay, Schedule? The posting includes salary range and benefits. No schedule info. So include Pay and Benefits sections. Also maybe Qualifications? The posting includes Skills And Experience and Competencies. Could combine into Requirements or Skills. Use headings: About the role (intro paragraph), Responsibilities (list), Skills And Experience (maybe as Requirements), Competencies? Could combine into Requirements. But we should not create thin sections. We have substantive content for About the role, Responsibilities, Skills And Experience, Competencies, Benefits, Pay. Could make sections: About the role, Responsibilities, Requirements (combining Skills And Experience and Competencies), Benefits, Pay. Ensure we don't repeat job title. No schedule.
We must remove boilerplate: EEO, accommodation, etc. Also remove "Job Classification Technology - Agile, Delivery, & Product" maybe part of heading? Not needed. Also remove "Prudential Long Term Care team is seeking..." that's part of About.
We need to preserve all substantive info. Let's extract About the role paragraph(s): The first paragraph: "The Prudential Long Term Care team is seeking an enthusiastic, creative, and experienced Senior Experience Designer to help shape, enhance, and scale PrudentialPeak®, our well-being and longevity portal. This role is embedded within the business team and will serve as a UX/product design lead and strategic thought partner, helping translate customer needs, business priorities, and cross-functional input into clear, accessible, and engaging digital experiences for policyholders and their loved ones. As a Senior Experience Designer, you will work closely with marketing, product, technology, operations, data, and compliance to deliver personalized experiences, enhanced capabilities, and deeper customer engagement for policyholders and their loved ones. You will play a key role in the continued evolution of PrudentialPeak®, helping the team connect customer insights, business goals, and design decisions across the end-to-end experience. In this role, you will bring a strong understanding of experience architecture, product strategy, and human-centered design to help advance the end-to-end experience for policyholders, support future growth of the site across other Prudential products, and explore opportunities to scale the experience to additional customer audiences. You will be expected to navigate ambiguity, frame design opportunities, influence cross-functional decisions, and move work forward in a fast-paced environment."
That's About.
Responsibilities: list bullet points under "Main Responsibilities". We'll extract each bullet.
Skills And Experience: list bullet points (starting with "6+ years...").
Competencies: list bullet points (starting with "For This Role, The Following Competencies Are Essential").
Tools: list bullet points? Might be considered part of Skills but we can include under Requirements maybe as a subsection? But we should not create thin sections. Could incorporate Tools into Skills And Experience as part of that list? The posting includes "Tools" separate. Could treat as part of Skills And Experience (maybe as a sublist). But we need to preserve all info. Could add a subsection under Requirements? But we must not create extra headings unless substantive. Could add a
- under Skills And Experience that includes tools as items. However the original separates them; we could keep them as part of Skills And Experience list.
Better: Have a section "Requirements" containing two sub-lists: "Skills and Experience" and "Tools". But that adds extra headings not allowed unless we keep as part of same section with maybe ? But instructions: use
- Translate customer needs, behavioral insights, business priorities, and operational constraints into practical design recommendations.
- Create intuitive information architecture, experience flows, prototypes, and digital touchpoints that support measurable customer and business outcomes.
- Identify patterns across customer journeys, service experiences, and stakeholder needs to recommend new product opportunities, experience improvements, and roadmap priorities.
- Apply human-centered design practices to define problems, generate concepts, test assumptions, and refine solutions that improve the Prudential Peak experience across key moments in the customer journey.
- Create and rapidly iterate wireframes, concepts, and interactive prototypes in accordance with user stories and journeys.
- Co-create practical, feasible design solutions with developers, marketing partners, product stakeholders, and business subject matter experts.
- Build clear, evidence-based recommendations for design improvements, articulating the customer need, business rationale, expected impact, and implementation considerations.
- Communicate design decisions with clear rationale grounded in customer insight, usability principles, accessibility standards, business objectives, and industry best practices.
- Plan and facilitate collaborative working sessions that help cross-functional teams align on challenges, priorities, concepts, and decisions.
- Analyze existing experiences to identify friction points, root causes, accessibility gaps, unmet customer needs, and opportunities for measurable improvement.
- 6+ years in Product Design, UX or equivalent design role, with a portfolio that demonstrates end-to-end digital product thinking, interaction design, user-centered problem solving, and measurable impact
- Agency and or corporate environment experience, preferably with work on a consumer product in the financial services, insurance, or similar sector
- Solid experience across core UX/product design methods, including research and user testing, information architecture and site mapping, journey and experience mapping, user flows, wireframing, prototyping, visual interface design, and workshop facilitation
- Experience working across multiple business units and cross-functional teams to frame complex business challenges as clear customer and experience problems, and identify practical paths forward
- Experience working both collaboratively and autonomously in a fast-paced cross-functional environment, including the ability to proactively identify needs, define next steps, and drive work forward with limited direction
- Strong understanding of information architecture, taxonomy, content strategy, plain language, and accessibility
- Experience working in lean and/or agile environments
- Basic front-end development integration and enablement knowledge
- Ability to translate design outputs, research insights, and recommended outcomes into compelling written narratives, presentations, and decision-making materials for stakeholders and leadership audiences of various backgrounds
- Collaboration and partnership—Build trusted relationships across marketing, product, technology, operations, compliance, and business teams; invite diverse perspectives; and help stakeholders move toward shared decisions.
- Continuous improvement—Bring progressive ideas, curiosity, and practical recommendations that improve customer experiences, team processes, and business outcomes.
- Growth Mindset—Actively seeking and embracing constructive feedback, integrating diverse perspectives to strengthen the work, and provide thoughtful, respectful feedback on the work of existing designs.
- Effective and decisive decision-making—Use insight, evidence, and sound judgment to guide tradeoffs, make recommendations, and keep work aligned to the intended customer and business outcomes.
- Leadership and communication—Communicate clearly and help teams understand the customer problem, design rationale, and recommended path forward.
- Challenge existing thinking appropriately—Listen, observe, ask timely questions, and use logic, customer insight, and reasoning to help teams evaluate options and choose the best solution for Prudential and its customers.
- Empathy and curiosity—Explore customer needs, behaviors, motivations, and pain points with openness and rigor, using what is learned to shape more useful, accessible, and relevant experiences.
- Tools: Figma, including component libraries, design systems, prototyping, collaboration, and developer handoff; UserZoom, UserTesting.com, or comparable research and usability testing platforms; Miro; Jira or comparable agile delivery tools used to document requirements, track design work, and collaborate with product and technology partners; PowerPoint
- Medical, dental, vision, life insurance, disability insurance
- Paid Time Off (PTO), and leave of absences, such as parental and military leave
- 401(k) plan with company match (up to 4%)
- Company-funded pension plan
- Wellness Programs including up to $1,600 a year for reimbursement of items purchased to support personal wellbeing needs
- Work/Life Resources to help support topics such as parenting, housing, senior care, finances, pets, legal matters, education, emotional and mental health, and career development
- Education Benefit to help finance traditional college enrollment toward obtaining an approved degree and many accredited certificate programs
- Employee Stock Purchase Plan: Shares can be purchased at 85% of the lower of two prices (Beginning or End of the purchase period)
- Eligibility to participate in a discretionary annual incentive program is subject to the rules governing the program, whereby an award, if any, depends on various factors including, without limitation, individual and organizational performance
for section headings only. So we cannot add extra headings inside a section. We could just combine all bullet points into one list under Requirements, preserving all items. That would lose the categorization but still preserve all info. That's acceptable? The instruction: "Prefer a few substantive sections over many thin ones." So we can combine Skills And Experience, Competencies, Tools into one Requirements section. That's okay.
Benefits: list items from "What We Offer You". Include bullet points.
Pay: include salary range.
Now produce HTML:
About the role
... (the paragraph)
Responsibilities
Requirements
Benefits
Pay
The salary range for this role is from $89,000.00 to $147,000.00. Specific pricing for the role may vary within the above range based on many factors including geographic location, candidate experience, and skills. Market competitive base salaries, with a yearly bonus potential at every level.
Check we didn't include schedule. Good. We removed boilerplate: EEO, accommodation, etc. Also removed "Prudential is required by state specific laws..." we kept that sentence as part of Pay? Actually we included that sentence in Pay paragraph. It's okay. We kept "Market competitive base salaries, with a yearly bonus potential at every level." from benefits? Actually that sentence appears after salary range. We included it. We also kept "To find out more about our Total Rewards package, visit Work Life Balance | Prudential Careers." That's a link; maybe considered boilerplate? It's a reference but not required. Might be considered navigation? It's a link to internal page. Could be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly those but could be considered navigation? It's a reference to more info. Might be okay to keep but maybe safer to remove as it's like a link. However it's not explicitly prohibited. I'd keep it? The instruction: "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is a navigation link to benefits page. Could be considered navigation. Safer to remove. Also "Some of the above benefits may not apply to part-time employees scheduled to work less than 20 hours per week." That's a clarification about benefits; could be kept? It's not boilerplate but it's a condition. Might be okay. Also "Prudential Financial, Inc. of the United States is not affiliated with Prudential plc..." that's legal boilerplate; remove. Also "Prudential is an equal opportunity employer..." remove. Also accommodation lines remove. Thus we should remove those lines. We kept the benefits list; we didn't include the part-time note. Could add it as a note but it's not essential. Might keep as aafter benefits? It's substantive? It's a condition. Could include as a
but it's not a list. Might be okay. However to keep sections thin, maybe omit. The instruction: preserve ALL