Jumio Software Engineer Interview Questions
& Process

Went through an interview via interview vector. First round involved 2 Leetcode easy questions and some basic Spring Boot questions. Second round was with the hiring manager, which was different from other companies. The recruiter said it would be a mix of situational and HLD/LLD, but surprisingly no HLD/LLD was asked. The interviewer focused on Kotlin, Java, and Spring Boot questions. I managed to answer about 80% with minimal help. The interview went over by 30 minutes, ending at 1.5 hours. The interviewer stated they were looking for 'GURUS' who could answer everything, implying this expectation even with an average salary. This company's lack of growth is unsurprising.

I got a recruiter call and then they set up a coderbyte round. They initially said it would be 2 questions for 2 hours, but then changed it to 2 hours 30 mins with 6 questions. I managed to complete 5 out of the 6 questions, and all my solutions were good (test cases passed). However, they still rejected me because I spent too much time on 2 of the questions, which resulted in me only getting 50% marks for them. This meant I didn't meet their requirement of 70% total marks. They never mentioned there was a time limit for each question. When I asked the recruiter, they checked with the team who designed the test. Apparently, they give 50% marks for a correct solution (all test cases passed) and 50% marks for completing it within the time limit. Neither the HR nor anyone else informed me about this rule. Even though I solved 5 out of 6 questions correctly, they rejected my application. The HR confirmed this. If I had known about the time constraint per question, I wouldn't have wasted my 2.5 hours.

I was contacted by a recruiter on LinkedIn about an opportunity at Jumio in Bangalore. The first step was a preliminary chat with a VP. We talked about designing a Twitter Feed and fundamental Java concepts. Following that, there was a 3.5-hour machine coding challenge where I had to architect a Book Store using Microservices. The third stage involved a panel with a VP and two other senior engineers, covering my machine coding submission, general engineering best practices, data structures and algorithms, and system design. Finally, I had a discussion with the recruiter.