Slashdot Mirror
Which IT Certifications for Specific IT Jobs?
outlander78 asks: "There have been several questions posted recently (Landing a job, College or Career? to list a few) discussing education and job searching. I have just completed a BSc Computer Science, and have 2 years of co-op experience. This is apparently not enough, as I have yet to get a single interview, despite many carefully written letters and resume submissions to job postings. I read here that a degree with certifications was a good combination, so now I need to know - which certifications are best for job seekers? Whether I work as programmer, sys admin or something else isn't an issue, since I need any job at this point, and enjoy most computer-related jobs - please, suggest whatever certifications you are hiring for or were hired because of."
The supply of tech professionals for operations, non-development, is far outpaced by the demand. Right now it is simply a buyer's market. What does that mean for folks who hire:
1) We can demand experience. We don't have to take the time to train someone and get them up to speed.
2) We don't have to offer the salaries and benefits we did two years ago.
3) Certifications aren't as valuable as they once were. The last boom in certifications was the Cisco program and that has stagnated as the technology and programs have become entrenched. It's all cyclical with certification programs anyway. You have to be in at the beginning to reap the benefits.
The other fact you need to face is the best way to secure employment is not through classifieds and monster.com, but personal contact with people in the field. Join user groups, go to vendor tech demos and start meeting people.
Good luck.
get an interview but will not get you a job. The answer to your question is that you need certs for which you have experience and which you can back up with knowledge that goes above and beyond what is needed to get the cert. Also you need to know who is hiring in your area. For example to get my current job I had a lot of experience with firewalls in general and I know a firm in my area which has *very* good reasons to be paranoid where hiring a networking guy. I also have a bunch of networking experience. I found out through a friend that they use Checkpoint based firewalls. So I downloaded a Checkpoint demo got a book spent some time on it and got a CCSA. Combined with my background that set me apart from the crowd enough to get the job. :) Do your homework and try to do something you have a good background in and it should work. Also just a note a good recuriter is worth their weight in gold. Many will say I'm wrong and YMMV but recuriters have worked wonders for me.
Cypherpunks: Civil Liberty Through Complex Mathematics. Those who live by the sword die by the arrow.
Your real problem is that the economy is in the tank, so you are competing with people with at least as much education and more experience. This happened to me back in '91 when I finished by B.S.
Keep at it, you'll find something eventually.
I'm getting very tired of certifications. I know too many "certified" people who have NO EXPERIENCE! They know all about how it's supposed to work, but can't fix it when it breaks. I'm tired of it! Get me somebody who has a true interest in computing, not just paper credentials and making money.
Ouch! The truth hurts!
To the extent that certifications act as a marker for a person's curosity, desire to learn, and humbleness in the face of the unknown, I will take them into account. However, I would rather have an English Lit major with zero technical background who can solve an unfamiliar problem from scratch than a 3 month/employer guy with a bag full of paper certifications.
To the extent that I consider certifications at all, I will look in order at Cisco certs (past the CNA), Novell CNE or Master CNE, Pine Mountain Group network analyst certs, a broad background in Unix, and of course any professional engineer certs.
But for what kind of job, you ask? Remember, I don't match up specific certs to my current position needs. I have never seen a person with a deep knowledge of Netware have any problem picking up what he needs to know about NT, but I have certainly seen the person with 38 Microsoft certs be unable to figure out how to configure a 2-router Cisco network.
My 0.02.
sPh
Or did somebody change the date for the monthly /.?
'which cert' question on
Anonymous posts are filtered.
Is that the big bulletin board with the pictures of people and things from the CS department? ;-)
T
---- It puts the lotion on its skin or else it gets the hose again. It does this whenever it's told.
To tell you the truth, you need to go out and market yourself. Listen to what I did. I worked for a company that Cisco Systems outsourced to making 10 bucks an hour. The waiting list was about 1 yr to get on a tech team. All I did was route calls for so-called IT professionals.
Most of the calls I took the pros on the other end were less knowledgable than me on many subjects. I was so sick of doing it that I started sending out resumes to those companies. NO LUCK. They didn't care if I knew more or had more certs. They didn't even want to see me.
I went out and started up a small business in my neighborhood about a year ago, just fixing computers and doing home networking. That got my foot in the door. I went on the street hawking my wares to small offices, law offices, insurance agents, real estate offices and so forth.
Word got around and I got a couple of support contracts with med-sized businesses doing sys admin on their boxes. Real simple stuff that anyone could do. It's called comparative advantage. Now I've got a couple of contracts, and I'm negotiating a contract with a local general contractor to pull cable for new construction at 2500 a house. I have a pager and a cell and I make my own hours.
By the way--I'm 25 with 2yrs of college education. Comp Sci is not my major, nor ever was. But this helps with school a lot, and I have a family to feed. The only certs I have are A+ and my CCNA. I don't plan on doing this beyond graduation, but it's always a handy thing to have on your resume.
One last warning and advice. Warning. Insure yourself for about 1,000,000 per claim: the more certs and education you have, the cheaper insurance is. I pay about 2000/yr on prof. liability. Advice, join a professional association. You can network a lot and land tons of gigs. It worked for me.
http://cincyboys.blogspot.com/ Everything Cincinnati. Including the word 'Finnih'
A BSc in Comp. Sci. and some co-op experience sounds more than enough to get your foot in the door (entry-level). Are you sure you are applying for the appropriate job? Perhaps you'll need to start lower than you want due to the sluggish economy? Since you are willing to work at any job, I would make sure that you aren't overlooking some of the lower end work (for the time being anyway) -- sys admin hopefully requires more experience than you have :) Likewise, look for "junior" positions as well. Look at non-tech companies that have tech needs (banks and insurance and investment companies for example).
:) of demonstrating over time that they are keeping pace with current technologies.
I don't think certificates early in one's career are that beneficial since it starts looking like you are just too obviously trying to make up for lack of real-world experience by overloading your resume with these certificates. Certificates, in my opinion, are good ways for senior practicioners (i.e. those over 25
Also, some people may use certificates to help with transitioning from a different career into tech (since going back to school is not an option).
My opinion: don't worry about the certificate issue and start doing a broader search for entry level tech positions.
** Also, it is hard for anyone to know WHY you didn't get an interview if we don't know exactly what your resume and cover letter contain and for what position you applied. You may just have a goofy sounding cover letter or weak resume.
Worse comes to worse, you can always do tech sales (I guarantee you can get a job there) -- man that phone boy!!!
To quote a CNN article:
"the most talented student will always have options."
Right now, the market is tight for programmers. This is no longer the field that anyone can get a degree in and automatically make 60K+ out of school. So, if you just got the degree because it was the hot thing to do, then your screwed.
If you really have a passion for computers though, then you will find that the market is still there. You just need to seperate yourself from everyone else. Forget certifications, that shows little self-direction, instead why don't you spend that effort developing a piece of open source software.
Write a piece of useful software that showcases your skills. Given the ability most folks have right out of college, this will definitely show that your worth hiring.
Or, if you can, take some time to really strengthen your skills. Companies are always hiring *good* programmers, regardless of the economy. Taking 6 months to study all the industry bibles (the GoF book, the Myers books, etc.) and learn the stuff that is actually useful in the real world. Do this instead of putzing around for 6 months looking at getting certs or drinking every night and you'll land a good job.
int func(int a);
func((b += 3, b));
As much as it sucks, certs aren't the answer. Speaking with a hea dhunter recently he did say companies care much more about certs now than they did a year ago - but that is because they can. There is a fairly large, experienced pool of talent out there.
Getting certs, however, is a very expensive proposition for osmeone currently unemployed. A typical test can now cost aroun $500, so accumulating a list of certs is not really an option.
Deciding WHAT you want to do is the first step. You might consider doing anything if the opportunity comes along, but in terms of getting certs you need ot focus more (unless you have more moneyt than you know what to do with, in which case why do you need a job so bad?). This means, yes, making a decision about your future. Youare free ot change it down the line, but you do have to choose - sysadmin/netadmin, development, dba, etc
After you figure what you want get experience doing it. The portfolio is becoming a tool of the unemployed developer. Showing first rate code that you have written, along with unit tests, use cases/user stories, UML diagrams etc make syou look better. Really, if you have littl eprofessional experience it is the best thing you can do to look good for a "walk in" interview.
Choose the direction you would like to steer and start a project, or get in on a starting project. Don't dive into an established open-source project. They might appreciate the help, but your goal here is to have somethign to show that YOU can claim 100% credit for. Comntributing bug fixes to gcc won't do that for you, though it might feel good.
The seoncd thing is become involved in the local development community. You might laugh, but this is possible. Hit Yahoo Group and search for any group in your area related for what you are doing. Make an emeail account that can accumulate spam, and sign up. Talk to people. Networking (people, not CCNA) is still the best way to find a job, period.
Only then, consider getting a cert or two. The ones I have seen being respected are the Sun Java developer certs (okay, JCP is sorta laughable, but the larger ones get nods), Cisco certs are respected, and Oracle certs are respected. Certs are no substitute for experience, unfortunately. Human resources may not realize this, but the hiring manager will.
FInally, find someone who IS a professional developer, who has undergone many code reviews, who knows how the system works in a decent shop and ask if they will review your code and designs. Buy them beer, coffee, crack, whatever it takes. When it comes down to the decision - your skill will determine your success. THis includes skill in talking the talk - and the only way to do that correctly is to really learn it. Most good developers are willing to help new people, it is flattering. There are various systems to try to make this easier via the net. In my experience these are not nearly as good as meeting someone via the aforementioned networking and offering to buy them a beer in exchange for picking their brain. While buying em a beer, slip in that you would really like if they could do somehting like a formal code review of your stuff - afterall, it is the only way to really improve.
Finally, read lots of code. Figure out how it works. Look at systems and make sur eyou understand em. A *great*, though boring as hell, way to do this is to write API docs for good projects. Do not contribute directly to them yet - your time is better spent building things you can claim redit for. Let's say you are into Java development, run by the Apache project and submit improved API docs. No one likes writing em, but to do it well you NEED to understand what the code does.
That, and know that you have my sympathies. The hiring market sucks right now.
-Frums
I expect a lot of people will weigh in on certifications, and the arguments for and against are pretty widely known. Here is what I understand:
1)the vendor certifications (Microsoft, Oracle, etc) have some marketability, but the courses and related material are overpriced. So are the predictions of median incomes that certified people enjoy.
2)it is impossible for certifications to measure the ability to program, to think creatively or to solve problems. However, they do measure in a rough way one's familiarity with an application/OS's mechanisms to accomplish tasks.
3)Aside from Microsoft, Oracle and Cisco, employers have usually never heard of
the certification you have.
4) Employers are impressed about certifications when it is hard to measure competence. It is a third-party objective criteria. What impresses them is that you took the initiative, that you had to study for some test. That's different from just sitting at a seminar and passively absorbing information.
5). Despite what people say, "paper certifications" and "paper mills" are not worthless. The problem with IT institutes is that no training program can cover the variety of problems and administrative functions that one encounters on the job. On the other hand, they do a good job of exposing you to some of the basic tasks.
6)The problem with "paper certifications" (especially vendor-sponsored ones) is that to pass them you need to learn skills specific to the application or OS. That puts the onus of chasing after skills (and paying for them) entirely on the job seeker. And surely by the time you pass one certification, you'll hear about another one that is the next best thing. You need to ask yourself, "why I am spending time immersing myself in vendor-specific information when I should be learning more general things: protocols, network architecture and programming theory and algorithms.
7)Certifications do matter in my own field: technical writing and training. They indicate some familiarity with a particular domain of learning.
8)If you seek a certification, seek it only because you find the subject in and of itself to be interesting. I sought the LPI 1 certification because I needed to know these concepts anyway and the certification provided a structure and path for learning the material. Right now, I am pursuing another certification, the Master CIW Administrator
certification. I'm not sure employers will even know what this certification is, but I know that the subjects on the certifications: network security, ip6 and unix/windows interoperability are things I would be learning anyway.
9)If you do seek certification, don't spend more than $100 on study material. There are hundreds of sites and forums that provide good study guides and practice tests for free. You'll also enjoy sharing in the learning and studying experience. My favorite is Exam Notes
Robert Nagle, Idiotprogrammer, Houston
SAGE, the Systems Administrators Guild has a junior-to-mid-level professional certification for systems administrators now, called cSAGE.
Unlike vendor/product certifications, this cert is designed to assess your ability to perform in an IT role -- namely, systems administrator -- rather than your ability to memorize features and functions of a particular product. It tests troubleshooting skill, background knowledge of process and procedure, and general junior-to-mid-level sysadmin proficiency, both in general and specific to Unix (they're working on a Windows module and several other, higher-level "merit badge" modules).
.@.
(emphasis added by me)
(and so on)
Perhaps while you're at college, you might consider taking some non-Engineering courses. Learn to spell, use proper grammar. Become a well-rounded individual. Learn to communicate concepts and ideas effectively. From all indications, while you may be one of those "people that do know computers for real," you're not a very appealing employment candidate due to your poor communication skills. Then again, I'm not quite sure what you mean by "know computers for real," since if you're not getting good grades in your CS classes, how much can you really know about CS? (Computer Science != just computers. there's a metric pantload of theory and algorithms to learn. It doesn't matter if you're the fastest linux installer in the West, if you don't learn that theory you'll never be able to call yourself a Computer Scientist, regardless of what your degree eventually says.)
College is about more than just hunkering down and focusing strictly on your one chosen subject. Sure, there's a time and place for that, but as long as you're going to be there for 4+ years (milk another year or two out of the parents while the economy's in the pooper), you may as well take some time and attend some interesting classes that will grow your knowledge in other directions than just computers computers computers.
No, no, no, no, no.
Must
Consult
Someone
Experienced