Shubham Upadhyay 💻

After all the layoffs in so many companies, finally a good news of job openings which can be a chance after long time for so many people. Feb and March are going to have a lot of new job openings. And if you are starting now, here's a list of to-do before hirings start, how to prepare and list of companies to monitor job openings, classification of these companies, job roles and requirements and what products they are working on. Source: Internal town-hall meetings, VPs and leads, HR discussions, and best of all- info. on upcoming ambitious projects and their funding in these companies. In short, anyone who’s been in Bengaluru for a few years and has some connections knows how this info travels. STEP-1: Let's list first, how to PLAN your preparation: 1️⃣ Make a simple Excel sheet, list companies, roles, and their requirements. You’ll thank me later when you start tracking everything properly. 2️⃣ Target at least 5 companies to apply everyday. Do it regularly through Feb–March. Don’t wait for “perfect timing.” 3️⃣ Make 2 resumes, small hack but works like magic. One resume for direct applying when you see the opening. Another one for referrals. (change your phone and email). And if referrals get delayed, you already have one application there. 4️⃣ Update your LinkedIn and Naukri profile. Very seriously, don’t waste time on fancy job alert sites — most of them share fake or old listings. 5️⃣ Track your interviews, make a folder and note down every interview — questions, discussions, feedback, everything. Even the rejections will help you improve. 6️⃣ Work on small AI and LLM projects, try building and deploying them on cloud. These skills will be useful because many upcoming roles are in such teams. Will list them down. 7️⃣ Talk to people from the companies you’re targeting. Referrals still work, there are people who say "koi fark nahi pdta(doesn’t matter)" but don't listen to stupidity. 8️⃣ If you don’t know something in interviews, just say, you have not worked on it but you are willing to learn. Honesty is always better than fake confidence. 9️⃣ Write your own resume. Use Google Docs to make it yourself. You know your story better than any AI tool. 🔟 Try to apply within the first week after a job is posted. No HR will go through too many applications till the end of their excel sheet. STEP-2: LISTING companies here: Tier-1: Vm Ware, Google, PayPal, Nvidia, Goldman Sachs, Arcesium, Intuit, Adobe, Linkedin, Philips Tier-2/3: Myntra, Epam, Sapient, Expedia, Bluejeans, FIS, Twilio, Virtusa I know it looks like few names, but there will be a lot of openings in these companies for different experience levels. And given the domains of these companies, I'm pretty sure soon I'll get info. on some more in the similar sector. Sorry, but due to word limitations, I'm stopping here. Will continue in next post on job roles, projects and more. → Keep learning. It's almost the right time. And keep helping others too, good karmas do come back🫶

725

28 Comments

🤔 98% teams lose SIH here, not in coding, but in their PPT..... Every year, I see the same story Teams rushing last minute, stuffing slides with text, and thinking: “Idea accha hai toh shortlist ho hi jayenge.” But this is not the reality, Dropping Part 2 of my Smart India Hackathon series 🔥. Here’s the truth I learned as a 2× SIH Winner ● PPT Tips That Judges Actually Care About: • Keep slides clean, consistent & professional, clutter kills. • No long paragraphs, clarity > quantity. • Show prototype screenshots or demo video, execution > promises. • Highlight the What, Why & How of your solution. • Focus not just on tech, but also on impact. • Who benefits? How much? 💡 Common Mistakes That Kill Chances: ▪︎ Slides overloaded with theory (Judges don’t want a textbook). ▪︎ No prototype in early rounds (Even a rough demo beats theory). And here’s a bonus: ▪︎ Sometimes, even the best solution gets rejected because of a poor PPT. • Sometimes, a good PPT carries a simple idea through. That’s why presentation is as important as innovation. ⚡ Pro Tip: In SIH, your PPT isn’t just slides, it’s your story. Make judges feel the problem, see your solution, and trust your impact. Start working on it now this step can make or break your SIH 2025 journey #SIH2025 #SmartIndiaHackathon #Hackathon #Innovation #Pitching #Engineering #BuildForBharat #Presentation #Startups #DeepTech #Entrepreneurship #AI #NationalInnovation

