
Cast.AI Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 20 interview experiences · FREE TO READ
Which role are you interviewing for?
10 roles · 20 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Cast.AI.
Senior Frontend Engineer
The whole thing took a few weeks, and I'd say it went pretty well. It kicked off with a quick chat with HR, then I spoke with the engineering manager. After that, there was a live coding challenge with two frontend engineers. Later on, I had a more in-depth technical review with another pair of engineers, and to wrap it up, I had a final call with the Director of Engineering. Everyone I talked to was cool, straightforward, and seemed genuinely interested in solving problems, not just ticking boxes. It felt more like genuine engineering chats than a rigid interview.
- Can you suggest ways to enhance this current code snippet?
- Describe your process for collaborating with backend engineers when the project requirements are ambiguous.
- What is your methodology for conducting code reviews?
Legal Counsel
The interview process at CAST AI started off well and seemed structured — I went through five stages in total: an initial screening call, a technical test, an interview with the hiring manager, and two separate culture fit interviews. This all took place over the course of about four weeks. Unfortunately, after completing all stages, I was completely ghosted. Despite following up multiple times, I never received any closure or response, even just to say I was unsuccessful. It’s really disappointing to invest so much time and effort into a process and not even get a courtesy email in return. A very poor candidate experience overall.
- Why do you want this company
Sales Engineer
This company has a terrible recruiting process. A recruiter from an agency called me on LinkedIn and scheduled a short intro call, but it went way over time and they were aggressive. I decided to keep going. The next step was a call with a senior person. The recruiter said to expect questions on sales methodologies like MEDDIC. Instead, it was a technical grilling on Kubernetes and a bunch of 'tell me about a time' questions that I wasn't ready for. The interviewer, who would have been my boss, then outlined a much longer process than I was initially told: another behavioral interview with him, more interviews with other teams, and a deeper technical test. He said he'd arrange the next steps with the recruiter. Then, I heard absolutely nothing. I was ghosted. It was unprofessional and disorganized. I'd think twice about interviewing here.
- Can you share a past experience that demonstrates a specific skill or situation?
- What is your background with Kubernetes?
- Could you describe a situation where you had to apply a particular sales methodology?
Product Designer
This was my first conversation for the Senior Product Designer role at CAST AI, and I spoke with the Lead UX Designer. Honestly, the experience left me with more questions than answers. The interviewer didn't give any real insight into the role, the team, or what kind of person they were actually looking for. Instead, they just kept repeating how complex the product is - without explaining why or what challenges they were hoping to solve with this hire. At one point, they asked how fast I could learn to work with different APIs, but when I asked for more details (like what kinds of APIs or how they're integrated), they couldn't give any examples. It felt like they expected a generic answer to a question that obviously depends on context. What really stood out in a bad way was how much they emphasized that they have a ton of candidates and can be super selective. I get that companies want to hire the best people, but the way they framed it felt cold and transactional - like they were more interested in reminding me how replaceable candidates are than actually trying to see if we'd be a good fit for each other. It raised concerns about whether the team values long-term collaboration or simply sees hiring as a filtering exercise. Overall, the whole process felt vague, unstructured, and impersonal. If you're considering an interview with CAST AI, be ready to push for clarity yourself because they won't offer it. And if you value a hiring process where both sides are genuinely interested in working together, this is not the best place.
- How quickly could you learn to work with different APIs?
Cast.AI Interview Questions
Quoted word for word from Cast.AI interview reports.
“Can you solve a probability question using simulations to get an approximate answer?”
Read reports →“What are some common pitfalls or advanced concepts in Kubernetes?”
Read reports →“Can you elaborate on Kubernetes and its inner workings?”
Read reports →“What information do you have about Cast AI?”
Read reports →“Can you suggest ways to enhance this current code snippet?”
Read report →“Could you build a basic simulation involving concurrency?”
Read report →“Can you tell me what you know about Kubernetes?”
Read report →“What AI tools are part of your design workflow?”
Read report →“Can you make a design on board that is exactly what they are doing? Expecting me to say some tricky words.”
Read report →Formats, difficulty and experience
Across all 20 Cast.AI interview reports.