Senior UX Designer

We need to output HTML fragment with sections: About the role? Actually we have sections: About The Organization, Major Responsibilities, Education & Experience, Knowledge, Skills, Abilities, Behaviors, Benefits. Also maybe "Job Summary And Qualifications" but we shouldn't repeat job title. We need headings:

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We have "About The Organization" -> could be "About the role"? Actually "About the role" is generic; but we have "About The Organization". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when appropriate. We need to include a section only when posting has real specific content. So we need to decide which sections we have content for. We have content about responsibilities (Major Responsibilities). That maps to "Responsibilities". We have qualifications (Education & Experience) -> "Qualifications". We have Knowledge, Skills, Abilities, Behaviors -> could be "Skills". Also maybe "Requirements" could be combined with qualifications? But we can put qualifications under "Qualifications". Skills under "Skills". Benefits under "Benefits". Pay and Schedule not present, so omit. About the role? We have "Job Summary And Qualifications" and "About The Organization". Could map to "About the role". Probably we can put a brief summary under About the role using the Job Summary And Qualifications paragraph (the first part). Let's extract: "Do you want to join an organization that invests in you as a Senior UX Designer? At HCA Healthcare, you come first. HCA Healthcare has committed up to $300 million in programs to support our incredible team members over the course of three years. Job Summary And Qualifications Position Summary The User Experience Center’s Clinical and Colleague Product Design Team is responsible for shaping complex healthcare software into intuitive, scalable, and technically sound products used across a nationwide ecosystem. Our work spans strategy, systems thinking, interaction design, and hands-on execution—often across multiple interrelated products with significant technical and organizational complexity. The Senior UX Designer is an experienced and capable individual contributor who operates at a high level of design craft and technical execution. This role takes ownership of the day-to-day design strategy and execution of several products within a given portfolio, including products with challenging constraints, immature processes, or complicated cross-functional team dynamics. Compared to a mid-level UX Designer, this role is expected to navigate ambiguity more effectively, influence outcomes more consistently, and elevate the quality of decision-making across teams. This designer brings deep expertise in human-centered design, strong systems thinking, and a practical understanding of modern front-end development. They work fluently with engineers, understand how design decisions translate into production, and execute with a level of rigor appropriate for large-scale, long-lived products. The Senior UX Designer leads by example, setting an aspirational bar for quality, communication, and technical depth for the product teams they support. Additionally, they may collaborate at the peer level to influence and shape internal standards within the Clinical and Colleague product design group." We can put that as About the role. About The Organization could be separate but we only have headings list; maybe we can treat About The Organization as part of About the role or we could add another heading like "About the organization" but not in list. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings. So we can combine About The Organization content into About the role or maybe we can omit it. But we need to preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. Could add a heading "About the organization" but not in the list; risk of violating instruction? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. implies examples, not exclusive list. So we can use other headings as needed, but better to follow examples. However we can incorporate About The Organization into About the role section, as it's about the organization. That would preserve info. Thus sections: - About the role (contains the initial motivational paragraph + Job Summary + About The Organization) - Responsibilities (Major Responsibilities) - Qualifications (Education & Experience) - Skills (Knowledge, Skills, Abilities, Behaviors) - Benefits (Benefits) We must not include Pay or Schedule. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to parse the responsibilities into list items. The responsibilities are bullet-like sentences under headings: Discovery & Testing, Design Execution, Design Systems, Technical fluency, Strategy & Culture, Influence, Communication, and Mentorship. Each has multiple sentences. We can make each bullet a

