Can I write about design patterns in my resume?
If you write it on your resume, be prepared to discuss it. If you aren't ready to have a technical discussion on the subject, don't put it on your resume. Generally, the questions start off general and broad
Anyways, what i am asking is. do the people who come to on-campus placements for taking interviews have any knowledge about design patterns
Any good software engineer should know, at a minimum, what design patterns are, their purpose, and a subset of patterns from their domain (enterprise patterns, concurrent patterns, and so on). I would assume that any technical interviewer would have this knowledge.
Though I think that would impress the interviewer if i am able to defend his questions but, on the other hand I think there can be three points I am worried about: 1. He might ask too deep questions to show me that I have written a wrong point. 2. He might not know about design patterns. 3. Besides he may ask of design patterns that are not in Head First. 4. he bounces on J2EE design patterns, which I am afraid to study right now.
I would hope the interviewer understands your current skill level and experience. Just because you have a professional interest in something doesn't mean you know everything about it. To me, it indicates that you have gone above-and-beyond and taught yourself at least something about the topic, but not that you are an expert.
If you can't have an intelligent, cohesive conversation about something on your resume, that's a huge mark off, I think. But you also can't be afraid to let them know exactly how much you know and that you know what you don't know. I, personally, wouldn't expect you to know everything, especially as a student or early in your career. I would expect you to have read the seminal texts on the subject and be prepared to have a cohesive, fairly detailed conversation on an appropriate level.
I, personally, wouldn't expect you to know everything, especially as a student or early in your career. In your example of design patterns, you should be able to discuss things such as the applicability, trade-offs, and general structure of at least some of the GoF patterns before I would consider you knowledable in the subject. I would also anticipate that you have applied at least some of these patterns appropriately in projects that you have worked on.
As an aside, age and experience have little to do with professional interests. I've stunned interviewers when I tell them that I'm interested in process management and improvement, project management, software quality, and measurements/metrics, and then have gone on to have fairly length discussions on these topics. Very few young software engineers and recent college graduates are interested in these topics - many just want to design and write code.