Discussion Locked

Experience redefined

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Why do companies in search of IT professional base "experience" on the amount of time an applicant has worked in the industry rather than his or her knowledge and skills? In my current situation, the company I work for is undergoing staffing changesand one of the issues I have a problem with is the new job title and compensation package. Under the new format, Engineers and Sr. Engineers are placed not by their knowledge and skills but by the length of time, they have been in the industry. I have experienced this not only with my current employer but when conducting job searches. I do not foresee any opportunity to change to current situation so what steps can I take to overcome the 5 year curse when search for new employment?

9 replies

by ruwon

Any idiot can read a textbook and pass these tests. That doesn't mean you can solve problems. No matter what classes you go to they are nothing compared to real world experiance. I have no official training whatsoever but I teach NAIT grads how to do the job Properly.

by ippacket

Well Ruwon, to point I agree with you, there are those that are not worth the paper. There is more than just paper here, 43 servers (running 3 OS?s), 80 + switches and routers, and over 2000 client nodes spanning 13 states. Resolving over 1000 levelII and III tickets a year, I have experience.
This is a legitimate question. You may be well versed in your field and so am I. By your logic, you should have an answer to this one. Why within the first week of employment a ?Sr. Engineer? asks a Desktop Tech how to access user manager on a remote machine? Then a year later he is ?getting the hang of this WINS stuff? after he discovers he is able to delete entries. That is from a 6-year veteran. How many do you have? If it is about six can I assume you are at the same skill level or should I base it on the merit of an individual?

My concern is with hiring practices. I am looking for a real answer with insight for someone without a chip.

by it tech

Longevity in the field is a big plus due to trouble shooting skill. Which IMHO is 98% of the job. The school and certs help (I myself don't have a cert one but do have 20+ year OJT). Like the Sr Engineer I have not worked much with VPN and less with WINS (like DNS better)on internal or external networks. But when I look at some one I like the time in the industry better than the papers he/she has because I will not receive as many call on HOW DO I FIX THIS, the exp of the person with a lot of time in the industry, will come with trouble shooting skill learned in the field. So I look for 4+ years of exp, when looking at new people. Oh ya 137 servers in my local and 6500 workstations 3 crays and more switches, printers and such than youcan shake a stick at.

by ruwon

Your employer is not only looking for the skills. Skills are important. Experiance is more important. But the absolute most important thing to any employer is knowing if you will be at work on time and every day. It doesn't matter what skills orcerts you have if you can't be bothered to show up to work on time. Or if you happen to be sick (insert maximum number of sick days here) every year. Most employers will take a less skilled but relaiable person over a more skilled one who has yet to prove that he can be trusted. That is why "Real World" experiance is so important to employers.

by schitzoid

The problem is that most people in charge of hiring don't have a clue themselves about the job they're hiring for, so the only yard stick they have to measure with is how long you can hold a job without getting fired. There's not much you can do to change that. And who cares what your job title is if you're getting the pay you want? When you're talking to prospective employes, be sure to stress your level of expertise without sounding like an arrogant newby.

by e-fellow

Proven, employer testifiable experience is king, paper proof is queen, paper certs are as good as the paper, talk is cheap and arrogance is crap.

So if you are a king married to a queen with a marriage certificate and good communication skills, and no crap,,, then you are tops.

by darpaicq

Good question. I think most companies want the most 'able' (knowledgable and skilled) and 'willing' (motivated). It's very difficult trying to judge the degree to which a person is 'knowledgable, skilled, and motivated'. Therefore the people who make the rules, non technical upper mgt types, use 'indicators' like experience, degrees, certs, etc. If you are seeking employment, sell your skills and accomplishments if that is your strong suit. If you need to grade peoples skill level, spend the time and do a thorough analysis (give tests, analyze past performance, etc).

by afong

It's human nature to take the easiest route. It's a lot easier for a manager to look at the years of experience and come to conclusion that "X number of years = X job level" than it is conduct an interview and get a more accurate picture of the employee's skills.

Since it's hard (to almost impossible) to change people, you'll have a better chance if you try to work within the culture first and seek changes later. For example, let management know you're building experience (spending time inthe position) and knowledge. Start showing them that your knowledge can increase faster than your experience. They won't come and ask you how good you are. You have to show them little by little. Eventually, they start to see the fallacy in their equation of "X years = X level."

by workinonit!

Just because I took a Visual Basic class three years ago, and I mess around with it every so often, doesn't meant that I can be a VB Programmer. I know people who have the same skill level (virtually non-existent) as I do in VB that put "Three years of experience in VB Programming" on their resume. HR managers have require some kind of proof (such as certification) along with the claim of experience. What's worse, a potential employer could call here and ask my boss if I have done VB Programming for three years, and she wouldn't be able to say whether or not I did. She doesn't really know.

This discussion is closed to new replies.