Product Designer, Growth Acquisition

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No metadata like Job ID. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The first paragraph after "The role". Actually there is a description: "We are looking for a Senior Product Designer to join our Acquisition team and help us evolve and rethink what a modern web experience can be." etc. That's the role description. - Responsibilities: The bullet list under "What you will do". That's responsibilities. - Requirements / Qualifications / Skills: The "What we are looking for" list includes experience, portfolio, systems mindset, etc. Also "You probably have:" list. Also "You do not need to be the deepest specialist..." but that's not a requirement. Also "How you think" maybe not a requirement but could be part of qualifications. Also "What success looks like" maybe not a requirement. Also "Not required" section. We need to decide which sections to include: About the role, Responsibilities, Requirements (maybe combine qualifications and skills), Benefits, Pay. Schedule not mentioned. So we omit Schedule. We must not include sections with filler like "commensurate with experience". Not present. We need to include Pay: they gave salary range SEK 65,000–SEK 82,000 per month. Also mention compensation details. So we include Pay section. Benefits: they mention comprehensive benefits package, link, also mention pension contributions, leadership program, etc. So we include Benefits. We must not include navigation/legal etc. Remove AI and Hiring, Culture, etc. Those are boilerplate? They might be considered extra but not required. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI and Hiring, Culture, Privacy Policy are likely boilerplate; we should remove them. Thus final HTML:

About the role

...

then

Responsibilities

...

then

Requirements

...

maybe also Skills separate? Could combine. But we could have Requirements and Skills separate if content distinct. The "What we are looking for" includes experience, portfolio, systems mindset, understanding of responsive design, accessibility, modern web tech, collaborating with developers, communication skills, knowledge of CRO, user behaviour, experimentation, understanding of SEO, experience using qualitative/quantitative insight, curiosity about AI, personalization, agentic experiences, fluent English. That's a mix of qualifications and skills. Could split into Requirements (experience, portfolio, etc.) and Skills (specific abilities). But to keep simple, we can have one section "Requirements" containing all. We also have "How you think" and "What success looks like" maybe not needed. Could omit as they are more about mindset but still substantive. However instruction: Prefer a few substantive sections over many thin ones. Could include them under Requirements or maybe as separate "Mindset" but not a standard heading. We'll stick to standard headings. We need to preserve all substantive information; we must not invent or summarize away detail. So we need to keep the bullet points exactly as given, but we can rephrase? It says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the content verbatim (or close) but not omit any details. However we can format as list items. We must not include duplicated lines. Ensure we don't repeat. Let's extract the "What you will do" bullet points: - Turn customer insight, behavioural data and business opportunities into hypotheses, then design and launch experiments, evaluate the results and use the learning to improve the wider system - Design thoughtful, high-quality web experiences that make complex ideas feel simple - Think in systems rather than isolated pages, creating reusable patterns, components and journeys, and help shape our design system for the web - Design for different audiences, intents and stages of the customer journey, making the experience more adaptive and personalized over time - Collaborate with content and SEO specialists to create content structures that work for people, search engines and AI discovery - Apply CRO principles to landing pages, navigation, messaging, forms and conversion journeys - Work closely with developers to take ideas from concept to live experience, using AI and agentic workflows to explore, create and ship faster - Balance consistency with experimentation, knowing when to use an established pattern and when to challenge it Now "What we are looking for" bullet points (under "You probably have:"): - 5+ years of experience designing websites, digital products or SaaS experiences - A portfolio showing distinctive, thoughtful and commercially effective web design - A systems mindset and experience working with design systems and reusable components - An understanding of responsive design, accessibility and modern web technology - Experience collaborating closely with developers and shipping work into production - Strong communication skills and the confidence to align people across design, marketing, engineering and growth - Good knowledge of CRO, user behaviour and experimentation - An understanding of SEO and how design, information architecture and content structure affect organic discovery - Experience using qualitative and quantitative insight to inform design decisions - Curiosity about AI, personalization and agentic experiences - Fully fluent English, with the ability to improve language, hierarchy and storytelling through design Also earlier: "You are a strong web and product designer with excellent visual craft. You know how to create experiences that feel considered, clear and human. But you also look beneath the surface. You understand that design affects discoverability, comprehension, trust and conversion. You are interested in how content is structured, how people navigate information and why some experiences perform better than others." That's also substantive; could be part of Requirements or a summary. We'll include as paragraph under Requirements maybe. Also "You do not need to be the deepest specialist in SEO, analytics or content. But you need to understand how these disciplines connect and be excited to work across their boundaries." That's also a note; we can include. Also "How you think" bullet points: ask questions etc. Might be considered part of mindset but we could omit to keep sections thin? But it's substantive. However we have limited standard headings; we could include under Requirements as additional paragraph. "What success looks like" bullet points: also substantive. Could be included under Requirements or maybe separate "Expectations". But we only have standard headings; we could include under Requirements as well. "Not required" bullet: "You don't have to know Swedish." That's also substantive but maybe not needed as a requirement; we could include under Requirements as a note. But we must not create sections with filler. Including all these under Requirements may be okay. Now Benefits: They mention: "comprehensive benefits package—learn more about it here: https://www.mentimeter.com/benefits/stockholm." Also later: "At Mentimeter we can offer a diverse and inclusive work environment supported by smart and driven colleagues. We believe in continuous professional development for all of our colleagues and therefore offer access to a leadership program (including external personal coach) and relevant education to ensure that we continue to be state-of-the-art when it comes to innovating and building Mentimeter. Your place will be in a growing company with lots of career opportunities, working on a beloved product used by more than 300 million people. It's not all about work though, we also offer a very healthy view on work-life balance. All of this comes attached with a competitive compensation and benefits package, including pension contributions. Learn more about our benefits by visiting our Benefits & Perks page" We need to preserve all substantive info; we can summarize but not omit details. We'll include a paragraph describing benefits: diverse and inclusive work environment, continuous professional development, leadership program with external personal coach, relevant education, growing company, career opportunities, product used by 300M, healthy work-life balance, competitive compensation and benefits package including pension contributions. Also link to benefits page. Pay: salary range SEK 65,000–SEK 82,000 per month, plus description about fair and transparent compensation, ongoing development conversations, salary evolves. We'll include Pay section with that info. Now we must not include navigation, legal, EEO, etc. So we cut out the AI and Hiring, Culture, Privacy Policy sections. Now produce HTML. Structure:

