🧭 Interview Rounds Overview¶

Most companies use a structured pipeline to evaluate candidates across problem-solving, communication, and real-world engineering ability.

🔁 Typical Interview Flow¶

1. Online Assessment (OA)¶

• Aptitude + coding test
• Platforms: HackerRank, Codeforces, company portals
• Used to filter large candidate pools early

📘 Learn pattern practice here:

• HackerRank Interview Preparation Kit
• LeetCode Interview Practice

2. Technical Interview Round 1¶

• Basic → medium DSA problems
• Time & space complexity analysis
• Problem-solving clarity matters more than speed

📘 Practice source:

• NeetCode Roadmap (Structured DSA)

3. Technical Interview Round 2 (Advanced)¶

• Medium → hard DSA
• System design basics (sometimes)
• Deep understanding of data structures & trade-offs

📘 System design reference:

• System Design Primer

4. HR / Behavioral Round¶

• Communication skills
• Cultural fit
• Salary expectations
• Personality evaluation

📘 Real HR patterns:

• Glassdoor Interview Questions
• Indeed Interview Guide

5. Group Discussion (if applicable)¶

• Communication clarity
• Team participation
• Logical reasoning under pressure

📘 GD communication reference:

• Harvard Communication Guide

⚙️ Technical Skills Preparation: Beyond DSA¶

DSA gets you shortlisted. But real engineering skills decide selection.

🏗️ Technical Stack Tiers¶

🔵 Tier 1: Core Fundamentals (Non-Negotiable)¶

These appear in almost every technical interview.

• Operating Systems (OS)
• Database Management Systems (DBMS)
• Computer Networks (CN)
• Object-Oriented Programming (OOP)

📘 Core reference sources:

• GeeksforGeeks OS Guide
• GeeksforGeeks DBMS
• GeeksforGeeks Computer Networks

🟣 Tier 2: Development (Differentiator)¶

Pick ONE stack and go deep:

• Web Dev → React / Node / Next.js
• Mobile → Flutter / React Native
• Backend → Java / Spring / Node
• AI/ML → Python / PyTorch

📘 Roadmap reference:

• roadmap.sh Developer Roadmaps

🟡 Tier 3: Industry Tools¶

These make you “job-ready”:

• Git & GitHub
• Linux basics
• Postman (APIs)
• VS Code efficiency

📘 Git reference:

• Pro Git Book

🗺️ How to Build Your Stack¶

1. Learn basics quickly (don’t over-study syntax)
2. Build small projects
3. Build 1 strong “capstone project”
4. Contribute to GitHub / open source

📚 Learning Sources (Trusted)¶

• roadmap.sh
• MDN Web Docs
• GeeksforGeeks

🧠 Key Insight¶

Companies don’t hire people who “know everything” They hire people who can think, explain, and build

❌ Common Mistakes¶

• Memorizing answers instead of understanding
• Ignoring core subjects (OS, DBMS, CN)
• Switching tech stacks too often
• Not practicing explaining aloud

✅ Technical Readiness Checklist¶

• Can you solve basic SQL problems?
• Can you explain what happens when a URL is opened in a browser?
• Can you explain Process vs Thread clearly?
• Do you have at least 1 strong GitHub project?