Summary
I interviewed at Jodo for an SDE 1 position in Bengaluru in February 2023. The interview process consisted of three rounds covering data structures, algorithms, computer science fundamentals, and low-level design, ultimately leading to a rejection.
Full Experience
My Interview Experience at Jodo (SDE 1)
I went through a total of three rounds for the SDE 1 role at Jodo in February 2023.
Round 1: Technical Assessment
This round primarily tested my technical acumen, focusing on data structures, algorithms, and fundamental computer science concepts. I was given two coding problems and several questions covering database ACID properties, differences between various types of database keys, and distinctions between network protocols like HTTP, TCP, and UDP.
Round 2: Behavioral and Past Experience
The second round was more about my professional background and soft skills. The interviewer asked questions related to my previous projects, work experience, and how I approach various situations at work. It was essentially a behavioral assessment.
Round 3: Low-Level Design (LLD)
The final round was a comprehensive low-level design challenge. I was tasked with designing the detailed architecture for an application similar to Splitwise, requiring me to consider various components, data flow, and system interactions.
Interview Questions (6)
Given an array of integers, I was asked to find all duplicate numbers present in it.
I was presented with the classic 'Climbing Stairs' problem: You are climbing a staircase. It takes n steps to reach the top. Each time you can either climb 1 or 2 steps. In how many distinct ways can you climb to the top?
I had to explain the ACID properties (Atomicity, Consistency, Isolation, Durability) of database transactions.
I was asked to explain the key differences between primary keys, unique keys, and foreign keys in the context of relational databases.
The interviewer asked me to differentiate between HTTP, TCP, and UDP protocols, discussing their characteristics and typical use cases.
I was tasked with performing a low-level design for a system akin to Splitwise, considering aspects like user management, expense tracking, group functionalities, and debt settlement logic.