As I've worked with more different languages over my career, I've become less and less able to answer those syntax / standard-library questions, simply because there are so many half conflicting memories of other ways to do it.
If the interviewer is any good--big if--they'll mainly be concerned about whether the candidate is making plausible code, regardless of whether it is String.split(s1,s2) or s1.split(s2) or StringUtil.split(s2,s1) ...
Luckily i never had to go through these interviews to get some work.
I'll be hiring programmers next year and only two things matter to me: their code - i want to see how clean they are, how they think, how they structure the logic and flow. And how capable they are for solving a problem. That's it. Nothing else truly matters. Programming is essentially a detective work of high level problem solving. I have couple of questions where i present a problem and ask for a solution - not code, just how they would solve it. And there is no bad answer, but i am looking for a particular way of thinking/solving things, so we're more in sync and that's about it.
If the interviewer is any good--big if--they'll mainly be concerned about whether the candidate is making plausible code, regardless of whether it is String.split(s1,s2) or s1.split(s2) or StringUtil.split(s2,s1) ...
reply