Abhay Singh

I admire SDEs earning 6 LPA. And I admire SDEs earning 30 LPA. But what really separates the two? → Mostly it's just 8–12 months of intentional, focused effort. I’ve seen this shift happen again and again in my 2+ years as an SDE. And no, it doesn’t come from randomly grinding LeetCode or binge-watching tutorials. 📌 It comes from clarity, consistency, and doing the work most people postpone. Here’s what I’ve noticed about engineers who break into top PBCs vs those who stay stuck 👇 ✔️ No passive prep ✔️ No “I’ll start next week” ✔️ No solving problems without a roadmap Instead, they: ▪️ Master ~20 core DSA patterns that cover most interview questions ▪️ Revisit CS fundamentals + design tradeoffs deeply ▪️ Take weekly mocks and review their mistakes seriously ▪️ Think in systems, not just functions ▪️ Upgrade their resume and communication alongside coding That’s what real SDE-2/SDE-3 prep at top PBCs looks like. So If you’re at 6–10 LPA today and targeting 30+ in your next switch, don’t wait for the “right time.” 📌 Revise deliberately. 📌 Ask for structured feedback. 📌 Prepare at the level you want to get hired for. And if you want structured, personalized prep built for working SDEs targeting top PBCs, Bosscoder Academy’s programs are designed exactly for that. 🔗 Explore their programs here: bcalinks.com/5mMnY9Q They’ve helped 2200+ engineers crack top PBC roles through: 💡 A structured curriculum to master DSA, System Design & AI 💡 Real-world, AI-powered projects with 24/7 doubt support 💡 1:1 mentorship from experienced engineers 💡 Resume reviews, mock interviews & complete job-switch guidance #collab #tech #pbc #jobswitch #dsa

636

58 Comments

If you apply to Zomato for an SDE role, you’ll face a System Design round. If you apply to Razorpay or Atlassian, you’ll face a System Design round. If you apply to Zepto, PhonePe, or Groww, you’ll definitely face a System Design round. If you apply to Hotstar, Flipkart, or Dream11, you must be ready for System Design. Every fast-growing Indian product company will test your system thinking skills. This is not a DSA round. This is not about writing code. This is about building scalable, real-world systems. What kind of problems are asked? Some examples: - Design a Rate Limiter - Design WhatsApp or Slack - Design Uber or Ola - Design a Notification Service - Design Zomato Feed - Design a File Storage System Almost every company tests this, and that’s exactly why I focused on System Design and compiled a detailed yet beginner-friendly guide to crack it. Here’s the link: https://lnkd.in/dte69Z5N What do they test? - Your thought process - Trade-off handling - Communication clarity - High-level design + Low-level components - Scaling and bottlenecks - Real-world awareness How should you approach it? - Ask the right clarifying questions - Don’t jump into the tech stack, start with use cases - Think in components - Always talk about data flow and scaling - Handle traffic, failure, and reliability - Prioritize clarity over complexity - Use diagrams to communicate This is what they look for: - Not whether you’ve memorized patterns. - But whether you can build systems like an engineer. 𝗞𝗲𝗲𝗽𝗶𝗻𝗴 𝘁𝗵𝗶𝘀 𝗶𝗻 𝗺𝗶𝗻𝗱, 𝗜’𝘃𝗲 𝗽𝗿𝗲𝗽𝗮𝗿𝗲𝗱 𝗶𝗻 𝗗𝗲𝗽𝘁𝗵 𝗦𝘆𝘀𝘁𝗲𝗺 𝗗𝗲𝘀𝗶𝗴𝗻 𝗚𝘂𝗶𝗱𝗲. 𝗚𝗲𝘁 𝘁𝗵𝗲 𝗚𝘂𝗶𝗱𝗲 𝗵𝗲𝗿𝗲: - https://lnkd.in/dte69Z5N Stay Hungry, Stay FoolisH!

177

26 Comments

