What is your approach to managing poor performers on your team?

"Everyone was extremely professional, polite and friendly. It was a very welcoming interview where they kept the pressure off and let the candidate shine."

"A recruiter reached out to me early in the year, gave me good prep material, and Google skipped the usual screen based on my resume, which already felt different. The loop itself was split into two remote rounds and then three in-person rounds, so it was a real five-interview final rather than the usual single onsite block I expected. What stood out most was that they were not only testing EM skills. They were looking for googliness, broader general competencies, and what I kept thinking of as cognitive skill, especially in how deep they pushed on system design. I felt both system design interviewers wanted me to go past the usual black-box architecture answers and explain how I would actually implement the core logic. I ended up failing the must-pass coding round, which was a very unusual code review and debugging exercise, and the recruiter told me I would need to wait 12 months before interviewing again."

"I applied and they called me the next day, which was faster than anything else I have seen. The process was a recruiter screen, a 55 minute phone screen, and then a five-interview final loop with no take-home, all done remotely even though the role was SF-based. The most unusual parts were that the recruiter gave me actual feedback between rounds and that the EM system design was really a critique of a prebuilt Anthropic-style inference design, not a blank-sheet design. Across the whole loop, they cared a lot more about my resume, project decisions, management style, and culture than coding or AI trivia. I ended up getting rejected, and the written feedback was that my people-management round did not show the depth they were looking for."

"Recruiter call and 1st round scheduled in March 2025 which was people management. Next round System Design and scheduled in March 2025. Cleared both and next round schedule in in May. which was again System Design. Post that code review round was scheduled in June and finally Googlyness in July. IN Augst got result that all rounds were positive, still waiting for team matching."

"In my case, I felt very well-prepared. I had done three mock interviews before Stripe and walked into the process confident in my readiness. However, the actual experience varied drastically depending on the engagement level of the interviewers. During the Execution and Strategy interview, one panelist had their video off the entire time, and the main interviewer never once made eye contact; his camera was angled at his forehead while he typed throughout. He rushed through questions without engaging meaningfully with my answers, and the lack of interaction made it extremely difficult to build any rapport or demonstrate depth. In contrast, the management round, held 45 minutes later, was far more conversational and created space for a thoughtful exchange. That difference matters. I did not make it through the process, and while I’m open to having fallen short on some answers, I also believe that interviewers have a responsibility to create an environment where candidates can do their best work. Unfortunately, that wasn’t consistently the case here. It’s disappointing to receive a rejection without any feedback, especially after investing so much time and energy. Interviews should be designed to bring out the best in candidates. I hope this note is taken seriously and helps improve the process for others."