What frustrate me about these interviews is one need to talk on phone and code at the same time. Who the fuck do that in real life.I am so fucked up with this thinking out loud shit.
It's why despite constantly being asked to interview at FANG I don't, as I just don't feel like dealing with that kind of stress. I prefer to stagnante to being obsolete where I am.
I saved up enough that I paid off my house and I opened a bar. I just don't have the heart for the /r/iamverysmart crowd, that always paints themselves into the same corners because "neat and new", or dealing with more political crap where the customer is never a thought in their equation
Don't worry, there are a lot of jobs that don't do this kind of high pressure interviews. Especially outside of web development there are huge markets of people who are really happy to get their issues solved, and don't really care if it takes one or two days.
I think you might be reading something that isn’t there. Look for comments by ankrgyl where he says that some candidates liked to talk about what they were doing as they did it, and others didn’t, and that it wasn’t really important to them one way or the other. Also, I think he said that these interviews were done in person, and that this replaced a question where coding on a whiteboard was expected.
I somewhat disagree with this article. Microservice is great for complex software modules. But some jokers in industry starts writing miscroservice for every small function/method in the code. It's better that microservice should be designed by experts.
Because we were educated before "flavor of the month" JavaScript framework...
And because if that we can appreciate elegant and practical tools and ideas. See also emacs and vim.
But it has survived - Clojure, a JVM lisp dialect, flourishes!
Feel part of what makes lisp fascinating is its simplicity and power leading to its place as a test bed for ideas such as continuations and Kanren, a new logic programming language.
1. It's all their feeble minds can understand. (This is the answer you were fishing for, yes?)
2. Too many MIT grads were brainwashed by SICP until MIT sensibly switched to Python in 2009. (Unfortunately they probably still secretly teach SICP somewhere.)
3. Lisp/Scheme readily implements "Maxwell's equations of software" which are believed to be important or useful for some reason.
I believe "shortcut books" like the one posted by OP appeal to some of us because it's a succinct source of, basically... lookup queries. That is, when we run across a question we can't answer, we'd prefer to Google that topic on our own and learn in our own nonlinear style. Don't give me a pile of textbooks corresponding to 6-10 semesters of classes, give me a single book like this and let me research by myself everything it refers to.
I make a point of never doing "projects" during a recruitment process. The fact is that there are too many good opportunities out there that will not require me two spend a full day or even several days in a week to complete a job application, without compensation. Whenever I hear that there is a "project" to complete, I just tell them that I already have tons of projects to work on and pass the "opportunity".
My problem with these line of numerous shallow books and courses are
1) Written by people who has no experience in industry or they are not working on "real" machine learning jobs
2) They think the standard in industry is pretty low and any BS works. For example the concept of "lagrange multiplier" is missing from the book. One need this concept to understand training convergence guarantee.
I ignore all of this. The OP is coming from a no name company and don't have any expertises. If you are senior and you don't have any expertises or deep experience in a domain, you will have tough time getting a job even in this hot market.
You should a little negative but I read you twice and there is some truth in your message. I am actually working in one of the popular FANG company. I receive solicitations every day (3-10). I have no time to answer everyone. I have over 15 years of experience and the few times I decided to reply I realized two things. First, once you start giving a range of compensation the discussion stop rapidly for 90% of the recruiters. The market is "hot" but for folks that are not that senior (or with lower expectation that I have maybe). The second thing is that when it goes well and we start the process that everything is super slow motion. Positive feedbacks but every step take weeks to move on. At a point where I lost any excitement. Hence, I suppose my field is not such in demand... that engineers with less years of experience get these positions faster than me since I am strict about my expectation. I might have the wrong conclusion here but I found that this "hot market" is not "hot" for the whole range of expertises and years of experience.
I've been actively interviewing for almost the past five years. I recently concluded my job search and basically landed my dream job (or very close to it). However I was extremely picky about what I was looking for which probably made my search take so long.
If I was less picky, I could probably have gotten a new job at a decent, but not spectacular, company, with probably at max, ~3 months of active interviewing.
Likewise one of my friends is what I'd like to describe as a "master networker". The way he can easily and quickly network his way into a new job is shocking - often times without an leetcode interview. These jobs typically tend to pay at least above average (hedge funds). However the caveat is that he has to be very unpicky about the exact nature of the role, sometimes working with very boring or unsexy tech stacks for example.
I spent two years looking and then just threw in the towel and took a job at GE. They turned out to have a far more inflated view of themselves than was warranted or even healthy...so that only lasted a few years. Consulting now with one of the few boutique firms in my city...which has been fairly nice.
Yes, I suspect there's a lot of title inflation going on in the industry.
I have a Senior title (at a "no name" company) and can probably get a Senior title elsewhere (I also get recruitment emails for those all the time), but perhaps only for some values of "Senior".
Phil is a great person and previously had director of engineering/product roles at Digital Ocean, Meetup/Wework, and Soundcloud. It's not worth dismissing his advice out of hand :)
I hadn't heard of it, but he also had Director titles at Meetup, WeWork, and DigitalOcean, which I very much have. (Also Buoyant, but I don't recognize that one either.)
Using intrinsics correctly generally requires understanding assembly, because they are supposed to match the assembly you'd want to generate. Just sprinkling them around because you're not familiar with x86 assembly is unlikely to be productive.
