How long does the SumUp interview process take?

Most candidates spend between 4 and 8 weeks from recruiter screen to offer. The onsite loop itself runs in a single day or is split across two half-days, with debrief and offer typically within 5 business days after.

How should I prepare specifically for SumUp?

Focus on three things: (1) the company DNA shown above - what they actually grade for, (2) the rounds in your loop, especially the round most candidates underestimate, and (3) drilling on the question types in this guide using a structured framework like CIRCLES or STAR.

Does this apply to engineering or design roles at SumUp?

The DNA stays the same - what changes is the round mix. SWE candidates face coding screens instead of Product Sense; designers face portfolio reviews and design exercises. The "what they value" and behavioral signals carry across all functions.

Other roles at SumUp:Product Manager Software Engineer Sales Marketing Customer Success

Growth · Software Engineer Interview Guide

How to Pass the SumUp Software Engineer Interview in 2026

The SumUp DNA (TL;DR)

SumUp's core mission to support small businesses, from Boba Tea shops to Beauty Supply stores, drives its interviewers to assess a candidate's practical aptitude for simplifying complex financial tools. They seek individuals who can articulate how their work directly empowers merchants, showcasing tangible impact over theoretical discussions.

The SumUp Interview Loop

Your onsite loop will typically consist of 5 rounds.

1
Round 1
Recruiter Screen
Motivation, role fit, logistics.
2
Round 2
Coding Screen
LeetCode-medium algorithmic problems under time pressure.
3
Round 3
System Design
Distributed systems, trade-offs at scale, architecture under constraints.
4
Round 4
Onsite Coding
LeetCode-hard, debugging, code clarity, edge cases.
5
Round 5
Behavioral / Leadership
Past evidence of ownership, influence, resolving conflict.

The Danger Zone: Top Reasons Candidates Fail

Based on our database of SumUp interview outcomes, avoid these common traps:

Describing a minor disagreement or focusing solely on the other person's fault.
Blaming the other party without taking responsibility for their own role in the conflict.
Introducing new complexities or 'clever' code that reduces readability.
Inefficiently iterating through the entire list for each query.

Test Yourself: Real SumUp Questions

Three real prompts pulled from our database.

Type · Debugging

Here is a piece of code that is supposed to calculate the average transaction value per merchant, but it has a bug. Find and fix the bug, and explain your debugging process.

Type · Algorithm

Implement a function to find the k-th smallest element in a stream of numbers. The stream can be very large, so the solution should be memory-efficient.

Type · System Design

Design a system to process and analyze real-time payment transaction data for fraud detection and business intelligence. Consider scalability, latency, and fault tolerance.

+ many more questions, signals, and worked examples

Unlock the rubric

SumUp Interview Question Bank

A sample from our database, grouped by round. Sign up to see the full set.

9 of 18 questions shown

Recruiter Screen

1
Type · Motivation
What interests you about SumUp's mission to empower small businesses, and how do you see your technical skills contributing to that mission?

Coding Screen

2
Type · Algorithm
Given a list of transactions, each with a timestamp and amount, write a function to calculate the total value of transactions within a given time window (e.g., last 5 minutes). Assume timestamps are in milliseconds.
3
Type · Algorithm
Implement a function that takes a list of merchant IDs and their associated transaction counts, and returns the top K most active merchants. Consider how to handle ties.
+ 1 more questions in this round (sign up to unlock)

System Design

4
Type · System Design
Design a system to process and analyze real-time payment transaction data for fraud detection and business intelligence. Consider scalability, latency, and fault tolerance.
5
Type · System Design
Design a notification service for SumUp merchants, allowing them to receive alerts for important events (e.g., large transactions, chargebacks, low balance).
+ 1 more questions in this round (sign up to unlock)

Onsite Coding

6
Type · Algorithm
You are given a log of API requests, each with a user ID, timestamp, and endpoint. Implement a rate limiter that restricts the number of requests a user can make to a specific endpoint within a given time window (e.g., 100 requests per minute per user per endpoint).
7
Type · Debugging
Here is a piece of code that is supposed to calculate the average transaction value per merchant, but it has a bug. Find and fix the bug, and explain your debugging process.
+ 2 more questions in this round (sign up to unlock)

Behavioral / Leadership

8
Type · conflict_resolution
Tell me about a time you had a significant disagreement with a colleague or stakeholder about a product decision. How did you approach it, and what was the outcome?
9
Type · Adaptability
The fintech landscape is constantly evolving. Tell me about a time you had to quickly adapt to a significant change in product, process, or market conditions. How did you manage the transition and ensure continued effectiveness?
+ 5 more questions in this round (sign up to unlock)