Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      Imaginary Cloud

      Engaged employer

      About
      Reviews
      Pay and benefits
      Jobs
      Interviews
      Interviews
      Related searches: Imaginary Cloud reviews | Imaginary Cloud jobs | Imaginary Cloud salaries | Imaginary Cloud benefits
      Imaginary Cloud interviewsImaginary Cloud Javascript Developer interviewsImaginary Cloud interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Centre
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy and Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent posts

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" and logo are proprietary trademarks of Glassdoor LLC.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalised job recommendations and updates by starting your searches.

      Javascript Developer Interview

      6 Feb 2020
      Anonymous interview candidate
      No offer
      Negative experience

      Application

      I applied online. The process took 3 days. I interviewed at Imaginary Cloud in Jan 2020

      Interview

      The interview process is divided into 3 steps: 1- Technical interview 30-60min with questions about OOP principles, linux, git and databases; 2- A non-technical interview in order to know you better; 3- A challenge to create an application with both backend, in NodeJS, and frontend, in ReactJS. It doesn't matter what is the role you are applying, you need to know the OOP, at least in theory. I have applied to a Javascript role and not a single question was made about it, which doesn't make any sense to me.

      Interview questions [11]

      Question 1

      what is an abstract class
      Answer question

      Question 2

      what is an interface
      Answer question

      Question 3

      what is a private method
      Answer question

      Question 4

      what is git
      Answer question

      Question 5

      what is git pull
      Answer question

      Question 6

      what is git rebase
      Answer question

      Question 7

      what is git push
      Answer question

      Question 8

      what "ls" command does
      Answer question

      Question 9

      what is the command to list the processes running
      Answer question

      Question 10

      what is the command to kill a process
      Answer question

      Question 11

      what is the database query to count the number of rows of a table
      Answer question
      avatar
      Imaginary Cloud response
      6y
      Hi, We regret to hear that you didn’t have a pleasant experience in our hiring process. As you mentioned, our hiring process is divided into three stages, that we often conduct in less than two weeks: Stage 1 - Understand how well the candidate knows the common body of knowledge for the position (in this case, Software Engineering); Stage 2 - Understand if we are the right place for that next step; Stage 3 - Understand how mature the candidate is in the technology/tooling that he/she is applying and if we like to work together; We look for people that can join our team and help us grow while growing with us. Thus why we designed Stage 1 the way you’ve done it. In our industry, technology shifts happen fast and often, and we need to ensure everyone is well prepared for those moments. We only dive into the specifics of the technology on Stage 3. The reason why we do this is that it’s easier to learn a technology (i.e. Javascript in your case) than to have a solid knowledge of Software Engineering or Computer Science. In any case, we thank you for your feedback. Best of luck in the future.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.