My Skill Matrix

If you are a regular reader of my blog, you probably have some idea about my skill matrix. If not, why not? Hmm? Photography, as it is easy to see, does not belong in my skill matrix. I just made a new header image, but I think it still needs improvement. Maybe I should add more light with an extra lamp.

My skills summary

The list of skills I have listed in LinkedIn is a veritable random hodgepodge. If I had to do it over again, I think I would have consulted with a career coach. I don’t want to pin myself to a certain profession, but I wouldn’t mind calling myself a software developer and technical books author.

LinkedIn imposes a limit of fifty skills and doesn’t allow you to define a dynamic list. What you would like to do is create a matrix, that is customized to the type of position you are looking for. It would be nice if you could indicate, when you first started using a skill, where, when you used this skill last and for how long. Which means that you need some kind of calendar, so that you can easily indicate – okay I used this skill this month or not. For instance, I think sometimes I don’t use XML for months and then there is a period that I do nothing but work with XML. Maybe not the best example.

Some skills don’t make me really proud. For example, Scrum and Agile. But you seem to need them listed, just to keep up appearances. I don’t have Pandas listed either and I hope I don’t have to. Also I decided that my NumPy, SciPy and Matplotlib skills are so obvious, that I don’t even have to mention them. I must have picked up some random knowledge too related to the businesses, where I worked, like bond calculations and financial instrument classification. If I listed the things I learned, when I studied Physics, then the matrix would become completely unmanageable. LinkedIn also has a Languages section, but that doesn’t appear to be very important, since English is enough for most business communication.

The skill matrix

A comment about soft skills first. If you need them, you are doing it wrong. Of course, you could go completely crazy and define all kinds of parameters for the matrix, but it seemed best to keep the number of a parameter to a minimum – knowledge and competence level with a score between 1 and 5:

  1. Beginner with academic or book knowledge.
  2. Experience in the real world.
  3. Comfortable to use the skill independently.
  4. Advanced.
  5. Expert.

I have to warn  you that this matrix was compiled without much effort so there was a bit of bluffing, posturing and guessing involved. I wanted to say ballparking, but apparently that involves hitting people over the head with raw hotdogs, so not appropriate in this case.

 

CategorySkillCompetence level
Operating systemsUnix3
Windows3
DatabasesOracle2
Sybase2
DB22
PostgresQL2
MySQL3
ScriptingUnix Shell3
Python5
Perl2
NetworkTCP/ IP2
ProgrammingJava5
C2
C++2
C#1
Fortran1
OtherSVN3
XML3
SQL4
Quality Assurance3
Technical Writing5
OOP5

This was the short version. I could have added some more comments and relevant information, but I forgot.


Cython, Map Visualizations and Brain Implants

http://storify.com/inningPalmer/cython-map-visualizations-and-brain-implants

 

By the author of NumPy Beginner's Guide, NumPy Cookbook and Instant Pygame. If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.
Share
This entry was posted in Uncategorized. Bookmark the permalink.