#how was the inteview?
1 messages · Page 1 of 1 (latest)
I definitely wouldn't call it easy lol
I had oa -> recruiter call -> technical #1 -> technical #2 -> full onsite -> technical #3
all of their technicals are weird non-leetcode things
my second technical was the technical from the onsite
and the third technical was because they still weren't sure about me after the onsite lmao
the normal process is just oa->technical->onsite
how hard was first technical @flat sluice ?
but I would rather do an extra technical than get rejected lol
my recruiter said i’m also skipping a HW round but idk what that is for an ML position
they might’ve meant HR
oh this was for software not ML
so you might have different questions
but did you have an open book code pair?
but all of mine were pretty difficult just because I spent like half the interview trying to understand the two-pages-long problem
I didn't
interesting ok, thank you!
would you be open to posting your offer? i wanna see if it’s worth going through with
sure, I don't have numbers yet because I just heard back from the recruiter but I'll post when I get an update
did anyone else think the system design was impossible i am tempted to quit the onsite halfway through
yea
ive never been more lost in an interview in my life
have a 30 min break now but i am tempted to just cut my losses and withdraw
no onsite
system design
yea
also had a bug on the first round so didnt get the test cases to work, so im tempted to just give up now bc there is another 90 minutes
yea i dont think there is anyway ill pass
damn i mean the phone is not bad at all in comparison
ive never seen such a hard system design question and ive done two sys design interviews before
lmao
it was literally like graphics processing which i know nothing about
whatever ill just push through bc there is just behavioral and bug round
@flat sluice What was ur offer? I got an offer for SWE and can't tell if they lowballed