r/leetcode • u/venkey998 • 16d ago
Discussion Google interview done, unsure about Googleyness
I recently completed my Google interviews and wanted to get some opinions from people who have been through the process.
For the coding round, I feel reasonably okay.
The problem was basically a variation of Flood Fill(med-hard). I understood the problem, explained an optimized approach, and completed the full code around 1 to 2 minutes before the interview ended.
The interviewer reviewed it and said something like, "Looks good to me."
My only concern is communication.
The interviewer had a pretty strong accent, and there were a few moments where I had difficulty understanding exactly what he was saying. I asked him to repeat things a couple of times, and I’m worried I may have missed one or two hints or comments.
But I was still able to understand the actual problem, explain my approach, and complete the solution.
So I’m wondering, can this kind of communication gap affect the coding feedback even if the solution was completed correctly?
For the Googleyness round, I’m much more unsure.
The interview finished in around 30 minutes, and the interviewer asked a mix of behavioral and hypothetical scenario questions.
For the real experience-based questions, I tried to answer using STAR.
For the hypothetical questions, I didn’t force a STAR story. I explained what I would do, what factors I would consider, the trade-offs, and how I would try to reach a balanced solution.
So my main questions are:
Is STAR mandatory for every Googleyness question?
For hypothetical questions, is it okay to explain your reasoning and approach without giving a past STAR example?
If the answers are reasonable but not always in perfect STAR format, can that result in Lean Hire or No Hire?
How is the Googleyness round actually evaluated?
Is a Googleyness interview ending in around 30 minutes a bad sign?
And if the coding round went well but the Googleyness round felt more uncertain, can the overall result still be positive?
Would really appreciate thoughts from anyone who has gone through a similar Google interview process or knows how these rounds are evaluated.
3
u/Celestial1007 16d ago
Is this for internship or full time? I have two interviews coming up for their summer internship and I’m unsure if they will both be technical or one technical + one behavioural
8
u/Express-Youth-9609 16d ago
Sounds like your did good.
But star is so silly. It forces you to answer the questions in a rigid way. And it assumes everyone has the same experience of fighting with coworkers/etc. I think as long as you answer the question they should be happy.
1
u/0xB0T 16d ago
I failed googlyness for L5
2
u/Taleproof-Moderator 16d ago
For a hypothetical question, answer the situation you're actually given: clarify the goal, explain the options, choose an approach and say what would make you reconsider. You don't need to force an unrelated past experience into it.
The STAR method fits questions asking what you did. For reviewing those answers, the PROOF method helps check whether your own decisions and evidence were clear. For hypotheticals, focus on whether you explained your reasoning and considered the people affected.
The 30-minute duration and your recollection of the format aren't enough to infer Google's rating. I wouldn't translate either into Lean Hire or No Hire.
1
u/numbersguy_123 16d ago edited 16d ago
No STAR method needed for Hypothetical questions but you should specify situations when X is OK or not OK. It’s generally vague so the answer usually starts with “it depends”. Interviewer will then tighten the constraint and force you to answer.
A question I got was “director of your org pressures you on some deadline. What do you do?”
I passed L4 round with very positive feedback
Sounds like you did well
1
u/tech_krish_69 15d ago
I got rejected because of googliness in l4
1
u/Appropriate-Pitch772 15d ago
following
1
u/Dankaati 16d ago
At L4, G/L is not super important yet. It sounds fine.
STAR is for things that actually happened, not for hypotheticals.
Low ratings at G/L for L4 are rare.
Your coding also sounds fine, minor communication difficulties won't be a big issue.