...As Ernest said, people lie in resumes, so I've got to find out what they know.
As to Java questions, if your friend has an SCJP, and the interviewer believes that, then questions about the language are unlikely, because that's what the exam is about.
As for the interviewer being prepared, well, it doesn't always work out. I try to read the resume beforehand and mark up the parts that I want to ask questions about. Usually I have the time, but not always. Which is not to say I'm not interested, or that my company is crappy because we don't even take time to read resumes of people we ask to come in. It's just that every once in a while something urgent comes up, and dealing with it is more important than preparing for an interview. After all, the candidate can tell me everything I should know about him in person (and score extra points by being eloquent about it). Most people who interview candidates do it too frequently to treat it as a super-special occasion that demand lots of preparation. Welcome to the real world
When one did not specify EJB and even CLEARLY says I did not work on EJB what makes it happy to dig into discussion on EJBs only.
You should respect the interviewers time and the company's interest in you, but at the same time, if they don't provide you with that same respect, don't work for them.
Originally posted by Ulf Dittmer:
Yes, you shouldn't talk about EJB in detail, but I would expect a candidate to know at least that much about EJB to be able talk about BMP vs. CMP, or the differences between the various types of EJBs.
oh so you use Hibernate framework ?
So originally the interviewee was asked about themselves. The level of the answer you mentioned is at that high level - I worked at ABC, moved to DEF ... So the interviewer has an idea about where the interviewee has been but may (or may not) have an idea about the interviewee themselves - what their interests are, what they do.
Interviewer : Tell me about your self
My friend: I'm XYZ... started my career with abc then moved to DEF and has been working with ABC company... blah blah blah.
Interviewer : ok so what do you do at ABC
[ABC is well known company which is known even to a 5th standard kid. What I do, I already told you in my above statement. Why the hell you are asking this]
My friend: sir, we are into product development.
Again, I don't have a problem with this sort of question at this stage (although I personally would not come back to it at a later stage of the interview).
Interviewer : ok. So you are working on Financial domain right, so what is Money laundering and how do you perform Anti money laundering
[Hey man ! did you first of all see my project before asking that question]My friend: Sir, I did not work on Anti-money laundering functionality. Our project has retail banking functionality
I would assume that your friend mentioned a view in their project. As has been mentioned earlier, interviewers like to know whether the interviewee actually has knowledge or whether they are using buzzwords. A common technique is to drill down on a specific area that an interviewee has said they worked on.
Interviewer : Anyway, what is a "View"
My friend: ok if you are speaking about the database ?
Interviewer : No no I'm not speaking about the database.I'm asking what is a "View"
My friend: ok so you are asking about the view in MVC pattern
Interviewer : No no I'm speaking about View in your project
My friend: My project contains blah blah blah .... went on explaing the whole project really irritated this time and felt like abusing
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton