
Derived from 1 submission for ALL. Format details may vary across different teams or locations.
The Conga SDE-3 interview process consists of three technical rounds covering database concepts, programming problems, and system design. The process is rigorous, with a strong emphasis on enterprise-level problem-solving, .NET ecosystem expertise, and scalable architecture design. Candidates with prior FAANG experience are expected to demonstrate depth in error handling, integration patterns, and real-world trade-offs.
Format: Discussion-based round focused on theoretical and conceptual questions. Topics Covered:
Exact Questions Asked:
Source: LeetCode Discussion
Format: Hands-on coding round with two problems. Focus Areas:
Exact Questions Asked:
10+20, 20-10) using OOP principles like polymorphism and encapsulation.Source: LeetCode Discussion
Format: Hybrid round combining theoretical concepts and system design. Focus Areas:
Exact Questions Asked:
Source: LeetCode Discussion
The candidate participated in three technical rounds covering database concepts, programming problems, and system design. Despite having 8+ years of experience, including work at FAANG companies, the candidate was rejected after the final round.
Discussion on differences between SQL and NoSQL databases, followed by a problem to design a recommendation engine similar to those used by Netflix and Spotify.
SQL vs NoSQL
Design a recommendation engine similar to Netflix and Spotify
Two programming problems were given. One involved extracting unique elements from a stream, and the other required evaluating mathematical expressions using OOP principles.
Program to extract all unique elements from a stream
Program to evaluate an expression using OOP principles (e.g., "10+20", "20-10")
A mix of theoretical and system design questions. Topics included abstraction vs. encapsulation, .NET Core vs .NET Framework, SDLC concepts, designing an ETL system, publisher/subscriber patterns, and enterprise integration patterns in the context of ETL, including error handling for heterogeneous source systems.
Real-world examples of abstraction vs. encapsulation
.NET Core vs .NET Framework
SDLC Concepts
Design an ETL System
Examples of the Publisher/Subscriber pattern
Enterprise Integration Patterns in the context of ETL (Message Id and Correlation Id)
Handling error scenarios in ETL systems with heterogeneous source systems