4 ms·
Most people aren't this consistent. At work does someone say that I will watch you code in a particular time of the day and you will be able to perform on a ran
by re-thc 4y ago
Most people aren't this consistent. At work does someone say that I will watch you code in a particular time of the day and you will be able to perform on a random question that's useless?
No.
Interviews have 0 context that's needed for anyone to perform. Usually you can't use your IDE, your settings or your ways of working and you've never paired up with the interviewer so might not feel comfortable.
To make matters worse the interview topic is 90% chance not what you do on a day-to-day basis. No 1 is answering leet code questions at work. We're going to be using a library or tool and not to try write an analytics algorithm.
- ryandrake 4y agoAnother harsh reality is that for most jobs, the initial interview is by far the hardest part of the job. Once you pass it, the rest is cake. It takes a lot less effort and brainpower to keep a job than it does to get it. I still look back to a FAANG interview a decade ago being the most difficult thing I've ever done in my life, and I've worked my way up from a shit mining town to the middle class, developed a complete complex software product starting from an empty text file, gotten an advanced degree, built a single engine airplane, and managed to stay married for 20 years. But out of all that, a stupid FAANG interview was the most difficult. It's just ridiculous what companies put people through.