Werken bij Belsimpel Product Manager Interview: Questions, Experience & Prep (2026)

Belsimpel is a Dutch telecom and electronics retailer that helps consumers compare mobile subscriptions, handsets, and accessories in one place. The company operates one of the Netherlands' leading telecom comparison platforms, with product teams responsible for digital journeys from plan discovery through post-purchase support.

With 57 open roles currently listed, the company is actively growing across product and technology. PM interviews at Belsimpel typically cover three areas: product thinking (how you define, prioritise, and measure), cross-functional collaboration (how you work with engineering, design, and commercial teams), and domain fluency (comfort with e-commerce or marketplace dynamics). Candidates report that interviewers value directness, curiosity about users, and comfort with ambiguity over formal framework recitation.

Because Belsimpel is headquartered in the Netherlands, interviews are generally conducted in English. Expect questions that probe your ability to reason through trade-offs clearly. The process typically involves a recruiter conversation, one or two product-focused interviews, and a case study or take-home exercise, though the exact sequence varies by level and team.

These questions reflect patterns candidates report across product and e-commerce roles at telecom-first consumer platforms. Use them to identify where your preparation has gaps.

1. Walk me through how you would improve the plan discovery experience on a telecom comparison platform like Belsimpel.
2. How would you define the north star metric for a subscription marketplace, and what leading indicators would you track alongside it?
3. Price sensitivity is very high in our market. How do you balance simplicity in the user experience with showing enough detail for an informed decision?
4. Tell me about a product decision you made using data that contradicted your initial intuition.
5. Describe a time a feature you owned underperformed after launch. What happened next?
6. How would you reduce cart abandonment in a high-consideration purchase flow, such as selecting and buying a mobile plan?
7. How do you prioritise your roadmap when stakeholder requests clearly exceed team capacity?
8. Walk me through how you would build a retention strategy for customers after they activate a new subscription.
9. A competitor launches a feature that was already on your roadmap. How do you respond?
10. How do you collaborate with engineering when a technical constraint blocks your preferred solution?
11. How do you stay close to user needs between formal research sprints?
12. How would you approach adding a new product category (for example, home broadband) to an existing telecom marketplace?

Q: Tell me about a product decision you made using data that contradicted your initial intuition.

*Situation:* I was PM for a fintech app's loan application flow. My assumption was that adding a progress bar would improve completion because users would feel more guided through a multi-step form.

*Task:* Before committing the sprint to building it, I wanted to validate whether the progress bar would actually address the drop-off we were seeing.

*Action:* I combined session recordings with drop-off data from the existing funnel. The pattern that emerged had nothing to do with progress visibility. Most users were abandoning on the income-declaration step because the field label used jargon they did not recognise. I redirected the sprint to rewriting that label and adding a plain-language tooltip, and shelved the progress bar for a future quarter.

*Result:* Completion on that step improved in a way our analytics team described as statistically meaningful. The progress bar was deprioritised with a clear rationale the team accepted. The takeaway I carry forward: validate the problem before committing to a solution.

---

Q: How do you prioritise your roadmap when stakeholder requests exceed team capacity?

*Situation:* I inherited a backlog with requests from sales, marketing, support, and the founding team, all flagged as urgent, with no shared understanding of how sequencing decisions were made.

*Task:* I needed a transparent, repeatable method that would reduce friction without creating a political problem across those groups.

*Action:* I introduced a lightweight scoring model covering impact on our north star metric, implementation effort, and strategic alignment. I ran a prioritisation session with each stakeholder group, shared the model before the meeting so no one felt ambushed, and documented every decision with its rationale in writing.

*Result:* Pushback dropped noticeably after the first two cycles. Stakeholders whose items did not make the next sprint understood why, and the team benefited from reduced context-switching between competing priorities.

---

Q: Describe a time you reduced drop-off in a checkout or purchase flow.

*Situation:* I was working on an e-commerce platform where funnel data shared by the analytics team showed high abandonment on the payment step.

*Task:* My goal was to identify the real cause and propose a testable fix within a single sprint, without assuming I already knew the answer.

*Action:* I paired session recordings with a short exit survey. The pattern was consistent: users who did not immediately see their preferred payment method assumed it was unavailable and left. I worked with design to reorder payment options by usage frequency and tested a 'most popular' label on the top option in an A/B experiment.

*Result:* The variant improved payment-step completion in our test. We rolled it to all users and monitored for regressions over the following two weeks before closing the experiment.

For 'how would you improve X' questions: Start by clarifying the goal (growth, retention, revenue, or satisfaction). Define the user and their core job to be done. Identify the biggest friction point using data or explicit assumption-mapping. Propose two or three ideas with trade-offs, go deep on one, and describe how you would measure success. Interviewers consistently flag candidates who jump straight to a solution without stating the problem.

