Anupam Singh

Behind every successful story of switching from @gmail.com to @google.com you see on LinkedIn is a long list of rejections that’s not always clearly visible. When I switched from Amazon to Google: - I was rejected from Uber - I was rejected from few mid scale startups It was humbling, and maybe for the first time in a long time, after being sure of myself, I didn’t feel confident that day. But that was required for me to grow to the next level and push past my limits and while rejections are painful and brutal, they’re also signals. If you’re getting rejected after you reach the final interview round, it’s a sign you need to sharpen your storytelling and communicate your impact with clarity. If you’re consistently falling short in technical screens, it’s a sign your fundamentals might need a deeper revisit If your applications rarely turn into interviews, it’s a sign your experience is not enough or resume or online presence isn’t telling the right story, or you haven’t built the right connections. If you keep hearing “good, but not the right fit,” it’s a sign you need to research the company’s culture and tailor your approach to show you can thrive in that specific environment. If feedback is always generic or non-existent, it’s a sign you need to ask better questions at the end, seek out honest feedback, or build relationships with interviewers and peers who will tell you the hard truth. The story always looks clean and linear on LinkedIn, but real growth happens in the messy, frustrating, deeply personal stretches. You only fail if you stop listening to what your rejections are teaching you. So if you’re facing setback after setback, adjust, reflect, and keep evolving. The best offers come right after you finally outgrow your old limits. Good Luck!

195

14 Kommentare

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🫶

727

28 Kommentare

✨ From 11+ Interviews to 3 Offers in Just 1.5 Months – My Learnings ✨ Over the last couple of months, I’ve interviewed with 11–12 companies for Frontend / MERN stack roles. The journey was intense, but I’m grateful to have received 3 offer letters so far, and I’ve also cleared 5+ final rounds where results are still awaited 🙌. One thing I realized is that you can control your interview by steering the discussion toward your strengths. Instead of giving short textbook answers, try to add depth and practical experience. Here’s what worked for me: 💡 On React Don’t just say “React is an open-source UI library”. 👉 Talk about its features – Virtual DOM, unidirectional data flow, component-driven architecture, JSX. 👉 Go a step further – explain how frameworks like Next.js extend React. 💡 On Components Instead of saying “Components are reusable pieces of UI”, 👉 Share how you structure them in real projects. 👉 For example, I explained my usage of Atomic Design (atoms & molecules) to separate logic from UI and maintain scalability. 💡 On State Management Don’t stop at Context API or Redux. 👉 Compare them based on application scope. 👉 Talk about pros/cons and where each shines. 👉 Share knowledge of middlewares like Redux Saga/Thunk, and modern approaches like Redux Toolkit. 🚀 Key takeaway: Interviews are not just Q&A sessions. They’re your chance to demonstrate deep understanding, structured thinking, and practical experience. I’ll be sharing some of the real interview questions I faced in my next post. Stay tuned, and let’s keep learning together! 💪 #FrontendDevelopment #MERNStack #ReactJS #Redux #InterviewPreparation #CareerGrowth #Learning

448

37 Kommentare

I have researched lots of product-based companies like Amazon, Microsoft, Netflix, Zomato, Goldman Sachs, Paytm, J.P. Morgan etc., for SDE1 2 roles, and found that these 20 system design questions are almost asked in every interviews, both at the fresher and experienced levels. 𝐅𝐫𝐞𝐬𝐡𝐞𝐫 𝐋𝐞𝐯𝐞𝐥 𝐒𝐲𝐬𝐭𝐞𝐦 𝐃𝐞𝐬𝐢𝐠𝐧 1. Design a simple URL shortening service. 2. Design a basic chat application. 3. Design a file storage system. 4. Design a simple social media platform. 5. Design a simple search engine. 6. Design a simple e-commerce website. 7. Design a basic ride-sharing system. 8. Design a basic video streaming service. 9. Design a simple recommendation system. 10. Design a basic food delivery app. 11. Design a parking lot management system. 12. Design a simple music streaming service. 13. Design a basic online ticket booking system. 14. Design a simple note-taking application. 15. Design a weather forecasting system. 16. Design a basic email service. 17. Design a file synchronization system. 18. Design a simple calendar application. 19. Design a basic online quiz platform. 20. Design a user authentication system. 𝐄𝐱𝐩𝐞𝐫𝐢𝐞𝐧𝐜𝐞𝐝 𝐋𝐞𝐯𝐞𝐥 𝐒𝐲𝐬𝐭𝐞𝐦 𝐃𝐞𝐬𝐢𝐠𝐧 1. Design a URL shortening service like bit.ly. 2. Design a distributed key-value store like Redis. 3. Design a scalable social network like Facebook. 4. Design a scalable recommendation system like Netflix. 5. Design a distributed file system like Hadoop's HDFS. 6. Design a real-time messaging system like WhatsApp. 7. Design a web crawler like Google. 8. Design a distributed cache like Memcached. 9. Design a content delivery network (CDN) like Cloudflare. 10. Design a scalable search engine like Google. 11. Design a ride-sharing system like Uber. 12. Design a video streaming service like YouTube. 13. Design an online food delivery system like Zomato. 14. Design a collaborative document editing system like Google Docs. 15. Design an e-commerce platform like Amazon. 16. Design a recommendation system for an online marketplace. 17. Design a fault-tolerant distributed database system. 18. Design a scalable event-driven system like Twitter. 19. Design a scalable photo-sharing platform like Instagram. 20. Design a distributed task scheduling system. Learn and solve these, and you’ll be fully prepared for your next System Design interviews.. System design can be tough to crack, but having the right resources makes all the difference. Came across this well-structured, in-depth guide definitely worth a read. 𝗖𝗵𝗲𝗰𝗸 𝗶𝘁 𝗼𝘂𝘁 𝗵𝗲𝗿𝗲: https://lnkd.in/gxRRyd2m #tech #collab

4.818

158 Kommentare