Earlier quoted context omitted.
Meh, I'm with previous commenter. I know what the event loop means, that JS is single threaded, and what setTimeout is supposed to do under normal circumstances. I consider the question stupid, moreover your answer to it is likely incorrect, because it depends on the implementation. I bet Node.js never interrupts the loop for example (and I never even done Node.js, it would just be a sane thing to do). And yeah, you…
Then please enlighten me what frontend questions you ask in your interviews. By the way, only 1 out of 10 frontend developers can answer what the event loop is, according to my experience.
My Job Interview at Google (2008)
161–169 of 169 posts
Re: My Job Interview at Google (2008)
#162I work at Google as an SRE, joined a few years ago. I am approaching 40, worked in a bunch of other companies before. My degree is is in the humanities, from a third world university you never heard of. I don't have any open source contributions. I speak lousy accented English (but I am a man and "white" if we are counting privileges.) I got contacted by a recruiter. I had a couple of phone interviews which felt like…
> The design doc culture at Google is excessive and silly
I have a friend who started there last year and said the same thing.
> My peer SREs actually know far more about all the nice Google architectural stuff than our peers in SWE-land, who are mostly implementing features on top of huge abstraction layers and typically are only exposed to one particular facet of the infrastructure. Google's infrastructure is impressive and something of a marvel. It doesn't mean it's perfect. SRE is the better point of view to observe it.
Interesting point here as well.
Re: My Job Interview at Google (2008)
#163Earlier quoted context omitted.
Then please enlighten me what frontend questions you ask in your interviews. By the way, only 1 out of 10 frontend developers can answer what the event loop is, according to my experience.
I am not saying understanding event loop is not mandatory for senior JS devs. It is just that your question is really obscure. Why not just ask what an event loop is and what are the consequences of that execution model?
So when you ask "What is the JavaScript event loop?", most will stare at you not knowing what it is. So then I jump to the practical side. They at least should have worked with either setTimeout, async/await and/or events. So then you start asking for practical consequences of the event loop, such as what happens with an infinite loop after setTimeout or await, or during handling of an event. That is a real practical example that they should know. If you don't then you don't know neither theory nor practice.
Re: My Job Interview at Google (2008)
#164Earlier quoted context omitted.
> Google employs the very elite of the elite I needed that laugh, thank you!
Google has at least 50K employees, spread all over the world. I guess it is quite possible to gather and recruit 50K employees who are much better developers than most others outside but I would not (rather cannot) call each one of them elite of the elite ! Look, a great deal of valuable software has been created by Google and other FAANGs. But I reckon most of that value has actually been created by the first or the…
There are other companies besides Google. Who's to say, for starters, that any of the engineers at the members of FAAN, or Microsoft, or the unicorns, are any less elite?
Re: My Job Interview at Google (2008)
#165Earlier quoted context omitted.
People who dedicate their lives to curing cancer and putting people on Mars are titans for making verrry verrry wee little dents in those problem areas. Your typical software engineer slept through the minimum amount of biology coursework required of them and has no special interest in chemistry beyond maybe like, a broscience-level grasp of pharmacology related to research compounds commonly viewed as smart drugs. I…
A lot of cancer research is about optimizing computation, which is what a lot of Google engineers do. I didn't pick the examples flippantly.
I'll explain why it sounds preposterous to me, and why the idea that google could change the fate of cancer research or missions to mars if not for its profit motives is patently unrealistic to the point of being insulting to everyone involved in this counterfactual.
1. Why cancer?
Number one cause of death is heart disease. Why not that? Surely the #1 problem is good enough for people currently working on adtech if the #2 problem is.
You said curing cancer, not "applying the numerical optimization expertise of a tiny fraction of google's workforce to the occasional omics problem in collaboration with a research lab" or "headhunting the PI of a lifesci research program to build an initiative at Google" or "throwing google infra at something other than Stadia". Even something far more obvious like "applying deep learning to diagnostics / early detection / etc."
These are the things Google can actually do, and they are the things Google already does. Examples: DeepMind for breast cancer screenings, Public Datasets program support for selected research. Still no cancer cure. So if you'd said that, well, they're doing it, to whatever extent they deem worth the prestige bump.
Unless they decide to become Microsoft and buy out entire sectors of applied biotech, they're not going to radically improve their hands-on involvement in lifesci relative to what they're already doing.
More, just ballpark the numbers. Google has 100k employees — "98771" in 2018-12 as per their SERP infobox. "A lot" of those employees absolutely do not by any stretch of the imagination possess the skillsets required to assist in meaningful ways on high-end cancer research, unless that work is conducted like some kind of wartime effort and the assistance is largely of a clerical nature.
And in the event that Google employees were being unilaterally drafted into this effort as grunts, the very first thing they'd do would be to crowdsource/outsource the bulk of the menial work to cheaper labor sources beyond Google. So their main contribution would undoubtedly be in building the scaffolding required to pass the buck.
2. Why Mars?
This constitutes a complete diversion of Google's autonomous driving and robotics people to an out of the blue project that they're out of position to handle. It would merely sabotage a division where Google is a market leader for the sake of starting up an incoherent, laggard mess in an area defined by maddening bottlenecks and complexity. Google has no substantial preexisting expertise in this area, afaik.
At one point they put up 30M USD in sponsorship prize money for a lunar lander competition, but that's about all that comes to mind. It also went pretty dismally. They had to repeatedly extend the deadline. Eventually the comp ran 11 years and ended in one launch -> one crash on the lunar surface. They threw a mil at the team as a consolation prize.
That project was more of an exercise in reifying the moonshot metaphor than anything else.
One far more recent indicator of how hard it is to make strides in this area is the DARPA Launch Challenge, intended to accelerate radical improvements to launch pipelines. It just closed without a winner. One team barely made it to the launchpad then scrubbed.
In terms of both social good that Google can do with its nearest preexisting R&D and profitability, it's clear that redirection would be disastrous. Autonomous vehicles are the play for them. This has nothing to do with the adtech people either way.
All in all, the relevance of Google to either of these problem areas is about what would be expected, cet par: not a lot. Modern work with any technical bent is hyper-specialized. There's no jump from literal cancer like adtech to actual cancer.
On top of that, adtech is largely a house of cards. You can't ever assume that 'data science' coupled to business requirements and marketing is in any way rigorous or indicative of the current state of the art in independent research. A lot of this work is pure smoke and mirrors operating on greater fool theory. To specialize in that sector is to specialize in window-dressing falsity. So it's not like you'd want adtech data jockeys touching subject matter that actually matters.
Re: My Job Interview at Google (2008)
#166Earlier quoted context omitted.
People who dedicate their lives to curing cancer and putting people on Mars are titans for making verrry verrry wee little dents in those problem areas. Your typical software engineer slept through the minimum amount of biology coursework required of them and has no special interest in chemistry beyond maybe like, a broscience-level grasp of pharmacology related to research compounds commonly viewed as smart drugs. I…
I'm not sure what the intention of the OP was but I read it as those engineers could help push those efforts forward by doing what they do best -- writing software. Not all of those involved in the effort to cure cancer are studying chemicals and making drugs. There's also people who have to run some matrix calculations with MATLAB code, or who have to transcribe experiments into excel sheets. It's hard to think that…
Parent comment: https://news.ycombinator.com/item?id=23124327
Re: My Job Interview at Google (2008)
#167[0]: https://medium.com/@simon/2008-how-i-got-hired-by-amazon-com...
Re: My Job Interview at Google (2008)
#168Earlier quoted context omitted.
I am not saying understanding event loop is not mandatory for senior JS devs. It is just that your question is really obscure. Why not just ask what an event loop is and what are the consequences of that execution model?
Some JavaScript developers know the theory, but not all of them. At least you should know how it practically works. So when you ask "What is the JavaScript event loop?", most will stare at you not knowing what it is. So then I jump to the practical side. They at least should have worked with either setTimeout, async/await and/or events. So then you start asking for practical consequences of the event loop, such as wh…
Re: My Job Interview at Google (2008)
#169I recently had an interview at a taxi firm that followed this format. One two three pre-interviews followed by a day of 5 grueling 1 hour interviews. I didn't get the role. Apparently the frontend guy I had the first interview of the days five was concerned about my technical skills. I mean, I find it insulting, having worked for the last 12+ years as a developer to be told that there were "concerns about your techni…
> having worked for the last 12+ years as a developer I've done plenty of interviews, and the amount of years someone worked does not mean they are technically capable. By chance, last week I interviewed a frontend JavaScript expert: couldn't explain 'scope', couldn't explain 'function context', didn't know what happens when setTimeout() is followed by an infinite loop ("After 10 seconds or so the browser will probab…