141–150 of 234 posts
Or maybe this is a signal to short dropbox, since so many of their high performers are interviewing?
I'm glad to see this getting roasted in the comments, as it's a really good example of how companies put out self-serving pseudo-statistical nonsense in an effort to promote themselves. There's no effort to quantify what "technical" or "communication" skills are - these are left to the interpretation of a the interviewer. It makes no effort to show where these engineers are going, what the interview process they're c…
> It perpetuates the myth that there's something really special about Silicon Valley engineers Does this myth still have much traction? If anything, my general regard for engineers in the bay area has steadily declined in the last few years. There are so many really worthless folks who have only figured out how look like they have a clue, but go any deeper and they flail. I know I'm painting with a broad brush, and t…
As an ex-Dropboxer, Dropbox asks legitimately tough questions. I only got in because I got asked the exact set of questions that I could figure out the answer for, once I joined and went through interview training I realized I would have failed about half of the questions that Dropboxers ask. I'm also not sure how it is at other companies (at Google but haven't gone through interview training yet), but Dropbox's rubr…
Dropbox was known as a hard place to interview since 2014, the tech companies that had the hardest technical interviews are Quora, Palantir and Dropbox(honorable mention fog creek)(this was from a few years back so things may have changed). Just because the company makes it extremely difficult to get in does not mean the company is generally all around awesome or pays great or employs the greatest engineers. It optim…
Are you suggesting that these jobs don't mainly consist of quickly banging out dynamic programming and DFS/BFS traversal algorithms as quickly as possible while a stranger stares at you? From interview experience, I assume this is what engineers mostly do at these companies all day.
As an ex-Dropboxer, Dropbox asks legitimately tough questions. I only got in because I got asked the exact set of questions that I could figure out the answer for, once I joined and went through interview training I realized I would have failed about half of the questions that Dropboxers ask. I'm also not sure how it is at other companies (at Google but haven't gone through interview training yet), but Dropbox's rubr…
You just described the entirety of the tech hiring experience. Sure some people are bonafide geniuses that can crack the hardest problems in their sleep. The majority of tech workers, however, are ones who got lucky with the specific combination of questions asked in the interview. Maybe they had seen the question before. Maybe the solution just "clicked". This is why the best strategy for acing such interviews is –…
Dropbox asks difficult questions, and it's hard to discern why. I don't believe the problems at Dropbox are particularly difficult relative to its peers. I don't think they innovate at a clip that's outsized, etc.. But they do this, and their engineering culture focuses on this.
Earlier quoted context omitted.
Props to the honesty
Just to argue against myself, I do think that if enough interviewers interview a candidate, you will get an aggregate score that will give you a pretty good sense of how well that candidate is likely to do on other interviews, and I have found that candidates that do well on these interviews tend to make good employees, although that's based only on the fact that everybody I work with has passed one of these intervie…
Why don't you take a leap of faith once in a while on someone who hasn't done well? Especially if you ever interview interns and have a bunch on that team, that's a near zero-cost gamble for a large corp.
Dropbox was known as a hard place to interview since 2014, the tech companies that had the hardest technical interviews are Quora, Palantir and Dropbox(honorable mention fog creek)(this was from a few years back so things may have changed). Just because the company makes it extremely difficult to get in does not mean the company is generally all around awesome or pays great or employs the greatest engineers. It optim…
The interview process is fairly long, accompanied by an office tour which touts the numerous "Freebies" they offer their employees. Then you find out after the entire process that you'll be getting paid 4050K LESS THAN the industry average. At the time I interviewed with them, I had five years experience in UI/UX and mobile development. What they offered me was essentially what I was making as an entry level dev.
It was easy to turn them down. No amount of free Red Bull is going to pay my mortgage.
Earlier quoted context omitted.
You just described the entirety of the tech hiring experience. Sure some people are bonafide geniuses that can crack the hardest problems in their sleep. The majority of tech workers, however, are ones who got lucky with the specific combination of questions asked in the interview. Maybe they had seen the question before. Maybe the solution just "clicked". This is why the best strategy for acing such interviews is –…
Of course, but this is a gradient. Struggling startup may ask a question that 80% of engineers are capable of answering (through luck, exposure, experience -- whatever dimensions). Dropbox asks difficult questions, and it's hard to discern why. I don't believe the problems at Dropbox are particularly difficult relative to its peers. I don't think they innovate at a clip that's outsized, etc.. But they do this, and th…
That said, I think what I noticed at Dropbox is that asking lots of tough questions gets you a lot of pretty talented folks who are very interested in solving hard technical problems. So from an infrastructure side, Dropbox was overflowing with talented people. From the product side, though, it was harder for teams to staff frontend projects or make progress when their ideas were challenged by infra.
Earlier quoted context omitted.
> graduating without programming skills is impossible I’ve encountered many who graduated from bachelor and even PhD programs without programming skills (even from European universities), so your statement is false. It also seems pretty weird to assume that a degree or certificate is foolproof for demonstrating programming skills. That seems like a lack of critical thinking skills.
I can only speak for myself, but I've never met a (CS) candidate from an accredited Scandinavian university / college that simply could not write code. There are obviously candidates that struggle with performing under pressure - even those that have gone completely blank, but through some simple guiding have bounced back. To be frank, at the schools I studied at, it would be impossible to fake your way through a who…
Earlier quoted context omitted.
Just to argue against myself, I do think that if enough interviewers interview a candidate, you will get an aggregate score that will give you a pretty good sense of how well that candidate is likely to do on other interviews, and I have found that candidates that do well on these interviews tend to make good employees, although that's based only on the fact that everybody I work with has passed one of these intervie…
>I suspect a lot of people who fail these interviews would also make pretty good employees, but I'll never know. Why don't you take a leap of faith once in a while on someone who hasn't done well? Especially if you ever interview interns and have a bunch on that team, that's a near zero-cost gamble for a large corp.
Related, interns are a fantastic way to hire because you get WAY better information about them. Instead of an hour or two of riddles, you've got a three month work history which a couple of trusted employees have witnessed. That's WAY better signal than any whiteboard interview problem could possibly get you.