#!process anyone heard back from goog

1 messages · Page 1 of 1 (latest)

acoustic stirrup
#

howd your interview go

tawdry widget
#

idk thought it went well

#

although the thing is that both interview q's were like a bit hard for me so I was only able to solve the question they gave me on the interview. Didn't have any follow up q's

#

but since I've heard many people always having time for followup q's that could the reason I'm gonna get rejected

verbal elbow
#

Might be a third round situation.

acoustic stirrup
#

wait is it true that not getting to the follow ups is a straight rejection. i thought you get a lean hire instead of a strong hire in that case

verbal elbow
#

I know someone who got the tiebreaker third round a week and a half after their interview.

tawdry widget
#

that's what I thought but why would it be taking this long. Lwk heartbreaking since this was my first interview

#

would have been goated to be able move from my first. But no idea what to expect

crystal owl
#

I got noti for 3rd interview like 5 days after

#

Email ur recruiter mayb like it’s jus taking a while

tawdry widget
#

I did but idk if it's a generic message this was the response

"I’m waiting on the interview feedback and hope to have an update for you by 10/16/2025 at the latest. I’ll reach out as soon as I hear anything."

#

oct 16th would be around 3 weeks after my interview which is a bit weird

#

oh man

#

sucks cause ive heard ppl taking interviews later than me and getting team match

visual mural
#

mhm for sure

unkempt robin
#

Bro hc is not reached yet dw its still October 💀

brazen bolt
#

who’s your interviewer

#

i man recruiter

marsh galleon
#

Recruiters are at summit rn or something

#

They will be back nexT week

quick folio
#

usually the follow up is just "whats the runtime/space complexity" and if you're on teh right track there its chill

crystal owl
#

Nah bruh hc is not backed up lmfao we only like 3 weeks in

tawdry widget
#

yea I felt that my communication was pretty good walked through the each problem looked at potential edge cases clarified sample space, created psuedo code and then finally coded