Telephonic / Exploratory discussion
- generally takes from 20 mins to a maximum of 60 mins
- used to assess eligibility/fitment of the candidate for the role
- can be technical or a mix of technical & non-technical questions
Notes:
- Telephonic discussion evaluates the candidate using a set of technical questions
- Exploratory discussion evaluates the candidate using technical/non-technical discussion
Tips:
- Brush your knowledge of the technologies and frameworks used in your projects and the skills expected
- Learn about the company and go through the job description very well
Machine coding / Assessment
- generally takes around 60 mins to a maximum of 120 mins
- used to assess core frontend skills or tech stack knowledge of the candidate
- purely technical round focused on frontend skills
Notes:
- Machine coding expects you to build or solve mini frontend projects or feature
- Machine coding round allows you to access internet to search code syntaxes
- Assessment can be a quiz or set of problems to solve (may involve both frontend & problem solving)
Tips:
- Practice HTML, CSS, JS and DOM mainpulations very well
- Machine coding problem can be asked to solve using pure HTML + CSS + JS or with a framework
Problem Solving
- generally takes from 30 mins to a maximum of 60 mins
- used to assess the analytical and problem-solving skills of the candidate
- purely technical round involving problem solving & DSA, but may not focus much on frontend skills
Note:
- expects you to understand the problem, get requirements clear, and come up with an optimized solution
- generally asked to live coding using google docs or code editor
- rather than final output and syntaxes, approach and methodologies are focused more
Tips:
- Practice various problems/DSA very well, by going through relevant materials before the interview
- Ask questions to clarify your understanding. Clarify all your doubts with the interviewer before solving
- Explain your approach to the interviewer and then proceed to solve the problem
- It should not be an issue if you are not able to come up with an optimized solution in the first go
- Think out loud while solving the problem and share your thought process
Take home assignment
- generally takes from 1 day to 1 week
- used to assess the capability of the candidate to work on real-time web application
- purely technical challenge which requires project setup knowledge from scratch
Note:
- will not be included if machine coding round is already conducted/planned
Tips:
- Prepare well on one of the frontend frameworks like React, Angular, Vue
- Also cover different aspects of the project such as:
- Project Setup
- Repo setup
- Unit testing
- Deployment etc.
Technical Discussion
- generally takes around 40 mins to 60 mins
- used to assess the technical strength of the candidate
- is a purely technical round focused on frontend fundamentals and libraries/tools/frameworks
Notes:
- won't be restricted to scripted questions and can include anything technical
- multiple technical discussions can be scheduled depending on the requirements
- generally involves live coding with execution over screen sharing
System design
- generally takes around 40 mins to 60 mins
- used to assess the understanding & knowledge of the candidate w.r.t product architecture & design
- purely technical round, focused on functional & non-functional aspects
Notes:
- won't be restricted only to frontend but can also involve engineering, UX, design thinking, etc.
- expects to explain the interaction and integration between different components/layers of the system
- will not be included for SDE1 role generally
Cultural fit / Managerial
- generally takes around 30 mins to 60 mins
- used to finalize if the candidate is fit for the job or role
- is generally a non-technical round, but may involve technical challenges and puzzles
Notes:
- expects the candidate to answer different scenarios based on the experience
- usually conducted by the hiring manager or higher management roles
Tips:
- Prepare and make notes of the projects you have worked on so far
- Follow the STAR approach to answer scenario-based questions
Visit FAQs section.