Ayush Kumar Shukla

Stop treating DSA like a checklist, esp. if you’re already a mid-level SDE in tech. Early on, I was obsessed with finishing problem sets and hitting “X” number of questions. It gave me a false sense of progress, but you have to know that the interviewers don’t just copy paste LeetCode problems and ask them in the DSA rounds. So the problems will definitely look unfamiliar no matter how much you grind LeetCode. ‘ But here are some patterns that I’ve personally seen show up in interviews a lot: 🔸 Two Pointers 🔸 Backtracking 🔸 Binary Search 🔸 Graph Traversals (BFS & DFS) 🔸 Dynamic Programming (Knapsack, LIS, LCS) 🔸 Monotonic Stack 🔸 Tree Traversals & Views 🔸 Top ‘K’ Elements (Heap/Priority Queue) 🔸 Bit Manipulation What interviews are really testing is → your ability to identify, adapt, and apply. And I faced 20+ rejections before finally focusing on patterns over problems, but you don’t have too. Learn to identify patterns. Build intuition. That’s what makes you interview-ready. If you’re a working SDE restarting your prep while juggling a busy 9-5, I strongly recommend getting mentorship from industry experts at Bosscoder Academy. 🔗 Explore their programs here → https://bit.ly/3JWWnKI They’ve already helped 2200+ engineers crack top product-based roles with a well-structured curriculum for DSA, SD, and full-stack development, 1:1 mentorship from industry experts, and 100% job switch support. #dsa #career #interviews #sdeprep #jobswitch #collab

1,781

104 Comments

From doing BCA in a Tier-3 college without any support or coding culture to cracking Amazon (30 LPA+) just 2 years later on his own...Vaibhav's story will teach you a lot. In 2020: Vaibhav Dangayach graduated from his BCA from a Tier-3 college, decided not to pursue MCA, and went on to build his skills. Just 2 years later, in 2022, He managed to crack Amazon as (his position) I recently had him over on my podcast, and I asked him his exact approach that he followed for Amazon. This was it:  1. Ruthless focus on DSA – Vaibhav’s first 12 months after BCA = pure DSA grind. – Picked one language (C++) and went all in. – Every single day: solved LeetCode & SDE Sheet questions.   → Not random practice, but pattern-based prep.   → Focused on arrays, strings, trees, graphs, DP, stacks/queues. – Target: Finish the entire SDE sheet before even thinking about Amazon. If you’re serious about DSA this year, do check out my latest DSA Cohort: https://lnkd.in/gJQZWGeh We’ve all this set up already for your growth: → Live DSA sessions to build deep problem-solving skills  → Gen AI module to stay ahead of the curve  → Low-Level Design recordings for strong backend prep  → And sessions with FAANG recruiters and engineers to understand how hiring really works Coming back to Vaibhav’s journey.  2. Mock Interviews & Speed Under Pressure – Joined online mock interview sessions & practiced timed coding rounds. – Simulated the exact Amazon environment:   → Solved 2-3 medium/hard questions back-to-back, no peeking at solutions.   → After each session, did a ruthless self-review:   * Where did I get stuck?   * Which patterns do I still fumble?   * Which topics kill my speed? – Weekly routine: 1–2 mock interviews with peers and checking back on his progress.  3. Projects & Resume – Didn’t spam the resume with college projects. – Picked 1–2 strong development projects:   → Deployed real apps, showed end-to-end ownership (not half-baked clones).   → Added GitHub links, wrote clear READMEs, included system design basics. – For Amazon, resume is your first filter.   → Highlighted only what mattered: skills, projects, impact.  4. Smart Application Strategy – Didn’t wait for campus drives (there weren’t any). –Applied everywhere off-campus: Amazon careers, LinkedIn, referrals, even via coding contests. – Built connections: reached out to employees for referrals, but only after having a solid resume + LeetCode profile to show. –  Not once was he asked about his BCA, CGPA, or MCA. – Every interviewer cared only about:   → Can you solve problems?   → Can you explain your code?   → Have you built anything real? – All that matters: your DSA, your projects, your interview skills. Continued in Comments ↓ If you’re in BCA, remember: → Get top-tier at DSA. → Build 1–2 real projects. → Prep for interviews like it’s a sport. → Apply everywhere, don’t wait for luck. That’s how Vaibhav did it. That’s how you can too.

