TL;DR

Just Eat Takeaway portfolio interviews in 2026 reward candidates who demonstrate marketplace-specific judgment, not generic product thinking. The problem isn't whether you can describe a feature launch — it's whether you can explain why a delivery driver would accept a €6.50 order at 11 PM on a rainy Tuesday in Amsterdam. The strongest portfolios show three things: platform-side tradeoffs, unit economics awareness, and a clear signal of ownership depth. Prepare projects that prove you understand the cold-start problem on both the demand and supply sides of a two-sided marketplace.

Who This Is For

This is for senior product managers targeting a Staff or Group PM role at Just Eat Takeaway, specifically within the European marketplace or logistics teams. You have 5+ years of experience, have shipped at least one platform product, and are currently earning between €130,000 and €170,000 total compensation at a B2C company. Your weakness is likely this: your portfolio shows features, not marketplace dynamics. You can talk about user growth but not driver churn. You need to reframe your work around the specific tensions that JET's leadership debates in quarterly reviews — not general PM theory.

What Makes a Just Eat Takeaway Portfolio Different From Amazon or Uber Eats?

The candidates who bring generic "I built a recommendation system" portfolios get rejected in the first five minutes of the portfolio review. I've sat in a JET debrief where the hiring manager said, "This person clearly worked at a search company. They don't understand why we care about pickup accuracy more than delivery speed."

The difference is structural. Just Eat Takeaway operates across 12 European markets with different restaurant density, different driver regulations, and different payment preferences. In Germany, 40% of orders are still paid in cash. In the Netherlands, most deliveries are by bike. Your portfolio must show that you understand this heterogeneity — not treat it as noise.

The first counter-intuitive truth is this: JET's leadership values supply-side thinking over demand-side thinking by a ratio of roughly 3:1. Most PMs naturally focus on the consumer app experience — better search, faster checkout, personalized recommendations. But the company's biggest unsolved problems are on the driver and restaurant sides: how to keep a driver online during low-demand hours, how to reduce restaurant wait times without penalizing quality, how to handle order cancellations when a driver has already accepted the route.

One candidate I saw in a Q2 2025 debrief had built a driver shift-scheduling tool at a logistics startup. The hiring manager leaned forward when the candidate described how they reduced shift no-shows by 18% by introducing a penalty system tied to future shift priority. That wasn't a consumer feature. It was a supply-side operational improvement. The candidate got an offer — €165,000 base, 0.03% equity, €25,000 sign-on.

How Do You Structure a Portfolio Project to Show Marketplace Judgment?

The problem with most portfolios is they tell a story about what you built, not about the judgments you made when you didn't have complete data. JET interviewers in 2026 are trained to probe for this. The portfolio review is not a show-and-tell. It's a judgment audit.

Structure each project around three specific decisions you made that could have gone wrong. For example: "I chose to prioritize driver arrival time accuracy over restaurant wait time reduction because our analysis showed that 68% of cancellations happened after the driver arrived but before the order was ready. The counter-argument was that restaurant partners would leave the platform. I accepted that risk because our restaurant churn data showed 85% of restaurants stayed for at least 6 months even with longer waits, provided we communicated the delay proactively."

This is not about listing features. It's about showing you understand the tradeoff between two platform metrics that compete. In a marketplace, improving driver experience often hurts restaurant experience. Improving consumer experience often hurts driver earnings. The best portfolios show a specific tradeoff, the data you used to decide, and the outcome—including the negative side effects you accepted.

Another candidate I reviewed had built a restaurant onboarding flow that reduced time-to-first-order from 14 days to 9 days. The hiring manager asked: "What did you break?" The candidate said: "We increased the number of incomplete menus by 22% because we removed the mandatory photo upload step. We decided that was acceptable because the revenue from faster onboarding offset the lower menu quality. Six months later, we added a post-onboarding photo prompt that recovered 80% of the missing images." That answer got the candidate through to the next round.

What Metrics Should You Lead With in a Just Eat Takeaway Portfolio?

Not DAU or MAU. JET's leadership doesn't care about user engagement in the way a social media company does. They care about order completion rate, driver acceptance rate, average wait time, and restaurant retention.

In a 2026 portfolio review, the interviewer will ask you to map your metrics to JET's operating model. They use a specific framework internally called the "Three M's": Marketplace health, Merchant satisfaction, and Margin per order. Your portfolio metrics must map to at least two of these three.

If you led a project that improved checkout conversion by 15%, that maps to Marketplace health. But if you can't explain how it affected Margin per order, you have a gap. The interviewer will ask: "Did your conversion improvement come from discounts? Did it increase average order value? Did it change the mix of payment methods?" You need to have answers.

One strong portfolio I saw used a metric called "driver earnings per active hour" as the north star. The candidate had built a route optimization feature that increased drivers' earnings by €2.30 per hour during low-demand periods. That metric maps directly to Marketplace health (more drivers online) and Margin per order (fewer unfulfilled orders). The candidate didn't mention DAU once.