“Startup folks are always grinding while MNC folks are chilling.” I used to say this as a joke… until it started feeling a bit real. Recently I had a deep conversation with a professional from Adobe. Their perspective was very clear: "Big companies are great when you have a family, EMI, and heavy responsibilities. The work is stable, well-structured, the load is manageable, and a lot of it is maintenance or extensions of existing systems with solid guidance." But they also admitted something important: in today’s market, no company can truly guarantee job security. Recessions and layoffs don’t knock only on startup doors. Right now I’m working at a startup, and the experience is completely different: -> I’m not just “writing code” – I’m helping build something from scratch. -> I’m involved in pipelines, architecture, coding, and integrations, not just a tiny module. -> I’m pushing things all the way to real hardware, making the software actually run on devices – which is insanely exciting to me. -> Once the product is ready, we don’t stop at “code is done” ... we also think about business strategy, product decisions, and real users. The salary at a startup may not match MAANG in the early years, but the learning curve and ownership are on a different level. You’re not just a software developer; you start becoming a founding engineer mindset person ... the one who understands tech, product, and business together. I’m genuinely enjoying this phase where I’m allowed (and required) to wear multiple hats: architect, developer, integrator, and sometimes even mini-PM and business thinker. For anyone early in their career: -> If you want stability and structure, big companies are great. -> If you want chaos, ownership, and accelerated learning, startups can be a goldmine. Both paths are valid — it just depends on what you want right now in your journey. 🚀 MAANG's : Google, Meta Facebook, Amazon, Apple, Netflix Startup : Drones Tech Lab :) #startupLife #FoundingEngineer #LearningByBuilding #SoftwareEngineering #CareerJourney

23

1 Comment

🛑 Stop Sending Applications. Start Submitting an Offer-Winning Strategy. I have worked at Microsoft as a Software Developer and I studied at Indian Institute of Technology, Kanpur. I've not only sat in the interview chair at top tech firms, but through Prepflix, I've helped 1000+ engineers break into Google, Amazon, and Microsoft with an average 350% salary jump. I know exactly what works, and what doesn't. The simple truth is: Your current resume is the primary bottleneck to your dream salary. 👉 The Brutal Math of the Job Market You might be a System Design genius or a LeetCode wizard, but all this is useless if your resume fails to communicate this instantly. Your resume is not just your history, it's a investment portfolio for your organization. They will be investing lakhs if rupees and hundreds of hours behind you based on this document. Your resume is just a bland list of duties you performed at various organizations. What is really needs to show is how you will be solving the organization's problems. The Problem: Most resumes are laundry lists of duties. They say, "I contributed to XBOX Marketplace development". The Winning Strategy: My students learn to frame this as: "Contributed to the development of the XBOX Marketplace platform, currently used by millions of customers worldwide, proving scalability in high-volume, global systems." See the difference? We shifted the focus from a task to business impact and measurable scale. That is the language of a Senior Engineer. 👉 Why Optimization is Non-Negotiable If you are tired of applying to jobs you are totally qualified for and not getting any replies, let me help you get you your next interview! I will create a resume for you that passes the two critical tests: The ATS Filter: Your document must be syntactically correct and keyword-dense to pass the automated screening systems. A faulty resume here means a guaranteed rejection, regardless of your talent. The Recruiter’s 7-Second Scan: Your value proposition—the 350% salary jump 11 potential—must be scannable and undeniable within the first glance. We know your time is better spent preparing for the actual interview. Let us optimize your single most important piece of professional collateral. FREE OFFER: The first 50 people to ping me will receive a full, done-for-you resume revamp at absolutely no cost!

13