About the role

... (the paragraph describing role)

Responsibilities

• ...
...

Requirements

... (paragraph about strong web designer, etc.)

• ...
...

... (You do not need to be the deepest specialist...)

... (How you think...)

... (What success looks like...)

... (Not required...)

But we must avoid too many thin sections; but we are using only one Requirements section with multiple paragraphs and lists. That's okay. We need to ensure we don't repeat content. Let's craft. About the role paragraph: Combine the sentences: "We are looking for a Senior Product Designer to join our Acquisition team and help us evolve and rethink what a modern web experience can be. This is not a traditional web designer role. Our ambition is to build an agentic web experience: a website that is increasingly intelligent, adaptive and able to help each visitor find what they need. We want to move beyond static pages and traditional funnels towards experiences that respond to intent, context and behaviour. You will help turn that ambition into something real. We are early in this journey. Much of today's work is improving pages, journeys and experiments, and you will help define what the agentic experience becomes. Our website is often the first touchpoint with Mentimeter. You will work at the intersection of brand, product, UX and growth on mentimeter.com, our most visible surface, where millions of people first meet our brand and start their journey with us. A key part of the role is shaping how we introduce the product: making what Mentimeter does easy to understand, relevant and compelling, and creating clear paths from discovery to trying the product. You will create distinctive, on-brand experiences that combine strong visual craft with thoughtful UX and a growth mindset. The goal is to help the right people discover us, understand our value and take the next meaningful step." That's a lot but we need to preserve all substantive info; we can keep as is. Now Responsibilities list as above. Now Requirements: We'll start with paragraph: "You are a strong web and product designer with excellent visual craft. You know how to create experiences that feel considered, clear and human. But you also look beneath the surface. You understand that design affects discoverability, comprehension, trust and conversion. You are interested in how content is structured, how people navigate information and why some experiences perform better than others." Then list bullet points from "You probably have:" as above. Then paragraph: "You do not need to be the deepest specialist in SEO, analytics or content. But you need to understand how these disciplines connect and be excited to work across their boundaries." Then maybe a paragraph for "How you think": "You ask questions such as: what is the visitor actually trying to accomplish? What information do they need next? How could this become a reusable system instead of another one-off page? What could we learn by shipping this sooner? How do we design an experience that works equally well for people, search engines and AI agents? You care about quality, but you do not hide behind perfection. You are comfortable putting ideas into the world, learning from real behaviour and improving them continuously." Then paragraph for "What success looks like": "You ship strong web experiences frequently, and the quality bar rises with each one. The website becomes more coherent, reusable and scalable because of the systems you design. Visitors understand our value faster, and more