4 ms·

A skill someone used 10+ years ago but not since probably has little to no relevance in an interview. I was doing Java in 1995, don't ask me about it now tho'..

• vonmoltke 9y ago
  That is highly dependent on the skill. I haven't troubleshot a circuit board (much) since 2006, but if you put me in front of one with a schematic and some test equipment I sure as hell could do it again right now. I haven't written signal processing code since 2012, but I could jump right back into that as well. Not all skills and experiences wither at the same rate. This industry has a bad habit of assuming all skills last about as long as your average JavaScript framework. I'm sick of being typecast based on what I have been doing for the past few years.
• daok 9y ago
  I tend to like to see more information that is more recent but is also interesting to see the journey of someone. You can get something interesting by knowing that someone is able to switch language without problem or maybe this person is more the type that doesn't change at all. It's also great to see a long track of achievements even if it's been 15 years. Again, information like knowing that someone has been doing technical positions for x amount of year and now is more in a leadership position can give a good idea where the person is moving and what he still could do or understand but has changed in term of priority. Again, every resume should filter the content as its age but someone in the industry for 30 years shouldn't fit everything on 2 pages in my opinion.