|
Ask The Hamsters[^]
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Great reply Griff. Most excellent in every way.
|
|
|
|
|
|
thanks!
|
|
|
|
|
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 never had to administer technical screens and interviews until recently. And I was saddened at the trivia questions one of my colleagues came up with -- concerning facts that have no application to what we actually do. A trained monkey can do what we need done - heck I had never even touched it when I started on the current project.
We've been interviewing primarily for SSIS developers, so I've been asking questions related more toward determining a candidate's breadth of experience rather than depth of knowledge. The best question is asking the candidate to describe a project they are particularly proud of.
|
|
|
|
|
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
|
|
|
|
|
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 f***'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
|
|
|
|
|
As always, the devil's in the details. As programmers, we should be used to that.
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.
modified 10-Oct-15 18:52pm.
|
|
|
|
|
+5 - except for the last one unless you add "and why?"
PooperPig - Coming Soon
|
|
|
|
|
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.
|
|
|
|
|
|
Hilarious. When I've been asked that question, I usually say "My greatest weakness is not tolerating people who don't do what they say they will do".
|
|
|
|
|
- Write a bubble sort in your favorite language, you have 10 minutes.
- In configuration management terms what is a "trunk" directory and how does it differ from a "tag" directory.
- Who is Tom Demarco.
Rage against the narrative.
"To Build a Fire" - A dystopian novel about project management, and I am the dog.
|
|
|
|
|
4. Spell "Bjarne Stroustrup" backward.
5. Implement a Turing Machine in XSLT. Have it compute the value of 6! .
|
|
|
|
|
6. Which can you do faster:
a. describe why you are probably not the right person for this position
b. describe why you are better off in the long-run not to have been offered a job.
«I want to stay as close to the edge as I can without going over. Out on the edge you see all kinds of things you can't see from the center» Kurt Vonnegut.
|
|
|
|
|
Ernst Iliov Stavro Blofeld wrote: Who is Tom Demarco
Third baseman for the Chicago Cubs
What we got here is a failure to communicate
|
|
|
|
|
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.
|
|
|
|
|
You'd prefer a harder question?
|
|
|
|
|
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.
|
|
|
|