Product Designer | SimpleStudy
for section headings like 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). 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. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to decide which sections to include based on content.
We have:
- About SimpleStudy (company description) – could be "About the role"? Actually "About the role" is typical heading for role description. But we have "About SimpleStudy". Could treat as "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to these headings where appropriate.
We have:
- Role description: "Senior Product Designer" (but we shouldn't repeat title). The content includes "About SimpleStudy" (company), then "What You Are Expected To Do" (responsibilities), "What You Need To Succeed" (requirements/qualifications/skills), "What Would Be a Plus" (nice-to-have), "What You Get" (benefits). Also location, remote, etc.
Thus we can create sections:
About the role
– could contain the company description and maybe location? But "About the role" maybe includes description of role and company. We'll include the SimpleStudy description and location info.
Responsibilities
– list from "What You Are Expected To Do".
Requirements
– maybe combine "What You Need To Succeed" (core requirements). Could also split into Qualifications and Skills but we can just use Requirements.
Skills
– maybe "What Would Be a Plus" as nice-to-have skills.
Benefits
– from "What You Get". Also includes remote Europe, equity, competitive salary, relocation support, etc.
We should not include Pay or Schedule unless explicitly stated. The posting mentions "Competitive salary — no fixed budget, flexible." That's about pay but it's vague. It says "Competitive salary — no fixed budget, flexible." That is somewhat specific? It says competitive salary, but no numbers. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive salary — no fixed budget, flexible." That is a statement about pay, albeit vague. Should we include a Pay section? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive salary, so we could include a Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." Might be better to incorporate pay into Benefits section? But Benefits is separate. The instruction lists Benefits as a possible heading. So we could have Benefits section that includes equity, remote, relocation, competitive salary. Pay could be separate but we could combine. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." Since they state competitive salary, we could create a Pay section with that line. But also they state benefits like equity, remote, relocation support. So we could have Benefits section for those, and Pay section for salary.
But we need to avoid filler like "commensurate with experience". The phrase "Competitive salary — no fixed budget, flexible." is substantive enough.
Schedule: not mentioned. So no Schedule section.
Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay.
But we need to ensure we don't create thin sections. Each should have substantive content.
Let's extract content.
About SimpleStudy:
"SimpleStudy is an AI exam prep platform that students find and choose for themselves. In Some Numbers 1.5M+ students across the UK, Ireland, Brazil, South Africa, and Australia 40–50k new students every week Web, mobile, and desktop apps $4M seed round with investors from Strava, OpenAI, and Meta The traction came fast. Now the company is refounding: rebuilding the brand, the design language, and the product experience from scratch. The product grew like a Jenga tower, one feature on top of another. The job now is to rebuild it as a pyramid. The team is ~30 people, remote with a Lisbon office — lean, product-led, and deliberately not a typical edtech company. You'll report to José, the Founding Designer, and work with him as a partner. José tends to lead early framing and direction. You bring strong craft and take the work to the finish line, in close sync with engineering. You both shape the new design language, and you push back with a better idea when you see one."
We can turn that into prose maybe with some
for numbers? But we can keep as paragraphs.
Location: "Location: Remote, Europe (preferably Western / continental); relocation to Lisbon possible". Could be included in About the role or Benefits.
We'll include location in About the role.
Now Responsibilities (What You Are Expected To Do):
List:
- Shape the new design language and brand: design system, rebrand, and the new mobile app.
- Own the full design process — from an ambiguous problem to a polished, shipped solution.
- Drive the consumer experience: onboarding, social features, retention, and the learning loop.
- Work in close sync with engineers and PM, not as a handoff step - polish the implementation together until it feels right.
- Bring your own initiatives and say "no, but…" when you see a better way.
- Raise the bar for the whole design team.
We'll put each as - inside
.
Requirements (What You Need To Succeed):
List:
- High craft — your visual work is polished and intentional; the details reveal your thinking.
- Storytelling over process — you take an ambiguous problem, frame it, and make it simple. Your portfolio shows artifacts, not diagrams; it has a point of view.
- Consumer instinct — you've shipped B2C products that people chose to use. You understand product metrics and use them as input, but you lead with feel and craft.
- Opinions with backbone — you have a design philosophy, can defend it under pushback, and bring your own initiatives. You don't wait to be told what to build.
- Energy and curiosity — you're an interesting person with a life outside work, and you leave people energised after a conversation.
- English — fluent, written and spoken.
We'll put as .
Skills (What Would Be a Plus):
List:
- A standout specialty: prototyping, illustration, animation, or motion.
- Experience with social or viral product mechanics.
- Background at consumer companies like Spotify or Strava.
- Early-stage or founding designer experience.
- Comfortable in code: prototyping or polishing the front end.
We'll put as .
Benefits (What You Get):
List:
- Build from scratch, at scale — a new design language for a product already used by 1.5M+ students.
- A strong partner - work closely with José, the Founding Designer (ex-Shopify), with direct access to the founders.
- Equity — generous stock options, early enough for them to matter.
- Remote Europe — work from where you choose, with in-person meetups three times a year; relocation support if you want to move to Lisbon.
- Competitive salary — no fixed budget, flexible.
We could split: Competitive salary maybe goes to Pay section. But we can keep it in Benefits. However we also have a Pay section maybe.
Let's decide: We'll create Benefits section for non-salary benefits: Build from scratch, strong partner, equity, remote Europe, relocation support. Then Pay section for Competitive salary.
Thus Benefits:
- Build from scratch, at scale — a new design language for a product already used by 1.5M+ students.
- A strong partner - work closely with José, the Founding Designer (ex-Shopify), with direct access to the founders.
- Equity — generous stock options, early enough for them to matter.
- Remote Europe — work from where you choose, with in-person meetups three times a year; relocation support if you want to move to Lisbon.
Pay:
- Competitive salary — no fixed budget, flexible.
Now we need to ensure we don't include any boilerplate like "How To Apply", "The vacancy is proudly presented by the hirehire recruiting agency." etc. Remove those.
Also remove duplicated lines.
Now produce HTML fragment:
About the role
SimpleStudy is an AI exam prep platform that students find and choose for themselves. 1.5M+ students across the UK, Ireland, Brazil, South Africa, and Australia; 40–50k new students every week; web, mobile, and desktop apps; $4M seed round with investors from Strava, OpenAI, and Meta. The traction came fast. Now the company is refounding: rebuilding the brand, the design language, and the product experience from scratch. The product grew like a Jenga tower, one feature on top of another. The job now is to rebuild it as a pyramid. The team is ~30 people, remote with a Lisbon office — lean, product-led, and deliberately not a typical edtech company. You'll report to José, the Founding Designer, and work with him as a partner. José tends to lead early framing and direction. You bring strong craft and take the work to the finish line, in close sync with engineering. You both shape the new design language, and you push back with a better idea when you see one. Location: Remote, Europe (preferably Western / continental); relocation to Lisbon possible.
Then Responsibilities:
Responsibilities
- Shape the new design language and brand: design system, rebrand, and the new mobile app.
- Own the full design process — from an ambiguous problem to a polished, shipped solution.
- Drive the consumer experience: onboarding, social features, retention, and the learning loop.
- Work in close sync with engineers and PM, not as a handoff step — polish the implementation together until it feels right.
- Bring your own initiatives and say "no, but…" when you see a better way.
- Raise the bar for the whole design team.
Requirements:
Requirements
- High craft — your visual work is polished and intentional; the details reveal your thinking.
- Storytelling over process — you take an ambiguous problem, frame it, and make it simple. Your portfolio shows artifacts, not diagrams; it has a
- 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. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - About SimpleStudy (company description) – could be "About the role"? Actually "About the role" is typical heading for role description. But we have "About SimpleStudy". Could treat as "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to these headings where appropriate. We have: - Role description: "Senior Product Designer" (but we shouldn't repeat title). The content includes "About SimpleStudy" (company), then "What You Are Expected To Do" (responsibilities), "What You Need To Succeed" (requirements/qualifications/skills), "What Would Be a Plus" (nice-to-have), "What You Get" (benefits). Also location, remote, etc. Thus we can create sections:
About the role
– could contain the company description and maybe location? But "About the role" maybe includes description of role and company. We'll include the SimpleStudy description and location info.Responsibilities
– list from "What You Are Expected To Do".Requirements
– maybe combine "What You Need To Succeed" (core requirements). Could also split into Qualifications and Skills but we can just use Requirements.Skills
– maybe "What Would Be a Plus" as nice-to-have skills.Benefits
– from "What You Get". Also includes remote Europe, equity, competitive salary, relocation support, etc. We should not include Pay or Schedule unless explicitly stated. The posting mentions "Competitive salary — no fixed budget, flexible." That's about pay but it's vague. It says "Competitive salary — no fixed budget, flexible." That is somewhat specific? It says competitive salary, but no numbers. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive salary — no fixed budget, flexible." That is a statement about pay, albeit vague. Should we include a Pay section? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive salary, so we could include a Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." Might be better to incorporate pay into Benefits section? But Benefits is separate. The instruction lists Benefits as a possible heading. So we could have Benefits section that includes equity, remote, relocation, competitive salary. Pay could be separate but we could combine. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." Since they state competitive salary, we could create a Pay section with that line. But also they state benefits like equity, remote, relocation support. So we could have Benefits section for those, and Pay section for salary. But we need to avoid filler like "commensurate with experience". The phrase "Competitive salary — no fixed budget, flexible." is substantive enough. Schedule: not mentioned. So no Schedule section. Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. But we need to ensure we don't create thin sections. Each should have substantive content. Let's extract content. About SimpleStudy: "SimpleStudy is an AI exam prep platform that students find and choose for themselves. In Some Numbers 1.5M+ students across the UK, Ireland, Brazil, South Africa, and Australia 40–50k new students every week Web, mobile, and desktop apps $4M seed round with investors from Strava, OpenAI, and Meta The traction came fast. Now the company is refounding: rebuilding the brand, the design language, and the product experience from scratch. The product grew like a Jenga tower, one feature on top of another. The job now is to rebuild it as a pyramid. The team is ~30 people, remote with a Lisbon office — lean, product-led, and deliberately not a typical edtech company. You'll report to José, the Founding Designer, and work with him as a partner. José tends to lead early framing and direction. You bring strong craft and take the work to the finish line, in close sync with engineering. You both shape the new design language, and you push back with a better idea when you see one." We can turn that into prosemaybe with some
- for numbers? But we can keep as paragraphs.
Location: "Location: Remote, Europe (preferably Western / continental); relocation to Lisbon possible". Could be included in About the role or Benefits.
We'll include location in About the role.
Now Responsibilities (What You Are Expected To Do):
List:
- Shape the new design language and brand: design system, rebrand, and the new mobile app.
- Own the full design process — from an ambiguous problem to a polished, shipped solution.
- Drive the consumer experience: onboarding, social features, retention, and the learning loop.
- Work in close sync with engineers and PM, not as a handoff step - polish the implementation together until it feels right.
- Bring your own initiatives and say "no, but…" when you see a better way.
- Raise the bar for the whole design team.
We'll put each as
- inside
- .
Requirements (What You Need To Succeed):
List:
- High craft — your visual work is polished and intentional; the details reveal your thinking.
- Storytelling over process — you take an ambiguous problem, frame it, and make it simple. Your portfolio shows artifacts, not diagrams; it has a point of view.
- Consumer instinct — you've shipped B2C products that people chose to use. You understand product metrics and use them as input, but you lead with feel and craft.
- Opinions with backbone — you have a design philosophy, can defend it under pushback, and bring your own initiatives. You don't wait to be told what to build.
- Energy and curiosity — you're an interesting person with a life outside work, and you leave people energised after a conversation.
- English — fluent, written and spoken.
We'll put as
- Shape the new design language and brand: design system, rebrand, and the new mobile app.
- Own the full design process — from an ambiguous problem to a polished, shipped solution.
- Drive the consumer experience: onboarding, social features, retention, and the learning loop.
- Work in close sync with engineers and PM, not as a handoff step — polish the implementation together until it feels right.
- Bring your own initiatives and say "no, but…" when you see a better way.
- Raise the bar for the whole design team.
- High craft — your visual work is polished and intentional; the details reveal your thinking.
- Storytelling over process — you take an ambiguous problem, frame it, and make it simple. Your portfolio shows artifacts, not diagrams; it has a
- .
Skills (What Would Be a Plus):
List:
- A standout specialty: prototyping, illustration, animation, or motion.
- Experience with social or viral product mechanics.
- Background at consumer companies like Spotify or Strava.
- Early-stage or founding designer experience.
- Comfortable in code: prototyping or polishing the front end.
We'll put as
- .
Benefits (What You Get):
List:
- Build from scratch, at scale — a new design language for a product already used by 1.5M+ students.
- A strong partner - work closely with José, the Founding Designer (ex-Shopify), with direct access to the founders.
- Equity — generous stock options, early enough for them to matter.
- Remote Europe — work from where you choose, with in-person meetups three times a year; relocation support if you want to move to Lisbon.
- Competitive salary — no fixed budget, flexible.
We could split: Competitive salary maybe goes to Pay section. But we can keep it in Benefits. However we also have a Pay section maybe.
Let's decide: We'll create Benefits section for non-salary benefits: Build from scratch, strong partner, equity, remote Europe, relocation support. Then Pay section for Competitive salary.
Thus Benefits:
- Build from scratch, at scale — a new design language for a product already used by 1.5M+ students.
- A strong partner - work closely with José, the Founding Designer (ex-Shopify), with direct access to the founders.
- Equity — generous stock options, early enough for them to matter.
- Remote Europe — work from where you choose, with in-person meetups three times a year; relocation support if you want to move to Lisbon.
Pay:
- Competitive salary — no fixed budget, flexible.
Now we need to ensure we don't include any boilerplate like "How To Apply", "The vacancy is proudly presented by the hirehire recruiting agency." etc. Remove those.
Also remove duplicated lines.
Now produce HTML fragment:
About the role
SimpleStudy is an AI exam prep platform that students find and choose for themselves. 1.5M+ students across the UK, Ireland, Brazil, South Africa, and Australia; 40–50k new students every week; web, mobile, and desktop apps; $4M seed round with investors from Strava, OpenAI, and Meta. The traction came fast. Now the company is refounding: rebuilding the brand, the design language, and the product experience from scratch. The product grew like a Jenga tower, one feature on top of another. The job now is to rebuild it as a pyramid. The team is ~30 people, remote with a Lisbon office — lean, product-led, and deliberately not a typical edtech company. You'll report to José, the Founding Designer, and work with him as a partner. José tends to lead early framing and direction. You bring strong craft and take the work to the finish line, in close sync with engineering. You both shape the new design language, and you push back with a better idea when you see one. Location: Remote, Europe (preferably Western / continental); relocation to Lisbon possible.
Then Responsibilities:Responsibilities
Requirements
- inside