
Trustly Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 185 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 185 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Trustly.
QA Engineer
The interview process was really positive and well-organized. I really liked that I always got quick feedback, so I never felt unsure about where I was in the process. It kicked off with a technical challenge that was pretty straightforward and had enough time to complete it without rushing. After that, I had a chat with HR about my background and what I'm looking for. Then came an English test covering reading, listening, and responding. Following that, there was a technical discussion with the quality team about past experiences and how I'd tackle daily issues. It was also a good chance to understand the team's workflow better. Finally, I spoke with leadership about alignment, culture, and mutual expectations.
- Tell me about your experience with Selenium.
- What's your approach to test planning in a project?
- How do you set up and structure your automated tests?
Senior Backend Engineer
The whole process went super well and was really fast. It took about two weeks from the initial recruiter contact to the offer. The steps were: first chat with the recruiter, an English assessment, a technical interview (no live coding, just a high-level system design, with optional tools and screen sharing), an interview with the squad manager, a final interview with the QA manager and the PM, and finally, they asked for three professional references.
- What are the differences between HashMap, TreeMap, and LinkedHashMap, and why would you choose one over the others?
- What would you change about your current workflow?
- If you had a bug affecting 1% of users and a performance bottleneck affecting 100% of users, which would you prioritize?
Fraud Analyst
It started with an HR call, then I had an interview with the team head for about 40-45 minutes. During that interview, she asked a few questions, like a general fraud question, a general SQL question, and some common behavior questions. She didn't ask any follow-up questions though. About 20 minutes in, she said she was done with her questions and the interview wrapped up after I asked her three questions. The next day, I got rejected. They said they wanted someone with direct experience right away, which is weird because that's not what they said in the first round.
- What is your understanding of fraud factors?
- What can you tell me about your SQL knowledge?
- Can you share some examples based on common behavioral questions?
Software Engineering Manager
I had a really good and professional experience interviewing for a Software Engineering Manager role at Trustly. I applied online on Jan 17 and heard back from the recruiting team a week later on Jan 24. On that first call, the recruiter gave me the lowdown on the company, what the job entails, and what to expect from the interview process, which they said would be thorough for a leadership role. It included five interviews with future colleagues, the HR Business Partner, a VP of Engineering, and the hiring manager. There was also a psychometric/logic test and an English test. After the initial screening, interviews happened on Feb 7, Feb 17, and Feb 19. I then chatted with a US-based VP on March 13, and the hiring manager the next day, March 14. The whole thing took about two months, but honestly, the interviews felt more like chats than formal interviews, letting me talk about my background and learn about Trustly’s culture, projects, and challenges. It felt like a place that’s growing and changing. I really liked hearing about their plans for online payments and how global they are, showing they care about innovation and growing their people. The recruiter kept me in the loop with updates on what was next and when, which made me feel more confident and ready. I got an offer on March 18, and it was better than I expected, plus they were cool about my start date. So yeah, even though it took almost two months, the process was organized, covered everything, and was managed well, which just confirms Trustly is a great company that wants to hire and support good people.
- Regarding my managerial experience, tell me about scenarios involving team leadership.
- Describe situations involving decision-making under pressure.
- How have you handled conflict resolution?
Trustly Interview Questions
Quoted word for word from Trustly interview reports.
“What are the differences between HashMap, TreeMap, and LinkedHashMap, and why would you choose one over the others?”
Read reports →“What are the architecture and components of real-time and near real-time machine learning pipelines?”
Read reports →“Could you explain the differences between Java's Map implementations like HashMap and TreeMap?”
Read reports →“How to handle when a model feature has much more weight than others?”
Read reports →“Could you explain the differences between List, Set, and Map data structures?”
Read report →“Could you explain in as much detail as you deem necessary what happens when you type "www.google.com" into your browser's address bar and press "Enter"?”
Read report →“How would you address a status indicator without using color as a feature?”
Read report →“How to implement user traceability through data such as ip, cpf, email, etc.”
Read report →“Were there instances where the language switched between Portuguese and English during the interview?”
Read report →Formats, difficulty and experience
Across all 185 Trustly interview reports.