🧑💻 Round 1: Technical Interview – DSA + CS Fundamentals
Started off with the usual introduction — pretty standard, but don’t skip it. It sets the tone and helps ease into the conversation.
Then came an interesting question:
👉 “Can you prioritize the core CS courses you’ve taken, based on your interest?”
I gave an honest answer — but kinda messed up by placing Computer Networks near the bottom, totally forgetting that the company’s domain is networking. 😅
So yeah, tip for anyone going in: know the company’s core focus and be smart while framing your interests.
After that, they threw in a very basic DSA question:
“Add an element at the head of a linked list.”
Super simple — almost felt too easy. So yeah, definitely brush up on basic DSA — even the ones you think are too easy to be asked.
🔁 Then it Escalated: CS Concepts Deep Dive
After the warm-up, things picked up quickly:
Pointers (memory address tracing)
Memory management in C/C++
Concepts of segmentation, page faults, and virtual memory
Linked how memory allocation works in OS with how programs run in user vs kernel space
What I really liked was how the interviewer linked these topics together — it wasn’t just question after question, but more like a flow of connected ideas. Definitely tests your conceptual clarity more than mugged-up answers.
🛠️ Round 2: Project-Based Interview
Focused entirely on my resume projects:
Had to explain end-to-end implementation
Got asked about why I chose certain tech stacks
They drilled a bit into one specific feature — so know your projects well
Also asked about challenges, trade-offs, and optimizations
Nothing too unexpected here, but be honest and don’t bluff on what you didn’t build — they can tell.