6 month Fixed Term Lead Product Designer, Lifecycle

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key info: - Role: 6 month Fixed-Term Lead Product Designer, Lifecycle. - About: description: Change.org is a social impact business, public benefit company, world's largest social change platform with 100 million users, 40k+ campaigns monthly, 100% user-generated revenue model. Users win campaigns for change once every hour. Working for a world where no one is powerless, creating change part of everyday life. They gave examples of mobilizations. - Key Outcomes (Responsibilities): bullet points: Design the post-petition supporter journey into clear chapters and ship email flows that regularly re-engage petition signers, clearly guiding them and showcasing petition impact. Extend and apply our existing modular email system across automated emails—refresh visual design, and develop new brand-aligned templates in collaboration with the Marketing team to improve key performance metrics. Deepen and evolve the visual identity of lifecycle emails by creating a cohesive system of layouts, imagery, and reusable assets that feel polished and on-brand across journeys; bonus: use AI tools to quickly explore variations and speed up production while maintaining craft. - Core Competencies (Skills/Requirements): list: Visual & Brand Design Craft – Exceptional eye for layout, typography, hierarchy, and art direction; creates striking, on-brand emails and original assets that feel editorial and product-quality. Lifecycle & Narrative Thinking – Designs chaptered journeys from post-petition onward; aligns message + visuals to user intent to drive shares, follows, and “second actions.” User Empathy: You center users' emotions, motivations, and pain points in your design process and you leverage qualitative research to uncover these insights. You can anticipate and map users’ emotional states at different touchpoints. Your designs reduce stress and uncertainty and inspire trust and confidence. Systems & Templates in Figma – Extends our modular email system with robust components, variables/tokens. Email Craft & Accessibility – Masters email constraints: mobile-first layout, copy hierarchy, CTAs, dark mode, image optimization, etc. AI-Augmented Creation (Proficient) – Uses AI tooling to ideate and produce on-brand assets quickly; maintains prompt libraries, style presets, and safety/quality guardrails. Collaboration & Influence – Works seamlessly with cross-functional partners; clearly communicates rationale, incorporates feedback, and champions design standards across the lifecycle program—while balancing performance goals, brand expression, and technical email constraints in every decision. - Target Experience (Requirements/Qualifications): bullet list: 7+ years designing lifecycle comms for consumer or mission-driven products. A portfolio of visually striking, brand-forward emails—shows systems thinking, strong typography/layout, and original asset creation. Figma expert (components, variables/tokens, Auto Layout, libraries) with experience extending an existing modular email system and documenting patterns. Proven ability to design chaptered journeys (e.g., post-petition share → follow/join → next action) that increase repeat engagement. Email craft & constraints: mobile-first, accessibility/alt text, dark mode, image optimization; basic HTML/CSS for email is a plus. AI competency: Proficient—regularly uses design-focused AI (Figma AI, image-gen) to ideate and produce on-brand assets; maintains prompt/style libraries and QA guardrails. Communicates rationale clearly, documents templates/guidelines, and helps others self-serve while keeping quality high. Bonus: civic tech/nonprofit experience; growth/lifecycle design; strong email copy chops. - Location and contract: This is a 6-month fixed term role based in the United States or Mexico. List of US states where they can hire. Compensation: The annual salary of a Lead Product Designer, Lifecycle is $218,000 in San Francisco and New York, is $207,000 in Austin, Boston, Chicago, DC, LA and Seattle, and is $185,500 in all other US locations. The salary of a Lead Product Designer, Lifecycle in Mexico is MX$132,916.67/month gross via a local third-party entity. Benefits and perks also vary based on location. - Evaluation Process: Recruiter Screen, Hiring Manager Screen, Team Interview, Executive Interview. Might be considered as part of process but not needed? Could be under "About the role" maybe not needed. The instruction: remove application instructions, but evaluation process maybe not needed? It's part of posting but not a section heading. Could be omitted or placed in a paragraph under About? Probably not needed. We can include a short paragraph about process if we want but not required. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Evaluation process is not exactly application instructions but could be considered part of hiring process; but we can keep if it's substantive. However they said "Prefer a few substantive sections over many thin ones." So we could combine some. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have info for About the role (company description, mission). Responsibilities (Key Outcomes). Requirements (Target Experience maybe). Qualifications (maybe overlapping with Requirements). Skills (Core Competencies). Benefits (mention benefits vary based on location). Pay (salary details). Schedule (6-month fixed term). Also location info could be part of About or maybe under Requirements? But schedule is fixed term 6 months. We must not create sections with filler like "not specified". So we include only those with content. We'll produce:

About the role

... description ...

Responsibilities

• ...
...

Requirements

• 7+ years designing lifecycle comms for consumer or mission-driven products.
... maybe also include portfolio, Figma expert, proven ability to design chaptered journeys, email craft & constraints, AI competency, communication, bonus items.

