Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Dec 17, 2012 07:48 PM by Dan Bracuk
Dec 13, 2012 10:09 AM|LINK
Couple of times we are asked to add questions on pool for recruiting cell.
This happened last week,
We had two ppl, N and X, with same kinds of skills applying for a position. But X had more knowledge on banking application.
Since, we were looking for ppl with business knowledge expertise. He got hired.
So, basically nothing went wrong.
N, the guy who didn't get hired, was more intuitive in answering logical questions, he had more framework exposure and fair knowledge of data structure.
While X, the guy who got hired, always floated around when we asked him abt Data Structures.
Q: What's the different between quick sort and bubble sort?
N's answer: Well, it's the implementation i read it somewhere in college. We can use Array.Sort() and so... He always twisted questions around API.
We had discussion, we dont have to know low level implemenations for busniess-service based applications. Well, maybe.
But i dont know i aint being adamant but these are building blocks. These are insights. These are mantras.
I've seen ppl making their own classes to implement features even it's given by built-in classes. They dont know it exists and end up messing up in long run.
Maybe, I'm old school
Dec 17, 2012 07:14 PM|LINK
Yes, you're old. lol
Sorting questions are outdated. Sorting is handled in the class objects now as I'm sure you know.
Now as far as your hiring decision, I think it was a bad decision. It's much easier to teach a technically competent candidate the business logic than it is to teach someone the programming.
Dec 17, 2012 07:48 PM|LINK
I get senior's discounts from some business and I've never heard of quick or bubble sorts.