ocjp 6 — Feeding a person with food is a great thing in this world. Feeding the same person by transferring the knowledge is far more better thing. The reason is the amount of satisfaction which we get through food is of only one minute or two. But the satisfaction which we can get through the knowledge is of life long.
Vishal Hegde wrote:What do interviewers tend to know when they say "say something about yourself?"
This kind of question ticks me off.
In my experience, that indicates, the interviewer has not bothered/has not got time to read your resume. To kill time, and cover up this snafu, you are told to tell something about yourself. Excuse me? Everything you need to know about me is already there on the resume. Did you bother to even read it?
I disagree, Maneesh. Everything you need to know about a person is definitely NOT on their resume.
Can they talk clearly, and make themselves understood? Can they talk to strangers? Can they put together a coherent statement, or do they ramble on and on without saying anything? Do they talk too much, and not know when to shut up?
Further, I consider this question one that helps put the interviewee at ease. Almost everyone likes to talk about themselves. If the first question you get is a tough one, it can put you off your game for the entire interview. This way, everyone kind of gets to know each other and it becomes more a friendly conversation than an adversarial inquisition.
There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors
Maneesh Godbole wrote:In my experience, that indicates, the interviewer has not bothered/has not got time to read your resume. To kill time, and cover up this snafu, you are told to tell something about yourself. Excuse me? Everything you need to know about me is already there on the resume. Did you bother to even read it?
First, I'll agree that this question is too generic. And personally, I don't ask such questions. However, I am also surprised (read shocked) at the amount of times, that I get a candidate that doesn't know what is actually in his/her resume !!
fred rosenberger wrote:I disagree, Maneesh. Everything you need to know about a person is definitely NOT on their resume.
Ok. Looks like "tell me about yourself" implies different things in India and US. In India, what it means is summarize for me what have you have you been doing since you came into programming.
I never ask this question, simply because I never liked it being asked to me. I usually scan the resume and form my initial opinion. Then if I find something in the resume which interests me, I ask specific questions about that. Else I ask the candidate, which project s/he liked working best. I usually want to know, how the framework was, the piece the candidate worked on, the challenges faced and the solution implemented. I expect a high level analysis, not in technical terms. This tells me if the candidate can identify and analyze problems, logically come up with a solution and articulate about it.
I also always make it a point to find out more "extra curricular activities", if not mentioned in the resume. Does the candidate like to read? If yes, what type, who are the favorite authors? What kind of music. Sports? What does s/he like to do after office hours? I also make it a point to express an opposing opinion and observe how the candidate reacts.
Maneesh Godbole wrote:Ok. Looks like "tell me about yourself" implies different things in India and US. In India, what it means is summarize for me what have you have you been doing since you came into programming.
To me it's more like "I am 170 cm tall" or "I like black olives better than green olives" or something else from a ridiculously wide range of possibilities.
I don't see anything being wrong with this question. The interviewees can be nervous, and this will be a good ice breaker question to start the conversation. It can also help assess some of the non-technical skills
-- How well you can communicate?
-- Do you take pride in your past accomplishments?
-- How well you can communicate and summarize things?
Also, as a an interviewee, it gives you a great opportunity to summarize your strengths and what you are looking for in your next role.
Vishal Hegde wrote:I later on said in next 3 years i will be completing my java certification and working in a good IT firm
this answer definitely ticks off your boss ;)
Joined: Oct 13, 2005
Those are standard interview questions; “tell me about yourself” at the start of the interview and “where will you be in ten years’ time?” at the end. The latter is easier to answer; you say you hope to be a website architect/professor of IT/development manager/entrepreneur in a startup or whatever.
The former can be answered by something like, “somebody who likes writing lots of code and seeing it work”.
Another related question is, “What do you enjoy about [our field of work]?”
Vishal Hegde wrote: where do you see yourself in the next 3 years??
The question is about whether you have goals.
Is it necessary to define a goal??
I mean its like at night should i define goals for tommorw as of what I am going to do and not to do !!!
If i tend to define a goal as of from now on I will hit the Gym early Morning evryday , but not implement it ...then whats the point in defining a goal ?
Not sure why you are debating this. This type of question is kinda useless because it's a freebie. Just make up an answer, preferably one that shows your skills, your drive, your dedication, etc. etc. etc, then work it out with your friends (and/or colleagues) til its perfect, and finally, practice it til it sounds natural. And if this question ever comes up during an interview (which standard interview questions tend to do), you got a free setup to a very well written, and well rehearsed answer.
It's a freebie. Have an answer ready. It is certainly better than not having an answer.
And BTW, this is the reason why I never ask such a question....
Joined: May 31, 2007
In addition to being freebie, these types of open-ended questions give you a great opportunity to sell your self effectively. So, it is worth the effort to prepare prior to interviews as to what you are going to say.
-- Reflect back on your resume to see what you have done and how it fits in with the job sec
-- Research the organization, etc.