Saumya Singh’s Post

Rejected after Google’s final round interview, Despite that, I applied to Nvidia, only to face failure once more 😓 This time, I analyzed my mistakes, realizing the need for company-specific preparation and improvement in my communication skills. I created a roadmap before my Amazon interview. I revised concepts, practiced problems, searched behavioral questions on LeetCode, and practiced them out loud. That day, I understood the crucial need for a structured plan, particularly for interviews at top MNCs. 💪🏻 I’m know that many of us have the struggle without proper direction. You can seek help from mentors through top platforms like Preplaced. They can help with your preparation by providing structured roadmaps that cover everything from tech skills improvement to behavioral round practice 🚀 Book a FREE session with them here - https://lnkd.in/gXvvv9dX Don’t give up! Seek help and keep going 🌟 #InterviewPreparation #Collab #PreplacedCollab #TechInterview

I’m about to complete 2 years at Qualcomm, and it's been amazing! ❤️ And throughout my entire journey, I’ve had a chance to connect with amazing professionals and learn a lot. Obviously, I was a bit hesitant and underconfident when it came to interviews, but it was the support of my mentors & belief in myself, that helped me crack the interviews. One round after another, my confidence started to build up, and I started trusting, that if I put my mind to a thing, nothing is impossible. What matters is our willingness to do more & our Consistency. ⭐ Throughout my preparation I made sure to keep these 3 things in mind → 🔸 Fundamentals are key. So, make sure you prepare Mathematics and programming language really well. 🔸 Never ever limit yourself to only theory. I made sure to engage in a lot of Real-world projects on Kaggle, etc. This helped me kill two birds with one stone: 👉 Prepare you for any kind of question in your technical interview. 👉 Show your ability to apply knowledge in practical situations (a key skill that major product companies look for) 🔸 Always stay open to Feedback & be curious to learn about new technologies. These things along with my CONSISTENT preparation, helped me crack Qualcomm, without any fuss. 🎉 I want to thank all my mentors and peers who have supported me in my journey, and without whom reaching this position would not have been possible. #aspire #linkedin

Engineering Manager Kajal Miyan shares how she maps out a vision board when hiring for her tech team at Carnegie Learning, as part of our Debugging Tech Hiring webinar. Stay tuned as we share more clips and expert advice every Friday! #techhiring #tech #hrtips

I have completed 1.5 years at Qualcomm! Sharing my interview experience for the first time. 🚀 📌 Online Assessment Test: Got questions from DSA, Aptitude, C programming, operating systems, computer networks, and core CSE fundamentals. 📌 2 Technical Rounds: Focused on project discussions and DSA problems, primarily greedy algorithms. 📌 HR Round: Focused on knowledge of Qualcomm’s products and behavioral questions. My preparation strategy included, ✔  Regularly revising core CSE notes and participating in LeetCode contests. ✔  Taking regular mock interviews, to strengthen my tech skills. ✔  Researching the company thoroughly and practicing common HR questions. Even with prior knowledge of the interview process, tackling the questions can be challenging. Hence, if you’re aiming to switch to a PBC → give mock interviews to improve your performance. You can easily find professionals from your target companies at Preplaced for mock practice. All you have to do is book a free session with them here: https://lnkd.in/gYkKCRW9 They also help with the overall interview preparation. These experts have helped many engineers get placed at top companies like Amazon, Atlassian, Salesforce, Uber, Target, Adobe and more. Do give it a try! 🔥 #interviewexperience #qualcomm #collab #preplacedcollab #interviewprocess

My path to Google wasn't a straight line – it was more like a rollercoaster with plenty of unexpected twists and turns. 🎢 Here's a glimpse of my journey: ❌ JEE Mains: Despite a year of preparation, I was not able to qualify (48/360). 📚I wasn’t a college topper, but I focused on gaining practical skills that would actually be useful in the real world. 🛠️ ❌ GATE Exam: Failed to qualify, after one year of preparation. 🚀 Landed my first job in the VLSI industry through campus placement in a small company and started my career as a Design Verification Engineer. 🤞 After two years, I began preparing for interviews for new opportunities. The Job Hunt: Rejection After Rejection: 🎯 500+ Applications 🤯: I applied to every opportunity that was related to my skills and interests but it often felt like my efforts were disappearing into a black hole, with no sign of progress. 😩 🎯 100+ Referrals 🤝: I had requested to many people on linkedin for referral, but hardly got a response from anyone. 🎯 Countless Rejections 🚫: Faced Rejections in 7+ companies. Rejections were tough, especially when I thought I'd done well in the interviews. I apparently found that I have a talent for getting to the final round of interviews and then getting rejected. 😂….but hey, it all led me to where I am today, so no complaints! Turning Point:  ✨ Finally, after numerous rejections, I received offers from two amazing companies and finally landed at Google 🎉 Reflections: 💫 Looking back, I realize that those rejections were invaluable. Each one pushed me to explore new paths, learn from my mistakes, and become more resilient. Key Takeaways: Rejections = Redirections 🧭: Each rejection opens doors to new possibilities you might not have considered. They forced me to grow, adapt, and explore new possibilities. Embrace the Journey 🛣️: The path to success is rarely a straight line. It's filled with twists and turns, ups and downs. Embrace the journey, and enjoy the ride. My journey taught me to embrace the setbacks, learn from them, and keep pushing forward. 💪 Your dream job might be just around the corner!🚀 #careerjourney #google #VLSI

