views:

331

answers:

3

Many times interviewer asked me following question:

How much you rate yourself in core java out of ten?
How much you rate yourself in web application out of ten?

Java is a popular language and having huge set of API. I am a web developer. But, there are many parts in core java which i never or least used e.g. file handling, RMI, Socket Programming. In real scenario, i use only 10-20% of API. If i rate myself 5 out of 10 in core java because there are lots of things i have to explore. 5 out of 10 makes bad impression to interviewer. The interviewer expect atleast 7 out of 10. Then they expect me to define the real scenario where i have used file handling, RMI.

What are the parameter on which i rate myself for the expertise in a programming knowledge?

+9  A: 

Interviewers are not looking for a numeric value to plug into some magic formula for their hiring machine...

Instead this type of question is a way of asserting the interviewee's general confidence, his/her honesty, his/her awareness of the domain in question and even his/her fondness for the underlying language/technology.

A short response similar to the one provided in the question is probably a good starting point for good (and hopefully honest) response.

Although some of the interviewers, in particular these for a first round / pre-qualifying type of interview, may not be well versed in any particular technology, they generally understand the difficulty of attaining "Expert" level in very many different disciplines. So while one may think of boosting one's self-assessed "rating", he/she may soon be seen as overly confident, with too many high ratings in too many disciplines; this is of course particularly true of younger, junior candidates (who even if gifted, would not have had the time to because so well versed in so many areas).

As pointed by Adeel, another risk with one's self evaluating towards the expert range is to prompt the interviewer to follow up with trick questions aimed at confirming the claim. By over-rating oneself, one doesn't only risk being seen as dishonest, but also as effectively unaware of the complexity and depth of the underlying domain.

mjv
i think another purpose of asking this is once you told that you are 8 out of 10 in java, than they will question and try to validate your claim. if you say 9, they will ask difficult question to validate this:)
Adeel
@Adeel: Good point, higher self evaluation ratings call for trick questions, in a attempt to catch the candidate in a "lie" (well, in a difficult situation, which is yet another "test": "Hum... I caught him/her in being overly cocky, let see how [gracefully, smartly, confidently] he/she handles this.
mjv
@mjv: "A short response similar to the one provided in the question is probably a good starting point for good (and hopefully honest) response." This is what i am going to do next time whenever interviewer ask me the proficiency. Thanks mjv..
Shashi Bhushan
+1. Definitely. Honesty is the best policy. If you're great at Java, but know there are corners of the API you've never used, you should just say that. It's a meaningful response. Employers are usually just trying to see if you're a good fit for the role, not usually just to see if you're honest (although the latter can be a small part of it). Giving a slightly longer, frank response addresses both of the employer's needs.
quixoto
+1  A: 

File handling is a must, sockets are very niche (haven't touched them since my uni days). Knowing the API is important, without that knowledge you'll just keep reinventing the wheel, which is time-consuming and error prone.

CurtainDog
+2  A: 

I agree with @mjv's answer. Additionally I use a question like this all the time. I don't care about the number I care about your reasons behind the number and your ability to be self critical and be honest. It is a vagues scale anyway so I'm not too worried if someone is off by a one. Don't go too low either! Looks like you are low balling then.

I have also been asked the question before. One time I think I said a 7 and the interviewer didn't do a good job following up on that. They asked me questions that seemed to be more at a 3 level. That, among other things, made me decide I did not want that job. So the question works both ways.

Mike Two