Candidate Information:
- The interview process begins with all shortlisted candidates gathering in a shared Zoom waiting room, followed by technical evaluations tailored to preferred roles and an HR round, featuring extended waits between transitions.
Shortlisting Criteria
- Shortlisting relies heavily on GitHub profiles rather than traditional resumes, prioritizing candidates with active repositories, meaningful contributions, pull requests (PRs), created issues, and resolved problems to demonstrate real coding initiative. This approach filters for practical builders over those with polished but superficial CVs. Maintaining a strong GitHub presence is thus the primary gateway to even reaching the interview stage.
Overview of Interview Process:
All shortlisted applicants first joined a common Zoom room where multiple interviewers were present in separate breakout rooms, and candidates were called one by one to those rooms while others waited silently in the main space. Once invited into a room, the interviewer began by asking for your preferred role and then tailored the questions accordingly, which in your case was the Associate React Intern position. After the technical interaction ended, you were asked to exit the room and wait again for your HR turn, repeating a similar waiting pattern.
Initial Screening
- The initial screening was effectively the first interaction in the breakout room, where the interviewer confirmed your preferred role and checked alignment with your application. This step functioned as a quick validation that you were indeed targeting the Associate React Intern role and understood what it involved. Only after this brief clarification did they move deeper into technical topics and your background.
Technical Round
- For the Associate React Intern track, the questions were strongly focused on DBMS, development fundamentals, Git, and SQL rather than only React or JavaScript. You were asked conceptual questions like the difference between Git and GitHub, their relationship and dependency, common Git commands and their purposes, core DBMS ideas such as why DBMS is used, what indexing is, and why normalization matters, and security/auth topics such as the difference between authentication and authorization, why JWT is used, and how authentication is implemented in general web apps. The round clearly emphasized practical understanding of backend concepts and workflows over memorized frontend theory.
Advice for future candidates:
- If you are targeting similar companies or this role, make sure your GitHub is active and well‑maintained, with meaningful project work rather than only cloned or tutorial repositories. Build projects where you actually understand the stack, implement features yourself, and can explain trade‑offs and decisions instead of just copy‑pasting code.
Closing Note:
- Just as importantly, know the basics of every technology you have used in your projects so you can confidently describe what you built, why you built it that way, and how it works, instead of relying on copy‑pasted code or surface‑level familiarity.