What are the "Real World" programming interview questions that everyone keeps talking about?
-
I'm going through interview cycles for a Software Engineering type job right now. I've been reading a few forums and blogs about general interview advice/rants from others. One of the things a lot of people keep complaining about is something along the lines of, "I've had 7-10 years of experience, and they wanted to test me on so-and-so algorithm which I could've googled in two minutes. Why test memorization? Why not ask questions about / in-depth discussions on how to solve difficult real world problems?" My question for those of you who have been part of plenty of interviews, what sort of questions qualify as "real-world non-trivial problems"? I guess the question is also directed at the Sr. Software Engineers who have complained in the past that the interview didn't test their "experience"; what type of questions would have highlighted your "non-trivial real-world experience" instead of asking about specific data structures or algorithms or implementation details?
1. First focus on Coding Ability of a candidate. Ask questions such as write a function to convert an array into a linked list. 2. Next focus on Logic. Write a function to find the number of occurrences of a sub-string inside a given string. 3. Next focus on Design. Write code to demonstrate the Command Pattern.
-
I've been on both sides of the table. There is no set pattern for an interview that works well with everyone. I usually ask these: What was a project that got you excited and why? How do you react to people criticizing your code/documents? What do you do when you get stuck with a problem you can't solve? What are your strengths and weaknesses as a developer? Do you favor Webforms or MVC? [Edit: the latter includes "and why?" :-)] Much better than technical questions since people will inevitably start discussing technology and how they used it.
-
I'm going through interview cycles for a Software Engineering type job right now. I've been reading a few forums and blogs about general interview advice/rants from others. One of the things a lot of people keep complaining about is something along the lines of, "I've had 7-10 years of experience, and they wanted to test me on so-and-so algorithm which I could've googled in two minutes. Why test memorization? Why not ask questions about / in-depth discussions on how to solve difficult real world problems?" My question for those of you who have been part of plenty of interviews, what sort of questions qualify as "real-world non-trivial problems"? I guess the question is also directed at the Sr. Software Engineers who have complained in the past that the interview didn't test their "experience"; what type of questions would have highlighted your "non-trivial real-world experience" instead of asking about specific data structures or algorithms or implementation details?
-
I'm going through interview cycles for a Software Engineering type job right now. I've been reading a few forums and blogs about general interview advice/rants from others. One of the things a lot of people keep complaining about is something along the lines of, "I've had 7-10 years of experience, and they wanted to test me on so-and-so algorithm which I could've googled in two minutes. Why test memorization? Why not ask questions about / in-depth discussions on how to solve difficult real world problems?" My question for those of you who have been part of plenty of interviews, what sort of questions qualify as "real-world non-trivial problems"? I guess the question is also directed at the Sr. Software Engineers who have complained in the past that the interview didn't test their "experience"; what type of questions would have highlighted your "non-trivial real-world experience" instead of asking about specific data structures or algorithms or implementation details?
divyamistry wrote:
I've had 7-10 years of experience
In my opinion it's not about experience at all... I've known people who had been doing the same for ten years and were outmatched in knowledge by juniors. My previous company hired someone with around thirty years of experience with various technologies at various companies, but he wasn't able to write a simple WinForms application! Needless to say we let him go after a month. For my current job I was asked to find the next number in a sequence, to reason about what would happen to a drop of mercury and a candle in an elevator if the elevator fell down a shaft (how the hell should I know, the only thing I know about mercury is that it was used in thermometers) and to write some code that anyone could look up on Google. It's all to "test how you think about problems." And then you get hired and you find out that most people don't think at all. Or that they know what happens with a drop of mercury, but they have no clue what happens inside a database or ORM. I recently read a post by a guy who paid promising job candidates (about $200) to conjure up a small application over a weekend and decided to hire them based on that. That shows some real world experience and it's a hell of a lot cheaper than hiring someone and finding out they aren't what you're looking for. Unfortunately I haven't been hired like that yet :sigh: Maybe more important is your personality. How well do you go with the team? What is your willingness to learn? Etc.
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
I'm going through interview cycles for a Software Engineering type job right now. I've been reading a few forums and blogs about general interview advice/rants from others. One of the things a lot of people keep complaining about is something along the lines of, "I've had 7-10 years of experience, and they wanted to test me on so-and-so algorithm which I could've googled in two minutes. Why test memorization? Why not ask questions about / in-depth discussions on how to solve difficult real world problems?" My question for those of you who have been part of plenty of interviews, what sort of questions qualify as "real-world non-trivial problems"? I guess the question is also directed at the Sr. Software Engineers who have complained in the past that the interview didn't test their "experience"; what type of questions would have highlighted your "non-trivial real-world experience" instead of asking about specific data structures or algorithms or implementation details?
Often those complaints then turn out to be about Kadane's or some other trivial algorithm. "Woe is me, they asked me how to implement a queue using two stacks, I just couldn't remember" - coder license revoked. Memorization my ass, just reinvent it on the spot. If they've forgotten heap sort so thoroughly so they don't know enough to reinvent it, then their working knowledge of algorithms is just shit - can they be trusted to pick the appropriate algorithm? Perhaps they have spent 7-10 years living under a rock software patterns book? If they complained that the interviewer wanted them to write a VRP solver on the spot, fine, I get it, that goes a bit far. On the other hand, that's a simplified version of a real world problem that someone may well have experience with. Not that ridiculous questions are never asked on interviews, far from it. But don't take the whiners too seriously. They are, for obvious reasons, over-represented on the internet. The interviews I've had so far were all perfectly reasonable (even if the job wasn't - and isn't that a more serious problem?).
-
Ernst Iliov Stavro Blofeld wrote:
Write a bubble sort in your favorite language, you have 10 minutes.
You have no idea how often I've seen programmers get the bubble sort wrong. Even the examples on some expert websites are wrong.
The difficult we do right away... ...the impossible takes slightly longer.
I have never, ever, needed to do a bubble sort in my professional career as a software engineer (15+ years). If someone asked me that question, I would leave the interview, after flipping them the bird.
-
I have never, ever, needed to do a bubble sort in my professional career as a software engineer (15+ years). If someone asked me that question, I would leave the interview, after flipping them the bird.
-
No, I think it is a stupid question.
-
I have never, ever, needed to do a bubble sort in my professional career as a software engineer (15+ years). If someone asked me that question, I would leave the interview, after flipping them the bird.
+1
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
No, I think it is a stupid question.
+1
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
I'm going through interview cycles for a Software Engineering type job right now. I've been reading a few forums and blogs about general interview advice/rants from others. One of the things a lot of people keep complaining about is something along the lines of, "I've had 7-10 years of experience, and they wanted to test me on so-and-so algorithm which I could've googled in two minutes. Why test memorization? Why not ask questions about / in-depth discussions on how to solve difficult real world problems?" My question for those of you who have been part of plenty of interviews, what sort of questions qualify as "real-world non-trivial problems"? I guess the question is also directed at the Sr. Software Engineers who have complained in the past that the interview didn't test their "experience"; what type of questions would have highlighted your "non-trivial real-world experience" instead of asking about specific data structures or algorithms or implementation details?
I started in a new job in February. During the first interview: They started to ask me some questions about the technology I was going to use... My answer: Stop this sort of questions. I have never used this technology, so I can't tell anything about it right now. But I am not afraid of new topics and I learn fast. Then they started to ask about my previous company... My answer: I am happy in my current job, I don't really want to leave. I am getting married and previous company is very far for a daily basis. That's why I am searching for something new not so far. Then they started to ask about my personality and my skills: My answers were honest, even when speaking about my defects. I got hired. Conclusion: Tech questions can say little. IMHO the most important thing is: try to know who are going to work with you and determine his/her principles, if he/she is fitting in the team, willing to learn and things like that. The rest... is only a question of time to learn. (btw... now I am already "walking solo" in the projects) I would probably hire a newbie willing to learn and showing engagement, than a lazy guru coming back from everything.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
1. Write a bubble sort in your favorite language, you have 10 minutes. 2. In configuration management terms what is a "trunk" directory and how does it differ from a "tag" directory. 3. Who is Tom Demarco.
Rage against the narrative.
"To Build a Fire" - A dystopian novel about project management, and I am the dog.Ernst Iliov Stavro Blofeld wrote:
Write a bubble sort in your favorite language
Who the heck cares. It's an inefficient algorithm and I would never write one myself.
Ernst Iliov Stavro Blofeld wrote:
In configuration management terms what is a "trunk" directory and how does it differ from a "tag" directory.
Obsolete. At best, describe how branches work in Git.
Ernst Iliov Stavro Blofeld wrote:
Who is Tom Demarco.
That's DeMarco. ;) Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
-
Ernst Iliov Stavro Blofeld wrote:
Write a bubble sort in your favorite language
Who the heck cares. It's an inefficient algorithm and I would never write one myself.
Ernst Iliov Stavro Blofeld wrote:
In configuration management terms what is a "trunk" directory and how does it differ from a "tag" directory.
Obsolete. At best, describe how branches work in Git.
Ernst Iliov Stavro Blofeld wrote:
Who is Tom Demarco.
That's DeMarco. ;) Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
Marc Clifton wrote:
Ernst Iliov Stavro Blofeld wrote:
Write a bubble sort in your favorite language
Who the heck cares. It's an inefficient algorithm and I would never write one myself.
I would hope that the questioner would accept your response (apart from the mild expletive) as being the correct answer. Refusing to do something because it is flawed shows that you are a programmer, not a code monkey. If the questioner still insisted, then you know that the company is not a good place to work at.
-
I started in a new job in February. During the first interview: They started to ask me some questions about the technology I was going to use... My answer: Stop this sort of questions. I have never used this technology, so I can't tell anything about it right now. But I am not afraid of new topics and I learn fast. Then they started to ask about my previous company... My answer: I am happy in my current job, I don't really want to leave. I am getting married and previous company is very far for a daily basis. That's why I am searching for something new not so far. Then they started to ask about my personality and my skills: My answers were honest, even when speaking about my defects. I got hired. Conclusion: Tech questions can say little. IMHO the most important thing is: try to know who are going to work with you and determine his/her principles, if he/she is fitting in the team, willing to learn and things like that. The rest... is only a question of time to learn. (btw... now I am already "walking solo" in the projects) I would probably hire a newbie willing to learn and showing engagement, than a lazy guru coming back from everything.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
Nelek wrote:
I learn fast.
Being able to show examples of this, is how excellent engineers get hired. End of story.
-
I've only given a handful of tech interviews. What I did was pick some easy technical questions that anyone should know, since nobody really likes being put on the spot. I was more interested in how the person thought it out, and way more interested in their personality. I've been on a lot more than I've given though. Very few of them are real world and more academic-type questions, such as "can you find an anagram of blah blah blah", which you just Google that nowadays. Very few tech interviews care about personality.
Jeremy Falcon
I agree. One of the interview questions I had for my current job was to write up a quick little code snippet of doing the recursive power function in either C++ or Java. My colleagues said all they were really interested in was that all of the applicants had a general idea of what the basics are for recursion; and I did get this particular question right even though I hadn't seen it be asked since the very early days as a college student :-\
"I've seen more information on a frickin' sticky note!" - Dave Kreskowiak
-
_Maxxx_ wrote:
except for the last one unless you add "and why?"
I would, of course. Just want to see them justify and hold a position.
-
I'm going through interview cycles for a Software Engineering type job right now. I've been reading a few forums and blogs about general interview advice/rants from others. One of the things a lot of people keep complaining about is something along the lines of, "I've had 7-10 years of experience, and they wanted to test me on so-and-so algorithm which I could've googled in two minutes. Why test memorization? Why not ask questions about / in-depth discussions on how to solve difficult real world problems?" My question for those of you who have been part of plenty of interviews, what sort of questions qualify as "real-world non-trivial problems"? I guess the question is also directed at the Sr. Software Engineers who have complained in the past that the interview didn't test their "experience"; what type of questions would have highlighted your "non-trivial real-world experience" instead of asking about specific data structures or algorithms or implementation details?
-
I've only given a handful of tech interviews. What I did was pick some easy technical questions that anyone should know, since nobody really likes being put on the spot. I was more interested in how the person thought it out, and way more interested in their personality. I've been on a lot more than I've given though. Very few of them are real world and more academic-type questions, such as "can you find an anagram of blah blah blah", which you just Google that nowadays. Very few tech interviews care about personality.
Jeremy Falcon
Jeremy Falcon wrote:
Very few tech interviews care about personality
Ironically, that's what I interview for. Whether I'm interviewing a candidate, or I am the candidate, there's only a single question I want answered: "Are you a jerk?" If I'm the candidate, I want to know what the place is like. Not to borrow a cliche, but I want to know what the culture is: constant panic, laid back, demoralized drone farm, happy unicorns. If I'm looking for a candidate, I have to know I can stand being around you for 40 hours a week. Do you have a life, or is code your holy calling? Can you take direction without whining? Can you give direction without being a prick? Our products have a 10-15 year life span. Will you deign to work on code that old, or are you a New Stuff Nancy? I've turned down job offers because the place had a dress code (ties, for fuck's sake). I've turned down candidates because they were too good, and to convinced of their own superiority.
Software Zen:
delete this; -
I've been on both sides of the table. There is no set pattern for an interview that works well with everyone. I usually ask these: What was a project that got you excited and why? How do you react to people criticizing your code/documents? What do you do when you get stuck with a problem you can't solve? What are your strengths and weaknesses as a developer? Do you favor Webforms or MVC? [Edit: the latter includes "and why?" :-)] Much better than technical questions since people will inevitably start discussing technology and how they used it.
I agree, but you should beware about asking about an interviewee's weakness: I would answer that question like this...[^] (thanks, Oatmeal)
-
Jeremy Falcon wrote:
Very few tech interviews care about personality
Ironically, that's what I interview for. Whether I'm interviewing a candidate, or I am the candidate, there's only a single question I want answered: "Are you a jerk?" If I'm the candidate, I want to know what the place is like. Not to borrow a cliche, but I want to know what the culture is: constant panic, laid back, demoralized drone farm, happy unicorns. If I'm looking for a candidate, I have to know I can stand being around you for 40 hours a week. Do you have a life, or is code your holy calling? Can you take direction without whining? Can you give direction without being a prick? Our products have a 10-15 year life span. Will you deign to work on code that old, or are you a New Stuff Nancy? I've turned down job offers because the place had a dress code (ties, for fuck's sake). I've turned down candidates because they were too good, and to convinced of their own superiority.
Software Zen:
delete this;Gary R. Wheeler wrote:
"Are you a jerk?"
Simple and to the point. Too bad we can't just flat out ask that.
Jeremy Falcon