For north star and metrics questions: Name one metric that moves when the business is genuinely healthy, not just one that is easy to track. List two or three leading indicators that predict movement in that metric. Explain why you would not rely on a vanity metric. For Belsimpel specifically, thinking about metrics like subscription activations, plan comparison depth, or repeat visit rate within a consideration window shows domain awareness.

For prioritisation questions: Use a simple model covering user impact, business impact, effort, and strategic fit. Avoid scoring that sounds mechanical. Show that you can hold trade-offs clearly in your head and explain your reasoning to a non-technical stakeholder without needing a spreadsheet in front of you.

For cross-functional conflict questions: Use the STAR structure, but make the 'Action' step clearly about listening before acting. Interviewers at product-led companies want to see that you build trust with engineers and designers rather than simply manage them.

For case or take-home exercises: Structure matters more than reaching the 'right' answer. State your assumptions upfront. Walk through your thinking in clear steps. End with a firm recommendation and name the one or two things you would validate before committing resources. Depth in a focused area is more impressive than twelve ideas at surface level.

Clarity over cleverness. Based on what candidates report from similar Dutch product-led companies, interviewers value structured thinking over impressive vocabulary. The ability to explain a complex trade-off to a non-PM stakeholder is treated as a core signal, not a nice-to-have.

Genuine user empathy. Belsimpel is a consumer-facing platform. Interviewers pay close attention to whether your examples show you actually talked to users, rather than relying solely on analytics dashboards and assumption.

Comfort with ambiguity. The telecom comparison space evolves quickly with regulatory shifts, new device launches, and changing consumer habits. Interviewers want evidence that you can make a reasonable call with incomplete information, and that you know how to frame the problem before reaching for a solution.

Commercial awareness. Belsimpel sits at the intersection of consumer experience and commercial partnerships with telecom operators. A PM who understands how marketplace incentives and supplier relationships affect product decisions will stand out from candidates who focus only on UX.

A collaboration track record. Candidates report that every loop includes at least one question probing how you work with engineers and designers. Prepare two or three specific examples that show you as a genuine team player, not just the person who announces final calls.

Week 1: Company and domain research. Use Belsimpel's product directly if you can access it, or study their app store page, reviews, and any publicly available coverage. Map out the core user journey from landing through subscription activation. Note what works well and what you would change, with a reason for each observation. Read what you can find about the Dutch telecom market and how comparison platforms compete in that space.

Week 1 onward: Practise structured answers. Write STAR answers for at least six of the questions listed above. Record yourself speaking each answer out loud. Listen back and cut anything that runs past two minutes. Remove jargon that an engineer or designer would not immediately recognise.

Week 2: Metrics and measurement fluency. Be ready to discuss north star metrics, funnel analysis, A/B testing basics, and retention measurement. You do not need a data science background, but you should speak fluently about what you would measure and why, and be able to push back on metrics that are easy to track but misleading.

Week 2: Prepare your questions. Write four or five thoughtful questions for your interviewers. Good areas: how the product team is structured, how roadmap decisions are made, what the biggest product challenge looks like right now, and how success is defined for PMs at your level. Avoid questions whose answers are already on the careers page.

Before each round: Re-read the job description. Map your experience explicitly to each listed requirement. Go in with two or three examples you are highly confident in, and be ready to stretch those examples across different question types if the conversation calls for it.

Jumping to solutions before defining the problem. The most common error in 'how would you improve X' questions is arriving at a feature idea before stating the user, goal, or current friction. Interviewers notice this immediately.

Being vague about your personal contribution. Every STAR answer should make the 'Action' step clearly about your choices and decisions. Avoid 'we did X' without explaining your specific role in making it happen.

Frameworks without real examples. Dropping terms like 'RICE scoring' or 'jobs-to-be-done' without showing how you applied them in practice reads as surface-level preparation to an experienced interviewer.

Ignoring the commercial side. Candidates who focus only on UX and ignore revenue, margins, or supplier constraints miss a dimension that matters at a marketplace business like Belsimpel.

Asking no questions at the end. No questions signals low interest. Specific questions that reference your research into the company and market show genuine engagement with the role.

Trying to cover everything in a case exercise. If you receive a take-home, rigour in a focused area is more compelling than broad coverage at low depth. Pick your strongest angle and go deep.

Not bridging the domain gap explicitly. If your background is outside telecom or e-commerce, do not leave the interviewer to make the connection. Say it directly: 'I have not worked in telecom before, but the dynamics I dealt with in X are similar because...'