
Cloud Devs Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 45 interview experiences · FREE TO READ
Which role are you interviewing for?
11 roles · 45 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Cloud Devs.
Web Developer
They had me do a front-end and a back-end test. The front-end one was coding a tic-tac-toe game in React, and for the back-end, I had to make a call to an API endpoint from their internal system.
- Program a tic-tac-toe game using React
- Make a request to an internal API
Senior Software Engineer
I applied on their website and then got an email to set up an interview. The first interview was pretty bad, felt like something that could have been an online form. The interviewer asked me to turn on my camera, but they didn't, which was weird. They asked about my years of experience with specific tech and what my strongest tech was, stuff that could totally go in a form. Then I got a link for a coding challenge, it was React and Node based and pretty easy, took about 20 mins for each part. After that, I got a third email asking me to schedule another call and send a copy of my ID, which felt super sketchy. Given how little info there was about the company and how the first interview went, I decided not to continue because asking for an ID seemed really suspicious.
- What is your experience level with various technologies?
- Which technology do you consider your strongest?
Backend Developer
The recruiter approached me on LinkedIn for a brief 15-minute chat with a 'senior dev' about the role. During this call, I was hit with a barrage of generic tech questions: 'Worked with X?', 'For how long?', 'Rate your experience with X?'. These were subjective and repetitive. The interviewer didn't even turn on their camera and seemed uninterested in how I used the tech, only caring about my GitHub profile. It's a shame if you only work with private client code like a normal developer. No details about the job or project were shared. Then, a coding challenge was assigned with a two-day deadline. Why would I waste time on an exercise for a job I know nothing about? Total waste of time, one of the worst approaches I've seen. I even gave this feedback to the recruiter, who ignored me and disappeared. No feedback was ever provided.
- Have you had any prior experience with technology <X>?
- For what duration have you been working with X?
- On a scale, how would you rate your proficiency with X?
React Developer
They didn't really give me a lot of info about the job they were hiring for. They set up a technical interview but didn't really say what they were going to cover. I was asked to present a project I worked on, but it felt like they didn't have any specific focus or direction for the interview. The person interviewing me seemed really eager to wrap things up fast and wasn't very pleasant or welcoming. After it was over, I didn't hear back from them at all for any feedback.
- Can you show me a project you've worked on?
Cloud Devs Interview Questions
Quoted word for word from Cloud Devs interview reports.
“Did you have to Google anything?”
Read reports →“Which programming language do you prefer the most?”
Read reports →“Can you tell me about computer science fundamentals?”
Read reports →“What is your tenure with Elastic Stack?”
Read reports →“What's your experience with Node.js in terms of years?”
Read report →“How would you approach this algorithm problem?”
Read report →“How many years have you worked with AWS?”
Read report →“Can you communicate fluently in English?”
Read report →“How did you find out about CloudDevs?”
Read report →Formats, difficulty and experience
Across all 45 Cloud Devs interview reports.