Founding Designer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
Thus we need to parse the posting and decide which sections to include.
The posting text:
"About We're building the future of storytelling and video editing. We're a small team that moves fast and builds things we're proud of. We care obsessively about taste: in design, in product, in every detail. We're solving these hard problems. We're backed by a Tier-1 global fund, YC, and founders of billion dollar companies. Design Video is the most powerful way humans tell stories. It always has been. But creating it today is still painfully hard. Fragmented tools, steep learning curves, and workflows that get in the way of the actual creative work. We're building Cardboard to change that. As our founding designer, you'll shape not just how the product looks, but how it works. You think product first and push back when something doesn't serve the user, and think through every user flow before a component gets shipped. In our team, everyone has incredible speed, taste, and care that they put into their work. You'll often see people coming up with micro-interactions nobody asked for and losing sleep over things that feel slightly off by a sheer two pixels. Your job is to accelerate and harness that energy to make sure everything we build feels cohesive and intentional. You will Own product design end to end: flows, UI, prototypes, and everything in between. Advocate for the user in every room like a PM does. Work closely with founders, engineering, and growth. Build a design system. Make something people love. Who you are You have taste. You own things end-to-end. You think like a PM. You notice the extra click, the label doing two jobs, the feature that shipped but isn't really done. AI-pilled and restlessly curious. Rive, Spline, Paper, Reve, Claude design, whatever dropped last week, you've already tried it. You're a Figma expert. You love micro-interactions. You've probably built parts of a design system, or at least felt the pain of not having one. Resourceful. When you need an illustrator, motion designer, or freelancer, you find them and direct them well. Bonus: you vibe coded or shipped a side project. What you get You'd be surrounded by people who are absurdly good at what they do. One started coding at 11 and shipped an app with 6M+ downloads in high school. One got into CS engineering at 14 and has been working on distributed systems for 8+ years. One's an ex-founder who took a company to 1.2M users and $300M+ in transactions. That's the team. We're looking for someone who'll raise the bar on the creative side the way we have on the technical and business side. Apart from that you'd get: Competitive salary and founding-team equity. Unlimited tokens. Use whatever you want, as much as you want. A healthy budget for tools, monitors, laptop, and anything you need to do your best work. Share: Your portfolio and resume. Your favorite product and one sentence on why. One piece of work that you're proud of. Optional: if you'd like, record and send us a quick video : )"
We need to remove application instructions: "Share: Your portfolio and resume. Your favorite product and one sentence on why. One piece of work that you're proud of. Optional: if you'd like, record and send us a quick video : )" Those are application instructions, so remove them.
Also remove any boilerplate like "About We're building..." but we keep the content.
We need sections: About (maybe "About the role"? but heading must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can use other headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. But we can also use other headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those exact headings if we have content for those categories. The posting has sections: About (description of company and role), Who you are (requirements/qualifications/skills), What you get (benefits). So we can map:
- About the role: corresponds to the "About" paragraph describing role and company.
- Requirements/Qualifications/Skills: "Who you are" includes qualifications, skills, traits.
- Benefits: "What you get" includes competitive salary, founding-team equity, unlimited tokens, budget for tools, etc.
We should not include Pay or Schedule sections unless explicitly stated. The posting mentions "Competitive salary and founding-team equity." That's compensation but not explicit salary number. It's still a benefit/compensation. Should we create a Pay section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive salary and founding-team equity." That's about pay/compensation. However they also list benefits like unlimited tokens, budget for tools. Could combine into Benefits section. The instruction says prefer a few substantive sections over many thin ones. So we could have Benefits section covering salary, equity, tokens, budget. No separate Pay needed.
Thus we will output:
About the role
... (the about paragraph)
Requirements
- ... list items from Who you are
But we need to preserve all substantive information; we should not lose details. The "Who you are" paragraph includes multiple sentences; we could convert each sentence into list items? The instruction: Use - for any list of duties/requirements/benefits. The "Who you are" is not explicitly a list but contains multiple bullet-like statements separated by periods. We could treat each distinct requirement as a list item. However we must not invent or summarize away detail. If we convert sentences to list items, we preserve the detail. That's acceptable.
Similarly for Benefits: we have "Competitive salary and founding-team equity. Unlimited tokens. Use whatever you want, as much as you want. A healthy budget for tools, monitors, laptop, and anything you need to do your best work." Also maybe mention "You'd be surrounded by people who are absurdly good at what they do..." that's more about team, not a benefit per se but could be part of Benefits? Actually that's describing team, could be part of About? But it's in "What you get" section after describing team. It says "Apart from that you'd get:" then list. So the team description is part of what you get? It says "You'd be surrounded by people who are absurdly good at what they do." That's a benefit. So we can include that as a benefit item.
Thus Benefits list items:
- You'd be surrounded by people who are absurdly good at what they do. (with examples)
- Competitive salary and founding-team equity.
- Unlimited tokens. Use whatever you want, as much as you want.
- A healthy budget for tools, monitors, laptop, and anything you need to do your best work.
We need to keep the examples about team members? The sentence includes examples: "One started coding at 11 and shipped an app with 6M+ downloads in high school. One got into CS engineering at 14 and has been working on distributed systems for 8+ years. One's an ex-founder who took a company to 1.2M users and $300M+ in transactions." Those are details about the team. Should we keep them? Yes, preserve all substantive information. So we can include them as part of that benefit item, maybe as a sub-sentence.
Thus benefit item: "You'd be surrounded by people who are absurdly good at what they do: one started coding at 11 and shipped an app with 6M+ downloads in high school; one got into CS engineering at 14 and has been working on distributed systems for 8+ years; one's an ex-founder who took a company to 1.2M users and $300M+ in transactions."
Now for Requirements list items: Let's parse "Who you are" paragraph:
"You have taste.
You own things end-to-end.
You think like a PM.
You notice the extra click, the label doing two jobs, the feature that shipped but isn't really done.
AI-pilled and restlessly curious.
Rive, Spline, Paper, Reve, Claude design, whatever dropped last week, you've already tried it.
You're a Figma expert.
You love micro-interactions.
You've probably built parts of a design system, or at least felt the pain of not having one.
Resourceful.
When you need an illustrator, motion designer, or freelancer, you find them and direct them well.
Bonus: you vibe coded or shipped a side project."
We can make each bullet a list item. Keep the bonus as separate item.
Now About the role paragraph: We need to extract the "About" section: from "About We're building..." up to before "Who you are". Let's copy that text exactly, but we need to ensure we don't include the "About" label? The heading will be
About the role
. Then with the prose.
The About text: "We're building the future of storytelling and video editing. We're a small team that moves fast and builds things we're proud of. We care obsessively about taste: in design, in product, in every detail. We're solving these hard problems. We're backed by a Tier-1 global fund, YC, and founders of billion dollar companies. Design Video is the most powerful way humans tell stories. It always has been. But creating it today is still painfully hard. Fragmented tools, steep learning curves, and workflows that get in the way of the actual creative work. We're building Cardboard to change that. As our founding designer, you'll shape not just how the product looks, but how it works. You think product first and push back when something doesn't serve the user, and think through every user flow before a component gets shipped. In our team, everyone has incredible speed, taste, and care that they put into their work. You'll often see people coming up with micro-interactions nobody asked for and losing sleep over things that feel slightly off by a sheer two pixels. Your job is to accelerate and harness that energy to make sure everything we build feels cohesive and intentional. You will Own product design end to end: flows, UI, prototypes, and everything in between. Adv
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to parse the posting and decide which sections to include. The posting text: "About We're building the future of storytelling and video editing. We're a small team that moves fast and builds things we're proud of. We care obsessively about taste: in design, in product, in every detail. We're solving these hard problems. We're backed by a Tier-1 global fund, YC, and founders of billion dollar companies. Design Video is the most powerful way humans tell stories. It always has been. But creating it today is still painfully hard. Fragmented tools, steep learning curves, and workflows that get in the way of the actual creative work. We're building Cardboard to change that. As our founding designer, you'll shape not just how the product looks, but how it works. You think product first and push back when something doesn't serve the user, and think through every user flow before a component gets shipped. In our team, everyone has incredible speed, taste, and care that they put into their work. You'll often see people coming up with micro-interactions nobody asked for and losing sleep over things that feel slightly off by a sheer two pixels. Your job is to accelerate and harness that energy to make sure everything we build feels cohesive and intentional. You will Own product design end to end: flows, UI, prototypes, and everything in between. Advocate for the user in every room like a PM does. Work closely with founders, engineering, and growth. Build a design system. Make something people love. Who you are You have taste. You own things end-to-end. You think like a PM. You notice the extra click, the label doing two jobs, the feature that shipped but isn't really done. AI-pilled and restlessly curious. Rive, Spline, Paper, Reve, Claude design, whatever dropped last week, you've already tried it. You're a Figma expert. You love micro-interactions. You've probably built parts of a design system, or at least felt the pain of not having one. Resourceful. When you need an illustrator, motion designer, or freelancer, you find them and direct them well. Bonus: you vibe coded or shipped a side project. What you get You'd be surrounded by people who are absurdly good at what they do. One started coding at 11 and shipped an app with 6M+ downloads in high school. One got into CS engineering at 14 and has been working on distributed systems for 8+ years. One's an ex-founder who took a company to 1.2M users and $300M+ in transactions. That's the team. We're looking for someone who'll raise the bar on the creative side the way we have on the technical and business side. Apart from that you'd get: Competitive salary and founding-team equity. Unlimited tokens. Use whatever you want, as much as you want. A healthy budget for tools, monitors, laptop, and anything you need to do your best work. Share: Your portfolio and resume. Your favorite product and one sentence on why. One piece of work that you're proud of. Optional: if you'd like, record and send us a quick video : )" We need to remove application instructions: "Share: Your portfolio and resume. Your favorite product and one sentence on why. One piece of work that you're proud of. Optional: if you'd like, record and send us a quick video : )" Those are application instructions, so remove them. Also remove any boilerplate like "About We're building..." but we keep the content. We need sections: About (maybe "About the role"? but heading must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can use other headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. But we can also use other headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those exact headings if we have content for those categories. The posting has sections: About (description of company and role), Who you are (requirements/qualifications/skills), What you get (benefits). So we can map:
- About the role: corresponds to the "About" paragraph describing role and company.
- Requirements/Qualifications/Skills: "Who you are" includes qualifications, skills, traits.
- Benefits: "What you get" includes competitive salary, founding-team equity, unlimited tokens, budget for tools, etc.
We should not include Pay or Schedule sections unless explicitly stated. The posting mentions "Competitive salary and founding-team equity." That's compensation but not explicit salary number. It's still a benefit/compensation. Should we create a Pay section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive salary and founding-team equity." That's about pay/compensation. However they also list benefits like unlimited tokens, budget for tools. Could combine into Benefits section. The instruction says prefer a few substantive sections over many thin ones. So we could have Benefits section covering salary, equity, tokens, budget. No separate Pay needed.
Thus we will output:
About the role
About the role
... (the about paragraph)
Requirements
- ... list items from Who you are
- for any list of duties/requirements/benefits. The "Who you are" is not explicitly a list but contains multiple bullet-like statements separated by periods. We could treat each distinct requirement as a list item. However we must not invent or summarize away detail. If we convert sentences to list items, we preserve the detail. That's acceptable.
Similarly for Benefits: we have "Competitive salary and founding-team equity. Unlimited tokens. Use whatever you want, as much as you want. A healthy budget for tools, monitors, laptop, and anything you need to do your best work." Also maybe mention "You'd be surrounded by people who are absurdly good at what they do..." that's more about team, not a benefit per se but could be part of Benefits? Actually that's describing team, could be part of About? But it's in "What you get" section after describing team. It says "Apart from that you'd get:" then list. So the team description is part of what you get? It says "You'd be surrounded by people who are absurdly good at what they do." That's a benefit. So we can include that as a benefit item.
Thus Benefits list items:
- You'd be surrounded by people who are absurdly good at what they do. (with examples)
- Competitive salary and founding-team equity.
- Unlimited tokens. Use whatever you want, as much as you want.
- A healthy budget for tools, monitors, laptop, and anything you need to do your best work.
We need to keep the examples about team members? The sentence includes examples: "One started coding at 11 and shipped an app with 6M+ downloads in high school. One got into CS engineering at 14 and has been working on distributed systems for 8+ years. One's an ex-founder who took a company to 1.2M users and $300M+ in transactions." Those are details about the team. Should we keep them? Yes, preserve all substantive information. So we can include them as part of that benefit item, maybe as a sub-sentence.
Thus benefit item: "You'd be surrounded by people who are absurdly good at what they do: one started coding at 11 and shipped an app with 6M+ downloads in high school; one got into CS engineering at 14 and has been working on distributed systems for 8+ years; one's an ex-founder who took a company to 1.2M users and $300M+ in transactions."
Now for Requirements list items: Let's parse "Who you are" paragraph:
"You have taste.
You own things end-to-end.
You think like a PM.
You notice the extra click, the label doing two jobs, the feature that shipped but isn't really done.
AI-pilled and restlessly curious.
Rive, Spline, Paper, Reve, Claude design, whatever dropped last week, you've already tried it.
You're a Figma expert.
You love micro-interactions.
You've probably built parts of a design system, or at least felt the pain of not having one.
Resourceful.
When you need an illustrator, motion designer, or freelancer, you find them and direct them well.
Bonus: you vibe coded or shipped a side project."
We can make each bullet a list item. Keep the bonus as separate item.
Now About the role paragraph: We need to extract the "About" section: from "About We're building..." up to before "Who you are". Let's copy that text exactly, but we need to ensure we don't include the "About" label? The heading will be
About the role
. Thenwith the prose. The About text: "We're building the future of storytelling and video editing. We're a small team that moves fast and builds things we're proud of. We care obsessively about taste: in design, in product, in every detail. We're solving these hard problems. We're backed by a Tier-1 global fund, YC, and founders of billion dollar companies. Design Video is the most powerful way humans tell stories. It always has been. But creating it today is still painfully hard. Fragmented tools, steep learning curves, and workflows that get in the way of the actual creative work. We're building Cardboard to change that. As our founding designer, you'll shape not just how the product looks, but how it works. You think product first and push back when something doesn't serve the user, and think through every user flow before a component gets shipped. In our team, everyone has incredible speed, taste, and care that they put into their work. You'll often see people coming up with micro-interactions nobody asked for and losing sleep over things that feel slightly off by a sheer two pixels. Your job is to accelerate and harness that energy to make sure everything we build feels cohesive and intentional. You will Own product design end to end: flows, UI, prototypes, and everything in between. Adv