1. Application/Resume Screening
What happens: Recruiters review your resume to match your skills with the job description.
Tips: Tailor your resume with keywords from the job posting. Highlight relevant projects and experience.
📞 2. Initial HR/Recruiter Call
Duration: 15–30 minutes
Focus:
Role overview
Resume walkthrough
Salary expectations
Availability
Tip: Be clear and confident. Know your resume well.
đź’» 3. Technical/Online Coding Assessment
Platform: HackerRank, Codility, or internal test platform
Types of Questions:
Algorithms & Data Structures (arrays, strings, trees, graphs, etc.)
Time/space complexity analysis
Tip: Practice Leetcode, Codeforces, or similar.
🧠4. Technical Interviews (1–3 Rounds)
Format: Live coding or problem-solving on a whiteboard or shared IDE
Topics:
Core programming (C++, Java, Python, etc.)
System design (for mid/senior roles)
Object-oriented design
Debugging and code review
Domain-specific questions (e.g., multithreading, networking)
Tip: Communicate your thought process clearly.
⚙️ 5. System Design Interview (For experienced candidates)
Focus:
Designing scalable systems
Trade-offs and architecture choices
Tip: Use real-world analogies and mention technologies appropriately (e.g., load balancer, caching, DB sharding).
🤝 6. Behavioral / HR Interview
Framework: STAR (Situation, Task, Action, Result)
Topics:
Team collaboration
Conflict resolution
Project challenges
Tip: Prepare stories from past experience.
âś… 7. Final Round / Onsite Loop
Often a series of 3–5 interviews in one day (remote or onsite)
Covers all of the above areas + sometimes a culture fit interview