Google Is Actively Hiring Frontend Engineers, ₹25-45 LPA+ Roles Are Real 🚀 Google is hiring Frontend / UI Engineers with strong fundamentals and real-world thinking. If you’re preparing for frontend roles, this is what big-tech interviews actually evaluate 👇 What Google Looks for in Frontend Engineers 1️⃣ Strong JavaScript Fundamentals Not frameworks first closures, async behavior, event loop, and performance. 2️⃣ UI + Engineering Balance Clean UI is expected. But how you manage state, re-renders, and data flow matters more. 3️⃣ Problem Solving Over Libraries You won’t be judged on how many libraries you know, but on how you break down UI problems. 4️⃣ Collaboration Skills Frontend doesn’t work alone you must explain how you worked with backend, designers, and PMs. Common Interview Focus Areas • Build a component from scratch • Optimize performance & re-renders • Handle async API states • Accessibility & responsive design • Explain trade-offs in your approach These are usually tested in machine coding + discussion rounds. Typical Interview Tasks • Build a scalable UI component • Design a dashboard with real-time data • Improve performance of an existing UI • Handle edge cases & errors gracefully Focus is on clarity, structure, and decision-making, not perfect code. Big companies don’t hire framework users. They hire frontend engineers who understand the browser, JavaScript, and users. If you’re targeting 2026 frontend roles, this is the roadmap you should align with. Save this post for your preparation. Share it with someone preparing for frontend interviews. Follow Ashish Misal Codes on IG: https://lnkd.in/dJqGy5_g 𝗜'𝘃𝗲 𝗰𝗿𝗲𝗮𝘁𝗲𝗱 𝗖𝗼𝗺𝗽𝗹𝗲𝘁𝗲 𝗠𝗘𝗥𝗡 𝗦𝘁𝗮𝗰𝗸 𝗚𝘂𝗶𝗱𝗲. 𝗚𝗲𝘁 𝘁𝗵𝗲 𝗚𝘂𝗶𝗱𝗲 𝗵𝗲𝗿𝗲 - https://lnkd.in/dauSXK5R Follow Ashish Misal for more insightful content. Stay Focused, Stay Consistent!

171

28 Comments

"Convenience wins. Speed wins. Technology that saves time always wins." – Akshay Saini I came across this today and couldn’t agree more. Akshay beautifully draws a parallel between how we dismissed Zepto and Blinkit initially ("Why not just walk to the store?") and how many today are dismissing AI tools in software development. Here’s the truth :- AI is not here to replace developers. It’s here to empower them. Faster prototyping, reduced development cycles, automation of repetitive tasks — that’s not a threat. That’s an evolution. We didn't stop using e-commerce just because the supermarket is nearby. Likewise, we won’t stop coding — we’ll just do it faster, smarter, and with new possibilities unlocked. Big appreciation to Akshay Saini 🚀 for sharing this perspective. It’s a great reminder that not every tech hype is a bubble — some are the beginning of a new normal. I’m starting to realize that the tools around us are changing fast. And instead of fearing that shift, maybe it’s worth exploring it — learning how to ride it. Because if we don’t, there’s a chance we might end up still waiting at the Kirana store, while the rest of the world has already moved on. #AI #coding #LLM #Developertools #techtrends #technology

13

Zomato Interview Experience | November 2025 | SDE-2 Application Mode: Referral (They only accept applications via employee referrals.) Round 1 Redis Why is Redis extremely fast? How does Redis handle large scale despite being single-threaded? Kafka How can consumer throughput be increased? What happens when consumption lags behind production? SQL Given: Order state transitions with timestamps States: Created → Confirmed → Reached Merchant → Reached Customer → Delivered Questions: Write a query to fetch all order IDs with their latest state in the last 1 hour Exclude orders that are already delivered How would this query behave at scale? What indexes would you add? Low-Level Design - Snake and Food Game Design snake movement logic Ensure movement happens in O(1) Handle food consumption and snake growth Explain data structure choices & trade-offs Write pseudocode Result: Rejected Key Learning A single round can deeply test multiple backend fundamentals—prepare breadth + depth. Rejections hurt, but they’re great feedback loops. More interview experiences are coming soon. #Zomato #SDE2 #InterviewExperience #BackendEngineering #Redis #Kafka #SQL #LowLevelDesign #SwitchPreparation

523

6 Comments