Senior Product Designer
or drop it." The initial paragraph is about the company, not role. Could be part of About the role? Usually "About the role" includes description of role and team. The company description could be considered "About the company" but we don't have that heading. Could we include it under About the role? Might be okay but maybe better to put it under About the role as introductory context. However we must not invent sections; we can include About the role with content that includes both company overview and role specifics. That seems acceptable. Alternatively we could split: About the role: The Role paragraph. Responsibilities: bullet list. Requirements/Qualifications/Skills: About You bullet list. Benefits: What we offer list. Pay: Compensation Range. We must not include sections with placeholder text. All content we have is specific. We need to output HTML fragment only, no /. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which content is list vs prose.
The role description paragraph could be prose (
). The responsibilities could be list items.
The "About You" could be list of requirements/qualifications/skills. Could split into Requirements, Qualifications, Skills but we may combine if not enough distinct content. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements, Qualifications, Skills into one section? But we have separate headings available. However we need to decide if we have enough distinct content for each. The posting lumps them together; we could treat "About You" as Requirements (or Qualifications). Since we have to include a section only when posting has real specific content for it. We could include Requirements (or Qualifications) and maybe Skills as separate if we can extract distinct lists. But the content is mixed; splitting artificially may create thin sections. Better to combine into one section, maybe "Requirements". Or we could have "Requirements" and "Skills" both but risk thin.
Given instruction to prefer few substantive sections, we can combine Requirements, Qualifications, Skills into one section called "Requirements". But we must follow the allowed headings list; we can use any of them. Using "Requirements" is okay.
Thus sections: About the role (prose + maybe list?), Responsibilities (list), Requirements (list), Benefits (list), Pay (prose). No Schedule.
Now we need to extract precise content.
About the role: Could include company description and role overview. Let's craft a paragraph that includes both: "RevenueCat gives app businesses the infrastructure and tools to build, run, and improve their monetization. Since graduating from YC's S18 batch, we've grown into the default monetization platform for mobile. We're in 50%+ of newly shipped subscription apps, we process $16B+ in annual purchase volume, and we help everyone from a solo developer to the OpenAI mobile team understand and grow their revenue. We're a remote-first team of 150+ people across 25+ countries, guided by values we actually practice: Customer Obsession, Always Be Shipping, Own It, and Balance. This isn't the right fit for everyone. The systems you’ll build here manage billions of dollars and touch hundreds of millions of end users, and we don’t take that lightly. You'll be expected to work hard and hold a high bar for what you ship, alongside some of the sharpest, most driven people you've worked with. If that sounds energizing rather than exhausting, keep reading." Then role specifics: "As a Senior Product Designer at RevenueCat, you’ll own complex product problems from discovery through production. You’ll work closely with Product and Engineering to understand customers, identify opportunities, shape what we build and why, and turn technically complex workflows into simple, polished experiences for developers. You’ll join a small design team with a high bar for interaction and visual craft. We’re looking for someone who is comfortable with ambiguity, talks directly to customers, prototypes and iterates quickly, and stays involved until the work is shipped and working well in production."
We could combine into one
or split into multiple
. Probably one
is fine.
Responsibilities: list items derived from role specifics: own complex product problems from discovery through production; work closely with Product and Engineering to understand customers, identify opportunities, shape what we build and why; turn technically complex workflows into simple, polished experiences for developers; join a small design team with a high bar for interaction and visual craft; be comfortable with ambiguity; talk directly to customers; prototype and iterate quickly; stay involved until the work is shipped and working well in production.
We could also include "Work closely with Product and Engineering, involve partners early, reduce scope intelligently, and stay engaged through implementation and follow-up." That's more from About You but could be responsibility. However we already have responsibilities list; we can keep as is.
Requirements: list items from About You: strong track record solving complex product problems in B2B, SaaS, developer tools, or similarly complex environments; able to frame ambiguous problems, identify opportunities, make sound trade-offs, and help shape what gets built and why; design clear, intuitive workflows and think carefully about information architecture, states, edge cases, errors, and interactions; have a high visual craft bar and care deeply about hierarchy, typography, spacing, composition, and polish; stay close to customers, using direct conversations and qualitative and quantitative evidence to inform decisions; work closely with Product and Engineering, involve partners early, reduce scope intelligently, and stay engaged through implementation and follow-up; communicate clearly in a remote, asynchronous environment and take ownership beyond the boundaries of a design handoff; understand technical constraints well enough to make realistic decisions and are comfortable using prototypes, code, or modern AI tools when they help you learn or move faster; excited about our mission to help developers make more money.
We could also include "In the first month..." etc as expectations but those are more about onboarding; could be part of Responsibilities? Might be better to include as part of About the role? But we already have responsibilities list; we could add a separate section for "First 3 months" etc but not needed.
Benefits: list items: Competitive equity in a fast-growing, Series C startup backed by top-tier investors, including Y Combinator; 10-year window to exercise vested equity options; A fully remote environment designed around autonomy and flexibility; 4-5 weeks of flexible time off annually; Paid desk at a co-working space; Workspace budget and continuous learning stipend.
Pay: Compensation Range: $220K. Could be a
.
Now ensure we don't include boilerplate like interview process, etc. Remove those.
Now produce HTML:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
Pay
Compensation Range: $220K
Make sure no extra whitespace? It's fine.
Now craft the content precisely.
Let's write About the role paragraph:
"RevenueCat gives app businesses the infrastructure and tools to build, run, and improve their monetization. Since graduating from YC's S18 batch, we've grown into the default monetization platform for mobile. We're in 50%+ of newly shipped subscription apps, we process $16B+ in annual purchase volume, and we help everyone from a solo developer to the OpenAI mobile team understand and grow their revenue. We're a remote-first team of 150+ people across 25+ countries, guided by values we actually practice: Customer Obsession, Always Be Shipping, Own It, and Balance. This isn't the right fit for everyone. The systems you’ll build here manage billions of dollars and touch hundreds of millions of end users, and we don’t take that lightly. You'll be expected to work hard and hold a high bar for what you ship, alongside some of the sharpest, most driven people you've worked with. If that sounds energizing rather than exhausting, keep reading. As a Senior Product Designer at RevenueCat, you’ll own complex product problems from discovery through production. You’ll work closely with Product and Engineering to understand customers, identify opportunities, shape what we build and why, and turn technically complex workflows into simple, polished experiences for developers. You’ll join a small design team with a high bar for interaction and visual craft. We’re looking for someone who is comfortable with
for prose. We need to decide which content is list vs prose. The role description paragraph could be prose (
). The responsibilities could be list items. The "About You" could be list of requirements/qualifications/skills. Could split into Requirements, Qualifications, Skills but we may combine if not enough distinct content. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements, Qualifications, Skills into one section? But we have separate headings available. However we need to decide if we have enough distinct content for each. The posting lumps them together; we could treat "About You" as Requirements (or Qualifications). Since we have to include a section only when posting has real specific content for it. We could include Requirements (or Qualifications) and maybe Skills as separate if we can extract distinct lists. But the content is mixed; splitting artificially may create thin sections. Better to combine into one section, maybe "Requirements". Or we could have "Requirements" and "Skills" both but risk thin. Given instruction to prefer few substantive sections, we can combine Requirements, Qualifications, Skills into one section called "Requirements". But we must follow the allowed headings list; we can use any of them. Using "Requirements" is okay. Thus sections: About the role (prose + maybe list?), Responsibilities (list), Requirements (list), Benefits (list), Pay (prose). No Schedule. Now we need to extract precise content. About the role: Could include company description and role overview. Let's craft a paragraph that includes both: "RevenueCat gives app businesses the infrastructure and tools to build, run, and improve their monetization. Since graduating from YC's S18 batch, we've grown into the default monetization platform for mobile. We're in 50%+ of newly shipped subscription apps, we process $16B+ in annual purchase volume, and we help everyone from a solo developer to the OpenAI mobile team understand and grow their revenue. We're a remote-first team of 150+ people across 25+ countries, guided by values we actually practice: Customer Obsession, Always Be Shipping, Own It, and Balance. This isn't the right fit for everyone. The systems you’ll build here manage billions of dollars and touch hundreds of millions of end users, and we don’t take that lightly. You'll be expected to work hard and hold a high bar for what you ship, alongside some of the sharpest, most driven people you've worked with. If that sounds energizing rather than exhausting, keep reading." Then role specifics: "As a Senior Product Designer at RevenueCat, you’ll own complex product problems from discovery through production. You’ll work closely with Product and Engineering to understand customers, identify opportunities, shape what we build and why, and turn technically complex workflows into simple, polished experiences for developers. You’ll join a small design team with a high bar for interaction and visual craft. We’re looking for someone who is comfortable with ambiguity, talks directly to customers, prototypes and iterates quickly, and stays involved until the work is shipped and working well in production." We could combine into one
or split into multiple
. Probably one
is fine. Responsibilities: list items derived from role specifics: own complex product problems from discovery through production; work closely with Product and Engineering to understand customers, identify opportunities, shape what we build and why; turn technically complex workflows into simple, polished experiences for developers; join a small design team with a high bar for interaction and visual craft; be comfortable with ambiguity; talk directly to customers; prototype and iterate quickly; stay involved until the work is shipped and working well in production. We could also include "Work closely with Product and Engineering, involve partners early, reduce scope intelligently, and stay engaged through implementation and follow-up." That's more from About You but could be responsibility. However we already have responsibilities list; we can keep as is. Requirements: list items from About You: strong track record solving complex product problems in B2B, SaaS, developer tools, or similarly complex environments; able to frame ambiguous problems, identify opportunities, make sound trade-offs, and help shape what gets built and why; design clear, intuitive workflows and think carefully about information architecture, states, edge cases, errors, and interactions; have a high visual craft bar and care deeply about hierarchy, typography, spacing, composition, and polish; stay close to customers, using direct conversations and qualitative and quantitative evidence to inform decisions; work closely with Product and Engineering, involve partners early, reduce scope intelligently, and stay engaged through implementation and follow-up; communicate clearly in a remote, asynchronous environment and take ownership beyond the boundaries of a design handoff; understand technical constraints well enough to make realistic decisions and are comfortable using prototypes, code, or modern AI tools when they help you learn or move faster; excited about our mission to help developers make more money. We could also include "In the first month..." etc as expectations but those are more about onboarding; could be part of Responsibilities? Might be better to include as part of About the role? But we already have responsibilities list; we could add a separate section for "First 3 months" etc but not needed. Benefits: list items: Competitive equity in a fast-growing, Series C startup backed by top-tier investors, including Y Combinator; 10-year window to exercise vested equity options; A fully remote environment designed around autonomy and flexibility; 4-5 weeks of flexible time off annually; Paid desk at a co-working space; Workspace budget and continuous learning stipend. Pay: Compensation Range: $220K. Could be a
. Now ensure we don't include boilerplate like interview process, etc. Remove those. Now produce HTML:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Pay
Compensation Range: $220K
Make sure no extra whitespace? It's fine. Now craft the content precisely. Let's write About the role paragraph: "RevenueCat gives app businesses the infrastructure and tools to build, run, and improve their monetization. Since graduating from YC's S18 batch, we've grown into the default monetization platform for mobile. We're in 50%+ of newly shipped subscription apps, we process $16B+ in annual purchase volume, and we help everyone from a solo developer to the OpenAI mobile team understand and grow their revenue. We're a remote-first team of 150+ people across 25+ countries, guided by values we actually practice: Customer Obsession, Always Be Shipping, Own It, and Balance. This isn't the right fit for everyone. The systems you’ll build here manage billions of dollars and touch hundreds of millions of end users, and we don’t take that lightly. You'll be expected to work hard and hold a high bar for what you ship, alongside some of the sharpest, most driven people you've worked with. If that sounds energizing rather than exhausting, keep reading. As a Senior Product Designer at RevenueCat, you’ll own complex product problems from discovery through production. You’ll work closely with Product and Engineering to understand customers, identify opportunities, shape what we build and why, and turn technically complex workflows into simple, polished experiences for developers. You’ll join a small design team with a high bar for interaction and visual craft. We’re looking for someone who is comfortable with