Slashdot Mirror
Marketing Yourself as an IT Jack-of-All-Trades?
ultimatemonty asks: "As an IT professional looking for a new job, I'm trying to figure out how to market myself as a 'jack-of-all-trades' IT worker. I'm currently employed at a medium sized university as a video conferencing specialist. I'm good (competent) at many IT related tasks (Linux server management, programming, Windows/Linux desktop support, video conferencing support, etc...), but specialize or excel in none of them, sort of like the lone IT manager in a small shop. What kinds of jobs would the you look for with this kind of work experience, and how would you market yourself (design your resume, cover letter, and so forth) to prospective employers so they get the full-breadth of your capabilities, without over-stating your abilities?"
as a generalist, you could qualify as "sysadmin" at a smaller shop, which because of their IT budget, usually means "guy that knows how to do everything for us". I'd emphasize creative problem-solving abilities and a drive to arrive at good solutions quickly.
Of course, you'll want to avoid coming off too arrogant -- no one wants to hire an I.T. jackass-of-all-trades, but we all know a few!
stuff |
I found myself in a similar situation, and found a place that suits me perfectly. It's a small development shop. I'd definitely recommend trying to find a smaller company; the smaller, the more freedom you have to use all your skills. Seems the larger the company, the more specialized they believe their IT folks need to be. The smaller, the less particular jobs are a specific person's responsibility. Just my two cents.
"Actually, I enjoyed this in the same vague, horrible way I enjoyed the A-Team" P. Opus
While I find a Jack of all trades very useful myself, and consider myself to be in that category, I don't think a lot of companies are looking for that. Most mid to large size companies like people to do very specific tasks with very specific job descriptions. Somebody who is a jack of all trades would probably fit in a lot better at a small company, which is where I happen to be, because they will have much more opportunity to work in many different areas. Small companies don't have entire teams devoted to database design, UI design, middle tier design, requirements gathering, architecture, testing, and all those other areas of software design, so the people who do work for small companies probably get to see at least a little bit, if not a lot from all those areas. Also remember that the full term is "Jack of all trades, master of none", however, I consider myself to be a "master" or at least really good in quite a few areas, and the all the rest of the "trades" just really help to back that up.
Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
When we do technical interviews, our policy is that anything on the resume is fair game to ask questions about. So, if someone comes in with a laundry list, we'll try to find a question to ask about some obscure technology they say they're proficient in (nothing too tough, just something that someone who knows the technology would know). This will tell us how much they're trying to puff themselves up.
We'll also ask progressively harder questions in each category that we have expertise in just to see what they do when they start becoming unsure of themselves or just flat don't know the answer. We are much more impressed by someone who simply says "I don't know" than someone who tries to bullshit us. If you don't really know a technology, don't go around pretending that you do.
What the parent poster said.
And also; make sure you are able to talk about Your Own Initiative:
Projects you managed. Problems you discovered and fixed, on your own, without oversight. Also, if other techs come to YOU for advice, detail those happenings as well.
If you're the go-to guy, and can be trusted with a small budget, and a certain amount of autonomy to come up with fixes to long standing annoyances that nobody else thought of even trying to solve (overcoming organizational inertia) - then try to convey that. Most managers would give their left nut/tit for this kind of worker. (and often, this kind of worker is misclassified as "junior").
Bottom line is: breadth of skill does nobody any damn good, if that skill does not come with initiative. Breadth of skill is difficult for a busy manager to manage. That level of management is usually tasked with fighting fires with his or her immediate superiors. They're too busy to task you - so you put your skills to good use, be everyone's hero.
These are my friends, See how they glisten. See this one shine, how he smiles in the light.
Some people don't want to be experts - I have absolutely no desire to be an 'expert' at anything. I am a generalist and have found a few roles where that is a bonus. And where there isn't a "need" for a generalist, I can go in to a specific role and branch out, letting my general skills help out where they can.
..." - I don't like the implication there. I am very competent, but I would find it exceedingly difficult for me to become "great" at any one part of my knowledge. I don't like to focus on one thing - I read multiple books at a time, I watch movies and read at the same time, I listen to music and surf and cook. I move from Windows to Linux to databases to development to application support to web to systems management many times a day, and I do them all well. Not everyone is made to become GREAT at things. I am a poster child for ADD and I think it's a great skill.
"If you really are competent then the step up
Not everyone wants to be an expert, and I don't think that should detract from their usefulness - like anything, you just need to find the right spot to apply your skills.
We emerge from our mother's womb an unformatted diskette; our culture formats us. - Douglas Coupland