Testimonials

Services

Priority DM . a day reply
₹1
Popular
Video meeting . 20 mins
₹500₹600
Popular

About me

I am currently working as a Senior Member of Technical Staff at Salesforce. I have more than 6 years of industry experience and worked with companies like Amazon and Microsoft before. Having worked at a diverse set of companies, from small startups to big MNCs, I can help the candidates explore their own career goals and help them figure out what best suits them. I am good with DSA and system design, so I will be able to help the candidates in navigating through any problems they might have with the same. I can also help with resume review, career advice, and interview tips

Frequently asked questions

What is a system design interview?

A system design interview is a hiring round, mostly used by product-based companies, where you are asked to design a large-scale system such as a URL shortener, chat app, or food delivery platform. Instead of one correct answer, you are evaluated on how you gather requirements, propose a high-level architecture, handle scale and failures, and justify trade-offs. It usually lasts 45–60 minutes and becomes especially important for mid-level and senior engineering roles.

How to prepare for a system design interview?

Start with the fundamentals — scalability basics, load balancing, caching, SQL vs NoSQL databases, sharding, CAP theorem, and message queues. Then study 10–12 standard designs like a URL shortener, rate limiter, WhatsApp, Uber, and Netflix, and practise designing each end-to-end within 40 minutes. Resources like the System Design Interview books by Alex Xu or the Grokking course give structure, but you must also speak your designs out loud and get feedback, because communication is half the evaluation.

How to practice for a system design interview?

Practise by doing, not just reading. Pick one problem at a time, set a 40-minute timer, and design it on a whiteboard or tool like Excalidraw exactly like the real round — clarify requirements, estimate scale, sketch the high-level design, then deep-dive into one component. Afterwards, compare your approach with a good reference solution and note the gaps. The biggest improvement usually comes from mock sessions where a peer or mentor questions your assumptions, since that mirrors real interview pressure.

What are the most common system design interview questions?

The classics that appear repeatedly include designing a URL shortener, a rate limiter, a chat application like WhatsApp, a social media feed, a ride-hailing app like Uber or Ola, a ticket booking system like BookMyShow, a notification system, and a distributed cache. Interviewers rarely ask these verbatim — they add constraints like "10 million daily active users" or "design for the Indian market" — so learn the underlying patterns instead of memorising one solution per question.

Is Grokking the System Design Interview worth it?

Yes, it is worth it if you are starting from zero, because it gives you a repeatable framework — requirements, estimation, API design, high-level design, deep dive — and walks through dozens of classic problems step by step. The limitation is that reading alone creates false confidence; you get the most value when you close the book after each chapter and design the same system yourself. If you already have design experience, Alex Xu's books plus mock practice may be enough.

How to learn data structures and algorithms?

Pick one language — Python, Java, or C++ — and stick with it. Learn the core topics in order: arrays and strings, hashing, two pointers, stacks and queues, linked lists, binary search, trees, heaps, graphs, and finally dynamic programming. Solve problems topic-wise instead of randomly, be consistent (1–2 focused hours daily beats 10 hours on Sunday), and maintain a mistake log for revision. Many students in India pair a curated sheet like NeetCode 150 with a book such as Data Structures and Algorithms Made Easy by Narasimha Karumanchi for theory.

How long does it take to learn data structures and algorithms?

For most people, 4–6 months of consistent daily practice is enough to become interview-ready for entry-level and mid-level product company roles. Complete beginners starting from scratch may need 6–9 months, while reaching an advanced level — hard dynamic programming, complex graph problems — can take a year or more. The timeline depends far more on consistency and regular revision than on long, irregular study sessions.

Is learning data structures and algorithms worth it?

Yes. DSA is still the primary filter used by almost every product-based company in India, from FAANG to Flipkart, Swiggy, and Zomato, and it is often what separates the pay bands between service-based and product-based offers. Beyond interviews, it sharpens how you reason about performance and scale in real engineering work. Even with AI coding tools becoming common, interviews continue to test DSA, so the return on the time invested remains very high.

Why are data structures and algorithms important?

Because they are the most objective way for a company to test problem-solving under constraints — how you break down an unfamiliar problem, choose the right structure, and reason about time and space complexity. They matter in actual work too: the difference between an O(n²) and an O(n) solution becomes very visible once you handle real traffic. That is why both campus placements and off-campus hiring drives weight DSA heavily, regardless of your college or branch.

What are the most frequently asked data structures and algorithms interview questions?

The highest-frequency problems include Two Sum, Valid Parentheses, Merge Intervals, Linked List Cycle, LRU Cache, Kth Largest Element, Course Schedule, and dynamic programming classics like Coin Change and Longest Increasing Subsequence. Most interviewers pick one easy warm-up and one or two mediums from these well-known data structures and algorithms interview questions, so preparing pattern-wise covers a large share of what you will actually be asked.

Is LeetCode worth it for data structures and algorithms?

Yes, LeetCode is still the single best practice platform for data structures and algorithms because of its problem quality, difficulty tagging, and company-specific question lists. Use it with a curated list like Blind 75 or NeetCode 150 instead of solving randomly, and revisit problems you failed after a week. Premium is optional — company-tagged lists help in the final weeks, but the free tier is enough for 90% of your preparation.

Is Grokking the Coding Interview worth it?

It is worth it if you feel lost after months of random grinding, because its biggest strength is teaching you to recognise around 20 recurring patterns — sliding window, two heaps, modified binary search, topological sort, and more — instead of treating every problem as new. If you have already solved 250–300 problems pattern-wise, the incremental value is limited, and you are better off spending that time on mock interviews and your weak areas.

Is Cracking the Coding Interview worth it?

It is still worth reading for its fundamentals and interview strategy — how interviewers evaluate you, how to think out loud, and how to handle behavioural rounds — but a portion of its question style predates the current LeetCode-heavy process at product companies. The practical approach today is to use it for concepts and non-coding-round guidance, while relying on LeetCode or a pattern-based course for actual problem practice.

Why are coding interviews so hard?

They compress problem-solving, clean code, and communication into 45–60 minutes while someone watches you, which is unnatural even for strong engineers. Questions are deliberately open-ended, companies use them as a filter because of huge application volumes, and most candidates prepare without structure — random solving with no pattern recognition or mock practice. With a structured plan and repeated mock interviews, the same format starts to feel predictable rather than impossible.

How long does it take to prepare for a coding interview?

If your DSA fundamentals are already in place, 2–3 months of focused preparation — around 1–2 hours on weekdays plus longer weekend sessions — is usually enough. Starting from scratch, plan for 4–6 months. Working professionals should keep the last 3–4 weeks purely for mock interviews, company-specific questions, and revision, because going into interviews with untested preparation is the most common reason candidates fail their first few rounds.