In my personal experience, having interviewed dozens of candidates (data science), I believe that asking "easy" and "simple" questions is the most effective way to probe the problem-solving skills of a candidate. Fun and interesting solutions to easy questions are hallmarks of great individuals. The question would go like this: Suppose I have a column-oriented file and I want to print out a column in a reverse-sorted…
How do you sort an infinite stream?
The dystopian world of software engineering interviews
161–170 of 851 posts
Re: The dystopian world of software engineering interviews
#162Earlier quoted context omitted.
If the problem was oversupply, we wouldn't be getting the cushy salaries and benefits we do. I think the issue is more that it's pretty easy for people with no programming ability to appear competent on a resume, especially to a clueless HR rep or headhunter. There are a lot of people out there whose backgrounds look good on paper who can't solve FizzBuzz...
Hypothesis: There's such a flood of qualified labor that employers can afford to arbitrarily shrink the pool of applicants without significantly worsening their outcomes. Their behavior indicates that just the top N% of the market is enough to fill the needs of all selective companies. "Top" can be a semi-random filter, since the pool of basically competent people is much deeper than N. (There's also a much larger fl…
Re: The dystopian world of software engineering interviews
#163Earlier quoted context omitted.
> Google might not need you to code some efficient algorithm to search a b-tree every day, but they pay top dollar and can rightly expect that their software engineers can come up with efficient and creative solutions to hard problems without dragging the rest of their team down. This is a non-sequitur. Being able to write good software has nothing to do with reading cracking the coding interview and practicing leetc…
Google has strong data that it does predict job performance, better than GPA, college degree and so on. What are your aggregate data showing that Google is wrong on this?
They flopped on wave and Google plus, hard. Those are the kinds of mistakes that kill most companies. Even Google glass still somewhat rankles and has left me with no confidence in any of their consumer things.
And I say this as a happy Google fi user. In that I'm not convinced any alternative is worth moving to. Still can't fathom why Android is wasting fully half of my storage for "system".
I'm not claiming they are crap. But I do have a hard time making all the things they do that are beyond the industry. Other than spend a ton of money.
Re: The dystopian world of software engineering interviews
#164Re: The dystopian world of software engineering interviews
#165> "The horrifically dystopian world of software engineering interviews" If you actually read the linked article, there aren't really any interviews. The OP is just getting let down by recruiters.
It seems that you were the one who didn't read the article. He mentions several.
Re: The dystopian world of software engineering interviews
#166Earlier quoted context omitted.
That's what I think every time I see one of these articles but tech companies still have a permanent door into every congressional office to plead the exact opposite while seeking to import more labor into the market.
When they say that, they want phds, not entry level candidates
Re: The dystopian world of software engineering interviews
#167Earlier quoted context omitted.
I must admit I always feel weird when I see numbers like that mentioned for software engineers. In Germany a more reasonable number with a few years of experience might be in the €50-55k ballpark. Granted, the cost of living is significantly lower in most cities here than it is in the bay area, but still it just feels... weird. Edit: Fixed a typo.
I think Europe (and the UK) undervalue software engineers. At least in the UK this seems like a cultural thing where management is high status/high value and engineers are low status/low value. I think the US generally gets this right (at least in silicon valley), but it could partly be because the US has some extremely valuable software companies that operate on a global stage that aren't really present elsewhere. R…
Re: The dystopian world of software engineering interviews
#168In my personal experience, having interviewed dozens of candidates (data science), I believe that asking "easy" and "simple" questions is the most effective way to probe the problem-solving skills of a candidate. Fun and interesting solutions to easy questions are hallmarks of great individuals. The question would go like this: Suppose I have a column-oriented file and I want to print out a column in a reverse-sorted…
A column orientated file? What format? Excel? CSV? What is cut, sort or head? Are you only accepting Linux candidates then, a tiny percentage of users? This sort of utter nonsense question, heavily loaded to your "standard" experience, which is anything but, is even worse than the questions cited in the article. All you're doing is filtering for people who are in your tribe, who followed the same path as you and thin…
OP asked a very open ended question, merely made a suggestion that it could also be done with some standard Unix programs (I grew up on windows and even I know about cut and awk because you spend enough time anywhere in tech you will know these). Why it triggered you, not sure, but perhaps the question it's doing its job after all.
Re: The dystopian world of software engineering interviews
#1691. Open source your entire codebase
2. Each user story, commit for feature, etc is tagged
3. Pending features are correlated to (2).
Finally, no interview or references. Simply hire people who can complete high level implementations for the features to extent one can given an arbitrary time frame.
Re: The dystopian world of software engineering interviews
#170Comedian Daniel Tosh had a bit about people that claimed to be smart, it's just that they were just bad at taking tests. He said, "oh, so you struggle with the part where we find out what you actually know?" I hear a lot of complaints about the "typical" software engineering hiring process, and it usually comes from the people that don't do well within the current system. Could the process be improved? Almost certain…
> Google might not need you to code some efficient algorithm to search a b-tree every day, but they pay top dollar and can rightly expect that their software engineers can come up with efficient and creative solutions to hard problems without dragging the rest of their team down. This is a non-sequitur. Being able to write good software has nothing to do with reading cracking the coding interview and practicing leetc…