READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 110 of 153
Interview experiences · Revolut
Revolut Data Analyst Interview Experience — Recruiter Call, Then a Four-Question SQL Screen
The recruiter call was pretty standard — they asked why I wanted to apply to Revolut, my past experience, then talked about how they're now moving headquarters to the UAE, a lot of the roles are for continental Europe rather than the UK, it depends on how the interview goes, and they sponsor visas for senior and above, etc. SQL interview questions. The SQL was actually pretty hard — four question…
Interview experiences · Revolut
Revolut New Grad Software Engineer Interview Experience — Rejected After a Concurrency Deadlock
I applied for the New Grad Java Backend Engineer role, base EU. The whole process was 1x OA + 1x Recruiter Screening + 2x VO (virtual onsite). Quick complaint first: I applied in October, and the recruiter didn't reach out until late January... The OA was on HackerRank — two easy coding problems plus a bunch of multiple-choice questions, including some simple algorithm questions and some picture-…
Interview experiences · Revolut
Revolut Operations Manager interview: 30-minute screen and aptitude-test cutoff
I began with a 30-minute screening call about introductory context and my background. Right after that, I took a UCAT-style criteria aptitude test. The threshold for moving forward was very high. I scored below it and was rejected immediately, so I did not get to later steps. It ended quickly, with no extended follow-up or extra rounds. The test was the whole gatekeeping moment, and it felt unfor…
Interview experiences · Revolut
Revolut Operations Manager interview: aptitude tests and a prepared case discussion
I started with an HR screening interview, followed by a couple of online assessments. One covered work style, and another tested criteria or aptitude. After those, I moved to a problem-solving case. HR gave me a 15-minute preparation session before the case discussion. It made the process feel tightly organized, though also high-pressure. I found the rounds difficult. The early tests felt decisiv…
Interview experiences · Revolut
Revolut Operations Manager interview: competency screening and psychometric testing
The first HR screening call was fairly intense. It opened with why I wanted to work at Revolut, then quickly moved to competency questions connecting my experience with the role. The pace made it feel as though they wanted to establish fit early. An online psychometric test was scheduled within the next few days. After the assessment, I had a more detailed discussion with a hiring manager, follow…
Interview experiences · Revolut
Revolut Operations Manager Interview Experience: a structured process with late red flags
My process was long and structured: a recruiter screen, a cognitive-style test, a home task, a case interview, a bar raiser, and a team-fit stage. The recruiter did a fair amount of preparation between rounds and kept things moving, although there were hiccups. Interviews could start more than 10 minutes late without much notice. The bar raiser was much shorter than I expected. Parts of the proce…
Interview experiences · Revolut
Revolut Operations Manager Interview Experience: take-home case rejected before deadline
The process had a recruiter screen, an online assessment, a live case interview, and then a week-long take-home business case. The assignment felt like substantial unpaid work: it involved a JIRA workflow, process maps, SQL queries, and a full fraud-detection analysis. I was rejected while I was still finishing the take-home, before its deadline. That made the process feel disorganized or dishone…
Interview experiences · Revolut
Revolut Operations Manager interview: take-home and logic quiz
My interview path had several steps and felt more like a consulting-company funnel than a role-specific evaluation. After the early stages, I completed a take-home project and then faced a timed logic-question quiz that immediately changed how the process felt. The next major step was an interview with someone in the role I was applying for. What threw me off was how little the questions seemed r…
Interview experiences · Revolut
Revolut Operations Manager interview: two months of shifting logistics
The process felt chaotic from the start. A recruiter first contacted me on LinkedIn, then passed me to another recruiter whose availability was about three weeks away. That call was cancelled at the last minute, and the rescheduling options were extremely late, around 1 a.m. and similar times. After scheduling, I was ghosted until I chased a different recruiter through contact details I had found…
Interview experiences · Revolut
Revolut Product Manager interview: hypothetical business case
My process felt lighter than the intense multi-round processes I had seen elsewhere. It started with an HR screen and moved into a case-style evaluation. Recruiter interactions were straightforward, prep materials were provided, and I was expected to do structured analysis. For the case, I worked through a business scenario and gave reasoning and a recommendation. The examples were hypothetical r…
Interview experiences · Revolut
Revolut Product Manager interview: structured cases and bar raiser
After a recruiter call, I went through about four stages over roughly a month. The first substantive interview was a business problem-solving case. I clarified the situation, organized it in a MECE way, formed hypotheses to ask for data, and held off on solutions until I thought I had confirmed the root cause. The next case combined product thinking with technical system design, including the des…
Interview experiences · Revolut
Revolut Software Engineer concurrency and database interview experience
The interviews centered on backend fundamentals: concurrency, databases, and how transactions behave under pressure. The process began with an HR round that included technical scenarios rather than staying purely behavioral. I was asked about concurrency and isolation, and we discussed database topics such as locking, CQRS, sharding, and indexes. Later technical interviews focused on production-r…
Interview experiences · Revolut
Revolut Software Engineer interview: distributed systems and opaque system design
The process started smoothly with a recruiter screen and technical rounds rooted in practical distributed-systems patterns. I cleared several early stages, but I did not get through the system design interview. That round was difficult because I could not tell what the interviewer wanted me to emphasize or how quickly to move through the discussion. The earlier coding and technical work was concr…
Interview experiences · Revolut
Revolut Software Engineer interview experience
I received what was described as a technical-screening invitation, but at the start I had to work out who I was speaking with and what they expected. The first technical prompts arrived in chat. Later questions switched to a verbal exchange without a clear explanation. That inconsistency made it hard to tell what the interview measured, and I spent attention decoding the process instead of the te…
Interview experiences · Reynolds and Reynolds
Reynolds and Reynolds Account Executive communication experience
The process was drawn out. Communication began strongly but faded after recruiter and hiring-manager conversations. I repeatedly encountered silence, with no clear timeline or closure, even after being told I would hear back. Some steps felt like boxes being checked rather than real engagement with my answers. In a few conversations, I felt the interviewer was not listening. I also completed stru…
Interview experiences · Reynolds and Reynolds
Reynolds and Reynolds Software Engineer interview: video screen
After I applied, the company contacted me by email and set up a video interview. It followed a normal format with common background and fit questions. Nothing about it felt hostile or disorganized. Afterward, they told me they would not continue with the hiring process. They mentioned that a cheek swab could come later in the process, but I never reached that point. It was a quick, routine experi…
Interview experiences · Rippling
Rippling Account Executive interview: advanced process followed by recruiter silence
My process began normally and I made it through several rounds. Near the end, it became clear they were not moving forward. The recruiter said they would contact me that day or the next, then I heard nothing. After multiple interviews and getting fairly far, the lack of follow-through bothered me. I can understand that an early process may be slow or ambiguous, but this silence came after I was a…
Interview experiences · Rippling
Rippling Account Executive Interview Experience: Structured mock call with managers
I applied and received a quick, positive response that let me choose a meeting time. The process began with a recruiter screen covering why I wanted sales, why Rippling, what the company does, and how my prior experience fit the role. I then spoke with hiring managers and reached a role-play mock-call stage. That portion was more structured and role-specific, and I did the mock call with managers…
Interview experiences · Rippling
Rippling Senior Backend Engineer Interview Experience — An Onsite Where the Coding Round Expected You to Use AI
Interviewed for a Senior backend role in July. Round 1 — Coding (60 min), AI use explicitly allowed The interviewer (Data Cloud team) opened by saying directly: "The environment has an AI assistant set up, use it the way you normally would at work, just don't let it make every decision for you." Problem: task scheduler. You're given a batch of tasks (description / due date / priority / completed…
Interview experiences · Rippling
Rippling Senior Software Engineer Interview Experience — 30-Minute Recruiter Chat, Rejected the Next Day
I got a reach-out email from their recruiter and we scheduled a 30-minute quick chat. The HR person was 5 minutes late, but it was no big deal, I've seen this a lot. After she joined she said she wouldn't turn her camera on, and told me I didn't have to either. Then we got started. Intro and work experience She first asked me to introduce myself, and I went over my work history. Then she asked me…
Interview experiences · Rippling
Rippling Senior Software Engineer Interview Experience — An 11-Minute Late Start, a Chaotic Round, and a Recruiter Swap
The interviewer was 11 minutes late. I was actually about to just leave the call and email the recruiter to say they were a no-show, but they showed up at the very last moment. After joining, there was no intro or behavioral portion at all — they went straight into technical. Right off the bat they asked whether I wanted an AI or non-AI technical round, and I picked non-AI. Then the interviewer j…
Interview experiences · Rippling
Rippling Senior+ Software Engineer Interview Experience — Phone Screens Plus a Four-Part AI-Team Onsite Building a Live LLM Chatbot
I interviewed with Rippling's new AI department, which has 3 teams and an already-launched product. Their main product is an internal chat agent system that can integrate with hundreds of integrations on top of employee data to answer all kinds of questions. Recruiter - 30 minutes. Talked about which project of mine stood out to them, my involvement in it, and whether I had led any projects of my…
Interview experiences · Rippling
Rippling Software Engineer interview: a dismissive phone screen
I applied online, and a recruiter contacted me a couple of weeks later to arrange a technical phone screen. The process went badly quickly because the interviewer seemed disengaged from the start. I was interrupted almost immediately during my introduction and could not finish it. The interviewer moved to the coding question and kept their camera off for most of the session. I still solved the pr…
Interview experiences · Rippling
Rippling Software Engineer interview: CodePair rules and a quick recruiter turnaround
I applied online, completed an online assessment, and then passed it. Recruiting invited me to schedule the next interviews. The process was organized, with a scheduling email that included prep resources: an overview video and links to an official interview kit. My first scheduled round was a one-hour technical interview with a Software Engineer II on CodePair. The session was recorded for train…