Sr. Staff Product & Visual Designer, Technology Workflows

We need to output HTML fragment with sections: About the role? Actually the posting includes Company Description, Job Description, What You Get To Do In The Role, Qualifications (Preferred Qualifications, Basic Qualifications), Pay info, Benefits, maybe Work Personas? But we must only include sections when posting has real specific content. We must not repeat job title. No headings for Job ID etc. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to these headings appropriately. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which of those are appropriate based on content. We must not create sections with filler. So we need to decide which sections have real content. We have: - Company Description: could be "About the role"? Actually "About the role" maybe about the role description. But we have "Job Description" which includes overview of role. Could map to "About the role" or "Responsibilities". The "What You Get To Do In The Role" is responsibilities. So we could have:

About the role

with company description? Or maybe "About the role" includes company description and role overview. But we need to avoid duplication. Better: Use "About the role" for company description and high-level role summary. Use "Responsibilities" for the bullet list of what you get to do. Use "Qualifications" for both preferred and basic qualifications (maybe separate subheadings? But we only have h3 headings; we could have one Qualifications section containing both preferred and basic qualifications as paragraphs/lists). Use "Benefits" for benefits info (health plans, 401k, etc). Use "Pay" for salary range. Use "Skills" maybe not needed; we could omit if no specific skills list beyond qualifications. The posting includes qualifications that include skills; but we could put them under Qualifications. The instruction says we can use Skills heading if there is real specific content for skills. We could include a Skills heading listing technical skills: React, modern CSS/SCSS, etc. But we already have qualifications covering that. Might be redundant. Safer to include only sections with clear content: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly Schedule? Not provided. So omit Schedule. We must not include boilerplate like EEO, accommodations, export control, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from company description, job description, responsibilities, qualifications, pay, benefits. We need to format lists with

