#!process got cooked Google R1

1 messages · Page 1 of 1 (latest)

sick raven
#

how bad

faint parcel
#

got the brute force and edge cases instantly, spent 30 minutes trying multiple approaches, found an optimal approach, dry ran the example on my optimal approach (was a bit iffy though as I was low on time)

timber ibex
#

Was it a lc hard question would u say maybe then you could be fine. Also did u ask for hints or nah

sick raven
#

not cooked, def passable

faint parcel
#

it was def an lc hard

#

the interviewer did acknowledge that I was on the right track, but I wasn't able to code up the optimal solution

sick raven
#

if its lc hard fs then ur prob alr

#

did u kill behavioral

faint parcel
#

yeah I rizzed up my behavioral interviewer so bad

sick raven
#

W

placid parrot
#

You should be fine if it was an lc hard lol, especially considering the behavioral went well

#

What was the behavioural like tho?

faint parcel
#

just regular behavioral problems, kinda aligned with their principles

faint parcel
placid parrot
#

Is that what you're talking about?

placid parrot
subtle stirrup
#

@faint parcel what do u recommend for prep, mine is tm

faint parcel
faint parcel
sick raven
#

i mean in interviews its back and forth tho. you present approach and ask for feedback

#

if its a markdown thats wild

faint parcel
faint parcel
cursive meteor
#

what was the q

opal mural
civic valley
#

How are the google interviewers? Do they control how you do the implementation or do they jsut sit there and just watch you type?

forest pagoda
#

hey anyone recently gave the interview? which topics are they asking more? last time I gave it was more of graphs, dfs/bfs and linked lists..

tired swift
#

do u have to dry run or can u immediately code it

clear breach
#

my interviewer took any hour with me so I could finish the problem. Is it cooked?

cursive meteor
#

can someone drop the qs they got