Applied AI Product Designer
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content from posting.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate.
We need to include sections only if there is real specific content.
Let's parse the posting.
It starts with "A Note From the Founder ..." then description of role, etc.
We need to decide sections: About the role (maybe summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content about role, responsibilities, what you will own, first 90 days, who you are, compensation.
We need to map to sections.
We should not invent sections like "About the role" if we have content. Probably we can put the founder note and role description under "About the role". Responsibilities: list of what you will own (consumer mobile experience, revenue product, design system, prototyping, machine, partnership). Requirements/Qualifications/Skills: the "Who You Are" bullet list. Benefits: maybe not explicit besides equity and salary? There's compensation: base salary and equity. Benefits maybe not listed. Pay: we have compensation. Schedule: not mentioned.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated: base salary $155k–$215k plus equity. So we can include Pay section. Benefits: not explicit besides equity (which is part of compensation). Could treat equity as part of Pay? The instruction: "Prefer a few substantive sections over many thin ones." We could combine Pay and Benefits? But we have separate headings allowed. If Benefits not explicitly stated, we should not create Benefits section. Equity could be considered part of compensation, but not a benefit like health insurance. So we omit Benefits.
Schedule: not mentioned, omit.
Now we need to output HTML fragment with headings and - for lists,
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Must not omit details.
We need to be careful to not lose any specifics.
Let's extract content for each section.
About the role: Could combine founder note and description of Citizen, role overview, why now, applied AI, etc. But we need to avoid too much duplication. We'll include a paragraph summarizing.
Responsibilities: list of what you will own: consumer mobile experience (iOS first, Android close behind; onboarding, map, incident experience, live video, alerts, Premium; every screen a user touches, and the system that holds them together). Category-defining work (live, AI-generated, ambient experiences). The revenue product (paywalls, plan mix, trials, reverse trials, upgrade path, payment at onboarding, everything a paying member sees; roadmap, experiments, ship decisions). The design system (visual language across product, brand, live broadcast studio: type, color, motion, sound, iconography). Prototyping and validation (high-fidelity prototypes in days, not weeks; Figma, Origami, SwiftUI, code; usability sessions, funnel data, live experiments). The machine (workflows above, designed, run, pushed forward; decide where human stays in loop). Partnership (daily with Founder/CEO; tightly with iOS/Android engineering; with Marketing; with Real-Time Operations; with agents). Also first 90 days could be responsibilities? Might be separate but we could include under Responsibilities or maybe a separate section like "First 90 Days". But we only have allowed headings; we could put under Responsibilities as a list? Might be better to create a separate section? Not allowed headings besides those eight. So we must fit into those.
We could treat "First 90 Days" as part of Responsibilities (what you will do). Or we could put under "About the role". Probably better to put under Responsibilities as a list of early milestones.
Requirements/Qualifications/Skills: The "Who You Are" bullet list includes many items: roughly a decade designing consumer mobile products that millions use, end to end, shipping them; taste, show work; discernment (given hundred options know which three worth human attention); made something that did not exist before (new interaction, category, product felt like future); high agency; build with AI already (opinions about tools, replaced parts of workflow with agents, paying attention to what's next); think in systems (type, color, motion, sound, design language survives contact with team and fleet of agents); owned an outcome, not only a surface (run paywall, pricing, onboarding test end to end, read result honestly, shipped or killed it on number; comfortable being product manager when not one); fluent in video and motion (prototype high fidelity fast on real device; comfortable with code to get idea onto phone without waiting for engineer; not engineer, lead by example, want to help small team); care about mission; make confident decisions without complete picture, take direct feedback from founder with strong opinions, give it back; first conversation: bring two things (something you made that didn't exist before, and part of your own workflow replaced with agents). Also "You have spent roughly a decade designing consumer mobile products that millions of people use, end to end, and shipping them." etc.
We need to preserve all details. We'll create a list under Requirements (or Qualifications/Skills). Since we have three possible headings, we need to decide which to use. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose any of those that have content. We should not create empty ones. We could combine Requirements and Qualifications and Skills into one section? But we have separate headings allowed; we could use one of them, e.g., Requirements, and put all the who you are content there. Or we could split into Qualifications and Skills. But we must not invent sections with filler. If we split, we need to ensure each has substantive content. Could split: Qualifications: experience, decade, shipping, taste, show work, discernment, made something new, high agency, built with AI, think in systems, owned outcome, fluent in video/motion, care about mission, confident decisions. Skills: maybe list of specific skills: Figma, Origami, SwiftUI, code, prototyping, usability sessions, funnel data, live experiments, etc. But the posting does not explicitly separate qualifications vs skills; it's mixed. Safer to use one heading, e.g., Requirements, and put all who you are content there. That satisfies having a section with substantive content.
Pay: base salary $155k–$215k per year, plus meaningful equity.
We should not include Benefits.
Now we need to ensure we don't repeat job title as heading. No job title appears.
We must not include boilerplate like "A Note From the Founder" maybe we can keep as part of About the role? The founder note is substantive; we can include it as a paragraph under About the role.
We must not include application instructions, EEO, etc. There's none.
Now produce HTML.
Structure:
About the role
... founder note and role overview ...
Responsibilities
- ... each bullet ...
Requirements
- ... each bullet from Who You Are ...
Pay
Base salary of $155,000–$215,000 per year, plus meaningful equity.
We need to ensure we preserve all specifics.
Let's craft About the role paragraph: combine founder note and description of Citizen, why now, applied AI, etc. Must not lose details.
Founder note: "I design. I always have. For years I did it with a small team and a lot of late nights, and it got Citizen to millions of people. Now I do it with agents, and the gap between an idea and a working build on my phone is measured in hours. I need one designer who works that way with me: someone with real taste who would rather ship the prototype than polish the deck, and who is willing to own what people pay for, not just what they see. You will get direct feedback from me, and I want it back. You will also see your work in front of millions of people faster than anywhere else you have been."
Then role description: "Citizen is the #1 safety app in the U.S. Every day, thousands of videos are captured live at the scene of real incidents and distributed in real time to people in every major American city. No other consumer product has this. It is a live network, a newsroom, and a safety tool at once, and it is growing again. We are rebuilding Citizen as an AI-native company. Engineering and operations already run with AI agents working alongside humans. Product design is next, and you will define what that looks like. You will be the senior product designer for Citizen's consumer mobile experience and the product owner of its revenue surface, reporting directly to the Founder and CEO, who designs alongside you. There is no product manager between you and the subscription business. Four outcomes are yours: a product people open every day rather than only on a bad one, interfaces that make real-time video and live safety feel effortless on a phone, a subscription experience that converts and keeps people, and a design operation where agents do the production work while you do the thinking. You inherit a product used by millions, a brand people recognize, a founder who cares about pixels, and the mandate to build the category's next chapter rather than polish its last one. You set the bar with your own work first. The design team is small today, and as it grows you will help shape how it works and who it needs."
Why Now: "Citizen built the public safety category and became the #1 safety app in the country. The next chapter is not a redesign of that product. It is a different kind of product: live, AI-native, ambient, and personal, built on the base and the distribution the first chapter earned. The person in this seat decides what safety looks like on a phone when an agent is watching the city for you. Almost nobody gets to invent a category twice from a real base with real distribution. You will."
What "Applied AI" Means Here: "You are a product designer first. The craft is the job: judgment, taste, the ability to look at forty variants and know which one is right and why. Anyone can generate options now. Almost nobody can choose. You are also the person who builds and runs the agents that do the production work. Variants by the dozen before lunch, assets at every size and locale without a human exporting them, a Figma frame turned into a working prototype the same afternoon. You decide what runs without a person, you raise the bar on the output, and you show the rest of the company what a designer with a team of agents can ship. If you are still exporting assets by hand in month three, something has gone wrong. The scope is yours. The CEO is your only approval. You do not open a ticket; if the tool does not exist, you build it."
We could include all that in About the role paragraph(s). Might be long but okay.
Now Responsibilities: list items from "What You Will Own" and maybe first 90 days.
What You Will Own bullet points:
- The consumer mobile experience. iOS first, Android close behind. Onboarding, the map, the incident experience, live video, alerts, Premium. Every screen a user touches, and the system that holds them together. The tempo is a prototype on a device the same day, not a review the following week.
- Category-defining work. Live, AI-generated, and ambient experiences that do not exist yet: what a notification becomes when it can show you the scene, what a safety app is when it talks back, what the interface is when the phone is in a pocket and the user is walking home. You are expected to bring ideas the CEO
- for lists,
for prose. We need to preserve all substantive information, not invent or summarize away detail. Must not omit details. We need to be careful to not lose any specifics. Let's extract content for each section. About the role: Could combine founder note and description of Citizen, role overview, why now, applied AI, etc. But we need to avoid too much duplication. We'll include a paragraph summarizing. Responsibilities: list of what you will own: consumer mobile experience (iOS first, Android close behind; onboarding, map, incident experience, live video, alerts, Premium; every screen a user touches, and the system that holds them together). Category-defining work (live, AI-generated, ambient experiences). The revenue product (paywalls, plan mix, trials, reverse trials, upgrade path, payment at onboarding, everything a paying member sees; roadmap, experiments, ship decisions). The design system (visual language across product, brand, live broadcast studio: type, color, motion, sound, iconography). Prototyping and validation (high-fidelity prototypes in days, not weeks; Figma, Origami, SwiftUI, code; usability sessions, funnel data, live experiments). The machine (workflows above, designed, run, pushed forward; decide where human stays in loop). Partnership (daily with Founder/CEO; tightly with iOS/Android engineering; with Marketing; with Real-Time Operations; with agents). Also first 90 days could be responsibilities? Might be separate but we could include under Responsibilities or maybe a separate section like "First 90 Days". But we only have allowed headings; we could put under Responsibilities as a list? Might be better to create a separate section? Not allowed headings besides those eight. So we must fit into those. We could treat "First 90 Days" as part of Responsibilities (what you will do). Or we could put under "About the role". Probably better to put under Responsibilities as a list of early milestones. Requirements/Qualifications/Skills: The "Who You Are" bullet list includes many items: roughly a decade designing consumer mobile products that millions use, end to end, shipping them; taste, show work; discernment (given hundred options know which three worth human attention); made something that did not exist before (new interaction, category, product felt like future); high agency; build with AI already (opinions about tools, replaced parts of workflow with agents, paying attention to what's next); think in systems (type, color, motion, sound, design language survives contact with team and fleet of agents); owned an outcome, not only a surface (run paywall, pricing, onboarding test end to end, read result honestly, shipped or killed it on number; comfortable being product manager when not one); fluent in video and motion (prototype high fidelity fast on real device; comfortable with code to get idea onto phone without waiting for engineer; not engineer, lead by example, want to help small team); care about mission; make confident decisions without complete picture, take direct feedback from founder with strong opinions, give it back; first conversation: bring two things (something you made that didn't exist before, and part of your own workflow replaced with agents). Also "You have spent roughly a decade designing consumer mobile products that millions of people use, end to end, and shipping them." etc. We need to preserve all details. We'll create a list under Requirements (or Qualifications/Skills). Since we have three possible headings, we need to decide which to use. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose any of those that have content. We should not create empty ones. We could combine Requirements and Qualifications and Skills into one section? But we have separate headings allowed; we could use one of them, e.g., Requirements, and put all the who you are content there. Or we could split into Qualifications and Skills. But we must not invent sections with filler. If we split, we need to ensure each has substantive content. Could split: Qualifications: experience, decade, shipping, taste, show work, discernment, made something new, high agency, built with AI, think in systems, owned outcome, fluent in video/motion, care about mission, confident decisions. Skills: maybe list of specific skills: Figma, Origami, SwiftUI, code, prototyping, usability sessions, funnel data, live experiments, etc. But the posting does not explicitly separate qualifications vs skills; it's mixed. Safer to use one heading, e.g., Requirements, and put all who you are content there. That satisfies having a section with substantive content. Pay: base salary $155k–$215k per year, plus meaningful equity. We should not include Benefits. Now we need to ensure we don't repeat job title as heading. No job title appears. We must not include boilerplate like "A Note From the Founder" maybe we can keep as part of About the role? The founder note is substantive; we can include it as a paragraph under About the role. We must not include application instructions, EEO, etc. There's none. Now produce HTML. Structure:
About the role
... founder note and role overview ...
Responsibilities
- ... each bullet ...
Requirements
- ... each bullet from Who You Are ...
Pay
Base salary of $155,000–$215,000 per year, plus meaningful equity.
We need to ensure we preserve all specifics. Let's craft About the role paragraph: combine founder note and description of Citizen, why now, applied AI, etc. Must not lose details. Founder note: "I design. I always have. For years I did it with a small team and a lot of late nights, and it got Citizen to millions of people. Now I do it with agents, and the gap between an idea and a working build on my phone is measured in hours. I need one designer who works that way with me: someone with real taste who would rather ship the prototype than polish the deck, and who is willing to own what people pay for, not just what they see. You will get direct feedback from me, and I want it back. You will also see your work in front of millions of people faster than anywhere else you have been." Then role description: "Citizen is the #1 safety app in the U.S. Every day, thousands of videos are captured live at the scene of real incidents and distributed in real time to people in every major American city. No other consumer product has this. It is a live network, a newsroom, and a safety tool at once, and it is growing again. We are rebuilding Citizen as an AI-native company. Engineering and operations already run with AI agents working alongside humans. Product design is next, and you will define what that looks like. You will be the senior product designer for Citizen's consumer mobile experience and the product owner of its revenue surface, reporting directly to the Founder and CEO, who designs alongside you. There is no product manager between you and the subscription business. Four outcomes are yours: a product people open every day rather than only on a bad one, interfaces that make real-time video and live safety feel effortless on a phone, a subscription experience that converts and keeps people, and a design operation where agents do the production work while you do the thinking. You inherit a product used by millions, a brand people recognize, a founder who cares about pixels, and the mandate to build the category's next chapter rather than polish its last one. You set the bar with your own work first. The design team is small today, and as it grows you will help shape how it works and who it needs." Why Now: "Citizen built the public safety category and became the #1 safety app in the country. The next chapter is not a redesign of that product. It is a different kind of product: live, AI-native, ambient, and personal, built on the base and the distribution the first chapter earned. The person in this seat decides what safety looks like on a phone when an agent is watching the city for you. Almost nobody gets to invent a category twice from a real base with real distribution. You will." What "Applied AI" Means Here: "You are a product designer first. The craft is the job: judgment, taste, the ability to look at forty variants and know which one is right and why. Anyone can generate options now. Almost nobody can choose. You are also the person who builds and runs the agents that do the production work. Variants by the dozen before lunch, assets at every size and locale without a human exporting them, a Figma frame turned into a working prototype the same afternoon. You decide what runs without a person, you raise the bar on the output, and you show the rest of the company what a designer with a team of agents can ship. If you are still exporting assets by hand in month three, something has gone wrong. The scope is yours. The CEO is your only approval. You do not open a ticket; if the tool does not exist, you build it." We could include all that in About the role paragraph(s). Might be long but okay. Now Responsibilities: list items from "What You Will Own" and maybe first 90 days. What You Will Own bullet points: - The consumer mobile experience. iOS first, Android close behind. Onboarding, the map, the incident experience, live video, alerts, Premium. Every screen a user touches, and the system that holds them together. The tempo is a prototype on a device the same day, not a review the following week. - Category-defining work. Live, AI-generated, and ambient experiences that do not exist yet: what a notification becomes when it can show you the scene, what a safety app is when it talks back, what the interface is when the phone is in a pocket and the user is walking home. You are expected to bring ideas the CEO