LaserToy

20 ms·

211.
by LaserToy 8y ago
I’m too old. I’m telling recruiters that I will not spend even 5 minutes preparing for the interview. I believe that interviews should be based on what you did, not on your ability to memorize a book of CS problems and solutions.if you a c
212.
by LaserToy 8y ago
Recruiter's job is to get you there at any costs. I've being told before that cool team A,B and C wants to talk to me just to find that some boring team D is interviewing me. Google stands on feet of clay
213.
by LaserToy 8y ago
I’m going to write a blog post about it one day. I believe it is inappropriate to ask engineer to prepare in advance for the interviews. Last time I got contacted by their recruiter and sent links to coding websites - I replied “Great for s
214.
by LaserToy 8y ago
I’m sorry, but this one is BS. Google interview is dehumanizing and arrogant. It sucks.
215.
by LaserToy 8y ago
They pay all in cash, other give stock. Almost same outcome.
216.
by LaserToy 8y ago
What is weird that company allows managers to fire people without trying to move them first. Hiring is hard and firing left and right sounds like a dumb idea. Managers should understand that they are not the center of the universe.
217.
by LaserToy 8y ago
Even engineers working for a company need to get much better at sales of their ideas. It is not the best idea that wins, is the best idea that was sold
218.
by LaserToy 8y ago
Based on what I read on their engineering blog they will eventually have a similar outage.
219.
by LaserToy 8y ago
It doesn’t really matter what they used, I just pointed out that their incident report is BS. I can blame virtually any production problem on network, but the ugly truth is - it is not networks fault in most of cases, but fault of engineer
220.
by LaserToy 8y ago
This incident report tells very little. I hope they release what actually happened and how it affected their services. And how they are going to avoid it in the future. Almost any issue can be publicly described as: stuff broke because of n
221.
by LaserToy 8y ago
I’m not a founder, but I think it is not about developers, but rather about personalities (read same things happen everywhere). So, for me the worst things I saw: Pure incompetence mixed with arrogance Bad temper - impossible to argue with
222.
by LaserToy 8y ago
Why distributed systems are hard? Because of many actors and communications overhead. Big companies are slow for the same reason.
223.
by LaserToy 8y ago
Heh, right :) Nope, they too far from SF
224.
by LaserToy 8y ago
I would talk about candidates experience, try to find some project he/she are proud of and dive deeper. I might ask to write some code, but it is not going to be CS exam and it will be in real IDE. I might ask a design question. At t
225.
by LaserToy 8y ago
done
226.
by LaserToy 8y ago
And what is it measuring exactly? In real life you don’t get the score. You either did it or not. Nobody cares about how you did it, only answer matters. And interviews are not pressuring, they are simple. No hard desisions, no anxiety whet
227.
by LaserToy 8y ago
Do you want to work for PlayStation Network team? We have plenty of open positions from DevOps to server or client side developers. And variety of work also there - commerce, social, video streaming, distributes databases, big data, ml. You
228.
by LaserToy 8y ago
Do I? There are a lot of great companies, why should I waste time on Google? Working there is not as fancy as you think. >> Everyone is busy, that's a terrible excuse not to brush up on your interview skills. I believe that their
229.
by LaserToy 8y ago
How many times did you solve a real problem with capturing all the edge cases in less than 45 minutes?
230.
by LaserToy 8y ago
Principal Engineer from huge gaming company here. White board coding interview are testing only one thing: how well candidate is prepared for it. And here what is wrong with it: The assumption that candidate should spend his/her valuab