Prakhar Singh Chauhan

Your friend take 3 mins, read the problem 3x, and then code and end up cracking SDE-1 Microsoft.  You read it once and start coding, you’re not the same bro. Your friend take the first 15 mins to decide approaches for questions and end up SDE-1 Amazon Meanwhile, you’re on your 2nd problem with no thought given, you’re not the same bro. Your friend see the problem & can immediately see the type of pattern on and end up SDE-1 Uber You see the problem and think, “ye meine pehle kiya tha kya”, you’re not the same bro. 95% of people who appear for the first DSA rounds at PBCs offering 25-30LPA get rejected there itself. The biggest factor for that is your preparation method for DSA. The wrong way will lead you: - force yourself to memorize solutions - panic if the problem is new and unseen - mess up constantly during coding live in an interview The right way will lead you: - be calm, focused, and use your time - never panic cause you know the patterns - never force cram anything, purely understand - impress the interviewer with your organized thinking A person who does pattern-based learning >>> will always win when compared to one who doesn’t. I know the right way, because I did the exact thing and it led me to results and so do all the other folks who’re getting results. It all starts with a good preparation strategy, one of the best resources you can go for is this DSA pattern cheat sheet that I’ve heard about from 100s of students out there. Check out the product here- https://lnkd.in/g_GkJUsN

546

35 Comments

Oracle laid off nearly 10% of its 28,800 employees in India, mainly from software, cloud, and support roles. Reports say this move is linked to their AI expansion plans and partnership with OpenAI for building AI infrastructure in the U.S. This is a reminder that AI is not just transforming tech, it’s reshaping jobs too. #Layoffs #Oracle #AI #Career #TechNews #Upskill

405

6 Comments

* Whether it’s Leetcode, GFG, or Blind 75 → At its core, it’s about understanding *why* the solution works, not just what the code is. * Whether you mug up Google’s “most asked” list or crack 200 Amazon questions → At its core, it’s about thinking on your feet, not recalling a pattern from memory. * Whether you’re prepping for system design at Uber or DSA at Microsoft → At its core, it’s about breaking down new problems, not just repeating what you practiced. * Whether you face a friendly interviewer or a senior who digs deep → At its core, it’s about communicating your thought process, not just spitting out code. * Whether you’ve solved 500 questions or just 50 → At its core, it’s about the fundamentals, problem solving, clear thinking, and adaptability. Once you’ve given enough interviews at FAANG+ companies, have faced rejections, and spent enough time in the industry, you realize the #1 mistake in coding interviews is thinking you can just memorize the answers. You can’t predict the exact questions. You can’t game the system. But you can train your brain to solve any problem, no matter how unfamiliar. * Practice talking through your logic, not just typing. * Try whiteboarding without syntax help. * Focus on understanding patterns, not memorizing them. Tools and question banks will keep changing. Deep problem-solving skills last your whole career. If you’re still stuck memorizing, you’re setting yourself up to fail when a curveball comes. Don’t memorize, master the fundamentals. That’s how you truly stand out.

191

20 Comments