Rishabh Raj Jha’s Post

Or with a mindset that you've seen it differently. A question may rewire your brain about AI. "Will AI replace and terminate the University of Cambridge?" We once asked ChatGPT, an icon of AI, this question and it's answer was: "Yes, but with low probability." This is a paradox and dangerous feature in data analytics for decision making support. Do you or any of your contacts need my expertise and my IP? We're selling, NOT talking. Thanks. Here is our pitch deck: "With our intellectual property (IP), a copyrighted multilingual metadata, we can do what ChatGPT, an icon of AI, can't do in data analytics. Without metadata, NO data can be found/retrieved, even by the most advanced technologies, like AI, supercomputers, etc. https://lnkd.in/g-aJFnXR Our IP can also make your information service UNIQUE in the world" Do you or any of your contacts need our expertise and our IP? P.S. We wrote this statement myself, without using any AI tool.

I got rejected in a Google interview because of this one mistake!! When I was in college, I appeared for a Google interview. I was excited, prepared, and confident. But when I was asked to analyze the time and space complexity of my solution, I fumbled. I got confused, unsure of my calculations, and the confidence I had built over months of coding practice vanished in minutes. That’s where I lost the opportunity back then. Looking back, I realize one common mistake we make while preparing for coding interviews: we focus on solving the problem but skip analyzing the solution. It’s not just about writing code that works. It’s about understanding how efficient that code is and how it can be optimized further. So, whenever you practice coding: 👉 Always calculate and analyze the time and space complexity of your solution. 👉 Explore multiple approaches to the same problem. See how your solution can improve and how you can optimize on the time and space complexity. This small habit can make a huge difference—not just in interviews but in how you think as an engineer. All the best!❤️

Did you know that Google just turned 26? It's incredible how this company evolved from a simple search engine to a comprehensive ecosystem that impacts nearly every part of our lives! But Google didn’t achieve this overnight. It had to constantly adapt, learn, and innovate to remain relevant. This is a powerful lesson for all of us, especially when preparing for interviews: 🔹 Keep evolving: Just like Google, we must continue refining our skills and knowledge. 🔹 Don’t settle for "good enough": Strive for excellence in your preparation. 🔹 Embrace challenges: Google faced competition and setbacks but persevered. We should adopt that same resilience! Whether it's updating your resume or practicing for interviews, the key is to keep improving. Stay curious, embrace new tools, and don’t let yourself get stuck in old patterns. Let’s commit to growth and take that next step together! #CareerGrowth #InterviewPreparation #Learning #Google

Did you know Google just turned 26? 🎉 It’s wild to think how much it’s evolved from a simple search engine to an entire ecosystem that touches nearly every aspect of our lives. From Gmail to Google Maps to YouTube, it's crazy how Google started in a garage and became this massive tech giant. But here’s the thing—it didn’t just get there overnight. Google had to constantly adapt, learn, and innovate to stay relevant and ahead of the curve. Now, why am I talking about Google when you’re here to prep for interviews? Because your career journey is no different. Think about it: ✅ Just like Google had to keep evolving, you need to keep learning and refining your skills. ✅ Google didn’t settle for “good enough,” and neither should you when it comes to preparing for interviews. ✅ It faced competition, challenges, and failures but kept pushing forward—and so will you! Whether you’re brushing up on your resume or practising for that big interview, the key is to keep improving. Adapt to new tools, stay curious, and don’t get stuck in old patterns. Ready to take that first step?

My Google Interview Experience Hi everyone, I’m excited to share my recent interview experience with Google, hoping it provides insights for those preparing for similar opportunities. After applying consistently since May, I received an email in October from a Google recruiter informing me that my resume had been shortlisted for a Software Engineer (SWE) role. I was thrilled to proceed to the next step. The interview took place on November 8th and focused on a problem that combined strings and file handling. While it reminded me of a LeetCode problem, Google’s signature twist made it unique and challenging. Initially, I felt stuck, but the interviewer provided a helpful hint that steered me in the right direction. I managed to complete my code within the Google Doc just in time. I couldn’t fully explain my solution due to time constraints, but the interviewer assured me that my code would be shared with the recruiter for further evaluation. This experience was both demanding and enlightening. It taught me the importance of staying calm under pressure and being open to guidance when tackling complex problems. For anyone preparing for Google interviews, I highly recommend focusing on problem-solving techniques and brushing up on foundational concepts. Believe in yourself, and don’t hesitate to ask for clarification during the interview. Good luck to all the aspiring Googlers out there! #Google #SoftwareEngineering #InterviewExperience #CareerJourney

Had a quick tech interview for a contract role at Google that I completely matched the JD for(infotainment related). Interviewer made me "code" in a... word document. Gave me a question completely out of left field that I wouldn't fully know unless I had been working with similar objects recently. Failed that interview(probably). It doesn't matter if you study medium leetcode problems all day cause you'll still be asked to code in a word doc and write a function using objects that you haven't used in years. The recruiters were like, "we can't fill this role, its been 2 months, cause no one gets passed the tech interview." Yeah man, because this shit is stupid. Could've started paying me 2+ months ago to get started, yet they're still interviewing people, writing 'code' in a word doc, and asking trick questions to try and get people instead of hiring someone to do the job an entire quarter earlier.

