531–540 of 674 posts
Earlier quoted context omitted.
then we make them go through an animated slideshow and do a quiz to get to an email address
And when that gets rigged by some wicked OCR, then a Super Mario simulation where the princess is the realdeal@email.com, and every 10 coins or every level would get them an additional resume-info nugget to consume. Okay maybe I took it too far.
Earlier quoted context omitted.
The problem is that what interests you now may not be economically valuable next year. They want you there past one project, because the future is too murky to guarantee your current role will continue to be needed. Google et. al. are hiring generalists because they want people of a mindset such that when the entire special-purpose they hired them for dissolves, they're willing and eager to ramp up on a new project a…
You are taking a much too narrow view of "specialization". If project foo is really the only project at Google that uses the skills I like and know best, I am probably not going to apply there. I get that there are people who don't care (much) what kind of code they are working on. If those are the people Google exclusively wants, that's fine. I just won't have a place there. I do not think this is a generally-advisa…
The big tech companies do also build well-crafted teams of specialists where appropriate (for instance, Google's Deep Mind team is all AI specialists). I don't know what sort of hiring process they use for those roles, but I would wager the process is a little more personalized, and also substantially more selective.
Earlier quoted context omitted.
then we make them go through an animated slideshow and do a quiz to get to an email address
And when that gets rigged by some wicked OCR, then a Super Mario simulation where the princess is the realdeal@email.com, and every 10 coins or every level would get them an additional resume-info nugget to consume. Okay maybe I took it too far.
You didn't take it too far, someone build the first online recruiter focused video game where the prize at the end of each level is the contact details for a more-and-more suitably qualified candidate.
I've been thinking about it for a while to try to transition from a mechanical engineer to a software engineer but are all the interviews as miserable as HN makes it seem? I feel like these interview structure is a form of deterrent. I had a quick call with one of the recruiters from Apple for a hardware engineer position. He said the interview will take about a week and needs about a month to prepare... I didn't cal…
Earlier quoted context omitted.
> The reason I won't work at Google is because Google is incapable of hiring the engineers I want to work with That's a very bold (even arrogant, sorry) statement about 57,000+ (googled it) employees. So 57,000 are worse devs then you ? This is what i hear from your statement, correct me if I am wrong .. Many extremely talented people want to work for Google. They will take the tests, even if they don't agree with th…
Since Google is an advertising company that even hires their own chefs, I would not expect 100% of their employees to be software developers. It's more on the order of 20k developers, not 57k. https://www.quora.com/How-many-software-engineers-does-Googl... >Have you found any correlation between poor code and being able to pass Google's interview ? cough cough Angular 2
There is an enormous difference between poor code and a library you don't like. I may not be a huge fan of Angular 2, but it's certainly not poorly written code.
Earlier quoted context omitted.
> The rest are the "dog properties" that go on the MLS and need heavy marketing to sell. That's... a strange way to look at the housing market. The norm is to list your property and then see what bids you get. Putting your house on the market is not some weird trick to pass a crappy house on to a bunch of rubes, or am I misunderstanding you? Like, how do you reliably find a willing buyer pre-listing, and how do you k…
The point is that the best homes(top 10%) rarely need to go on the market. The hotter the market, the more realtors know buyers willing to pay a lot for the first home that meets all their needs. Hence more homes are sold before listed.
I think that's locale specific. Except in the 15million+ bracket, auctions (here in Melbourne at least) tend to get the best money for the seller.
A lot of comments here, not many saying "Disclosure: I (used to) work there"
Earlier quoted context omitted.
I'd pay at least a few dollars per month / tens of dollars per year for this service. I'm not kidding. Dear HN reader, please steal this idea!
If everyone does this, then recruiters will simply start to spam the yesireallydidreadthisgiganticemail2017@mydomain.com emails without reading the autogenerated "profile".
To me, getting this done on interesting domains seems to be the hard part. For people with their own domain, getting a separate server to deal with email for that is some hassle. You can't really do this on a generic domain either, cause that looks a lot less professional. Signing people up for gMail accounts might work, but that's probably against google eula. I'd guess the same for other webmail services that are at least somewhat professionally acceptable.
Best way I see is to give people with their own domain as easy a time as possible to set up DNS correctly. Getting through DKIM and SPF reliably seems like a minefield though.
Earlier quoted context omitted.
> it is not sensitive to non-algorithmic skills and talents that interviewees have. I work at Google and do interviews (though I don't enjoy them). We do ask questions around domain expertise, software design, etc. It's not all just coding and algorithms. A good question: 1. Has a low enough floor that a poor candidate can still make some progress and not feel like they are doing poorly and get stressed out. 2. Has a…
Speaking as someone who's done these interviews (but was never, for the record, asked about anything other than coding/algorithms): I think the core premise is flawed. The idea that a good developer is somebody who can regurgitate knowledge they learned on Wikipedia in a few hours from memory is just not a good base for determining if the engineer is good. More importantly, a developer who cannot regurgitate the know…
I don't think Google's hiring people thing that that's what a good developer is, as much as they think it positively correlates to good developers.
(I don't know to what degree that's true, but it's how I assume they arrived at the current interview process.)
> More importantly, a developer who cannot regurgitate the knowledge from memory is not necessarily a bad developer
This is also a valid concern, but Google is much more concerned about false positives than false negatives. Missing out on a good candidate is a bummer. Hiring a bad one can be a nightmare. So the process is skewed to avoid the latter even if it costs the former.
Earlier quoted context omitted.
> it is not sensitive to non-algorithmic skills and talents that interviewees have. I work at Google and do interviews (though I don't enjoy them). We do ask questions around domain expertise, software design, etc. It's not all just coding and algorithms. A good question: 1. Has a low enough floor that a poor candidate can still make some progress and not feel like they are doing poorly and get stressed out. 2. Has a…
you're missing something important about my comment. the issue isn't the hair-splitting difference between what you call "puzzle or trick questions" and what you describe as "a good question" (with your eight criteria). the issue is that Google style interviews ONLY ONLY ONLY ask coding questions in a pressure cooker environment. I've interviewed at Google and the interview experience was sufficient to convince me th…
By "pressure cooker", to you mean in terms of time, or more social intensity? There's not too much Google can do about time. Like I said, it's not fair to ask candidates to dump weeks of their life into the hiring process.
If it's about the social intensity, I agree, that's hard. Many programmers are introverted and being "on" for an interview is really really difficult. It's one of the reasons I don't like doing interviews—it's hard for me on the other end too.
We are trained to try to make it as relaxing and pleasant of an experience as we can, but there's only so much we can do. The reality is you're in a 1-1 conversion with someone with a fixed time bound and where your performance may alter the trajectory of your life.
That is a stressful experience, no two ways about it.