What's your greatest weakness? To be 100% honest, I'm not a huge fan of this question since it's a lose-lose question: if the individual being interviewed is completely honest, they probably won't get the job, and if they give a flat out lie it will be evident very quickly.
However, throughout the years I have had several managers ask me this question, so it's important to have a well thought out answer ready. Since I've been on both sides of the interview chair, I have put together a list of the worst ways to answer this question and then some of the best answers.
So first of all, these are the kinds of answers you should avoid to the infamous question about what is your great weakness when you're in that coding interview:
- Hard time saying no: This will say that you are weak and will take on too many projects, typically resulting in poor performance.
- Can have a hard time staying on a single task: This means you should probably either learn how to focus or that you are supposed to be an entrepreneur, working for a company usually means long hours on long, repetitive tasks, and if someone is bouncing from project to project they're not going to be a good asset to the team.
- Can be arrogant: I had a professor in grad school, Dr. Richard Gelfond, who is one of the most brilliant computer scientists I've ever known, who said this about arrogance: "Being arrogant occasionally doesn't matter, but it's never good". An arrogant employee won't be able to work well with others and will have a hard time taking correction or learning anything new… because they already know it all.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.