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

Werken bij Belsimpel is the hiring brand of Belsimpel, a leading Dutch telecom and mobile retail platform known for clean, user-first product experiences. The company sells mobile phones, SIM cards, and subscription plans, and its design team is known for building e-commerce flows that reduce friction for customers comparing and buying devices online.

As a Product Designer here, you would typically own work end-to-end: from user research and discovery through wireframing, prototyping, and design-system contributions. The team operates in a commercially driven environment where design decisions are expected to connect clearly to business outcomes.

Candidates report the interview process typically includes a portfolio review call, one or two design-focused rounds, and a final culture or values discussion. All rounds are conducted in English. Interviewers tend to evaluate design thinking and communication as closely as visual craft.

Of the 393 Product Designer roles tracked across India as of July 2026, 57 are currently open at Werken bij Belsimpel, making it one of the more active hirers in this space right now.

1. Walk us through a project in your portfolio where you improved a checkout or purchase flow. What was the problem, and how did you measure success?

1. Belsimpel customers compare mobile deals across many options. How would you design a comparison experience that helps users decide quickly without feeling overwhelmed?

1. Describe a time you had to simplify a complex product offering (such as plans, add-ons, or device compatibility) for a non-technical user. How did you approach it?

1. How do you work with product managers when business goals and user needs point in different directions? Give a specific example.

1. Tell us about your experience contributing to or maintaining a design system. How did you manage consistency across a product at scale?

1. How do you conduct user research when timelines are short? What shortcuts do you accept, and which do you refuse?

1. Have you ever designed for a high-traffic or high-stakes conversion moment, like a promotional sale? What did you learn from that experience?

1. How do you handle feedback from engineers who say your design is too complex to build as specified?

1. Describe your process for designing for accessibility. Can you give a concrete example from a past project?

1. If you looked at the Belsimpel product detail page with fresh eyes, what is the first thing you would investigate and why?

1. How do you prioritise which usability issues to fix when there are more problems than your sprint can handle?

1. Tell us about a design decision you made that turned out to be wrong. How did you find out, and what did you do next?

Q: Walk us through a project where you improved a checkout or purchase flow.

*Situation:* I was at a mid-sized e-commerce platform where cart abandonment was a known problem, but no one had mapped exactly where users were dropping off.

*Task:* My goal was to reduce drop-off specifically at the payment step, working within a short sprint window and no budget for external research.

*Action:* I reviewed session recordings and found that users with prepaid cards were hitting a confusing error state with no recovery path. I redesigned the error message to explain the problem in plain language, added a 'try another payment method' shortcut, and tested two variants with a small group of internal users before handoff to engineering.

*Result:* After the fix shipped, the PM confirmed a meaningful drop in payment-step abandonment in the following review cycle. The error-state pattern became a template for how the team handled similar moments across the checkout flow.

---

Q: How do you work with product managers when goals and user needs conflict?

*Situation:* At a previous role, the PM wanted to add a promotional banner to the cart page. User research showed most customers were ignoring it or finding it distracting.

*Task:* I needed to push back without blocking the underlying business goal, which was to increase add-on purchases.

*Action:* I put together a short document with the behavioural data and proposed an alternative: a contextual upsell card that appeared only after the user had confirmed their main item. I framed it as a way to hit the same metric with less friction to the primary purchase path.

*Result:* The PM agreed to run a test. The contextual card outperformed the banner, which was then dropped. The episode also helped us build a shared habit of grounding design decisions in observed behaviour rather than assumption.

---

Q: Tell us about a design decision you made that turned out to be wrong.

*Situation:* I redesigned an onboarding flow for a SaaS product. Benchmark data from similar tools suggested that removing the setup wizard would reduce cognitive load and get users to value faster.

*Task:* I owned the full onboarding experience, and the goal was to reduce the time to a user's first meaningful action in the product.

*Action:* I stripped the wizard to a single welcome screen and replaced step-by-step guidance with contextual tooltips. Internal prototype testing felt encouraging.

*Result:* After launch, activation rates dropped. Exit surveys showed new users felt lost without structured steps. I reintroduced a lightweight wizard with a 'skip for now' option, and activation recovered. The lesson: what feels like unnecessary friction to a designer can feel like essential guidance to someone using the product for the first time.

