Hacker News new | ask | show | jobs
by sph 1393 days ago
Be prepared to have to do off-screen and later screen-shared, timed leetcode challenges. Fail one, it's an automatic disqualification.
4 comments

I'm not sure where you got that info from, but unless you completely tank everything, there isn't an automatic disqualification. Even if you fail two out of three questions, you'll still get a chance to meet with the screener.
Source: myself.

I did all tests in half the required time, 100% success rate, had a bug during the interview with the screener, in the last of 5 overall I've done, I probably could've fixed it with 2 more minutes but no, I failed and was asked to practice leetcode puzzles and apply again one month later.

Yeah, I don't think I will.

The thing that bugs me the most is it was obvious the interviewer wasn't an engineer. There weren't able to tell how close I was to the solution. I dunno, that method might work in some cases, but I've been doing software engineering for 16 years. I guess I'm not good enough.

Also fuck having to solve puzzles with a timer with someone looking over your shoulder. I have done emergency "servers are on fire" maintenance in the middle of the night for big customers and it's less stressful than that.

Hmm, i just cbf with leetcode grinding again.

What about for a React/frontend role. Surely no leetcode

It's probably just "'a' + 1 + null , what's the return value?" :D
I mean that one is pretty easy; 'a1null' , first thing is a string so it'll try to concatenate with 1, coerce 1 to a string and get 'a1' then same thing will null. Makes perfect sense ;p
Thanks, I think I'll give up on my desire to have side gigs now.
For me the screen-shared leetcode/React challenge was stupid easy, I failed in the later take home project because I half assed it (no testing/CRUD validation)
What was the take home project about?