3 ms·
Eh, I just got approached by Google via LinkedIn and went for it even though I was sure I wouldn't get it. Sure enough, I did not get it, but it was nevertheles
by donaq 16y ago
Eh, I just got approached by Google via LinkedIn and went for it even though I was sure I wouldn't get it. Sure enough, I did not get it, but it was nevertheless a valuable experience. I have learned two things:
1) An n^2 algorithm runs in polynomial time, but it is no longer good enough when n ~= 100000000. Assuming 1000000 operations a second, that is still a few hundred years. I have never thought of it because I've just never encountered that sort of scale. I may never do, but it was still a revelation for me.
2) It confirmed that I am really rusty at algorithms due to one too many jobs writing CRUD web apps. I need to do something about this. For a start, practice in my free time and secondly, look for a job that allows me to develop in that area.
I'm not saying that it wasn't disappointing even though I knew my chances weren't good, but I gave it my best shot and I am choosing to use the experience positively. Is that serendipity?
- nostrademons 16y ago1) There's nothing quite like looking at your MapReduce status page and seeing "Estimated completion time: 79 years."
- drgath 16y agoInterviewing for jobs you know you won't get is one of the best things you can do in your career. The insight you gain on both their hiring process as well as their expectation is priceless. I've interviewed with 5 big web companies, failed many, but landed one (after a failed first attempt). I credit my experiences learned from the failed attempts as the reason I was eventually hired.