492

21 Comments

🚀 Beginner → Advanced SDE Roadmap When I started my journey in tech, the biggest question was: "Where do I even begin?" With so many resources out there, it’s easy to get lost. That’s why I decided to put together a step-by-step roadmap (Beginner to Advanced) for anyone who wants to become a Software Development Engineer (SDE). 📌 What’s inside this roadmap PDF? ✅ Programming fundamentals (where to start) ✅ DSA patterns that crack interviews ✅ System Design & OOPS ✅ Development skills (Web/Backend/DBs/Cloud basics) ✅ Advanced topics to stand out ✅ Projects + Resources to practice This isn’t just a list of topics. It’s a structured path you can actually follow – whether you’re in college, switching careers, or polishing your SDE skills. 💡 If I had this when I was starting, it would have saved me months of confusion. Hopefully, it saves you that time! 📄 Download the PDF roadmap here: [Attach PDF / Link] Would love to know 👉 Which stage are you currently at: Beginner, Intermediate, or Advanced? ❗ Need personalized guidance for your GSoC journey? Get 1:1 mentorship to crack GSoC 2025 with confidence 👉 https://lnkd.in/gEvwbS4p #SDE #Roadmap #CodingJourney #SoftwareEngineering #DSA #SystemDesign #Programming #CodingRoadmap #SoftwareDeveloper #InterviewPreparation #TechCareer #100DaysOfCode #LearnToCode #CodeNewbie #CareerGrowth

709

74 Comments

Janta ne manga, and here it is �� A lot of freshers messaged me asking if they need to complete my full System Design course to sit for companies like Uber, Zomato, etc. So here’s the answer — No, you don’t need to watch the entire LLD playlist if you're aiming for an SDE-1 role. And to give you a more structured answer, so that there’s ZERO confusion, I’ve made a 15-minute video explaining exactly what and how much you should cover from the playlist, based on whether you’re aiming for SDE-1, SDE-2, SSE-1, or SSE-2. Check it out : https://lnkd.in/ga4qBDHK

604

16 Comments

🚀 How to Reach 1800+ on LeetCode (Knight Tier)... Climbing to 1800+ on LeetCode isn’t about magic — it’s about consistency, contest strategy, and smart upskilling. Here’s what actually works (from experience and observation 👇): ⚔️ 1. Target Consistency, Not Perfection To get to 1800+, you don’t need to win contests — just place consistently in the top 1-2k. This usually means solving 3 problems every time. ⚡ 2. Speed is King for the First 2 Problems Problems 1 and 2 are often standard — just well-disguised. Practice quick, crisp implementation. Read constraints. Think clean. Type faster. 🧠 3. Master the Standard Toolkit Make these second nature: ✔️ Binary Search on Answer ✔️ Prefix Sum Tricks ✔️ Dijkstra, BFS/DFS ✔️ Union-Find (DSU) ✔️ Bit Manipulation Basics ✔️ 1D/2D Dynamic Programming If you can implement these blindfolded, you’re ahead of most. ⏱️ 4. Simulate the Pressure Give every contest, or do virtuals regularly. They're only 90 minutes — but that time flies. You must think + code + debug fast. That takes practice. 🎯 5. Accuracy Over Speed In a contest, getting it right first time matters more than being fast. 5-minute penalties + debug time can destroy your rank. Train yourself to think clearly and code once. 📦 6. Learn Intermediate Tools (Even as Black Boxes) The 3rd problem often hides behind a known trick. Even if you don’t deeply understand them (yet), know when to use these: ✔️ Segment Trees ✔️ Sparse Tables ✔️ Binary Lifting ✔️ Bitmask DP ✔️ Tarjan’s / Kosaraju’s (SCC) ✔️ Ternary Search ✔️ Rolling Hash / Z / KMP A good template + intuition can be enough to break through. 📈 TL;DR – Rating Grows With Patterns Solve enough contests and you'll see: ✅ Patterns repeat ✅ Speed improves ✅ Pressure becomes manageable ✅ Confidence builds And suddenly, 1800+ isn’t a ceiling. It’s just another checkpoint. Stay tuned for more such content!! ✌🏻🚀

