4 ms·
The point, in this case, being that they weren't going for a coding position. They would not expect to solve that kind of problem as part of their job - becaus
by AndrewDucker 13y ago
The point, in this case, being that they weren't going for a coding position. They would not expect to solve that kind of problem as part of their job - because they were going for a community liason/management role, not a technical one.
- tptacek 13y agoI can't help you do a better job getting a job at Google, but I can help you with tech job interviews in general: don't suggest big libraries as solutions to small programming problems, and especially don't stick to your guns after the interviewer asks for the DIY solution.
- leokun 13y agoI think the gist of the problem is that when Google acquires a company the way they handle the non-technical staff can be a bit off-putting. Instead of working hard to find them a place within Google during the acquisition process, or just laying them off with some kind of severance, they put the burden on the individual. You have a year to find a place? Basically that just means, you have a year to find a new place to work.
- quesera 13y ago> when Google acquires a company the way they handle the non-technical staff can be a bit off-putting. True enough. Depending on the acquisition and the acquiring company, non-technical staff might not even get an interview -- they're just sent on their way with some thank you money, sometimes. The standard year is the "don't say bad things about us" move done by companies that are sensitive to that kind of negative PR. But really, finding a place for staff members that you would not have hired involves a lot of energy which can almost certainly be put to better use elsewhere in the business.