CloudHealth Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 8 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at CloudHealth.
CloudHealth
Software Engineer
Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Behavioral Technical Coding System Design
Had three interview rounds with recruiters and engineers. The recruiter was unresponsive, which added about a month and a half to the process. I had to repeatedly email them to get any replies. The technical interview questions were generally fair and focused on design, but they expected me to know TypeScript, which wasn't on my resume. Two weeks after the technical interview, and after following up with the engineers, I still hadn't heard back. When I finally reached out to the recruiter, they said the team had decided against moving forward. The whole experience felt disrespectful, and I felt my time was wasted.
Confirmed questions4 questions
- What are common design patterns for backend development?
- Can we discuss your resume and assess your culture fit?
- How would you build and test a React component in a code sandbox?
CloudHealth
Software Engineer
Mid Average Positive experience Accept offer 4 rounds
Interview process
Phone screen Technical screen Onsite Onsite
Interview formats
Behavioral Technical
I had a phone screen, then a 30-minute Google Hangout chat, followed by a 4-hour on-site interview, and finally a 2-hour final on-site interview. I met with a total of 7 interviewers, ranging from fellow engineers to the VP of engineering. The technical part wasn't too difficult; each interviewer during the first on-site had one question for me each hour, which lasted about 15-20 minutes. The remaining 40 minutes were dedicated to discussing my background and assessing cultural fit. The second on-site involved meeting with more senior administrators who explained the company's operations, current initiatives, and future goals. They also gave me an opportunity to articulate my motivation for joining the company. Before any interview, consider if you are a persistent, hard-working, helpful, and passionate engineer. If you can affirm this, you're well-prepared. The HR team was also incredibly friendly!
Confirmed questions1 question
- Tell me about the most challenging part of your most recent project and how you could have improved it.
CloudHealth
Software Engineer
Entry Average Positive experience Accept offer 3 rounds
Interview process
Phone screen Onsite Onsite
Interview formats
Coding Technical Behavioral
It was a three-part interview process. First, a phone screen over video where I got some easy questions and a coding challenge. I was tired and didn't do my best, but they still passed me for the onsite interviews. The onsite interviews involved whiteboard problems and questions, no actual coding. I was better rested for those and performed better. Finally, I had onsite interviews with leadership and my potential manager.
Confirmed questions1 question
- Could you solve an optimization problem to identify the optimal AWS product for a given customer's usage patterns, given that it's an NP-complete problem that requires finding a good approximation in polynomial time?
CloudHealth Software Engineer Interview Questions
Quoted word for word from CloudHealth interview reports.
“Can you reverse a linked list into separate odd and even linked lists?”
Read reports →“Can you create a function that transforms a number into its string form, given the number and its base?”
Read reports →“Could you write a function to reverse a linked list without using extra space?”
Read reports →“How would you build and test a React component in a code sandbox?”
Read reports →“Build a mini data aggregator using your preferred language and tools, given access to specific APIs.”
Read report →“What are common design patterns for backend development?”
Read report →“Could you solve an optimization problem to identify the optimal AWS product for a given customer's usage patterns, given that it's an NP-complete problem that requires finding a good approximation in polynomial time?”
Read report →“Can you implement an LRU cache, focusing on planning and discussion?”
Read report →“Were you expected to have specific knowledge of TypeScript?”
Read report →Formats, difficulty and experience
Across all 8 CloudHealth interview reports.