440

16 Comments

Not gonna lie, cracking service-based companies is way easier than what most people think — especially compared to PBC prep. If you're aiming for companies like TCS, Infosys, Wipro, Cognizant, etc., you don't need to grind 1000+ LeetCode mediums or get deep into DP, Graphs, Segment Trees, and all that. What actually works is clarity on basics + consistency. Here’s literally all you need to focus on 👇 🧠 DSA (don’t overdo it) Arrays & Strings (palindrome, frequency, sliding window basics) HashMap / HashSet Sorting & Searching (including Binary Search) Stack/Queue – basic problems Time & Space complexity 💻 Language Basics Stick to one language (Java, C++, or Python). Make sure you’re good with: Loops, functions, conditionals Arrays & Strings OOPs 📘 Computer Fundamentals OS: Processes, Scheduling, Deadlocks DBMS: Joins, Normal Forms, ACID CN: OSI Model, TCP/UDP basics OOPs: Inheritance, Polymorphism, Abstraction, Encapsulation 🧩 Aptitude > Hard Algorithms (for most SBCs) Time & Work, Series, Puzzles English grammar + comprehension Use IndiaBix, PrepInsta – they’re more than enough for online tests 💬 HR Round ≠ Just Talking Tell me about yourself Why this company Situational Qs (team, pressure, conflict, etc.) If you're prepped on these, SBC prep feels more like revision than a grind. It's honestly more about consistency and knowing what not to waste time on. If you’re prepping, hope this gives some clarity. Follow 🤝 : Prateek Goel #consistency #coding #leetcode #learning #sbc #pbc #tcs

278

13 Comments

🚀 DSA for Frontend Engineers If you’re a frontend engineer thinking, “Why should I learn DSA? I just build UI…” That’s where most people go wrong. Top product companies and FAANG aren’t just looking for people who can make buttons look pretty, they want engineers who can solve problems, optimize systems, and think in algorithms. That’s what separates a developer from a software engineer. Even if you work with React or Node, DSA builds the foundation that helps you reason better, write efficient code, and stand out in interviews. Don’t escape it. Just learn it properly, one concept at a time. Because the truth is, Frontend interviews at good companies still have the same bar as backend ones. Master your DSA. Build your foundation strong. 🧠 If you want to learn from me, checkout Namaste DSA - https://lnkd.in/gaQh7M-P Just try Namaste DSA once, I bet you'll start loving DSA. And in case you feel it's not for you, just take your money back. We have a 7 day no questions asked refund policy. Cheers, Akshay Saini 🚀 #dsa #frontend

1,238

17 Comments

