Product Manager Intern

We need to output HTML fragment with sections: About the role? The posting includes description of company, role responsibilities, qualifications, benefits, etc. Need to follow rules: 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. We need to parse the posting. The posting text: "Aircall is a unicorn, AI-powered customer communications platform used by 22,000+ companies worldwide to drive revenue, resolve issues faster, and scale customer-facing teams. We’re redefining customer communications by bringing voice, SMS, WhatsApp, and AI together into one seamless workspace. Our momentum comes from a simple idea: help teams work smarter, not harder. Aircall’s AI Voice Agent automates routine calls, AI Assist streamlines post-call work, and AI Assist Pro delivers real-time guidance so people can do their best work. The result is higher revenue, faster resolutions, and teams that scale with confidence. Aircall is headquartered in Paris, our European HQ, with a strong North American presence anchored in Seattle, our North American HQ, and teams across Madrid, London, Berlin, San Francisco, New York City, Sydney, and Mexico City. We’ve built a product customers love and a business that’s scaling quickly, backed by world-class investors and driven by rapid AI innovation across multiple product lines. At Aircall, you’ll join a company in motion. We’re ambitious, product-driven, and execution-focused, with visible impact, fast decisions, and real growth. How we work at Aircall: We’re customer-obsessed, data-driven, and focused on delivering meaningful outcomes. We value ownership, continuous learning, and thoughtful speed. If you thrive in a collaborative, fast-moving environment where trust and impact matter, you’ll feel at home here. Meet directly with customers to gather feedback, discuss pain points, and validate potential improvements.Synthesize qualitative and quantitative feedback into clear opportunities, and translate them into product recommendations that shape the roadmap.Partner with Product, Design and Engineering to define requirements and prioritize enhancements that improve user experience and agent efficiency.Align dependencies and facilitate tradeoff discussions with stakeholders across product areas.Follow the development cycle end-to-end to ensure we ship the best possible experience in an agile manner.Contribute to Knowledge Base articles, FAQs and product demos to support launches and go-to-market.Gather and synthesize usage and performance data from multiple sources (interaction logs, analytics, customer feedback).Identify patterns, bottlenecks and opportunities in product workflows, and turn them into more intuitive experiences.Use modern data tools and, where relevant, AI/LLM-based approaches to enrich analysis and uncover deeper insights.Research, recommend and help implement tools and frameworks for tracking key product metrics (e.g. latency, reliability, usability).Collaborate with teams to define and monitor KPIs aligned with product goals.Help set up dashboards, alerts and reports to support ongoing performance evaluation and decision-making.[Mandatory] Master's student (last year) from an engineering or business school.Fluent in English.Comfortable running customer conversations — asking good questions, listening carefully, and following up.Comfortable working across teams, aligning dependencies and navigating tradeoffs with peers and stakeholders.A first experience (internship) in a product or project team is a plus.Knowledge of SaaS, product development cycles, and our business is a plus. Why Join us? 🚀 Key moment to join Aircall in terms of growth and opportunities 💆♀️ Our people matter, work-life balance is important at Aircall 📚 Fast-learning environment, entrepreneurial and strong team spirit 🌍 45+ Nationalities: cosmopolite & multi-cultural mindset 💶 Competitive salary package & benefits De&I Statement At Aircall, we believe diversity, equity and inclusion – irrespective of origins, identity, background and orientations – are core to our journey. We pride ourselves on promoting active inclusion within our business to foster a strong sense of belonging for all. We’re working to create a place filled with diverse people who can enrich and learn from one another. We’re committed to ensuring that everyone not only has a seat at the table but is valued and respected at it by providing equal opportunities to develop and thrive. We will constantly challenge ourselves to make sure that we live up to our ambitions around diversity, equity and inclusion, and keep this conversation open. Above all else, we understand and acknowledge that we have work to do and much to learn. Want to know more about candidate privacy? Find our Candidate Privacy Notice here. We may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us." We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The De&I statement is likely EEO boilerplate; we should remove it. Also the candidate privacy notice and AI tools note may be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The De&I statement is EEO, so remove. The candidate privacy notice and AI tools note might be considered legal boilerplate; likely remove. Also the "Why Join us?" section includes bullet points with emojis; those are benefits. We need to include Benefits section if posting actually states them. It does: "Key moment to join Aircall in terms of growth and opportunities", "Our people matter, work-life balance is important at Aircall", "Fast-learning environment, entrepreneurial and strong team spirit", "45+ Nationalities: cosmopolite & multi-cultural mindset", "Competitive salary package & benefits". Those are benefits. So we should create a Benefits section with those items as list. Also we have responsibilities: many bullet-like sentences after "Meet directly with customers..." etc. Those are responsibilities/duties. We should put them under Responsibilities heading as

  • . Qualifications: The mandatory and plus items: "[Mandatory] Master's student (last year) from an engineering or business school.Fluent in English.Comfortable running customer conversations — asking good questions, listening carefully, and following up.Comfortable working across teams, aligning dependencies and navigating tradeoffs with peers and stakeholders.A first experience (internship) in a product or project team is a plus.Knowledge of SaaS, product development cycles, and our business is a plus." We need to separate mandatory vs plus? The rules: Use
    • for any list of duties/requirements/benefits. Could have Requirements section for mandatory, and maybe Skills or Qualifications for plus? The headings list includes Requirements, Qualifications, Skills. We can decide: Use Requirements for mandatory, Qualifications for plus? Or combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine mandatory and plus into one Requirements section? But we need to preserve all info. Could have Requirements (mandatory) and then a separate "Preferred qualifications" but that might be thin. Better to have one Requirements section with both mandatory and plus, maybe differentiate with text. But we need to follow headings list: we can use Requirements for mandatory, and Skills for plus? However plus includes knowledge of SaaS, product development cycles, and business - that's more like skills. The first experience internship is a plus - could be experience. Could treat as Skills. Let's decide: Use Requirements for mandatory items. Use Skills for plus items. Or use Qualifications for plus. The headings list includes Qualifications, Skills. We'll use Requirements for mandatory, Skills for plus. Also we need About the role section: maybe a brief paragraph summarizing role? The posting includes description of company and role? The first paragraph is about company; then "How we work at Aircall:" then responsibilities. There's no explicit "About the role" paragraph besides the company description. Could treat the initial company description as About the role? But the instruction says 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. The company description is not a heading; we could put it under About the role as prose. However the posting does not have a distinct "About the role" heading; but we can create one if we have substantive content. The company description is substantive. So we can have

      About the role

      with a paragraph summarizing the company and role context. Alternatively we could skip About the role and go straight to Responsibilities. But the instruction says prefer a few substantive sections over many thin ones. Having About the role may be okay. Let's structure:

      About the role

      [company description paragraph]

      Responsibilities

      • Meet directly with customers to gather feedback, discuss pain points, and validate potential improvements.
      • Synthesize qualitative and quantitative feedback into clear opportunities, and translate them into product recommendations that shape the roadmap.
      • Partner with Product, Design and Engineering to define requirements and prioritize enhancements that improve user experience and agent efficiency.
      • Align dependencies and facilitate tradeoff discussions with stakeholders across product areas.
      • Follow the development cycle end-to-end to ensure we ship the best possible experience in an agile manner.
      • Contribute to Knowledge Base articles, FAQs and product demos to support launches and go-to-market.
      • Gather and synthesize usage and performance data from multiple sources (interaction logs, analytics, customer feedback).
      • Identify patterns, bottlenecks and opportunities in product workflows, and turn them into more intuitive experiences.
      • Use modern data tools and, where relevant, AI/LLM-based approaches to enrich analysis and uncover deeper insights.
      • Research, recommend and help implement tools and frameworks for tracking key product metrics (e.g. latency, reliability, usability).
      • Collaborate with teams to define and monitor KPIs aligned with product goals.
      • Help set up dashboards, alerts and reports to support ongoing performance evaluation and decision-making.

      Requirements

      • Master's student (last year) from an engineering or business school.
      • Fluent in English.
      • Comfortable running customer conversations — asking good questions, listening carefully, and following up.
      • Comfortable working across teams, aligning dependencies and navigating tradeoffs with peers and stakeholders.

      Skills

      • First experience (internship) in a product or project team (plus).
      • Knowledge of SaaS, product development cycles, and our business (plus).

      Benefits

      • Key moment to join Aircall in terms of growth