Timeline for Is it wise to ask about design decisions made on a product during an interview? [closed]
Current License: CC BY-SA 3.0
39 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 17, 2015 at 21:11 | history | closed |
durron597 user40980 Bart van Ingen Schenau user53019 user22815 |
Opinion-based | |
Jun 16, 2015 at 18:12 | review | Close votes | |||
Jun 17, 2015 at 21:11 | |||||
Mar 25, 2012 at 10:25 | history | edited | yannis |
edited tags
|
|
Jan 5, 2012 at 11:32 | history | edited | Desolate Planet | CC BY-SA 3.0 |
deleted 65 characters in body
|
Nov 27, 2011 at 11:38 | history | edited | Desolate Planet | CC BY-SA 3.0 |
edited body
|
Nov 18, 2011 at 17:54 | comment | added | David Hayes | Sounds like you had a lucky escape the interviewer sounds like an insecure (at least insecure about his technical decisions) jerk. I wouldn't want to work for anyone who reacted like that to a simple and perfectly reasonable question. I've interviewed dozens of people and I'd be pleased to get a question like that | |
Nov 16, 2011 at 17:20 | comment | added | Steven Evers | @DesolatePlanet: haha. I take notes all the time in my interview. I have a checklist (modified joel test) and a list of questions that I prepare before the interview. I write their answers (in bullet form) and mark my checklist when necessary. That way, there's no awkward silence, there's no "Have any questions?" "Uhh.. nope." and I've got a whiteboard-backup just in case. | |
Nov 16, 2011 at 16:38 | comment | added | Desolate Planet | @SnOrfus - I can't say I ever done this or heard of anyone who has done this. I think keeping eye contact and actively engaged in the interview is pretty important and taking time to write notes would distract me from that. That's just me though. I could very write random stuff like a shopping list and look like I'm taking notes :) | |
Nov 16, 2011 at 14:34 | comment | added | Steven Evers | Take notes in the interview (even as the interviewee). People are calmer when you do this. Seriously. | |
Nov 16, 2011 at 14:12 | history | edited | Desolate Planet | CC BY-SA 3.0 |
deleted 58 characters in body; Post Made Community Wiki
|
Nov 15, 2011 at 14:35 | vote | accept | Desolate Planet | ||
Nov 14, 2011 at 17:22 | answer | added | Emilio M Bumachar | timeline score: 1 | |
Nov 14, 2011 at 16:58 | answer | added | Jaydee | timeline score: 1 | |
Nov 14, 2011 at 16:53 | answer | added | smp7d | timeline score: 3 | |
Nov 14, 2011 at 16:44 | history | edited | Desolate Planet | CC BY-SA 3.0 |
added 4 characters in body
|
Nov 14, 2011 at 15:25 | answer | added | Wayne Molina | timeline score: 3 | |
Nov 14, 2011 at 13:04 | comment | added | Desolate Planet | @jhocking - Yep, again, I don't think he was expecting me to ask questions on their software stack, he obviously assumed I was desperate for work and I was going to ask simple questions about holiday allowance etc. I'll never understand why he reacted the way he did, but it was probably one of my worst interview experiences. | |
Nov 14, 2011 at 12:59 | comment | added | jhocking | I think my favorite part of the story is "When prompted to ask questions". So he asked if you had any questions, and then blew up when you did? | |
Nov 14, 2011 at 12:00 | history | edited | Desolate Planet | CC BY-SA 3.0 |
deleted 15 characters in body
|
Nov 13, 2011 at 18:00 | history | edited | Desolate Planet | CC BY-SA 3.0 |
added 232 characters in body
|
Nov 13, 2011 at 6:39 | comment | added | Matt | I probably wouldn't ask "why use this over that". You just don't know. Instead you may just want to ask, "what was the decision behind using x language?" | |
Nov 13, 2011 at 3:50 | comment | added | yannis | I've very limited interviewing experience, and typically I'll meet the candidate after (s)he had successfully dealt with the HR people. One candidate initiated an architectural discussion during the interview, and he actually identified a few things we could improve. When he got his first paycheck he was amazed to see that it included a second check for the couple of hours of the interview. The sad thing is that if he had probed the HR people, I'd probably never meet him. | |
Nov 13, 2011 at 1:08 | comment | added | Lou | I think you just explained why it is good to probe on arhictectural choices. It is better to find these things out before you've committed to a new job. I would however speak to the HR person before leaving the interview so that they can be aware of why you've left. | |
Nov 12, 2011 at 22:54 | answer | added | anon | timeline score: 1 | |
Nov 12, 2011 at 21:44 | history | edited | Desolate Planet | CC BY-SA 3.0 |
added 44 characters in body
|
Nov 12, 2011 at 20:49 | history | edited | Desolate Planet | CC BY-SA 3.0 |
added 3 characters in body
|
Nov 12, 2011 at 20:42 | answer | added | NimChimpsky | timeline score: 12 | |
Nov 12, 2011 at 20:37 | history | edited | Desolate Planet | CC BY-SA 3.0 |
added 1 characters in body
|
Nov 12, 2011 at 19:12 | history | edited | Desolate Planet | CC BY-SA 3.0 |
deleted 1 characters in body
|
Nov 12, 2011 at 18:57 | answer | added | JasonTrue | timeline score: 15 | |
Nov 12, 2011 at 18:46 | history | edited | Desolate Planet | CC BY-SA 3.0 |
added 69 characters in body
|
Nov 12, 2011 at 18:31 | history | edited | Desolate Planet | CC BY-SA 3.0 |
added 8 characters in body
|
Nov 12, 2011 at 17:47 | answer | added | tp1 | timeline score: -5 | |
Nov 12, 2011 at 17:21 | history | tweeted | twitter.com/#!/StackProgrammer/status/135406795710660609 | ||
Nov 12, 2011 at 17:16 | comment | added | Blrfl | I've never had to do it, but that kind of behavior on an interviewer's part would be met with "I'm sorry, you have failed the interview" followed by my departure. | |
Nov 12, 2011 at 16:59 | answer | added | Bryan Oakley | timeline score: 16 | |
Nov 12, 2011 at 16:33 | history | edited | Desolate Planet | CC BY-SA 3.0 |
added 26 characters in body
|
Nov 12, 2011 at 16:12 | answer | added | pdr | timeline score: 53 | |
Nov 12, 2011 at 15:57 | history | asked | Desolate Planet | CC BY-SA 3.0 |