I grinded Leetcode, CodeChef & Codeforces for 3+ years before I finally got my first internship during placements. Back then, there were about 2000 total problems on Leetcode, today they’re over 3500+ (It's really too much) Yet 90% of MAANG+ companies are still asking Leetcode-style questions, and the most common questions college students ask me about Leetcode: – How do I even start? – How many questions are enough? – How to select which questions to solve? Well, this post is the answer to everything. How to Start (Step-by-Step):  1. Learn the Basics Before Jumping In  - Stick to one language you’re comfortable with (Python, Java, or C++).       ◘ Python is beginner-friendly and has helpful libraries.       ◘ Focus on basics: loops, conditions, arrays, strings, functions, and classes.  - Data Structures and Algorithms:    ◘ Start with arrays, strings, linked lists, stacks, queues, hash tables, and binary trees.    ◘ Learn sorting, binary search, and recursion. These are crucial for many problems.  2. Choose the Right Problems    ◘ Start Small: Solve easy problems first to build confidence.    ◘ Use curated lists on Leetcode, you can find them easily  ◘ Focus on common patterns like sliding window, two pointers, backtracking, and dynamic programming.  3. How Many Problems Are Enough?    ◘ 300 high-quality problems is the sweet spot. This ensures you cover all key topics and patterns.    ◘For each topic, solve 4–5 easy problems, then move to mediums. Skip hard problems until you’re confident.  4. Practical Tips While Solving Problems    ◘Spend 30–60 minutes per problem.    ◘ If stuck, check solutions, but rewrite and re-solve them yourself.    ◘ Focus on why the solution works and the key insight that simplifies the problem.  5. Consistency is Everything    ◘ Solve 1–2 problems every day. Don’t rush to finish. Quality matters more than quantity.      - Revisit tough problems after a few weeks to strengthen your understanding.  6. Simulate Interviews:  ◘ Practice in timed conditions:        - Easy: 15 minutes        - Medium: 30 minutes        - Hard: 1 hour    ◘ Use mock interviews or contests to get used to pressure.  LeetCode can feel overwhelming, but it’s about consistency and working smarter. Focus on patterns, solve the right problems, and revisit tough ones. Stick to the process, you’ve got this. P.S: If you’re currently preparing for DSA, HLD, and LLD. Check out my one-stop resource guide on Topmate: https://lnkd.in/e-detVTg (280+ students are already using it) This guide will help you with: - DSA, HLD, and LLD for interviews - good resources that I used included to save you time - lots of problems and case studies for DSA and system design

1,362

42 Comments

This blind 75 leedcode challenge can help you switch an SDE role at MAANG💪🏻 This is the blind 75 leedcode challenge which will help you revise & strengthen your problem-solving skills before your next SDE Interview. When it comes to mastering DSA, don’t ever fall into the theory trap. ❌ Instead, focus on solving more and more problems. This doc will help you solve 75 problems that are important for DSA interviews. Thanks to Bosscoder Academy for creating this resource 🙌. Check their program here: https://bit.ly/3PzsWOz They can help you with: 💡 Structured programs for learning DSA, System Design, and Full Stack Development. 💡 Personal mentorship from industry veterans. 💡 Live classes and 24/7 doubt support. 💡 Real-life, relevant projects with Job Switch Assistance. Save this doc for your preparation and crack your dream job! #softwareengineer #maang #interviewprep #dsa #collab

356

21 Comments

Freshers, Stop Ignoring Core CS Subjects Just mugging up DSA does not make you industry-ready. Too many are skipping: OS (Processes, Threads, Scheduling) DBMS (Indexes, Transactions, Normalization) Computer Networks (HTTP, DNS, TCP/IP) Basic System Design Why Core CS Matters: Tech interviews often include DBMS, OS, and CN questions. DSA clears round 1. Core CS helps in LLD/HLD, real-world projects, and long-term growth. You can’t build reliable systems if you don’t understand how they work under the hood. Quick Resources: OS: Galvin, Neso Academy (YouTube) DBMS: Ramez Elmasri, Gaurav Sen (YouTube) CN: Computer Networking by Kurose System Design: System Design Primer (GitHub) Tip: 70% DSA + 30% Core Subjects = Balanced Prep Follow Upasana Singh for more such reads.

639

21 Comments

I’m an SDE-2 with 3 YOE. And I’ve noticed almost every mid-level SDE make this one mistake (including me, once)👇 → Believing that coding alone will get you your next big switch. That is not career growth. That is tunnel vision. And tunnel vision can hold you back. For me, it wasn’t just endless solving LeetCode. It was things like: 🔸 Showing impact (not just “code pushed,” but what it solved or improved) 🔸 Building visibility (sharing learnings, starting discussions, writing small posts) 🔸 Practicing system design regularly (not just before interviews) 🔸 Asking for feedback (even when it was uncomfortable) And honestly, when hiring managers see you combine coding with ownership, design, and collaboration, that’s when you really start to stand out. So here’s my real growth tip for SDE-2s and above: “Stop the endless DSA grind. And start building a profile that shows breadth, depth, and consistency.” That’s when the opportunities start chasing you. And if you’re preparing for your next switch while managing full-time work, Bosscoder Academy can help you get structured with the right balance of DSA, System Design, and Full Stack. 🔗 Explore their programs here: bcalinks.com/fTFNESL  They’ve already helped 2200+ engineers switch to top PBCs with structured prep in DSA, System Design, and Full Stack, 1:1 mentorship, mock interviews, resume support, and 100% job switch guidance. 📢 P.S. Their FESTIVE Sale is LIVE and all their programs are 25% OFF for a limited time, so time to upskill now! #career #jobswitch #sdeprep #pbc #tech #collab

585

14 Comments

Discord pays 1.3 crore for SDE-1 role😱😱😱 How discord indexes trillions of messages Initially there architecture was very simple - New client messages went to a Redis queue. - Background workers read messages from Redis and indexed them into an Elasticsearch cluster. - Messages were grouped (sharded) by channel or guild. They weren’t able to scale this system after 2017 - Redis had no replayability: if ES or workers went down or errors occurred, some messages could be lost. - The Elasticsearch cluster grew very large (~200 nodes), which led to increased failures, coordination complexity, and difficulty doing rolling upgrades or restarts. - For very large guilds / channels, the shared‐channel approach hit limits — huge indices, resource contention, and inefficiencies. - Bulk indexing batched messages across many shards/nodes; a failure of one node meant the whole batch often failed → high message loss (e.g. ~40% failure in some bulk batches) when nodes dropped. New architecture- - Replaced Redis with a Pub/Sub system for indexing messages (for replayability) - Discord Deployed Elasticsearch on Kubernetes - Instead of a single giant ES cluster, they moved to many smaller clusters (in a “cell” architecture) - Bulk indexing was improved: messages are batched by destination, i.e. per index/cluster, so bulk operations happen within a single node or small subset rather than fan‑out to many - They introduced better support for very large guilds (called “Big Freaking Guilds” or BFGs): for those, use indices with multiple primary shards, and use a reindexing flow to gradually move to a new index with more shard capacity, all while keeping queries live. Discord #discord #systemdesign

179

11 Comments

Dear LeetCode Grinders, Sometimes, just sometimes, do look beyond solving problems��� Yes, DSA is important. But thinking it’s the only thing that matters? That’s where many go wrong. Here’s the reality: System design matters – Even for SDE-1 and SDE-2 roles, companies check if you understand how to structure real-world applications. Projects & real-world work – Your resume shouldn’t just say "Solved 500+ DSA problems." Hiring managers want to see what you’ve built and how it works. Have at least 1-2 good projects you can talk about. Communication matters – You might be great at coding, but if you can’t explain your approach or talk about teamwork and challenges, it can cost you the offer. Mock interviews help more than you think – Writing code in silence is one thing. Explaining it under pressure is another. Practice real interviews before the actual ones. DSA will help you clear the coding round but won’t get you the job alone.  Focus on the full picture, and you’ll have a much better chance of cracking your dream role. So start preparing with intention, not just repetition. And if you need guidance, platforms like Tutort Academy can help you structure your efforts the right way. Check more-https://bit.ly/41DwEfC With a proven track record of helping over 1,250 professionals land roles at top companies, Tutort Academy provides the support and resources you need to succeed. #interviewtips #leetcode #dreamjob #tutortacademy

102

18 Comments

DSA this. System Design that. As an SDE with 4+ YOE, I’ve cracked offers at Google, Atlassian, Adobe, Uber, etc., with just this one trick: Company Specific Preparation (My personal Leetcode Strategy) I learned this the hard way. In my early attempts, I used to prepare the same way for every company, same topics, same mock questions, same study plan. But when I started appearing for interviews, I realised something simple but game-changing: every company tends to follow a pattern. That’s when my prep changed completely 👇 ✅ Filtering questions on Leetcode → I started picking problems by Company Tags on LeetCode. This helped me focus on what’s actually asked, not just “top 100” lists. ✅ Used Discuss Section → On Leetcode real candidates share question variants, edge cases, & interviewer expectations there. ✅ Mock Assessment → I simulated real interviews using LeetCode’s assessment feature, and it helped me manage pressure better. Apart from this, I also read the reviews for each company beforehand, this helped me analyse the interview structure, & even specific rounds like ‘Googliness’ etc. All this took time. And when you’re working full-time, juggling tasks and interviews, it’s hard to do this alone. So you can check out Bosscoder Academy. 📌 Check them out here: https://bit.ly/4lett6B They don’t just teach, they help you strategically prepare for your target companies. And they’ve already helped 2200+ engineers crack top product-based roles with a well-structured curriculum for DSA, System Design, and Full Stack Development, 1:1 mentorship from industry experts, and 100% job switch support. #sponsoredpost #Google #Atlassian #Tech #Career #InterviewPrep #Growth

1,638

73 Comments