Idfc

Role: Senior Developer

College: Not Specified

Interview Date: Not Specified

Interview Type: Full-Time

Result: Cleared all rounds

Difficulty: Not Specified

Rounds: 4 rounds (Initial Screening (OA), L1, L2, L3/CTO)

Topics Asked: Data Structures (Priority Queue, Max Heap), Projects (architecture, tech stack, scaling policies), System Design (Instagram with basic features, Notification Banner System for an apartment), API Design, Database Design (SQL vs NoSQL), Class Design, Behavioral (passion for technology, adaptability under pressure), SOLID principles, TDD.

Experience:

An interview experience for a Senior Developer role at IDFC First Bank was shared on LeetCode Discuss, with the candidate clearing all rounds. The process involved an initial screening, L1, L2, and an L3/CTO round.

The Initial Screening Round consisted of two Online Assessment (OA) questions, which were reportedly around priority queues.

L1 Interview focused on current projects, including architecture, tech stack, and decision-making processes. A specific scenario involved explaining scaling policies for a microservice. The candidate was then asked to design Instagram with basic features, covering database selection, API design, and schema. Implementation of a Max Heap was also requested.

L2 Interview started with an introduction and project discussion. The main task was to design a "notification banner system" similar to a stock market board for an apartment. This was an open-ended system design question, requiring the candidate to ask clarifying questions and design the system, including class, API, and database design, and extending it for various scenarios.

L3/CTO Round was similar to L3, focusing on behavioral aspects such as passion for technology, adaptability under pressure, and other soft skills. Tips provided included following SOLID principles, having TDD experience, deep project knowledge, and the ability to select and defend architectural components (e.g., choosing NoSQL over SQL for Instagram design due to lack of transactional capabilities and schema flexibility).