
Coalition Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 194 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 194 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Coalition.
Insurance Operations Specialist
The whole interview process, from the recruiter chat to the final offer, was fantastic. My hiring experience with Coalition was honestly the best I've ever had. The recruiters were super professional, really nice, and totally on top of everything: they gave clear timelines, updated me regularly, sent notes after calls, provided helpful prep tips, and followed up quickly. Big thanks to Anjelica for making it all so easy and enjoyable. Her calm, respectful way of handling things and always following through set a really high standard for how candidates should be treated. The approval part took a little longer, but it was obvious they wanted to make sure I was the right fit, which I appreciate. All the interviewers were prepared, asked good questions, and made it feel like a real two-way chat about the job's impact and what to expect. Communication was solid all the way through, scheduling was flexible, and I always knew where things stood. You can really sense the company culture from the start: it's respectful, collaborative, and truly focused on people. It was a great experience overall that shows off a strong company culture and high standards. I'm glad for the process and excited to join the team.
- Can you describe your experience with insurance claims?
Insurance Operations Specialist
the whole hiring journey was top-notch, from the first chat with the recruiter right up to the offer. Seriously, it's been the best hiring experience I've ever had. The recruiters were super professional, really friendly and welcoming, and just incredibly organized. They gave clear timelines, kept me updated, sent notes after talking, provided helpful prep tips, and always got back to me fast. Big thanks to Anjelica for making it all so easy and actually enjoyable. She was so calm and respectful, and always followed through, which really sets a standard for how candidates should be treated. The approval part took a bit longer, but it was obvious they wanted to make sure I was a great fit, which I totally appreciate. Everyone I interviewed with was prepared, asked good questions, and it felt like a real two-way chat about what the job entails and what's expected. They communicated well the whole time, were flexible with scheduling, and I always knew where things stood. You can really sense the company culture right away – it's all about respect, teamwork, and putting people first. It was a fantastic candidate experience that shows off a strong company culture and high standards. I'm so glad for the process and excited to join the team.
- Can you tell me about your past experience handling insurance claims?
Data Analyst
The interview process started with a recruiter phone screen, followed by two technical interviews (one coding and one case study). Then there was a panel interview with senior leadership, a senior technical person, and the hiring manager. I have to say, this was the best interview process I've ever been through. They were really respectful of my time and genuinely interested in me as a candidate. The recruiter, Dave, even went above and beyond to help me prepare for the panel and provided constructive feedback afterward. It's rare to find that level of care, and I really appreciated it.
- Perform a series of analytical tasks on a given dataset and derive conclusions.
- How would your conclusions and action items differ when presenting to the actuarial team?
- How would your conclusions and action items differ when presenting to the operations team?
Software Engineer
So I applied for this Software Engineer - Underwriting role in Toronto, Canada. It turned out to be a total scam, a waste of my time. It felt like they were just trying to hit their internal numbers, not actually find the right person. I went through a recruiter video call, then a 1-hour technical screen, and finally two 1-hour onsite interviews. The interviewers actually seemed to like me, saying all the comments were positive. The recruiter was super friendly, almost too friendly, which felt off later. They talked up the benefits and pay before the onsite and said I'd hear back in two days. After the onsite, the recruiter said they'd share an update, but then went silent for four days, only to send a survey. I gave them a good score then, thinking it would help, but now I regret it because they were clearly just trying to get good feedback before rejecting me. Six days later, the recruiter finally called to say they went with candidates who were a better technical fit. When I asked for feedback, they said they couldn't give any because they're HR, not an engineer. After pushing, they said they'd try to get feedback but never did. The craziest part is that they're still posting the same job and other software engineer roles. So it's obvious they lied about moving forward with others. When I asked about other roles, they said I wouldn't be considered and then just ended the call. No formal rejection email either. I'm sharing this because I regret the survey score and want to save others their time.
- Standard LeetCode style coding questions
- Practical coding questions
- Behavioral questions
Coalition Interview Questions
Quoted word for word from Coalition interview reports.
“What is the length of the longest contiguous subarray containing non-negative prime numbers that are even and happy numbers”
Read reports →“For the TypeScript task, how would you fix a function that fetches data as an array of two elements and then pushes it into a new array?”
Read reports →“Could you fetch data from the provided API and manage the returned data as a promise?”
Read reports →“Design an engine class preloaded with problems, which is more like OOD questions instead of Leetcode questions.”
Read reports →“What are SQL joins and grouping, and what trends do you see in this sample bar chart?”
Read report →“Using features a, b, and c, can you build a simple model to predict the claim amount?”
Read report →“What school did you attend and why did you not attempt to go to Cornell?”
Read report →“Could you translate the given text into executable code, given that there was partial code presented?”
Read report →“Looking at this architecture diagram for a Logstash deployment, how would you make it better? Also, how would you deploy a containerized app?”
Read report →Formats, difficulty and experience
Across all 194 Coalition interview reports.