• containing the sentences (maybe multiple sentences). That's okay. Similarly for Qualifications: Education & Experience: we have bullet-like lines: Bachelor's degree ... required, 5+ years ... required. Could be list. Skills: Knowledge, Skills, Abilities, Behaviors: many bullet-like lines. We'll list each as
• . Benefits: list of benefits: Comprehensive benefits..., Wellbeing support..., Time away..., Savings..., Education support..., Additional benefits..., plus note about eligibility and recognition. We'll list each as
• . We must not include boilerplate like "Note: Eligibility for benefits may vary by location." That's still substantive? It's a note about eligibility; we can keep as a list item maybe. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The note about eligibility is not boilerplate; it's relevant. We'll keep. Also we have recognition statements: "HCA Healthcare has been recognized as one of the World's Most Ethical Companies® by the Ethisphere Institute more than ten times. In recent years, HCA Healthcare spent an estimated $3.7 billion in cost for the delivery of charitable care, uninsured discounts, and other uncompensated expenses. "Good people beget good people."- Dr. Thomas Frist, Sr. HCA Healthcare Co-Founder We are a family 270,000 dedicated professionals! Our Talent Acquisition team is reviewing applications for our Senior UX Designer opening. Qualified candidates will be contacted for interviews. Submit your resume today to join our community of caring! We are an equal opportunity employer. We do not discriminate on the basis of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status." These are boilerplate/EEO etc. Should be removed. So we strip those. Thus final HTML fragment:

  About the role

  ... (combined paragraphs)

  Responsibilities

  • Discovery & Testing: Facilitate discussions and gather key stakeholder feedback on live products. Plan and facilitate user research using qualitative and quantitative methodologies (e.g., user interviews, A/B testing, usability testing, surveys, live product analytics and more). Document and create discovery-related deliverables that clarify research findings, including but not limited to user journeys, personas, jobs-to-be-done, information architecture maps, and service blueprints.
  • Design Execution: Serve as lead product designer on multiple products within the portfolio. Partner with business stakeholders, product leaders, and engineering peers to design product solutions for mobile, digital, and responsive web applications that serve user goals and provide quantifiable business value. Execute design deliverables including but not limited to user flow diagrams, wireframes, visual designs, interactive prototypes, animation and motion prototypes, and more. Demonstrate sound judgment in applying the right design and technology solution to solve the problem at hand, knowing when to leverage collaborative sketching software, when to execute AI-assisted proof-of-concept prototypes, and when to produce fully refined and spec’d visual design artifacts for custom development. Balance momentum with quality, prioritizing durable, scalable solutions over short-term expediency. Translate complex requirements into clear, elegant experiences while accounting for technical constraints and long-term maintainability.
  • Design Systems: Thoughtfully apply, consider, challenge, and contribute to the HCA product design system, Neutron, working in partnership with Design Ops and front-end engineering. Apply system components thoughtfully while knowing when and how to extend patterns responsibly. Help improve system adoption and quality through clear usage, strong examples, and technically informed decision-making.
  • Technical fluency: Collaborate deeply with front-end engineers, with a good understanding of component-based development and modern frameworks. Design with awareness of implementation methods, such as React or Vue component models and utility-first styling approaches like Tailwind CSS. Leverage AI-assisted design and development tools to accelerate exploration, prototyping, and iteration, with the ability to adapt quickly as tooling evolves. Ensure design intent is accurately realized in production through close partnership with engineering and QA colleagues.
  • Strategy & Culture: In partnership with the Manager of Product Design, drive conversations with product and engineering partners to lead teams through ambiguity and help immature or evolving product teams arrive at more strategic, cohesive outcomes than they would reach independently. Foster a UX-centric culture through teaching, sharing, and coaching others on best practices, UX methodologies, and standardized UX toolsets. Present product design artifacts and strategies to stakeholders to solicit feedback, create consensus, and foster a culture of human-centered design thinking.
  • Influence, Communication, and Mentorship: Lead by example in design quality, communication, and presentation. Provide thoughtful feedback in group workshops and demonstrate growing skill in providing guidance to junior designers through direct critique, collaboration, and informal mentorship. Communicate design rationale clearly and persuasively to a wide range of stakeholders, including senior leaders, tying design decision-making to outcomes for the user, the product, and the business. Influence quality and outcomes through clarity of thinking, strong storytelling, and calm authority in complex discussions. Practice and adhere to the “Code of Conduct” philosophy and “Mission and Value Statement.” Perform other duties as assigned.

  Qualifications

  • Bachelor's degree in human computer interaction, user experience, product design, graphic design, or associated field required
  • 5+ years of experience in user experience or design-related role(s) required

  Skills

  • Demonstrated expertise in human-centered design principles and UX best practices.
  • Strong design craft across interaction, visual, and systems design.
  • Strong systems thinking with the ability to operate across multiple products.
  • Experience contributing to or working within a mature design system used in production environments.
  • High comfort with ambiguity and the ability to create clarity and direction.
  • Comfort operating independently while remaining highly collaborative.
  • Strong communication and presentation skills, including the ability to present in senior leader-facing discussions.
  • Ability to influence outcomes without formal authority.
  • Growth mindset and curiosity for evolving tools, workflows, and technologies.
  • Demonstrated skill using industry-leading UX tools—primarily but not limited to Figma’s suite of products including Figma Design, FigJam, and Figma Make to achieve desired outcomes.
  • Experience with additional AI-based vibe coding and code-authoring tools including Copilot, Cursor, Codex, Claude Code, Replit, v0, Lovable, etc. preferred
  • Prior experience collaborating closely with front-end engineering teams.
  • Working knowledge of modern front-end frameworks such as React, Vue, and Tailwind CSS, with an understanding of how design artifacts become production code in modern development workflows.

  Benefits