𝗠𝘆 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗘𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 𝘄𝗶𝘁𝗵 𝗚𝗼𝗼𝗴𝗹𝗲 My journey wouldn’t have been the same without the invaluable free resources and shared interview experiences that guided me along the way. Now, it's my turn to pay it forward. I hope sharing my interview experience with Google below proves helpful to others navigating a similar path. 𝗝𝘂𝗹𝘆 𝟭𝟴, 𝟮𝟬𝟮𝟰: Reached out to a Google recruiter while actively exploring new opportunities. 𝗔𝘂𝗴𝘂𝘀𝘁 𝟭, 𝟮𝟬𝟮𝟰: Had a recruiter call, discussed my background, and requested one month for preparation. 𝗣𝗿𝗼𝗰𝗲𝘀𝘀 𝗨𝗽𝗱𝗮𝘁𝗲: Recruiter decided to skip the phone screen based on my profile. 𝗢𝗻𝘀𝗶𝘁𝗲 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 (𝗳𝗿𝗼𝗺 𝗦𝗲𝗽𝘁𝗲𝗺𝗯𝗲𝗿 𝟵, 𝟮𝟬𝟮𝟰): 𝗥𝗼𝘂𝗻𝗱 𝟭: Data Structures and Algorithms (Strings, Medium difficulty). 𝗥𝗼𝘂𝗻𝗱 𝟮: Data Structures and Algorithms (Dynamic Programming, Hard difficulty). 𝗥𝗼𝘂𝗻𝗱 𝟯: Data Structures and Algorithms (Arrays, Hash Tables, Math, Hard difficulty). 𝗥𝗼𝘂𝗻𝗱 𝟰: Googleyness and Leadership (behavioral and cultural fit). 𝗣𝗼𝘀𝘁-𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀: Entered the team-matching phase. 𝗛𝗶𝗿𝗶𝗻𝗴 𝗗𝗲𝗰𝗶𝘀𝗶𝗼𝗻: Hiring committee gave a positive response. 𝗢𝗰𝘁𝗼𝗯𝗲𝗿 𝟭𝟴, 𝟮𝟬𝟮𝟰: Received my offer letter. #InterviewExperience #CareerJourney #TechInterviews #GoogleInterview #DSA

Interviewing at Google is an experience in itself. I shared my own interview experience from 2005 here - https://lnkd.in/gSVxtF45. "Challenge the status quo" is one of Google values which I experienced from the day I interviewed to this very day. I shared how this showed up in the article I mentioned above. Specifically what it means to be Googley or what is Googleyness (which in itself is an interview focus area). I also shared some interview tips in the article. How does your organization evaluate candidates? Do you evaluate for culture fit to create a homogeneous environment? Do you see if candidates would "challenge the status quo"? Share your thoughts and perspective.

✨ A Journey of Growth and Learning ✨ I recently had the opportunity to interview with Google, and it has been an incredible experience. From getting my resume shortlisted (without a referral!) to going through a rigorous screening round and two technical interviews where I tackled medium and hard problems and solved them efficiently, I was excited to reach each new stage. After the interviews, I even received a call from the recruiter requesting my documents and marksheets—naturally, I was thrilled and hopeful that I was getting closer to an offer. But today, I received a rejection email. Today marks 21 days to the moment when I finished with all the interview process at google. I was hopeful to get selected but luck really matters. While it’s disheartening not to have made it to the finish line, I’m proud of how far I’ve come. This experience tested my skills, helped me grow, and gave me the confidence to know that I can compete at such a high level. 💪 To anyone facing similar challenges—remember that every step, even the setbacks, is part of the journey to something greater. Onwards and upwards! 🚀 Thank you Google for this experience. #growthmindset #resilience #techinterviews #google #neverstopgrowing

𝗘𝘅𝗰𝗶𝘁𝗲𝗱 𝘁𝗼 𝗦𝗵𝗮𝗿𝗲 𝗠𝘆 Google 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗘𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲! Recently, I had the incredible opportunity to interview with Google for the 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗜𝗻𝘁𝗲𝗿𝗻 position, and I wanted to share my experience with you all! 🔍 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗗𝗲𝘁𝗮𝗶𝗹𝘀: The 𝗳𝗶𝗿𝘀𝘁 round interview lasted for 45 minutes and consisted of 𝘁𝘄𝗼 intriguing questions: 1️⃣ 𝗔𝗿𝗿𝗮𝘆𝘀 + 𝗛𝗮𝘀𝗵𝗠𝗮𝗽 2️⃣ 𝗢𝗽𝘁𝗶𝗺𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗼𝗳 𝘁𝗵𝗲 𝗳𝗶𝗿𝘀𝘁 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻 💡 𝗞𝗲𝘆 𝗧𝗮𝗸𝗲𝗮𝘄𝗮𝘆𝘀: Throughout the interview, I found the questions to be both insightful and challenging. The interviewer was particularly interested in my problem-solving approach and thought process. Here are some key takeaways that I believe could be helpful for anyone preparing for technical interviews: * Understanding the constraints of the problem is crucial. * Strive for efficient solutions in terms of time and space complexity. * Emphasize writing clean and efficient code. * Approach problems in a structured and organized manner. * Be versatile in utilizing different data structures. 📞 𝗔𝗳𝘁𝗲𝗿𝗺𝗮𝘁𝗵: Following the interview, I received a call from HR informing me that I didn't advance to Round 2. While it was disappointing not to move forward, I'm incredibly grateful for the opportunity and the valuable insights gained throughout the interview process. It has provided me with a deeper understanding of the expectations and challenges present in the software development industry. 🌟 𝗧𝗵𝗮𝗻𝗸 𝗬𝗼𝘂, Google! I want to extend my sincere gratitude to Google for the opportunity and for facilitating such an enriching interview experience. I'm eager to apply the lessons learned to future endeavours and continue my journey in the world of software development! 💻 #Google #InterviewExperience #SoftwareDevelopment #ProblemSolving #TechCareer #LinkedInPost