The question you should ask at your next interview...
-
"Which one did you mean?" Should do that... ;)
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
They had a list and asked me to pick one to track down.
You'll never get very far if all you do is follow instructions.
-
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
Besides the typical employment questions, I ask: What source control system do you use? Is your database schema normalized? What's the spec's on the dev's workstations? Who does your testing? Do you even do testing? What's your code coverage? (I love the "well, that's really hard to measure" dance) How do I work from home? And then for the real fun question: I'd like to see an example of some specification / requirements documents. And one more: Do you pay for your employees to go to training seminars or to take online courses? Marc
-
Besides the typical employment questions, I ask: What source control system do you use? Is your database schema normalized? What's the spec's on the dev's workstations? Who does your testing? Do you even do testing? What's your code coverage? (I love the "well, that's really hard to measure" dance) How do I work from home? And then for the real fun question: I'd like to see an example of some specification / requirements documents. And one more: Do you pay for your employees to go to training seminars or to take online courses? Marc
Oh Marc, Marc... I wish I had this list a few years ago. I'm in a very nice arrangement now, but I would have loved to see this interviewer prick squirm.
Charlie Gilley You're going to tell me what I want to know, or I'm going to beat you to death in your own house. "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
-
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
Duncan Edwards Jones wrote:
I think next time I'm going to ask to see some code.
If I was asking that question, I don't think I would have accepted any job offer.
-
Besides the typical employment questions, I ask: What source control system do you use? Is your database schema normalized? What's the spec's on the dev's workstations? Who does your testing? Do you even do testing? What's your code coverage? (I love the "well, that's really hard to measure" dance) How do I work from home? And then for the real fun question: I'd like to see an example of some specification / requirements documents. And one more: Do you pay for your employees to go to training seminars or to take online courses? Marc
I've been on the other side of the desk for some years now (I'm not a good interviewer, I think it is pure luck we have a quality team) and have never heard these type of questions. I've even had a few who have no questions at all. I hate interviewing, from either side of the desk.
Never underestimate the power of human stupidity RAH
-
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
-
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
-
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
I actually ask to take a closer look at the workspace. I'm not interested in the nice office of the boss. One of my last pointy hairs used to sit at a desk right before rows of desks like a teacher before a school class. And guess what, spying on his people was one of his dirty little hobbies. A good look at the way the team works and their little specialties tells me far more than they would ever tell me voluntarily. If I get to see some code, that's also nice and well. I hope for the best, expect the worst and am rarely disappointed.
The language is JavaScript. that of Mordor, which I will not utter here
I hold an A-7 computer expert classification, Commodore. I'm well acquainted with Dr. Daystrom's theories and discoveries. The basic design of all our ship's computers are JavaScript. -
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
This is an interesting topic, seeing that I interview a lot of candidates. Obviously asking annoying questions will mark you as being a troublesome characters which most developer teams prefer to avoid. But beyond being polite, and beyond checking if the candidate took actual interest into our workplace, this question does come up, and I am wondering what I would ask if I was to be interviewed myself. I think I would ask: "Can I spend a few minutes with one of the developers who is working now, to see what kind of environment you are working in"? This would give you a chance to look at the work environment (hardware), and to ask some 'none formal' questions (QA, testing, dev software, procedures, etc), and of course check out the people where you may find yourself spending an incredible amount of time with in the near future.
-
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
-
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
-
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
That's an excellent idea.
Software Zen:
delete this; -
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
Bah! Go for the gusto. Here's my favorite -- from either side of the interview:
"Assume there are Plutonians. Assume there are elves. If the elves attacked Pluto without warning, tomorrow at 9 AM local time, which side would you be on?"
Note that there are three answers to that question, not two -- and perceiving the third is almost as important as choosing it.
Of course, if you think the above question would make you "look silly," the old fallback "Are your stools black and tarry?" is always available.
(This message is programming you in ways you cannot detect. Be afraid.)
-
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
I've gotten very good at this one, through bitter experience of being grilled to within an inch of my life and then asked to write database layer code, or sit around hassling server admins for certificates and fill out forms... ALWAYS: 1. Ask to meet the team, maybe have lunch or coffee. 2. Ask to see some code, but accept that might not be an option 3. Ask to see the workspace. 4. Ask about the typical workday scenario, bug fixes etc. 5. Ask about how disputes are resolved. Usually your prospective boss is in the room. Use this to find out how he reacts to confrontation. 6. Ask about code standards and who is in charge of what goes into the codebase. Sometimes: Ask a curveball... Example; "So, say after this interview, we're both happy, we move forward, and I comne to work for TechCorp LLC. But, fast forward three months down the line, and I'm sitting in this office handing you my resignation letter. What's the most likely reason this has happened?" This is again a challenge to see if they react well. Be careful who you ask this one to though. If it's an old project, ask questions about how it came about. Get a good sense of the history of it. Old projects have a way of being cash cows, and this makes them cumbersome and unwieldy. Companies romanticize them.
I too dabbled in pacifism once.
-
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
The three question I always ask are: What's your beverage situation? (Do they provide free soda, or will I have to go to the corner deli for my Diet Coke needs) What provisions are there for my bicycle? (Is there is inside bike rack? Can I take it up the elevator and put it under my desk? (It folds)). Why is working here less evil than working at a bank? (Always interesting to see how creative their answers are)
Truth, James
-
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
I'm not sure how relevant that would be – every company has some good code they could bring out for such purposes, and most of what they actually work on will be under IP agreements so they can't show it to you until you join anyway, I'd think. Having a look at where the devs actually work so you can get a feel for the place and the people is the most important, I think. Here at my company our second stage 'interview' includes the prospective new employee doing some coding on a computer in our main dev office, so they get to see how we all work and whether they like the working environment.
-
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
-
You know the bit where the interviewer(s) turn to the candidate and ask "Do you have any questions for us?" I think next time I'm going to ask to see some code. You see - as a developer the application source code is a very significant component of my working environment and if it is like the aftermath of an explosion in a Scrabble(tm) factory I'd rather not get involved.
like the aftermath of an explosion in a Scrabble(tm) factory Great! LOL!
-
Comments on this. - Why do I want to see their code? i am being hired to help them write better code usually so it doesn't matter what it looks like now. I really only need a few things. Good quiet working conditions(dual monitors, comfy chair, bathroom somewhere close and clean(It has been an issue for a friend)), Training so that I can continue to grow and extend the team and myself, The Ability to make changes(Introduce Code Repository, Introduce formal testing) To setup things the way they should be setup. Don't overlook the ugly coding job with the boss who is willing to let you have the above. Especially if you get to setup the testing plans and the code repository and code reviews and builds and deploys. I have this now. Things are working well 3 years in. Mainly because I came into nothing but a nice window cube and a good machine and the willingness of my boss to let me get things setup correctly(according to ME). Now: The team works together, We share, we do code reviews. It was nice to just have people listen and to try to follow some standards and they were begging for standards and some consistency. Starting from scratch was AWESOME!
To err is human to really mess up you need a computer
