Yes, I was interviewed at Google last year. This was basically what happened. Sure, they have your resume, I am not sure if they read it throughly, the interviewer didn't even know my major until I told him at the end of the interview. While, they don't stop inteview and say you made mistake, it's competitive and it's not possible to hire you. But, you know at that moment that you are not getting hired. I guess, they need plenty of reasons to hire a candidate, but just one reason to reject. I am not complaining, it seems to work for Google very well.
I am speaking from personal experience here, they don't count a lot of factors while rejecting a candidate, you make one mistake on their particular set of questions, you are out. They don't even look at your resumes until all your 4 interviews are completed. However, selecting a candidate is a different matter, in that decision they might consider everything.
In the long run, this could affect Google, but, then again, if they change their hiring policies for better even after long 5 years, the best talent that might had been rejected before would still go to work at Google. So, still I don't think Google really consider it as an issue for them. Though, I have been burned once myself by them.
Yes, exactly, since it's Google, they can afford to have strong filters which will definitely filter out a bad hire, may be at the expense of rejecting a good candidate. Their policy might expect good candidate to get absorbed in Google one way or other, but they definitely want to filter a bad hire. However, in the recent years, I have seen this to be not working as expected. Still, I don't think it matters to Google as an big organization.
Google interviewers are strictly told to ask these data structures and algorithms questions, it doesn't matter to them if they are relevant for future work. I have even read reviews by PhD candidates where even they were asked these questions in the interviews. When I interviewed with Google last year, I remember that the interviewers had a blueprint of the type of questions they were allowed to ask. They hardly concentrate on your resume during the interviews.
I guess they might operate at a loss for a few years. While its a difficult goal, but it is possible. They have the biggest market possible. Language is elementary for humans. I think if they can target schools and universities with a commercial model, it could really generate the kind of revenues your talking about.
So, in a way, you are actually running a software consulting/development firm, however, in this case, you just have to manage yourself. Scouting for clients, deadlines are similar to a firm/agency running multiple contracts. I get that it requires pretty good networking and communication skills. Thank you for sharing your experience.
I am not even sure now that this will work in good economic times, since there is saturation in contract-based assignments, with agencies hiring programmers on very low rate in developing countries.
All I can take away from this is that, one needs to have experience and a great network (potential clients) before thinking about contract work. Thank you for your input.
You could be very right here, since most of the people I come across working on contracts are already in the market for at least 10 years. In today's market, for someone new starting out, I guess there will be cut-throat competition to get programming contracts, with people ready to work at a very low rate (e.g. on Freelancer, oDesk).
Yeah, as obvious as it is, one always tends to forget what are the ultimate goals one is working for? As long as there is motivation, maybe it wouldn't be so bad.
I am going to start working soon. This makes me think if full-time work is really worth it. Wouldn't multiple short-term contracts with regular breaks be able to cut it in today's world? Isn't there people with experience on working on short-term contracts and still living well-off?
While, I am sure governments at some level try to reduce poverty, but they can't do it without educating the people. Internet is rather cheap and provides a great way for the same.
"Give a man a fish and you feed him for a day; teach a man to fish and you feed him for a lifetime".
Actually, HP had been doing that since quite some time. In 2008, they announced that they have discovered the memristor and would bring it in the market by 2012, which then shifted to 2014, then 2015, and now they are still not sure whether they will be able to utilize this by 2020. No surprise here.
I agree, with the type of growth Swift has shown in the past, there is going to be a big demand for Swift developers now. Swift could possibly rule the mobile/web. I have already added it on my #TODO list :)
While Graph Engine definitely looks useful, I agree that the comparison is unfair. GE is an optimized implementation while associative containers (unordered_*) in C++ are more generalized implementations.
The above blog provided clearly explains optimized implementations of associative containers in C++. It would be interesting to see how these compare with GE.
You are only considering the cost of infrastructure. What about the basic salary for the people working on the application and monitoring infrastructure, who will pay for that, if not users and not ads and not government?
Either users will pay with their money or pay with their data (getting ads), else the model is not sustainable. Since, messaging using Internet is being considered here as basic necessity, one could argue that Messaging apps turns to be non-profit organizations or government supported organizations (but anonymous).