
Synthesized from 16 candidate submissions for ALL.
Hiring at Conga appears to be primarily focused on behavioral assessment and professional background alignment rather than rigorous technical screening. The interview process is generally straightforward, often consisting of a single HR-led conversation that prioritizes salary expectations and cultural fit.
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
The interview process was very simple and consisted of a single discussion regarding salary expectations.
A brief discussion regarding compensation expectations.
What are your salary expectations?