When I get interviews for jobs, there's typically 1 language/tool out of the job requirements that i don't have professional experience working with. Languages such as Java, C, Visual and Basic, tools such as Nant and protocols such as HTTP/HTTPS, DNS, SMTP are technologies that are familiar but not too experienced.
I'm tired of saying that "I am familiar with X technology". Is there a better way to say I don't have a particular skill?
You could describe how good and quick you are at learning. E.g. "I learned the basics of RoR in 3 days."
If using this technique, make sure it is related to the original item - don't say "I learned Vi in only 4 years" when the company makes Visual Studio add-ins. Instead, try showing your experience in Eclipse or #develop, for example.
Yes. Say, "I don't have that particular skill". Then elaborate, saying, for instance, "I read all the articles about it, but I've never used it professionally". Or, "Really? How do you use that here? I've always thought it was too slow".
Whatever the truth is, say it. Sometimes the truth will be good enough. But a lie will never be good enough.
Try saying "I don't work with the Devil's tools/languages."
If it applies, I would say something along the lines of this:
I have worked with X and X in the past. I currently have not used X in a professional environment, however, I have read up on X and am confident I could pick it up quickly when the need arises.
This generally works if you have a solid grasp of programming fundamentals (say lots of experience in C++) and the job says Java or something generally similar and/or possibly equivalent. Instances where this won't work if the job requires experience in a certain area you've never worked with.
Say something like "Oh yeah, I have always wanted to learn that!!" and go on about some of the things you like about it, etc.
Don't sugar coat it at all. That will be trouble later when they decide that you are not an honest person.
Be honest about it.
See if you have experience that is similar.
Your best course is to emphasize your ability to learn and adapt to new technology quickly. If possible, back that up with examples of your other knowledge, transcripts of coursework and other learning and how you applied it.
Be blunt, if the company you're trying to get hired/contracted for can't understand that our skill as developers doesn't lie in the impossibility of knowing about every single technology out there but in our ability to pick up new technologies quickly, you don't want to work there.
In fact, explain that to them. Tell them you recognize that you are unable to learn everything so what you concentrate on is learning the principles on which everything is based. If you know the basics of IP then it's not too difficult to understand how TCP works. If you know how TCP works you can understand HTTP. If you understand HTTP you can understand Web Services. If you understand Web Services you can understand AJAX. So on and so forth.
Just be honest. In general an experienced developer can pick up a new skill without too much trouble, especially if you have experience with many related technologies.
On the other hand, if the same tool/language keeps coming up, maybe that is a good indication you ought to pick it up :)
You have to be honest, but you can certainly say I've been using X for a personal project and used these methods and you picked it up in a few days.
Another good thing to say is 'I'm reading Using X for Y by respected Author Z to learn X'
There may not be an easy way to say it, but it needs to be said. Don't ever try to BS your way through, because you will eventually be found out, and things will be much worse.
Be honest: "I don't have much practical experience with <<product x>>, but I've done some personal projects, and I'm a quick learner.
Most interviewers want to see that you have the basics, the ability to learn new things, the ability to solve problems, etc. A new language or technology is just sugar-coating. If you have a solid foundation, you can always learn new tricks.
Many jobs I see throw everything, including the kitchen sink, in the job requirements. In my experience most of the time only a few of those are actually used.
If you don't have experience it is best to admit that. If they really need someone experienced in that area, and you get the job it will become pretty obvious you don't have experience. If it was just thrown in there then they won't care.
You should always remember it is ok to say, "I don't know." You don't have to have an answer for everything. I have known a few interviewers who actually ask questions that they don't expect the person to know to see if they will admit they don't know the answer. It is very painful to sit there watching an interviewee squirm to come up with something besides "I don't know."
When asked questions that you don't know about admit you don't, then steer the interview to the most applicable experience you have.
I have found that if you are careful you can manipulate the course of the interview to showcase your strengths.
Personally I always treat "familiarity with X" as a red flag in CVs. It usually means "I've heard of it, but I'm going to try to make you think I've done more."
If it's a technology that's really relevant to your job, read up on it, experiment with it, and put it down as "investigated technology X" or something. Otherwise, be prepared to accept that either:
Or - Experience isn't critical, the interviewer will know this, and just wants to see if you have an "extra".
Willingness and ability to learn is important. In my experience, candidates who can't admit they don't know something, usually can't learn it either (as they daren't ask the necessary questions)
Familiarity with equivalent or related technologies will also stand you in good stead.
I've had good luck with the honesty route too. As painful as it is to admit that you don't know X or Y or sometimes even Z; few things indicates an honest personality like being honest when it hurts your chances to get something you want.
I will admit that I was once (that I know of) removed from consideration for a job because I wasn't familiar with a Java framework and I was honest about it. But, I felt better when I looked up the framework afterwards and found out that the only way to have five years of experience with it was to have been one of the framework developers.