What is the best Interview question that you have ever been asked ?
Let it be anything C++/Java/OS/Algorithms/Data structures or even an HR Question, it should just be the best in your opinion.
You can post more than one questions also.
thanks
|
What is the best Interview question that you have ever been asked ? Let it be anything C++/Java/OS/Algorithms/Data structures or even an HR Question, it should just be the best in your opinion. You can post more than one questions also. thanks |
|||||||||||||||||||||
|
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.
They were trying to get a feel for what kind of research techniques I use and what resources I'm familiar with. My answer, which they were pleased with was: Google, blogs, msdn, co-workers, books - generally in that order (SO/decent Q&A sites weren't well known at the time). |
|||||||||||||||||
|
|
Without being sarcastic or cynical the best question for me was:
|
|||||||||||||||
|
|
For a network heavy development position, "describe everything that happens, in as much detail as possible, when you open up a web browser on your desktop and go to www.foo.com". |
|||||||||||||||||
|
The answer of course, is that it depends on which features those 80% are. If you're focusing on the most important features first, then the 80% of complete features should be the most important 80%, which means that shipping should come first. If your design process is haphazard then the 80% of features complete might not be the ones you need the most, and you'll need to delay. The key, I pointed out, was that it was a fine line between "Delay for two weeks" and "Duke Nukem Forever". You always have to be careful when walking that line. |
|||||||||||||||||
|
|
Long before there was an internet... I was given a manual for a language that they knew I didn't know, paper and pen, and put in a room with a problem for a half hour. I think the problem was something about synchronizing two databases using this language, but the actual problem wasn't that important. What was important was how we dealt with a problem when we didn't know the language. Some people just sat there for the half hour, because they didn't know. I started working it out anyway. That was testing attitude, is the person a problem solver, or do they give up easily? I got the job. |
|||||
|
|
"So, how do you ensure the quality of your code?" Well, the answer involved TDD, version control, peer review practices and everything else pretty much under the sun. Got the gig as well - well pleased. |
|||
|
|
|
Best: "Tell me about your side projects" -- This tells you a huge amount about the candidate. If a developer candidate writes software on the side, you can learn how complex of a project they are comfortable with, how much development experience they have, how skilled they are at engineering, how they manage their own time, etc. If your prospective developer spends all his spare time modding his car, you can infer that this is not his dream job and he may not be with you long. Honorable mention: "What is your ideal job?" -- This was from my current employer, and it started us talking about what I actually enjoy doing. He has ever since tailored the job to meet my needs and I am much more valuable to the company as a result. "Write your own question. Pick any question you want that shows how valuable you are, and answer it." -- Heard my boss ask an intern candidate this last week after she alleged that our logic puzzles were a biased metric. |
|||
|
|
(within the team) |
|||||||||||||||||
|
|
"What do you do when you are certain that the solution is to use technology/technique/algorithm X, but your supervisor is equally convinced that the solution is technology/technique/algorithm Y?" I gave an answer about making a detailed presentation as to the virtues of X over Y, but then once a decision had been made, doing my best to respect/support the decisions of upper management. |
|||||||||
|
|
For me it is
That's the time I first realize though learning programming for years, I have not done anything really exciting that I can be proud of ... |
|||
|
|
It doesn't sound like a great question. On the surface, it won't tell the interviewer anything about which design patterns you know, which ORMs you use, whether you can write FizzBuzz without resorting to hard-coding all of the lines, or even whether you know that However, I found it revealing on both sides. Here's a guy who probably grew up hacking on a computer that his parents bought him "for schoolwork" rather than someone who got into programming because VB looked like it could be lucrative. He probably writes code for fun when he's not at work. In short, he's probably been a coder for most of his life and loves doing it. He's probably someone you could learn a thing or two from and will enjoy working with. Unfortunately, now that your computer choices are basically limited to an IBM-compatible PC running one of 3 different operating systems, this question is becoming more and more obsolete. |
|||
|
|
|
I am a web-application developer. So, when-ever I go for interview, I am asked this question
Anyone here, have been asked a similar question. |
|||
|
|
|
I onced got the question,
The question completely popped me. I nearly started laughing because it was so far away from my mindset. I develope for making things work, not to remember my mistakes. I ended up with no answer on this question. Which of course was a bad sign. An experienced developer without one single mistake in the luggage. Well, that would ring warning bells to who? I mean, who haven't deployed the test connnectionstring or forgot the test string "Mamals can eat" on the GUI? So, word of my, have some old mistakes in mind, preferably one with a little touch of humour. |
||||
|
|
|
My favorite interview question was "Design an application for a ping-pong tournament."* From that start it turned into a series of questions that I was really into. Like, I asked if it was a web application, or desktop, or some other platform (web app). Then I asked if it's a real ping-pong tournament or a virtual simulation (a real tournament). And so on. Once I gathered a bunch of additional information, then I started drawing out functional requirements (eg. the app behaves differently for players, spectators, and referees) and planning what objects would be involved and how they relate. Once I drew a block diagram on the board he decided I'd answered the question well and we moved on to another topic. It was a great question because it started off fairly vague and had a lot of meat to it for him to evaluate/me to show off how I would design an application. *yes I realize that's not a question, you know what I mean. |
|||
|
|