#!process meta reject (after final)
1 messages ยท Page 1 of 1 (latest)
recruiter initials?
interviewer?
Did u get optimal for both?
yes, but I barely finished in time
sorry about that mate
yes, both tagged
interviewer initials?
I ended up with:
- one lc hard with tons of tons of edge cases (hint: lc editorial for that problem says the hard part is edge cases)
- one lc medium that is very implementation heavy - multiple people in the comments say this should be classified as hard (hint: why you shouldn't apply with multiple accts. think about what may happen)
starts with j but do not remember last initial
did u mess up time complexity?
actually luck based interview questions
thats fucked
or space complexity, or needed a major fix in the solution?
ACCOUNTS MERGE? ๐ ๐
๐ ๐
if he solved both i dont understand why tho
sorry bro @lunar tundra
fuck meta anyways
probably it
interviewer was very cold and standoffish throughout
damn that sucks bruh. probably the reason
international interviewer?

accounts merge is cancer tho. u gotta implement DSU and hashmap spam hell
another hint: does not require fancy algorithms, but tons of edge cases. within top 100 but after top 50 in tagged list.
these are insane
ye those are genuine just vibe checks dw bout it man, u got unlucky
i remember seeing both during my studying and praying i wouldnt get them lmao
yes
same
When was ur final man? Also sorry man this is so rng based what the
accounts merge is hard is hell how is this medium rip
interviewer literally went out of his way to select the hardest problems possible
tough, bad luck of the draw
it is a lc hard question
between 50 - 100 in the tagged list
it is
also interviewer came late by 2 minutes
it is what it is. no amount of mock interviews could have prepared me for what I faced
thats pretty unfortunate, seems like most people on this server get medium-easy questions and the success rate seems pretty high
But u solved both optimally?
What were the Weak points in the interview in ur opinion?
I missed a couple of edge cases initially
but corrected them in the end
how did you get rejected if u solved the problem optimally
wtf
they shouldn't expect anyone to solve every single edge case from the start ๐
my guess is ||insert into a sorted circular linked list||
I received lc hard, the problem you guessed is medium
oh oops mb
that one wasnt too bad
yeah i misread it as "medium but the edge cases make it hard", i just remember that problem having a lot of annoying cases
Oh yea that's second q is annoying as fuck
But there's a really quick dfs/connected components solution where you model the edges as the emails
If you didn't do the q before tho it might be hard to implement
I don't think it's worth make a DSU for it, but dfs / connected components should work out