799

18 Comments

I cleared every round… until one question ended it all 💔 Lost a ₹28 LPA Cashfree Payments offer. Still hurts Round: System Design Question: How will you design a scalable notification system? What I did: I used Kafka, stored notifications in a DB, and wrote the logic to send emails or SMS via 3rd party APIs. Result: A polite rejection email the next week. Here's what I should have actually done: - Before jumping to tools like Kafka or APIs, a good answer starts with thinking. - I should’ve started by asking: - What kind of notifications are we sending? (real-time, scheduled, bulk?) - What channels? (email, SMS, push?) - What’s the scale? (100 users? 10 million?) - What’s the expected delivery time or SLA? Flow like this: 1. Producer Service - Let’s say an OrderPlacedEvent occurs in the Order Service. - This gets published to Kafka, decoupled and asynchronous. 2. Kafka Topic - Kafka buffers events and handles spikes. 3. Notification Service (Consumer) - Consumes the event - Checks user preferences (email/SMS/push) - Transforms the event into a message: Your order #1234 has been placed - Sends it via APIs (like SendGrid/Twilio/Firebase) 4. Retry & Failure Handling - On failure, retry with exponential backoff - After N retries, send to a Dead Letter Queue - Log all outcomes: success, failure, retry count 5. Database Use - Not just for storing messages, but for: - Auditing (what was sent to whom and when) - User notification history (like an inbox) - Debugging (support teams can trace delivery issues) Older data? - Archive to S3 or similar cold storage. - For observability, stream logs to Elasticsearch + Kibana. This way, the system is scalable, resilient, and extensible. Because in a system design interview, it’s not about naming tools. It’s about how you think, how you break things down, and how you solve real problems. 𝗞𝗲𝗲𝗽𝗶𝗻𝗴 𝘁𝗵𝗶𝘀 𝗶𝗻 𝗺𝗶𝗻𝗱, 𝗜’𝘃𝗲 𝗽𝗿𝗲𝗽𝗮𝗿𝗲𝗱 𝗶𝗻 𝗗𝗲𝗽𝘁𝗵 𝗦𝘆𝘀𝘁𝗲𝗺 𝗗𝗲𝘀𝗶𝗴𝗻 𝗚𝘂𝗶𝗱𝗲. 𝗚𝗲𝘁 𝘁𝗵𝗲 𝗚𝘂𝗶𝗱𝗲 𝗵𝗲𝗿𝗲: - https://lnkd.in/dte69Z5N Stay Hungry, Stay Foolish!

167

27 Comments

This was the FIRST LLD question I got in 2 out of 3 interviews. And I messed it up 🫤 The question seemed harmless “Design a leave approval system.” I jumped into code. Nested if-else. Done. ✅ 🤣 But then came the follow-up- ➤ “What if I want to add another approver?” ➤ “What if Director is on leave?” ➤ “Can you make it scalable and clean?” That’s when I blanked 😭 Here’s what I wish I knew back then- The interviewer was looking for Chain of Responsibility, not hardcoded logic. Think of it like a relay race. 💡 This one pattern teaches: • Clean code separation • Extensibility for real-world needs • Reusability across different systems Whether you're prepping for system design or writing backend logic—this pattern is gold. Especially when you want your code to grow with your product. Dive into a full breakdown (with Java code)-> https://lnkd.in/gPPQzybF

154

Java is not outdated. It’s just busy running the world. While you’re chasing the next trending language, Java is quietly powering: → Your UPI transactions → Your bank’s backend → Your airline bookings → Your favorite OTT platforms like Netflix 🚫 Don’t fall for the hype. ✅ Go deep instead. → Learn how Java manages memory → Master Collections, Streams, Lambdas → Build real backend systems with Spring Boot → Understand design patterns, logging, debugging, and exception handling Trends fade. Strong fundamentals scale. If you’re serious about backend, Java is still one of the strongest bets. #java #springboot #backend

738

35 Comments