tuoply
Active Member
This is a catch-22 though. If it's directly related to your job, you're admitting you're underqualified. If it's not related to your job, then who cares?
I'd like to sharpen and focus my game programming skills so I can get out of web application programming. I'd like to expand my encyclopedic knowledge of design patterns and standard algorithms. I'd like to have a greater knowledge of all the cutting-edge technologies that keep emerging. But I'm sure as hell not going to use any of those in an interview. The first suggests I'm unsatisfied with my career path; the next two say I'm underprepared; the last one says I don't keep up.
I disagree. I'd prefer to have a candidate that can reflect on themselves, rather than someone who thinks that they know everything. If you can demonstrate the aptitude to learn, I'd rather know that. Rarely will you have a candidate that fits the job criteria 100%. Sure, core skills are important, but it's the intangibles beyond the guy who can put his head down and churn out code that is important to *my* organization.
For those things that you'd like to improve, why do you want to improve them? That'd be my response to you if you said that they were growth areas. If your response was to get out of web programming, I'd want to know why you'd want to get out of there... I would want to put you in a position that you want to work at, rather than one where you're not going to be happy. That doesn't help either of us...