Just playing, but "If you have n servers that take requests, and server Sᵢ can take a request every tᵢ seconds, and you need to distribute requests to them as efficiently as possible, how do you do it?" can be done very easily in Go. You have a shared channel which contains the pending requests, and a goroutine per server that simply loops doing: read from the shared channel, perform the request, wait for the sleep p…
A Wretched Google Interview Experience
111–120 of 359 posts
Re: A Wretched Google Interview Experience
#112Google's recruiting seems like it must be at least partially the responsibility of short-tenure contractors. Every time I've dealt with people from their recruiting department, even the very nice ones seemed forgetful, inattentive and poor at communication. The actual Google employees who do the interviewing are on average very bright, good at actively interviewing candidates (instead of just rattling off questions),…
The crazy thing is they don't give feedback, then call back in a few months and ask if you want to interview again for the same position like the OP said. Talk about completely confusing people. . .
Re: A Wretched Google Interview Experience
#113An acquaintance of mine applied for a product management job, did two interviews in NY that went fine, then was flown out to MTV for a series of interviews. When this person got there, two of the people they were supposed to meet with were traveling on business and hadn't notified the recruiter. A third was out sick. The supposed-to-be fourth, now first interview walked into the room and said, "Look, I don't have any…
This made more sense after I figured out MTV was Mountain View, not Music Television. O_o
Re: A Wretched Google Interview Experience
#114Instead, my last communication with Google was a phone call where I was told that one of the interviewers still hadn't handed in their written review. It's now three months later, and that's the last I heard.
That left a sour taste in my mouth. I wasn't expecting to get the job, and really it was just a backup plan in case Algorithmic.ly didn't work out, but you'd think they'd have the common courtesy to get back to me. I'm sort of expecting that 6 months from now I'll hear from them out of the blue...that's how disorganized the process is.
Re: A Wretched Google Interview Experience
#115I think this is very unfortunate. I've seen a lot of good candidates get rejected for no obvious reasons. The lack of communication seems driven I think by the sheer deluge of the number of resumes/interviews going on at Google, and what appears to be, a reliance on temps and contractors as part of the process. I had a friend who interviewed at Google, who is an excellent software engineer I've worked with for years,…
My recruiter failed to call me at the scheduled time. Twice. I wasn't too terribly dismayed, as I was already home at the time anyway, but that put me in a pretty bad mood to begin with. I failed the first phone interview spectacularly because he asked about data structures and estimating powers of two, and I haven't done any of that after 4 years in the industry. I guess fair enough; if that's what they expect of th…
Re: A Wretched Google Interview Experience
#116An acquaintance of mine applied for a product management job, did two interviews in NY that went fine, then was flown out to MTV for a series of interviews. When this person got there, two of the people they were supposed to meet with were traveling on business and hadn't notified the recruiter. A third was out sick. The supposed-to-be fourth, now first interview walked into the room and said, "Look, I don't have any…
And they can do all of that just because everybody still wants to work at Google. Let's say the have 100 applicants for a position, out of which 10 are qualified for it. Then they can still screw 9 of them and hire the one person that for one reason or the other had the luck of interviewing with the right people and talking to the right recruiters.
Re: A Wretched Google Interview Experience
#117In addition to having been in IT for a very long time I am also very knowledgeable on capital markets having successfully taken CFA (Chartered Financial Analyst) tests. The CFO of the company that interviewed me was shocked that someone in IT passed those tests. The IT people, it was all algorithms and programming minutia. After the interview, they strung me along for weeks and then I just stopped calling them to check up on status and they stopped calling me. Then they would call me every few months asking me to interview again. I finally asked them to stop calling me.
The reason I bring this up is because I think sometimes candidates are excellent candidates for a $100,000 to $150,000 salary position. The only problem is the candidate is already making $250,000 and the prospective employer knows it after you fill out the application. I may be just thinking this to make myself feel better but I just thought the issue with the company was that I made too much. I probably would've had to literally walk on water and bring their dead relatives back to life to justify what they would've had to pay me to steal me from my current company.
Maybe that's the problem Google had with you?
Re: A Wretched Google Interview Experience
#118Re: A Wretched Google Interview Experience
#119Earlier quoted context omitted.
Maybe it's a subtle form of age discrimination?
Not sure how it could be considered age discrimination though. You tend to forget 'knowledge' like this fairly quickly. I know for my part at least I generally have to brush up on this kind of learning about every six months (or even less perhaps), if I wanted to retain it.
It would be like requiring you to recite all the marks you received on all your assignments in all your classes in your last semester of your senior year of college. I assume that if you had just graduated, this would be easy, but if you had graduated 10 years prior, this would be hard (feasible if you'd kept the paperwork--but hard).
Re: A Wretched Google Interview Experience
#120Cached: http://webcache.googleusercontent.com/search?q=cache:http://...
Funny, that cached version is not loading either on my machine.
http://webcache.googleusercontent.com/search?q=cache:http://...