Ryan Newquist, MS’ Post

Google's former programmer detailed postmortem on a service outage is a masterclass in transparency and accountability. 👇 In this analysis, he highlight the importance of thorough incident reviews and the value of learning from mistakes. For anyone in tech, it's a reminder that failure is inevitable, but how you handle it defines your reputation. It's not just about fixing the problem but understanding its root cause to prevent future occurrences. This approach is crucial for continuous improvement and maintaining user trust. #TechLeadership #IncidentManagement #ContinuousImprovement #Google https://lnkd.in/ds4dYhFf

Googleversary 2 Unlocked: 2 Years of Learning, laughing & coding! Two years ago, Google welcomed this bright-eyed newbie. Today, those eyes are still wide with wonder (those perks, though!), but now they're backed by a whole lot of experience, knowledge, and pure Google magic. A huge shoutout to my amazing manager Saurabh Pahuja - the ultimate trifecta of mentor, cheerleader, and a friend. To the leadership team: your vision fuels our fire. And to my incredible team, you're the special ingredient that makes Google Google. Let's break down these two years, Google-style: Lines of code: More than a few. Way more. Meetings: If they were pixels, they'd fill a jumbotron. Laughs with colleagues: Enough to power a small city. Problems tackled: A modest mountain's worth. Lessons learned: Let's just say my brain is overflowing. To my team and this inspiring Google culture: you've made these two years the highlight reel of my career. Here's to two years of being Googlified, and a million more moments to come! Thank you Google! Thank you Ram for showing me the path to Google! #TwoYearsStrong #Googleversary

When I was at Google, I got promoted to senior software engineer in one year because I convinced my manager to support my promotion. Here is how I did it. The two principles I applied: - Show, don’t tell: I wrote my self assessment and collected evidence of my eligibility before having a conversation with my manager about it - Self-advocacy: Using my self assessment, I advocated for why going for promotion that cycle was a reasonable attempt, I was delicate about it and not pushy, letting him make the final call He was convinced and the rest is history. Read the full story here:

I am proud to say I completed a google career certificate, it all started from a minor conversation with a friend, day to day discussions and I finally got intrigued. started off casually and got even more motivated daily. I dedicated all my time to it and I can't wait for the next chapter #growwithgoogle #GrowWithGoogle

Book review: Software Engineering at Google (a new blog post) Ever wondered how Google builds (or shall we say, engineers) its software products? I recently finished reading Software Engineering at Google, and I've written a (high-level) review of the book: https://lnkd.in/gh2aYpcj If you've ever been curious about how Google does its "magic," then this is the book for you.

Hi everyone, Another year passed by, it’s my second Googleversary . Glad to have gotten this opportunity to work with such bright and insightful people, so much of learning, and so much of growth, all the credits go to my supportive team. Thanks a lot everyone for making it so much easier. Of all the lessons I’ve learnt, couple of important things worth sharing: 1. It’s always okay to ask for help. As programmers, we carry our pride on our sleeves, but it’s completely acceptable to seek for help. Do you remember the first dynamic programming problem, when we had to go seek solution? because it was not very straightforward, but we did that and here we are, so it's completely okay to ask for help. 2. Good news should be told fast, bad news faster. We’re bound to make mistakes, and there’s nothing wrong with that. What’s important is the intent to either solve or hide the problem when it surfaces. Be honest, say it out, yes I made a mistake, it becomes easier, trust me. With all love and respect, thank you Google for another amazing year. #SecondGoogleversary #Googleversary #Google #lifeatgoogle

Working in a company for 20 years, especially in the fast-paced tech environment of Silicon Valley, is a testament to the power of a strong company culture in keeping people motivated and consistently delivering outstanding products. My friend, Sumitran Raghunandan, shares his incredible journey of 20 years at Google in his blog titled “My Journey at Google: 2 Decades of Learning and Growth — Part 1.” I strongly believe we can all gain valuable insights from his experiences.

Reflecting on My Journey with Google: A Lesson in Growth and Resilience From September 26th to October 24th, I immersed myself in a challenging yet rewarding preparation journey for my interview with Google.I revised all algorithms, brushed up on problem-solving strategies, and tackled numerous coding problems. I didn’t make it this time and faced rejection . The rejection wasn’t easy, but I see it as a stepping stone to the next big opportunity. I’m more determined than ever to continue learning and improving, and I know this experience will help me in my future endeavors. Here is my experience at google interview Round 1: Purely based on DSA. Graph + DP problem. Difficulty level: medium to hard. I was able to solve the problem, but the issue was I didn’t optimize the space complexity. The interviewer gave me a hint, and I then corrected it to the optimal solution, but that shouldn’t have happened. In 1 hour, I was able to solve only one question. Although I figured out the optimal solution, I wasted time on the recursive solution before presenting the optimal one, which shouldn’t have happened. Round 2: DSA + "Googly" questions. Array + Monotonic stack. Difficulty level: medium to hard. For this question, I was able to provide a brute-force approach but failed to optimize the space complexity. The interviewer pointed out that before optimizing time, I should focus on space complexity. I realized my mistake, corrected my code, and provided the optimal approach. However, I couldn’t optimize the time complexity until 45 minutes had passed. Lessons learned: 1. If you figure out the optimal solution, don’t waste time explaining the brute-force method (especially in time-constrained interviews). Just go with the optimal one and start coding. 2. Aim to solve 2 medium to hard questions in 45 minutes. 3. Don’t focus only on time complexity—optimizing space complexity is just as important. 4. Don’t rely on LeetCode questions. Challenge yourself with follow-up questions, and work towards solving problems in the most optimal way with both time and space complexity in mind. The questions weren’t hard, but I failed in the basics (I need to work on space optimization). #Google #TechJourney #Resilience #GrowthMindset #NeverGiveUp #CodingLife #SoftwareEngineering

As I am nearing my 20 year tenure at Google, I wanted to relive the experience of being part of this great company and also share what I have learnt along the way. Hence I wrote my first article in medium.com. I hope this article is informative and thought provoking. Please share your comments and your experiences as well.