| || |
| || || |
| || |
Ok thanks you gave me the impression that you were like Google.
That is the reason I might not give my CV to Google. I do not assume myself to be able to answer such tests. Although I might have a couple of papers in my name I still lack technical details. I have been taught to identify the problem, study the difficulties of it and then searching for the best solution.
My professors at least follow this mindset: they give more attention to the theoretical dimensions of the problem.
They assume that the implementation is trivial and straightforward. That is why in universities you are not learned all the programming languages. But only the object-oriented approach with some practice with java.
But I think this is opposite to the real world and industrial companies. Implementation matters. I see ads that expect to know two or three languages in detail and of course have working experience.
| || || |
Just apply to Google; you've got nothing to lose and they love PhD or masters candidates. They will want to see some coding abilities (Java will be fine) even if you're applying for a non-coding (e.g. project management) role. Typical coding questions you might have to answer (might be in general terms or you might have to code it) would be: complexity lookup times (big O) for various data structures (hash table, tree, etc); how such structures would be implemented; graph theory; range intersection (somebody I know had to code a range intersection algorithm at the interview).