CloudHealth Interview Questions
& Process

The role of Technical Account Manager is essentially a Sales Engineer position. Solution Architects seem to be limited to custom report generation and basic customer troubleshooting. While the development side might be interesting, the technology is quite basic, making the sales/support titles seem inflated. AWS certification is valued more than perceptiveness or intelligence. Focus on knowing about Glacier. This environment is suitable for recent graduates rather than experienced professionals. The job advertises aggressive pay, but it's definitely under 100k. The lack of follow-up, whether positive or negative, was unprofessional and disorganized, leading to a low rating.

The interview experience was disappointing and felt like a waste of time. I was interviewed by a Staff Engineer who seemed distracted by Slack messages throughout the session. The interview, scheduled for an hour, included two problem-solving questions. I successfully coded solutions for both, achieving optimal O(n) time and O(1) space complexity without any hints, covering all edge cases. Towards the end of the hour, another question was posed. I explained my approach and discussed it for an additional 20 minutes beyond the scheduled time, without writing code. Post-interview, I verified my solutions on Google and confirmed they represented the best possible time and space complexity. Despite this, I received a rejection, and I'm unsure about the evaluation process, especially given the interviewer's level.

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!

The CloudHealth interview experience was really smooth. It started with an InMail from Brandi, followed by a screening call with their recruiter, Alex. After discussing my background, Alex explained the role and set up a 1:1 with the hiring manager for the next day. A few days later, I had 5 more interviews (2 in-person, 3 remote) with team members at their Boston HQ. This part required some studying on cloud computing, cost optimization, and governance. I discussed my background with each person and asked about the company, product, and industry. There were a few brain teasers and questions related to the study material. I prepared notes on AWS Reserved Instances, EC2, and S3. Then, I had an on-site interview at their Boston HQ, with hotel and airfare covered. It was their first day in the new office, but things ran smoothly. I met with leadership, including the VP of Customer Success and the CEO, which was a great sign. I asked direct questions about long-term viability and the competitive landscape, and got thoughtful answers. After returning, Alex scheduled two more interviews: one with a TAM and another with the CFO, to address lingering questions. The company culture is amazing, customer focus and core values were key. The recruiting team was great, providing updates, answering questions, helping with prep, and keeping interviews on time. I highly recommend joining CloudHealth, it's a great time to join this growing company in a fast-growing space.