#how well would u say u did?
1 messages Ā· Page 1 of 1 (latest)
How long after the final?
3 full weeks
Did they call to reject or was it an email
i think i did pretty decent overall, i missed 2 tiny edge cases in one of them and ran out of time in the last one to code the last if condition
call š„²š„²
recruiter hinted at that they basically want to optimized and basically bug free and code should be condition to run fwiw
So basically if you dont hear back after 2 weeks, its prolly L
i refuse to believe google engineers can write bug free code either tbh, its just all ego
it seems like if you donāt get team matching form or whatever that is within a week itās gonna be a L
I got it two days after final but idk if my recruiter is proactive

you just a š bro
Thereās no fucking way
Idk tbh
She said in the essence of time cause I had a deadline
I think it was just really proactive
out of 10
5 is average
Um Iād say like 8/10 or 8.5/10
gotcha, thats still really good
im just scared for follow ups
Yeah same 
Nicee, today marks 1 week from my final 
i had 2 interviewers who joined google 3 months ago, im not going to talk shit but they shouldnāt be doing technical interviews lol
yeah in my last interview i got the entire logic correct minus some indexing part, which i caught while testing it. All I had to do was change index++ to index = rightIndex and that would have solved it.
my interviewers were all recent grads, somehow
Tbh mine had a more trivial solution but I didnāt think about it at the time
I think I needed to keep a separate array of hash sets to store indexes and shit
i explained the correct indexing logic the entire time but idk it seemed complicated to include indexing through a string with recursion
maybe yall werent verbal enough? maybe u have to yell during ur interview
to actually have good communication
i think my communication was solid though
just that in 2/4 of the interviews i didnt do more than 1 follow up
you mean passing the indexes along as a recursion parameter?
nah, basically had to do some recursive string replacement and the indexing was for the original string indexing as i went thru the string char by char
my interviewer initially didnt even realize that recursive string replacements were possible lol, he just pasted the question and then when i clarified that he was like "oh yeah good observation"
ii think this is my best shot at a full time job but its google and their gatekeeping interviewers so idk thats always the thing that ruins dreams 
well goodluck homie, hope it turns out good for you
i heard many people had math questions? does that mean i have to brush up on my math
you too guys
And u got L?? No way
Weāre all ur other solutions optimal
ya and she called me to tell me this which was so odd
And did I finish coding all follow ips?
i got optimal solution, but i didnt finish coding all the way in one of them
and missed some tiny edge cases in another one of them
For the first qn?
second
Damn k
Seems u did good
Ye
Ye I thought ppl got away with one bad interview + some hiccups in others
Fk
I hope my interviewer has a bad histogram or something
So benefit of doubt comes in
Itās just bad interviewer. I bet they canāt do that either and that theyāll fail google if they tried again
The only people who are technical gods at google are people like Jeff Dean and Sanjay Gemawat
No they werenāt
In my second technical I had only one question
He didnāt ask me a follow up so idk
I see
But I got to the optimal solution right away so maybe thatās why?
I took 33 mins on that one
This one was like merge intervals
So idk I think I fucked up my onsite 
Ye same
Ik I aced 2
Did ok on 1 (coded half of follow up)
And bad on 1 (suboptimal + no time to explain follow up)
I think I aced 2.5, ok on 1 and Meh on 0.5
But overall none of my solutions were suboptimal
not like impossible but relatively hard, i just had 2 interviewers who barely knew english so it was just really tough in that regard
i also had to ask "can you repeat that" "i dont understand can you rephrase" multiple times so it honestly mightve made a bad impression, but there's no workaround for that bc i deadass couldn't understand
one of my interviewers yawned loudly into the microphone
hot