My answer was "introspection. Next question, please". I didn't get the job.
job interview: "what's your bad quality?" - Page 17
Forum Index > General Forum |
Anonymous_Coward
United Kingdom1347 Posts
My answer was "introspection. Next question, please". I didn't get the job. | ||
Krohm
Canada1857 Posts
Overall though I've landed all but 1 job I've had an interview for. I'd say I got my interview skills down pretty well. I'm also overqualified for a lot of the jobs I've went into and the HR person was hesitant in hiring me. Fortunately I've convinced them otherwise, but in the long run hiring me was probably a bad idea because I jump ship once I find a higher paying job. (I do give notices though, because it's NEVER a good idea to burn bridges.) | ||
RemedySC
Canada176 Posts
| ||
dLKnighT
Canada735 Posts
| ||
Mawi
Sweden4365 Posts
Name 3 of your biggest weakness 1. Im short 2. Overwork 3. Overplan things For some reason my boss was allways like hmmm i like your'e hired | ||
HuggyBear
Australia377 Posts
I said I was: 1) Inexperienced 2) Cheap 3) I want this job and I'm willing to work $50 less per week than the next guy His expression was priceless, and we both got a good laugh from it. Good thing he didn't take me seriously. lol | ||
SuperPro
99 Posts
| ||
kingcoyote
United States546 Posts
Most people would be shocked at how few comp-sci majors are hire-able because they completely lock up when given the most basic programming task. http://www.codinghorror.com/blog/2007/02/why-cant-programmers-program.html | ||
Archontas
United States319 Posts
On April 05 2012 11:01 visual77 wrote: This is semi related, but if you're a comp-sci major, you'll get farther being able to do a fizzbuzz in every language on your resume than figuring out the perfect answer to a question like that. Most people would be shocked at how few comp-sci majors are hire-able because they completely lock up when given the most basic programming task. http://www.codinghorror.com/blog/2007/02/why-cant-programmers-program.html Reading this article made me very sad. I'm an electrical engineering major but I filled up on CS courses for tech electives, I remember a former teacher telling us about a student who, after graduating and entering the workforce, still didn't know what the difference between a stack and a queue was. The professor demanded that he return his diploma. | ||
obesechicken13
United States10467 Posts
On April 05 2012 19:14 Archontas wrote: Reading this article made me very sad. I'm an electrical engineering major but I filled up on CS courses for tech electives, I remember a former teacher telling us about a student who, after graduating and entering the workforce, still didn't know what the difference between a stack and a queue was. The professor demanded that he return his diploma. Stack and Queue? Wait a stack is when you have pushes and pops. Hardware stuff. Queues are just a container for holding stuff. Yes no? Or does it have to do with how you remove stuff from the two data structures? Like LIFO for stacks and FIFO for queues? | ||
Skilledblob
Germany3392 Posts
On April 05 2012 11:01 visual77 wrote: This is semi related, but if you're a comp-sci major, you'll get farther being able to do a fizzbuzz in every language on your resume than figuring out the perfect answer to a question like that. Most people would be shocked at how few comp-sci majors are hire-able because they completely lock up when given the most basic programming task. http://www.codinghorror.com/blog/2007/02/why-cant-programmers-program.html it's probably more a case of inflated knowledge instead of genuine not knowing. You learn so much in school and university that you will forget most of it fast if you dont use it constantly. So a fresh master in comp science might be really great at the complicated stuff but completely fail at the more entry level stuff because in the last 2 years he never had to think about that or do anything related. | ||
MisterD
Germany1338 Posts
On April 05 2012 21:02 obesechicken13 wrote: Stack and Queue? Wait a stack is when you have pushes and pops. Hardware stuff. Queues are just a container for holding stuff. Yes no? Or does it have to do with how you remove stuff from the two data structures? Like LIFO for stacks and FIFO for queues? haha why is push and pop hardware stuff? :D do you think there's some kind of buffer with a spring inside your computer where it physically pushes in things and pops them off again like a PEZ dispenser? i hope not ^^ Of course it's all data structures. The classic memory stack is just the most popular way of organizing the memory bank your hardware offers, but it's still a behavior definition rather than a hardware element. LIFO and FIFO is pretty much the correct distinction. For a queue you think horizontally, you add to the end (or sometimes in the middle if you have a priority queue) and take out at the front, for a stack you think vertically, both adding and taking out is done on top (or both at the bottom, whichever way you like more, point is everything behind the one end point is "benched" and inaccessible). | ||
micronesia
United States24342 Posts
Also surprised there were multiple people trying to use their "track record" on interviews to give their opinion credence. I'd like to see a list of every interview they've been on along with how competitive and high level it was. | ||
kingcoyote
United States546 Posts
On April 05 2012 21:11 Skilledblob wrote: it's probably more a case of inflated knowledge instead of genuine not knowing. You learn so much in school and university that you will forget most of it fast if you dont use it constantly. So a fresh master in comp science might be really great at the complicated stuff but completely fail at the more entry level stuff because in the last 2 years he never had to think about that or do anything related. If you can't do a fizzbuzz, you can't do complicated stuff. It's using the most common programming commands possible that would be used routinely by anyone who writes anything. At it's heart it is a loop, some if statements and some print statements. | ||
rally_point
Canada458 Posts
1. after learning something new you need time to yourself to absorb and refine the ideas (ie study alone) 2. You tend to over prepare for important tasks (ie stress out), which may cause you to adjust the priority of other tasks (don't need to say the second part I guess) It's allllll in the wording haha. Also it'd be nice if you had examples I am a 25 year old engineering grad (at age 23) that just got a job in the finance sector if you're curious. And only been through two interviews since grad (got both jobs). I'm inexperienced though at both life and interviews so take my advice with a grain of salt :p | ||
zul
Germany5427 Posts
On April 05 2012 22:34 micronesia wrote: Something that surprises me about this thread is how many people use whether or not they got a job to justify whether or not their answer to one question in particular was good. You could easily give a poor answer and still get the job. You could easily give a great answer and not get the job. Also surprised there were multiple people trying to use their "track record" on interviews to give their opinion credence. I'd like to see a list of every interview they've been on along with how competitive and high level it was. so whats your bad quality? | ||
micronesia
United States24342 Posts
I already addressed what I would want to talk about if asked this earlier in the thread. I would not give the same answer each time necessarily. And no, I don't believe that I specifically have one bad quality that stands out over all other qualities. | ||
killa_robot
Canada1884 Posts
On April 05 2012 11:01 visual77 wrote: This is semi related, but if you're a comp-sci major, you'll get farther being able to do a fizzbuzz in every language on your resume than figuring out the perfect answer to a question like that. Most people would be shocked at how few comp-sci majors are hire-able because they completely lock up when given the most basic programming task. http://www.codinghorror.com/blog/2007/02/why-cant-programmers-program.html Lol, I actually had an interview where right at the end they gave me 5 minutes to do something like this. I screwed up. I didn't fail it by any means, as the logic was there, but my syntax was wrong so ultimately it didn't work. Kinda happens when you haven't really programmed in a while. Needless to say I didn't get the job, but that doesn't mean anyone that did it right was a better programmer than me, nor that I can't program well. People panic, freeze up, and make mistakes, especially in an interview setting. | ||
kainzero
United States5211 Posts
| ||
DemonDeacon
United States158 Posts
one thing i have said is that i can be forgetful but i make up for it by being organized and keeping a detailed calendar with all my appointments on it. | ||
| ||