
Cardlytics Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Cardlytics.
Software Engineer
The interview process went pretty well. The recruiter was super responsive and helpful. The whole thing took about 4 weeks because I couldn't give many dates for the interviews. There were 5 technical interviews, not counting the initial recruiter call. It started with a tech screening with the hiring manager, then a coding round. After that, there were 3 more interviews, including one for system design. The interviewers were nice and made it feel like a team effort, giving feedback as we talked. Overall, a great experience.
- Questions related to Data Structures and Algorithms.
- A question involving pair programming.
- A question about system design at a high level.
Software Engineer
It all kicked off with a 30-minute chat with a technical recruiter, followed by a 45-minute meeting with the hiring manager, both happening within a few days. Then, about a week later, they scheduled me for three technical interview rounds. The first was with a senior principal engineer, who dove deep into my past experience and technical hurdles, and also threw in a system design question. The next technical interview focused on data structures and algorithms. The final one involved a real-time coding challenge!
- Can you elaborate on any technical difficulties you encountered in past projects and the solutions you implemented?
- Tell me about technical difficulties faced in previous projects and how did you solved it.
Senior Staff Software Engineer
The interview process included a Hackerrank test for the first round where the goal was to write a program that passes all test cases. The second round was a Technical Interview. Then there was a third round, another Hackerrank program that needed to be implemented and executed with unit testing. The fourth round was also a Technical Interview. In this last interview, the interviewer had a list of complex questions and expected precise answers. If you didn't know an answer, the questions would continue to focus on the same topic, which could be demotivating to have the conversation linger for an hour on something not answered.
- Could you explain object destructuring in C#?
- How about destructuring an object in Javascript?
- What about object destructuring in ES?
Cardlytics Software Engineer Interview Questions
Quoted word for word from Cardlytics interview reports.
“Can you determine the type of a triangle given its side lengths?”
Read reports →“Write queries using GroupBy and self join.”
Read reports →“Describe setting in C# to pass a request to another server when an OutOfMemoryException occurs.”
Read reports →“What is query tree correlateid?”
Read reports →“Explain selectmany.”
Read report →“Can you destructure an object in Angular?”
Read report →“How do you merge an array in Angular?”
Read report →“What are projections in LINQ?”
Read report →“What about object destructuring in ES?”
Read report →Formats, difficulty and experience
Across all 11 Cardlytics interview reports.