But we also have Skills section separate. Could combine Requirements and Qualifications? The instruction says we can have sections for Requirements, Qualifications, Skills. We need to decide what goes where. We could treat: - Requirements: mandatory experience (7+ years, portfolio, Figma expert, ability to design chaptered journeys, email craft & constraints, AI competency, communication). - Qualifications: maybe bonus items (civic tech/nonprofit experience, growth/lifecycle design, strong email copy chops). - Skills: core competencies list (Visual & Brand Design Craft, Lifecycle & Narrative Thinking, User Empathy, Systems & Templates in Figma, Email Craft & Accessibility, AI-Augmented Creation, Collaboration & Influence). But there is overlap. However we must not repeat content. We need to preserve all substantive info; we can split but ensure no duplication. Let's extract each piece: From "Target Experience" bullet list: - 7+ years designing lifecycle comms for consumer or mission-driven products. - A portfolio of visually striking, brand-forward emails—shows systems thinking, strong typography/layout, and original asset creation. - Figma expert (components, variables/tokens, Auto Layout, libraries) with experience extending an existing modular email system and documenting patterns. - Proven ability to design chaptered journeys (e.g., post-petition share → follow/join → next action) that increase repeat engagement. - Email craft & constraints: mobile-first, accessibility/alt text, dark mode, image optimization; basic HTML/CSS for email is a plus. - AI competency: Proficient—regularly uses design-focused AI (Figma AI, image-gen) to ideate and produce on-brand assets; maintains prompt/style libraries and QA guardrails. - Communicates rationale clearly, documents templates/guidelines, and helps others self-serve while keeping quality high. - Bonus: civic tech/nonprofit experience; growth/lifecycle design; strong email copy chops. From "The Most Important Core Competencies For The Role Are" list: - Visual & Brand Design Craft – Exceptional eye for layout, typography, hierarchy, and art direction; creates striking, on-brand emails and original assets that feel editorial and product-quality. - Lifecycle & Narrative Thinking – Designs chaptered journeys from post-petition onward; aligns message + visuals to user intent to drive shares, follows, and “second actions.” - User Empathy: You center users' emotions, motivations, and pain points in your design process and you leverage qualitative research to uncover these insights. You can anticipate and map users’ emotional states at different touchpoints. Your designs reduce stress and uncertainty and inspire trust and confidence. - Systems & Templates in Figma – Extends our modular email system with robust components, variables/tokens. - Email Craft & Accessibility – Masters email constraints: mobile-first layout, copy hierarchy, CTAs, dark mode, image optimization, etc. - AI-Augmented Creation (Proficient) – Uses AI tooling to ideate and produce on-brand assets quickly; maintains prompt libraries, style presets, and safety/quality guardrails. - Collaboration & Influence – Works seamlessly with cross-functional partners; clearly communicates rationale, incorporates feedback, and champions design standards across the lifecycle program—while balancing performance goals, brand expression, and technical email constraints in every decision. We see overlap: many items appear both places. To avoid duplication, we could decide to put the core competencies under Skills section, and the target experience under Requirements/Qualifications. But we need to ensure we don't duplicate same content. We can place: - Skills: the core competencies list (Visual & Brand Design Craft, Lifecycle & Narrative Thinking, User Empathy, Systems & Templates in Figma, Email Craft & Accessibility, AI-Augmented Creation, Collaboration & Influence). - Requirements: the mandatory experience items (7+ years, portfolio, Figma expert, ability to design chaptered journeys, email craft & constraints, AI competency, communication). However note that email craft & constraints and AI competency also appear in Skills; but we can phrase them slightly differently to avoid duplication? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication across sections? It says "Do NOT repeat the job title as a heading" and "do NOT put Job ID / requisition numbers as headings". It doesn't explicitly forbid repeating content across sections, but better to avoid duplication. However we could keep them in both if needed but risk being considered duplication? Not explicitly prohibited but "Prefer a few substantive sections over many thin ones." Duplication may be considered thin? Not sure. Safer to avoid duplication. Thus we need to split the info such that each piece appears only once. We can assign: - About the role: company description, mission, impact examples. - Responsibilities: Key Outcomes (design post-petition journey, extend modular email system, deepen visual identity, use AI tools). - Requirements: mandatory experience (7+ years designing lifecycle comms, portfolio, Figma expert, ability to design chaptered journeys, email craft & constraints, AI competency, communication). (We'll include these as bullet list.) - Qualifications: bonus items (civic tech/nonprofit experience, growth/lifecycle design, strong email copy chops). Could also include location eligibility? But location is more about where role based; maybe we can put under About or a separate section? There's no section for Location; we could include location info in About or maybe under Requirements as note. But we have Schedule section for 6-month fixed term. Location could be part of About or maybe a separate short paragraph under About. We'll include location info in About or maybe a separate short paragraph under About after mission. - Benefits: mention benefits and perks vary based on location (no specifics). Could we include that? It's substantive