SumUp logo

SumUp Android Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 7 interview experiences · FREE TO READ

3.4 Rounds average
Average Typical difficulty
14.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at SumUp.

Showing 3 of 7
SumUp logo
SumUp

Android Developer

Engineering · a year ago

Entry Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Behavioral Coding

Primeira etapa com RH, já em inglês. Segunda etapa com live coding também inglês, implementar algumas coisas simples em um app já criado. Pode consultar a internet. A próxima etapa seria uma entrevista técnica falando também do que foi feito no live coding.

Confirmed questions6 questions
  • How would you approach modularization?
  • Do you have experience with unit tests?
  • Do you have experience with compose?
SumUp logo
SumUp

Senior Android Engineer

Engineering

Senior Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical Coding

The interview experience started positively up until the final stage, which unfortunately soured my overall impression of the company. It began with a 30-minute recruiter call, which was standard, covering my background and career aspirations. This was followed by a 1-hour hiring manager call, delving deeper into my experience, focusing on projects I'm proud of and my methodologies, along with some high-level discussions on technologies I've used. The next stage was a 1.5-hour technical assessment with two interviewers. This was divided into reviewing and improving Kotlin code snippets, and a live coding task in Android Studio involving Compose UI. The final interview, a 1-hour cross-functional/team fit call with the Engineering Manager and Product Manager, took a negative turn. While the aim was likely to understand my work approach, my answers, reflecting experience in mature environments, seemed to displease the EM, who became confrontational. This led me to suspect issues with their management style or the company culture. The EM also appeared reluctant to answer my questions, providing vague responses or ignoring some entirely, such as inquiries about success criteria for senior/staff engineers, stating that documentation would be provided only upon joining. I'm unsure if my preferred work location, nationality, LinkedIn photo, or work process preferences influenced the outcome, but it's clear I won't be engaging with SumUp recruiters again.

Confirmed questions4 questions
  • Review the provided Kotlin code snippets and identify any design flaws.
  • Explain the execution flow and final output of these Kotlin asynchronous code snippets.
  • Could you quickly build out a screen layout using Compose UI?
SumUp logo
SumUp

Android Engineer

Engineering

Mid Average Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Take home Technical screen Recruiter call Panel
Interview formats
Technical Coding Behavioral

It was 5 rounds of interviews! I was technical from the very start. The first HR interview already involved technical questions. Then I had an interview with their team lead, which was an hour of technical questions. After that, I got a take-home task. I completed it thoroughly, including testing and screenshots. Then there was another 1.5-hour technical interview with two engineers where I had to modify and improve code. Following that, I had another session with the HR person. They gave me really positive feedback based on what everyone else said. Then came one more interview round with two Product Managers asking team-related questions, like how to handle conflict and similar typical questions. They said I did well, and after a day, I got rejected. It took 3 weeks of hard work.

Confirmed questions3 questions
  • Can you recall the last instance you provided constructive criticism to someone?
  • Have you encountered colleagues that were difficult to collaborate with, and if so, how did you manage?
  • What is your approach to working with legacy code?

SumUp Android Engineer Interview Questions

Quoted word for word from SumUp interview reports.

Explain the execution flow and final output of these Kotlin asynchronous code snippets.

Read reports

Could you quickly build out a screen layout using Compose UI?

Read reports

Can you recall the last instance you provided constructive criticism to someone?

Read reports

Could you elaborate on your work with Android Camera APIs?

Read report

Formats, difficulty and experience

Across all 7 SumUp interview reports.

Interview formats

Technical 31.2%
Coding 31.2%
Behavioral 31.2%
Case 6.2%

Interview difficulty

Easy 42.9%
Average 57.1%
Difficult 0%

Candidate experience

Negative 71.4%
Neutral 14.3%
Positive 14.3%