🌟 Calling All Engineers! 🌟 As a recruiter, I am constantly on the lookout for top engineering talent, and I know that the field is constantly evolving. So, I want to hear from you - what tips and tricks have you discovered that have helped you make the most of your engineering skillset? Whether it's a new coding technique, a productivity hack, or a communication strategy, I want to know what has helped you excel in your role and share this with others to help build a stronger community within this sector! 🤗🤝👏 Share your insights in the comments below and let's learn from each other to continue pushing the boundaries of engineering excellence. 👩💻🔧🚀 #EngineeringExcellence #InnovativeEngineering #SkillsForSuccess

I was selected for three teams at Qualcomm🥸✨ Let me share one of my interview experiences today! I applied through LinkedIn and connected with the recruiters. Then, I was called for 3 rounds: ✅ Technical 1: I was asked coding problems on memory management, scheduling, and OS. ✅ Technical 2: This round focused on checking my problem-solving and logical skills. ✅ Technical 3: A senior engineer asked me HLD questions on embedded systems and design. The HR took my final round to test if I could work under pressure and handle complex situations. Thanks to my practice with mock interviews, I answered clearly and got into Qualcomm's team🥳 If you are aiming for top MNCs, practice questions and boost your confidence through mock interviews. You can try using Preplaced to connect with top engineers who will conduct your mock interviews. Moreover, they will provide end-to-end guidance and support in cracking such top companies🚀 Book a FREE session with them to get started: https://lnkd.in/gJGHUHSj P.S.: Their end-to-end program with training sessions on tech and tailored feedback has helped thousands of people crack top companies. It can help you too✨

8th Apple Interview and still new discoveries. I attended this interview more out of curiosity as I could see, even from the requirements, I was not a good fit (curious why being called to interview for a role with only 30% of the requirements, while perfect matches are ignored). I told myself: no pressure, no preparation, just take what happens and enjoy the interview counter (for the same company) increase once more. I was interviewing for a Site Reliability Engineering role and got interested in understanding the difference from a Software Engineering role. So here is my understanding of a SRE... in one sentence 👉👉 SWE are feature driven, SRE are feedback driven 👈👈 SREs tackle problems of reliability and availability of services, which are generally a consequence of dealing with huge infrastructures, networking issues, scalability, systems automation... As an SRE there are two major goals to accomplish: 1) Make problems stop bleeding as soon as possible: for instance, you don't want the service you provide to be unavailable for long time. (What if this service is YouTube? How much money per minute can the unavailability of service cost?) 2) Adopt long-lasting automated techniques for example to help SWEs deploy to production more safely. SWEs are moved by business needs, by the necessity to build new software, and introduce new features that may serve other Software Engineers or directly the customers. #softwareengineering #sitereliabilityengineering

🌟 Calling All Engineers! 🌟 As a recruiter, I am constantly on the lookout for top engineering talent, and I know that the field is constantly evolving. So, I want to hear from you - what tips and tricks have you discovered that have helped you make the most of your engineering skillset? Whether it's a new coding technique, a productivity hack, or a communication strategy, I want to know what has helped you excel in your role and share this with others to help build a stronger community within this sector! 🤗🤝👏 Share your insights in the comments below and let's learn from each other to continue pushing the boundaries of engineering excellence. 👩💻🔧🚀 #EngineeringExcellence #InnovativeEngineering #SkillsForSuccess

I failed badly in my Google interview during my on-campus placements because of this one mistake! When Google visited my college for interviews, I was unaware of the differences between a Technical Solution Engineer (TSE) role and a Software Engineer (SWE) role. However, I now understand the significant distinctions between a TSE and a Software Engineering role: ✅ Focus area: 📍Software Engineers primarily focus on coding, debugging, and optimizing software solutions. 📍Technical Solution Engineers, on the other hand, bridge the gap between Google's technical products and customer needs. ✅ Skill emphasis: 📍Software engineering interviews heavily emphasize technical skills related to coding, algorithms, and system design. 📍Interviews for technical solution engineering roles assess a candidate's technical knowledge and their ability to communicate complex technical concepts to non-technical audiences. The key topics asked are OS, CN, Linux commands, troubleshooting etc. Connect with me on Instagram for more such content - https://lnkd.in/gi7DH39s Need a dedicated 1:1 call? Check this - https://lnkd.in/grXPhqVc Btw, did you know the difference between a TSE and a SWE role? Let me know in comments 🙌🏻 #preplaced #google #googleinterview