
CData Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 22 interview experiences · FREE TO READ
Which role are you interviewing for?
12 roles · 22 reportsCandidate interview experiences
First-hand accounts from people who interviewed at CData.
Business Development
The CData interview process included a video call with the recruiter, then a call with the hiring manager who is a great person to learn from, followed by a call with an SDR and AE to assess culture fit, another call with a senior manager, and finally a call with the Director of Sales.
No confirmed questions were included in this interview report.
Software Engineer
The interview process felt very unstructured, like lazy homework. It included a recruiter call, an Engineering Manager (EM) interview, one technical interview, and one system design interview. The recruiter changed the order right before the technical interview. When asked about the focus of the technical interview (e.g., framework-specific or LeetCode-style), there was no answer. The technical round was strange, focusing on a TypeScript Express controller review for a C#/Java-heavy role. Despite this, I did well as it was my current stack and received positive feedback. For the system design, when I asked for context, there was again no answer. I was asked about HTTP, how to make an app multi-tenant, and other generic questions. When generic questions are asked, generic answers are received. The interviewer corrected my understanding of their intentions, suggesting they expected mind-reading. These questions seemed too simple even for junior roles. I was expecting STAR-based or similar questions. After 6 rounds, I failed without a clear reason and was ghosted when I asked for feedback. It's a shady process, and I recommend looking elsewhere as new hires seem overlooked. The motivation behind this is unclear.
- Can you review this Express controller?
- Can you explain some generic backend concepts?
- What would be the context for this system design?
Technical Support Engineer
The interview process was great! They communicated well and on time before the interview, which helped me prep. The interviewers were nice, professional, and seemed interested in me as a person. The questions were on point, and I liked that they mixed technical stuff with questions about my background and skills.
- Tell me about your experience with SQL, specifically window functions.
Platform Engineer
I got a call from Michael Page, and the whole thing was pretty smooth and they were really supportive. The interview itself went okay, they just asked a few technical questions. The person interviewing me seemed to have a good vibe, and I managed to answer most things pretty practically. It was a bit of a shock to get rejected though, so I'm guessing there might have been something internal going on at CData.
- Could you explain what a stage is in a Pipeline, and what are the jobs and tasks within a Pipeline?
CData Interview Questions
Quoted word for word from CData interview reports.
“Can you identify the error in this SQL query?”
Read reports →“What does the execution plan for a SQL query entail?”
Read reports →“In detail, what is dom manipulation in javascript?”
Read reports →“What are the fundamental concepts of OOP?”
Read reports →“Could you explain what dom manipulation in javascript is?”
Read report →“Could you write a script to process a JSON file and perform different actions on it?”
Read report →“Could you explain the concept of OOPs and its different types in detail?”
Read report →“How do you make an application multi-tenant?”
Read report →“Can you review this Express controller?”
Read report →Formats, difficulty and experience
Across all 22 CData interview reports.