• . For prose use

  . We need to ensure we don't repeat job title. Let's extract content: Company Description paragraph: "It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started. Join us to put AI to work for people." Job Description paragraph: "At ServiceNow, we embrace representation in and from all professional and personal backgrounds and cultures. This diversity inspires passion and creativity among our teams and propels innovation in our products. We are looking for a Senior Staff Product Designer (Design Technology & Craft Lead) to serve as an elite, hands-on craft visionary bridging advanced visual design, fluid motion choreography, and front-end code. This role sits within our Technology Workflows organization, directly shaping flagship, next-generation AI platforms, and design frameworks. This is not a traditional systems-architecture or wireframing UX role. We are seeking an exceptional practitioner who blurs the boundary between high-end digital aesthetics and front-end engineering. You will be the team’s creative technical anchor: setting the benchmark for visual depth, kinetic responsiveness, and production-grade prototypes. Working shoulder to shoulder with product designers, design systems teams, and engineering peers, you will define and codify how our AI experiences look, move, and respond across complex enterprise workflows. You must be obsessed with craft excellence, unapologetic about visual polish, and driven to turn complex technical interactions into fluid, responsive, consumer-grade software." What You Get To Do In The Role: bullet list items (each starts with bold heading). We need to preserve each bullet's content. List: - Build Reference-Grade Prototypes: Develop high-fidelity, interactive code prototypes and sandboxes (React, modern CSS/Tokens, WebGL/Canvas) that test and prove out next-generation UX for AINPX and Lux before production handoff. - Pioneer AI Kinetic Systems: Codify motion design patterns, timing curves, elevation models, and dynamic state transitions (such as AI thinking, streaming, settling, and ambient feedback) into production-? Actually text: "such as AI thinking, streaming, settling, and ambient feedback") into production-ready specifications. - Partner with Design Systems: Collaborate directly with centralized Design Systems engineering teams to translate motion guidelines, visual tokens, and micro-interactions into scalable components used across ServiceNow workflows. - Elevate Team Craft through Direct Pairing: Champion a player-coach culture by embedding directly with product designers on critical paths. Pair-design interactions, run code-backed workshops, and actively raise the visual and kinetic craft floor of the broader team. - Bridge Design and Engineering: Serve as the definitive technical translator between design vision and front-end execution, ensuring that intended motion physics and pixel-perfect visual nuance survive into production code. - Thrive in an AI-Native Workflow: Rapidly experiment with code-backed AI design tools, algorithmic prototyping, and generative interaction paradigms to accelerate design cycles and unlock new interface capabilities. Qualifications: Preferred Qualifications and Basic Qualifications sections. Preferred Qualifications bullet list (looks like a paragraph with multiple items separated by periods? Actually it's a paragraph: "Experience in leveraging or critically thinking about how to integrate AI into work processes, decision-making, or problem-solving. This may include using AI-powered tools, automating workflows, analyzing AI-driven insights, or exploring AI's potential impact on the function or industry." Then "10+ years of experience as a Product Designer, Design Technologist, Creative Technologist, Motion Designer, or Hybrid Visual/UI Designer working on complex web applications." Then "A portfolio showcasing world-class visual craft, sophisticated motion/animation choreography, and real interactive prototypes." Then "Proven proficiency in modern front-end web technologies (HTML5, modern CSS/SCSS, JavaScript/TypeScript, React) and component-based workflows." Then "Deep expertise in kinetic design and prototyping tools (Framer, Principle, After Effects, Rive, or code-based animation libraries like Framer Motion or GSAP)." Then "Experience designing and engineering for dynamic AI interactions, including agentic state visualization, streaming tokens, and responsive real-time feedback loops." Then "Demonstrated ability to collaborate with and influence cross-functional peers across Product, Design, and Front-End Engineering." Basic Qualifications bullet list: "Experience scaling tokens and kinetic animation systems within enterprise-grade design systems." "Strong background in micro-interaction design, spatial elevation, accessibility (such as reduced motion support), and performance profiling for web rendering." "Familiarity with AI-native developer tooling, code-backed design environments, or LLM API integrations for rapid prototyping." "Prior experience delivering consumer-grade polish to complex enterprise, developer, or data-intensive workflows." "Bachelor's degree in Design, Computer Science, Human-Computer Interaction, Digital Media, or equivalent practical experience." Pay: "For positions in this location, we offer a base pay of $171,900 - $300,800, plus equity (when applicable), variable/incentive compensation and benefits. Sales positions generally offer a competitive On Target Earnings (OTE) incentive compensation structure. Please note that the base pay shown is a guideline, and individual total compensation will vary based on factors such as qualifications, skill level, competencies, and work location." Benefits: "We also offer health plans, including flexible spending accounts, a 401(k) Plan with company match, ESPP, matching donations, a flexible time away plan and family leave programs." Also there is mention: "Compensation is based on the geographic location in which the role is located and is subject to change based on work location." That's part of pay. We also have "Work Personas" section but that's maybe not needed; it's more about work flexibility. Could be considered as "Schedule"? But we should not create Schedule unless posting actually states them. It does mention flexible work personas but not explicit schedule. Might be considered as schedule info. However instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state work personas (flexible, remote, or required in office). That could be considered schedule info. But we might treat that as "Schedule" section. However we need to see if we have real specific content: "Work Personas We approach our distributed world of work with flexibility and trust. Work personas (flexible, remote, or required in office) are categories that are assigned to ServiceNow employees depending on the nature of their work and their assigned work location. Learn more here. To determine eligibility for a work persona, ServiceNow may confirm the distance between your primary residence and the closest ServiceNow office using a third-party service." That is specific content about work flexibility. Could be placed under a "Schedule" heading. But the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could include Schedule if we have content. However we must not create a heading followed by filler/placeholder text. This is real content. So we could include Schedule. But we also have "Requirements" heading maybe not needed if we have Qualifications. Could combine. We need to decide which sections to include to avoid too many thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So we should combine where possible. We could have: - About the role (company description + role overview) - Responsibilities (What You Get To Do) - Qualifications (both preferred and basic) - Benefits - Pay - Schedule (work personas) That's six sections. Could be okay. We must not include "Skills" unless we have specific skills list separate from qualifications. We could omit. Now we need to format. We'll produce HTML fragment:

  About the role

  Company description paragraph...

  Job description paragraph...

  But note: The About the role section should not repeat job title; we already have the role overview in job description paragraph. That's fine. We need to ensure we preserve all substantive information: includes company description, job description paragraph, responsibilities list, qualifications lists, benefits, pay, schedule. We must not include boilerplate like EEO, accommodations, export control, etc. Now craft the HTML. We'll need to escape any HTML special characters? Not needed as plain text. We'll put lists for responsibilities and qualifications. For qualifications, we could have two subheadings? But we only have h3 allowed for section headings; we could use

  ? Not allowed per instruction? It only says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just use

  for subheadings like "Preferred Qualifications:" and "Basic Qualifications:" as bold text? But we need to preserve the content; we can include them as within

  . That