Sahil Gaba’s Post

Moral of this post: Interviewing is part skill, part luck. My addition: If luck played the bigger role in your interviewing, put energy to deserve the offer you got.

Good perspective with perseverance

Which regimen can get you an interview at Google 5 months after writing your first Hello World? Would love to the probability of this happening and if possible how to achieve similar results.

  I have interviewed at Google 3 times. Here's my experience. Resharing Sahil Gaba`s post 🗓️ 2016 - 5 months after I wrote my first "Hello, World!" - Applied through referral. - Got the standard recruiter call. - Received online assessment. Solved 2 out of 3 problems. - Moved to phone screen round. - Passed phone screen. - Went to Mountain View office for an onsite. - Had 4 Coding interviews. Solved all questions with minor hiccups. - Received a rejection call. 🗓️ 2018 - 1 year of work experience - Applied through online portal. - Got a standard recruiter call. Invited for a phone screen round. - Got a hard problem. - Rejected after phone screen. 🗓️ 2021 - Working for Amazon. 4 years of work experience. - Google recruiter reached out on Linkedin. - Passed phone screen. - Virtual onsite with 4 Coding rounds and one Googleyness interview. - Received the verbal offer but got lower level than expected. - Did not accept the offer. - Was asked to take 2 more coding interviews to reassess the level. - Received the offer for the higher level. - Talked to 4-5 different teams before accepting the offer. If you toss a coin and call heads, your probability of winning is 50%. If you toss a coin 7 times and keep calling heads, your probability of winning is about 99%. Interviewing is part skill, part luck. Keep tossing the coin. Good luck!

I have interviewed at Google 2 times. Here's my experience. 🗓️ 2022 - 4 year of work experience - Applied through referral. - Got the standard recruiter call. - Moved to phone screen round. - Passed phone screen. -Virtual onsite with 2 Coding rounds ,one system design and one Googleyness interview. - Recuiter informed your all feedbacks are either positive or super positive - But unfortunately hiring freeze happened and position got closed 🗓️ 2023 - 5 year of work experience - Applied through online portal. - Got a standard recruiter call. Invited for a phone screen round. - Virtual onsite with 4 Coding rounds and one Googleyness interview. - Received offer but got lower level than expected. - Did not accept the offer. #job #softwareengineering #Google #interviews Moral - Companies brand value shouldn’t override job satisfaction, choose wisely

I'm excited to share that today marks the start of my second week as a Software Engineer at Google 🎉 I'd like to thank one person, in particular, my recruiter Jeffrey Rosas, who's been the KINDEST recruiter i've met so far. He's very responsive, optimistic, quick to get on a call whenever i had any questions, shared useful tips for interviews. (He is currently hiring for positions at Google). Here's everything I learnt along the way and hopefully it helps out others too - 1️⃣ Don't judge yourself and just apply. For the longest time, i didn't apply for positions at Google because i didn't feel ready to interview at Google. Somehow, i decided to just apply and once the process started, things started becoming easier. If you can takeaway anything from this post, let it be this. Things will always seem harder from the outside, but it definitely gets easier when you start taking steps towards your dream, even if it's doing it while being scared. 2️⃣ Don't skip mock interviewing 📞 . When i interviewed at Amazon approx 2.5 years after working in the industry, my interviewing skills were bad, and as expected, i was rejected. Fortunately, i was able to figure this out and mock interviewed couple times before interviewing at Google. I received valuable feedback and confidence boost during my mock interviews, which helped me get ready for actual interviews. 3️⃣ Take complete ownership and learn from failures. When i was rejected at Amazon, I spent a good amount of time analyzing my interviews and how i could get better at communication and problem solving. Eventually, I was able to figure out my shortcomings and create a plan to work on myself before interviewing again. Abraham Lincoln is often credited with saying, "The best way to predict your future is to create it". With that said, I'm excited to see what my future holds at Google. I can already tell it's going to be amazing considering my experience with Google so far 🎉 #google #noogler #softwareengineering