How Do You Handle the "You Didn't Work at a Food Delivery Company" Objection?

This is the most common pushback in JET portfolio reviews. The hiring manager will say: "Your experience is at a SaaS company. How do you know food delivery is different?"

The answer is not to defend your general PM skills. It's to acknowledge the difference and demonstrate that you've studied it. I've seen candidates lose the offer because they said "product management principles are universal." That's true at a high level but irrelevant to JET's specific problems.

The better approach: "I understand that food delivery has a real-time supply-demand matching problem that my previous work doesn't replicate directly. However, I've spent 40 hours in the past month reading JET's public blog posts on logistics, interviewing two former drivers on Reddit, and analyzing the publicly available data on delivery density in Amsterdam. I know that in JET's model, the key constraint is not restaurant capacity but driver availability during peak hours. Here's how I would apply my experience in supply optimization to that problem."

This answer works because it shows humility, research effort, and a specific bridge between your experience and the role. In a debrief I observed, this exact response turned a "no" into a "yes" after the hiring manager said, "They actually did the homework. Let's give them the chance."

Should You Include a "Failure" Project in Your Portfolio?

Yes — if you choose the right failure. The worst failure stories are about things you couldn't control: a competitor launched a feature, the market shifted, the budget was cut. Those are not failures. They are excuses.

The right failure is a decision you made that was wrong based on the data you had at the time. For example: "I launched a subscription bundle that combined delivery fees with a monthly credit. We expected 15% adoption. We got 3%. The mistake was that we assumed price sensitivity was the main barrier to ordering frequency. It wasn't. It was restaurant variety. Users didn't want to commit to a subscription because they wanted to try different cuisines each week."

Then show what you learned and how you applied it to a subsequent project. The failure must lead to a specific operational change. Without that second half, the story is just a confession.

In one JET portfolio review, the candidate described a failed driver incentive program that increased costs by 12% without improving delivery times. The interviewer asked: "What did you do differently next time?" The candidate said: "We shifted from a per-delivery bonus to a weekly guaranteed minimum earnings model. This reduced driver churn by 8% and kept costs flat because drivers stopped gaming the system by only taking short deliveries." That candidate advanced.

Preparation Checklist

  • Audit your portfolio against JET's Three M's framework: Marketplace health, Merchant satisfaction, Margin per order. Remove any project that maps to fewer than two metrics.
  • Replace all DAU/MAU metrics with marketplace-specific metrics: driver acceptance rate, order completion rate, average wait time, restaurant retention.
  • Prepare a two-minute verbal summary of each project that starts with the tradeoff you faced, not the feature you built.
  • Identify one project you can reframe as a supply-side improvement, even if you originally focused on the consumer side.
  • Practice answering the "you haven't worked in food delivery" objection using the specific research approach described above.
  • Work through a structured preparation system (the PM Interview Playbook covers marketplace-specific portfolio framing with real JET debrief examples from European hiring panels).

Mistakes to Avoid

Mistake 1: Leading with consumer growth metrics.

BAD: "I grew the user base by 40% in six months through a referral program."

GOOD: "I improved order completion rate from 72% to 81% by redesigning the driver arrival notification system, which reduced cancellations caused by drivers arriving before the order was ready."

Mistake 2: Avoiding the "cold start" problem in your portfolio.

BAD: "We had 10,000 users at launch because we had a strong marketing budget."

GOOD: "We started with 200 restaurants and 15 drivers in a single postal code. I personally recruited 8 drivers through Facebook groups. The first month, we had a 40% order failure rate because drivers couldn't find the restaurants. I redesigned the geocoding system and failure rate dropped to 12%."

Mistake 3: Presenting a project without showing the negative side effects you accepted.

BAD: "We reduced delivery time by 15%."

GOOD: "We reduced delivery time by 15% but increased driver idle time by 8% because we forced drivers to wait at restaurants longer during peak hours. We accepted this because consumer satisfaction improved by 22 points, and we later optimized driver routing to recover the idle time."

FAQ

Does Just Eat Takeaway care about my portfolio more than my behavioral answers?

Yes — by a significant margin. The portfolio review is the highest-weighted section in the interview loop. JET's culture values demonstrated judgment over personality traits. If your portfolio shows strong marketplace thinking, behavioral answers can be weaker. The reverse is not true.

Should I include side projects or open-source work in my portfolio?

Only if they demonstrate marketplace-specific judgment. A side project that shows you can build an app is worthless. A side project where you analyzed driver shift data from a public dataset and proposed a scheduling optimization is valuable. The medium doesn't matter — the judgment signal does.

Can I use a project from 3+ years ago?

Yes, but only if you can show how you've evolved your thinking since then. The interviewer will ask: "What would you do differently now?" Your answer must show that you've learned from the experience, not that you've moved on to bigger things.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.