Thank you for applying to Remotebase!

The recruitment process is going to take up two weeks after which the decision on your
application will be shared with you. The process will consist of the following rounds:

Interview Stages:

The interview process consists of three stages:

Stage 1: Pre-screening - a 30-minute non-technical interview with HR and an online test on

HackerRank.

Stage 2: Technical Interview with the CTO

Stage 3: Meeting with the CEO

STAGE 1: HR INTERVIEW

Instructions:
• Acknowledge your participation in the calendar invite, for the interview.
• Make sure you have a stable internet connection for the course of your interview.
• The interview might be around 30 minutes long.
• Make sure you join in from your laptop not your phone

Evaluation Criteria:
• Educational background
• Relevant work experience
• Specific skills or “technical skills”
• Ability to work in a team environment
• Leadership qualities
• Critical thinking and problem solving
• Communication skills

Tips:
• Identify your core competencies keeping in mind the role that you are applying for
• For behavioral questions, you can cite examples from your professional life or your
academic life.
• Look up the company on LinkedIn and other places before the interview
• Keep your answers concise, relevant and authentic

STAGE 2: TECHNICAL INTERVIEW WITH THE CTO

Instructions:
• Make sure you join in from your laptop not your phone and have the correct
development environment setup that you will need to code i.e compiler, ide, etc.
• Acknowledge your participation in the calendar invite, for the interview.
• This interview will be conducted over a video call, so make sure you have a
functioning microphone and webcam.
• Make sure you have a stable internet connection for the course of your interview.


• Making sure you have the correct permissions configured for screen sharing mode on
google meet call.
• The interview might be around 50mins - 1 hour 30mins.

Evaluation Criteria:
• Fundamentals
• Live Coding
• System Design
• Domain (React, Node, relevant to candidates' area of expertise)

What you (the candidate) should expect from the following parts of the interview:

Live Coding

The candidate will be given a "real world" interview question. These would be the types of
problems an engineer could expect to regularly encounter in their workflow. Good example
questions for this would include JSON parsing or using an open-source, third-party API,
array manipulation, and string manipulation questions.

This interview evaluates a candidate's coding ability. It will reflect the candidate's efficiency
and ability to write code for most engineering tasks given to them of simple to medium
complexity, along with their simple problem-solving skills.

Algorithms

The candidate will be given an algorithmic question, whose solutions may involve topics
such as data structures, graph theory, and dynamic programming. They will be assessed on
their ability to solve algorithmic problems and the efficiency in solving these types of
problems. These questions should be of equivalent difficulty to "Medium" to "Hard"
problems. Example questions of appropriate difficulty include determining the diameter of a
binary tree.

This interview evaluates a candidate's Intelligence (Complex Problem Solving Skills).

Candidates who perform well in this interview will be more likely to solve complex problems
and will be able to take on the hardest tasks that many other engineers may not be able to
solve on their own.

Domain Knowledge

In this interview, the candidate will be asked questions from their domain that they have
worked on, their level of skill, experience, and understanding will be judged specific to their
area of expertise. Domain knowledge includes frameworks, libraries, tech stacks, systems,
etc.

Systems Design – If Needed

In this interview, the candidate will be asked to design and architect a system, related to their
field of expertise, to solve a specific problem or achieve a specific goal. This part of the
interview will be entirely conceptual (no coding!) and should be used to assess their ability to
think about the "bigger picture" and how they'd approach a real-world project.


This interview evaluates a candidate's Sophistication. This trait is required for performing
architectural design decisions and writing technical specifications. As this is a task usually
only performed by Senior and Principal Engineers, this trait would only be important for
engineers applying to those roles.

STAGE 3: MEETING WITH THE CEO

Instructions:
• Acknowledge your participation in the calendar invite, for the interview.
• Make sure you have a stable internet connection for the course of your interview.
• The interview might be around 1-hour long.

This will be a general discussion with the CEO to learn about you as a person, and how well
you fit into our company culture. Among other things, there will be a discussion on the
company’s vision and how it can align with your goals.

Lastly, the most important thing is to remain positive and breathe. We wish you all the
best!