For portfolio and process questions, lead with the problem before the solution. Interviewers at companies like Belsimpel want to see that you start from user and business context, not from a visual idea. A reliable structure: the goal you were given, the gap you discovered in research, the choices you made and why, and what you learned from the outcome.

For conflict and collaboration questions, resist framing yourself as always right. Show that you use data and structured conversation to resolve disagreements. Phrases like 'I proposed testing both approaches' or 'I pulled the session data to check which assumption held up' tend to land well because they show process rather than opinion.

For hypothetical redesign questions (like 'how would you look at our product detail page'), resist jumping to solutions. Walk the interviewer through what you would investigate first: what the current metrics suggest, what user jobs-to-be-done are at stake, and what constraints you would need to understand. This signals design maturity more than a quick idea does.

For technical collaboration and handoff questions, be honest about your actual involvement level. Describe how you write clear specs, flag open questions early, and stay available during the build phase. If you use tools like dev mode or design tokens to support handoff, mention them in context rather than as a feature list.

Based on what candidates report from product companies in the e-commerce and telecom space, Belsimpel interviewers typically look for a handful of clear signals.

Clear thinking over polished slides. Interviewers want to understand why you made a design decision, not just what it looks like. A strong portfolio explanation beats a visually impressive one with thin reasoning behind it.

Ownership without ego. The team tends to value designers who take responsibility for outcomes (including failures) and who involve engineers and PMs throughout the process rather than treating handoff as the end of their job.

Commercial awareness. Belsimpel is a retail platform. Answers that connect design decisions to conversion, retention, or user trust tend to resonate more than purely user-centred arguments that ignore business constraints entirely.

Simplicity as a core skill. The company's entire brand proposition is making telecom decisions easy for customers. Candidates who can show they make things simpler, not just cleaner, tend to stand out.

Clear English communication. Since the company is Dutch-led and hires internationally, being articulate under pressure matters as much as the portfolio itself. Candidates report that interviewers pay close attention to how clearly you explain your thinking, not just what you show on screen.

Step 1: Understand the product. Spend time on the Belsimpel website and app. Go through the full purchase journey for a phone and a SIM plan. Note where the experience feels intuitive and where it creates doubt. These observations give you real, specific material to reference if you are asked a hypothetical redesign question.

Step 2: Curate, do not collect. Pick two or three projects that show end-to-end design work, ideally including one transactional or e-commerce flow and one research-led project. For each, prepare a brief spoken walkthrough covering the problem, your process, and the outcome. A few strong, well-explained case studies beat a long portfolio with shallow coverage.

Step 3: Practise out loud. Run through the questions in this guide with a friend or record yourself. Check whether you lead with context (the problem) or skip straight to the solution. Adjust until context comes first naturally.

Step 4: Prepare your own questions. Good topics include how the design team is structured, how design gets prioritised against engineering capacity, and how the company approaches user research. Thoughtful questions signal genuine interest in the role.

Step 5: Sort your tech. Most rounds are conducted remotely. Test screen-sharing so your portfolio loads cleanly, your audio is clear, and you are not hunting for files mid-call.

Showing too many projects. Candidates often try to impress with volume. A handful of well-explained case studies beats a long list of shallow ones. Interviewers can absorb only a few deep stories in a single session.

Starting with the solution. Opening with 'I redesigned the checkout' without explaining what was failing users and why it mattered makes the work hard to evaluate. Always start with the problem and the evidence that confirmed it was worth solving.

Vague impact claims. Saying 'users loved it' or 'the design was well-received' without any supporting signal is easy to dismiss. If you have no metrics, describe something observable: 'the support team stopped getting those calls' or 'the PM shipped it without requesting further revisions.'

Downplaying failures. When asked about a wrong decision, candidates often describe a very minor issue. Interviewers respect honest accounts of real mistakes far more than carefully managed answers. Describe what actually went wrong and what you changed because of it.

Ignoring the business context. Belsimpel is a commercial product company. Answers that are entirely user-focused without acknowledging business constraints can come across as naive. The strongest answers hold both in view at the same time.

Not asking questions. Candidates who ask nothing at the end signal low curiosity or low interest. Prepare at least two genuine questions about the team or the product direction.