Worth putting knowledge of/skills in Virtual PC/Virtualization software on CV?

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

I was wondering whether it would be worth adding to my CV that I've developed skills in using Microsoft Virtual PC, Virtual Box and other virtualization software?

Your thoughts?

 

No, I meant using it on my own home PC.

 

No I was just wondering, that's all.

 

yes if your confident with the software/technology then it can't do any harm.

 

Yes never put it under previous job roles as then they will take it as commercial experience. I tend to put things I have non commercial experience in under other skills but to be fair removed it not long ago as I closed the gap on everything on that list with commercial experience.

 

If you're looking to pad your CV, you might list it as "Familiar with virtualization technologies, including Microsoft Virtual PC and Virtual Box", but not "Experienced with virtualization technologies, including Microsoft Virtual PC and Virtual Box." One implies that you have studied about it and worked with it in a lab environment... the other implies that you have experience in a production environment with the technology.

 

Disagree with that as commercial experience isn't the only kind of experience.

 

It's the only kind of experience that most employers consider as "experience". Setting up stuff on your home lab gives you knowledge... but it's not the same as doing it in a production environment, and employers realize that.

Go ahead and put "experienced" on your CV... but that'll be a big red flag when employers discover that you don't have real-world business IT experience with it.

 

The difference is that in production you have to act responsibly as there's no place for mistakes. Everything needs to work and there's no place for downtime. If you mess something up in a lab you can wipe it out and start from scratch. This isn't possible in production.

I think that is one of the reasons why lab experience isn't considered as experience by employers. They want someone who can do something in production and not in the home lab.

 

Chances are you will gain more knowledge from a lab than production environment for that exact reason that you can't mess around with a live system. All I'm saying is that commercial experience isn't the only type of experience. I learned more about Exchange in my home lab than the 2 years I've had access to Exchange in a working environment. Whilst I wouldn't put it down as having commercial experience on his CV I would put it under an other skills section on his CV as still having experience. That way the employer isn't under any illusion he has commercial experience.

 

So your trying to tell me your company allows you to install Exchange when you want, dismount databases, delete and migrate them and other things that otherwise would disrupt the functionality of Exchange if so lucky you.

 

Yes I did for the simple fact that if I messed around with a live system just so I could see what this setting did and what that button did and brought the system down I would of been sacked. I personally think you learn more from home labs as you have the freedom to do and break what you want. Also for the example of Exchange it was already setup so I didn't get to really set it up at work or drill into the settings but did using my home lab so yes I did learn more.