How many applications is "too many" at one company? You may hate this answer 😂 It depends! I would recommend considering the following: 🔵 How big is the company? (i.e. applying 30 times among the thousands of listings at a behemoth like Amazon, vs applying 30 times at a mom-and-pop shop that has ... 30 jobs listed) 🔵 Are you applying for targeted roles, or clearly "spraying and praying? (i.e. you're a new grad applying to Principal or Director roles; or you're someone in HR applying to scientist jobs. Yes, people do this often! It shows that you aren't being selective in your search and may not be using good judgment) 🔵 Did you recently fail a screen or interview? You may need to wait 3/6/12 months before you'll be allowed to proceed again, per the internal company guidelines (most companies won't post these, and shy away from sharing them explicitly, but generally in tech you need to wait 6 months between failed phone/tech screens and 12 months between failed final rounds) I hope this helps! And if you really need an application # to avoid, it's 1,001 precisely. Because I did see an applicant in Amazon's ATS when I was working there who applied this many times, and it's not a good look 👀 PS: Heads up! If you apply under multiple emails as a way to get in more apps without looking like you're doing so, most ATSs will flag your matching name and contact info to the recruiter and we will merge your duplicate profiles into 1 profile, showing us that you do indeed have 1,001 apps in our system.

Service to Product is not a transition, It is a TRANSFORMATION ✅ Making the switch from PubMatic to Amazon was one of the toughest challenges I’ve faced.  It wasn’t just about getting a new job—it was about completely transforming my skills, mindset, and approach. Here’s how I made it happen: ✅ Tech Skills Upgrade: I focused on DSA, System Design, and advanced frontend development to prepare for the tech rounds. ✅ Resume Revamp: I showcased my real achievements, added impactful projects, and made sure my resume was ATS-friendly to increase my chances of getting noticed. ✅ Strategic Job Search: I dedicated time to connecting with recruiters, asking for referrals, and updating my profiles to keep my job search focused and effective. I didn’t realize how much effort and transformation this switch would demand until I was deep into it. But after months of hard work, I made it to Amazon! 🙌 If you’re looking to make a similar transformation, follow these steps. But remember—if you are struggling to do so you can always seek for guidance. Top SDEs who’ve cracked roles at major MNCs are here to help you with: - Personalized roadmaps - Tech skills guidance - Mock interviews - Resume building & more! Book your FREE session now and get the support you need - https://lnkd.in/g33RRnuj #CareerTransformation #JobSwitch #TechCareers #PreplacedCollab #CareerGrowth

Google receives around 3 million applications per year. They have an acceptance rate of around 0.2%. To put this into perspective, you have a better chance of getting into Harvard (3.59% acceptance rate for the Class of 2028 according to Forbes). In 2014, insiders described the hiring process as 'awful': 👂 It could take up to 9 months 👂 People could sit in on up to 25 interviews 👂 Sundar Pichai went through 9 interviews to become SVP of Product Development before his appointment as CEO This exhausting process did little to help the overworked employees, needless to mention its effect on the candidate experience. Google's People Analytics Team examined 5 years of interviewing data & feedback which led to their implementation of 'Rule of 4'. The findings were that "Four interviews were enough to predict whether someone should be hired at Google with 86 percent confidence." 🌞 It reduced time-to-hire 🌞 Freed up employee time 🌞 & Improved the candidate experience What do you think- is 4 the optimal number? #Hiring #Interview #GoBeyond 🔑

[𝐀𝐭𝐭𝐞𝐧𝐭𝐢𝐨𝐧] 𝐃𝐢𝐬𝐜𝐨𝐯𝐞𝐫 𝐆𝐨𝐨𝐠𝐥𝐞'𝐬 𝐇𝐢𝐫𝐢𝐧𝐠 𝐏𝐫𝐨𝐜𝐞𝐬𝐬 𝐟𝐨𝐫 𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐬!!! I’ll be taking a deep dive into the 𝐆𝐨𝐨𝐠𝐥𝐞 𝐒𝐖𝐄 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 𝐏𝐫𝐨𝐜𝐞𝐬𝐬 in an upcoming session! 💻🔍 🗓 𝐒𝐞𝐬𝐬𝐢𝐨𝐧 𝐃𝐚𝐭𝐞: 3:00 PM, Today What we'll cover: 1. Understanding Google SWE Levels and their corresponding roles 2. A detailed walkthrough of the recruitment process for each level 3. Breaking down the interview stages: coding, system design, and beyond 4. Proven strategies to crack coding & system design interviews 5. Live Q&A to answer all your questions! Link of the session in comment section. Whether you're gearing up for your next big tech interview or just curious about how Google hires, this session will provide valuable insights you won’t want to miss! #interview #jobs #software