Slashdot Log In
Which IT Careers Are Hot and Which are Not?
Posted by
Cliff
on Fri Mar 23, 2007 07:48 AM
from the where-should-one-go-from-here dept.
from the where-should-one-go-from-here dept.
necromante asks: "I've been working on different IT positions through my career: support; some networking; DBA; web development; project management; even working on the client side for a little while. However, I don't feel like I am really a specialist on any of those subjects and I feel I need to focus on a particular field. So, I decided to ask for some feedback before making my decision. I understand that this depends everyones tastes, likes and dislikes. However, I would like to have a better idea of which are the available options, and I hope the results of this discussion can benefit other readers. Is there any IT career that I should consider more than the others? Which are the emerging fields? Is there any industry I should focus on in particular? Which careers on IT are actually more in demand and which ones not? Is it a better path to focus on moving into management?"
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
Good techies don't necessarily make good managers (Score:5, Insightful)
Re:Good techies don't necessarily make good manage (Score:5, Insightful)
Parent
Re: (Score:3, Insightful)
Re:Good techies don't necessarily make good manage (Score:4, Informative)
Parent
Re: (Score:3, Interesting)
Re:Good techies don't necessarily make good manage (Score:5, Insightful)
The thing I have noticed is that a lot of people in a more technical role feel that they would be better in charge but in reality would probably just hate the position. I love being in control (hence owning my own business) but at the same time I'd rather leave the more managerial duties up to my business partner while I really worry about the technical side of things.
I have been a manager at a few places and while I did a decent job and my staff liked working for me, but I didn't enjoy the role as much as I enjoy being in the forefront with my technical skills. I did learn a lot about running a business from these positions which is a benefit now, though, and don't regret having been a manager. I just didn't enjoy it.
Parent
Re:Good techies don't necessarily make good manage (Score:5, Insightful)
Parent
Re: (Score:3, Funny)
I just can't get my hair pointy enough [wikipedia.org] to do it.
That IS the "dark side" of management. (Score:5, Insightful)
You see, that IS the real "dark side" of managment -- when you become a micromanager or some other type of manager that constantly second-guesses their employees because you "know better." Even worse is the type that is constantly trying to make people prove themselves to them by withholding information to see if their subordinate is "smart enough" to come to the same conclusions (and then berate them if they don't either due to a difference of opinion or a crucial missing piece of information).
I've had four jobs since I entered the IT field. Every single manager I've had was a former programmer with the exception of one boss's boss (who was entirely awful because she was more interested in office politics and backstabbing for advancement... but I digress).
All the good bosses I've had gradually abandoned the programming side and learned to act as mentors. They used their knowledge of the system to give pointers on where to look when you were stuck on a problem and trusted you to get things done, only prodding every now and then when a schedule was threatened. All the bad bosses I've had (save the one mentioned above) second-guessed you constantly and either went around your work to put someone else on it (like themselves) or constantly made you justify ever single moment you spent your day on. In both cases, the attitude comes from the thought that they could do it better if they didn't have to do all this management crap instead.
In other words, the secret to going from a technical role to being a good manager is learning to let go. Use your skills and knowledge to aid your subordinates and shield them from upper management by understanding what they are doing. If necessary, use you knowledge to call their BS if they're actually slacking, but don't envy them or treat them as irritating time-wasters blocking you from doing "your real job." Otherwise, you're just demonstrating the Peter principle. [wikipedia.org]
Parent
Re:Good techies don't necessarily make good manage (Score:5, Interesting)
Parent
Domain Knowledge (Score:4, Insightful)
emerging fields: (Score:5, Funny)
Editor who doesn't rely on spell check.
Re: (Score:3, Informative)
Being a manager... (Score:5, Insightful)
Seriously, if you like something, why stop doing it and start just watching people do it?
Oh, money.
Re: (Score:3, Interesting)
Once you get older and start a family the time that you have outside of work to sit down and learn D++ or Python.Net or whatever gets a lot harder to come by.
If you have the opportunity to learn on the job that's great. But it's not always the case.
Even if it's what you love to do it's still gets harder to find time to do. So moving into management seems like a reasonable step.
Although I'm put
The Fileds You Love (Score:5, Insightful)
Personally, I value breadth over depth. And I'm going to propose a reason why everyone should also: in the world of computer science, at any minute a once vital skill could be obsolete. Granted, it doesn't happen often (as we still need workers to maintain cobol & fortran code) but, instead of spending my free time hunched over Enterprise Java Bean projects learning their delicate intricacies, I find myself learning about Ruby, Spring, Hibernate, etc. Now, I might not be an expert in any of these fields but I may be glad when their time comes. All good things come to an end--and if EJBs were to be retired, I'd certainly like to know my way around these other frameworks & tools. I think the same can be said about fields of computer science. Be wary of the web developer that doesn't know the first thing about networks & server/client communication--that's often a pitfall for security.
So if you want my honest opinion about which "are hot or not," I think they're all pretty damn hot and I bleieve you can find money in any job where you make yourself usefull & valuable to a decent business. I find them all attractive because I enjoy setting up networks in my house and playing network administrater even though I don't do it at my job. I love networking Linux, Windows, FreeBSD, Solaris, etc. and I like toying around with different databases. I love to start new projects that rarely go anywhere but leave me with more understanding of how technologies or products work. I'm not a "trained expert" at any of them though, most importantly, I feel that I could easily become one if a situation deemed it necessary. If you don't enjoy doing some of these things--DON'T DO THEM. Who cares if they pay alot or are "hot"? I'd rather die happy & poor than rich & sad. Of course there is, it's the career you enjoy the most
Choose your path wisely.
Re:The Fileds You Love (Score:5, Interesting)
There's also a third option in many larger companies: a cross-functional, multi-domain expert. While many people are familiar with the Java/Routing/InfoSec/DB2/etc. expert who has developed extensive expertise and attained mastery in the technical domain, the multi-domain expert is another option which can be quite professionally rewarding.
Both my brother and I had IT careers (he in client app development and me in infosec and internetworking), and both of us went back to school. He added a marketing undergraduate and a MBA with a marketing focus, while I added a finance undergraduate and a Master of Science in Economics. For both of us, it was an exceptional career move. He's a marketing information systems manager for a Fortune 500 company, handling most of the IT projects for the different product brands of the company and gets to work with developing them the way he wants for his clients - architecting the solution, developing cross-functional dev teams, etc.
The finance and economics addition to an infosec and networking background has helped me become a dual-domain expert in operational risk management (an area that needs many more experts who understand both IT operations and the whole quantitative aspect). I get to design and develop metrics that help us analyze, track and improve our operations, manage the development of the systems that collect and report these metrics and then evaluate them to assess the company's global risk.
The cool part is if you like to set yourself apart from the crowd, it's a great way to accomplish that. It certainly isn't easy committing time to develop that second domain, and takes very careful job selection to get into a place where you can start using both domains. However, because companies seem to have serious problems communicating between different functional areas (e.g. marketing can't speak IT, and IT can't talk marketing), people who span the gap get very nicely compensated, have significant creative authority and overall get to see their ideas implemented.
*scoove*
Parent
Re:The Fileds You Love (Score:5, Funny)
And use enough buzzwords to make the tech implementer roll their eyes and mock you behind your back. . .
Parent
Re:The Fileds You Love (Score:4, Insightful)
It only sounds like buzzwords because you probably don't work with it. That's what we call quantified measurements, and those in operations management, finance, risk management, etc have to do that to really get at a problem. Otherwise we're practicing the behavior you're inferring by your comment: making totally subjective, qualitative guesses.
A good piece of advice is not to mock someone for using language you don't understand, especially if it sounds like management speak. If you're going to represent more than one domain, you have to stop talking the geekspeak of your locale and be able to represent concepts in the dialect of the group you're working with. It does me no good to go rambling about GARCH models and problems with autoregressive conditional heteroskedasticity in my time-series dataset, but that's ineffective and inappropriate.
My job is to apply my expertise to find solutions for my clients, not to wow them with big terms. Nobody cares that you can talk fancy words in your area of expertise. They assume you know your stuff - that's why you're there to do the job. Whenever you work out of your locale, communicate in their language and you'll find you're much more effective.
Parent
Re:The Fields You Love (Score:5, Interesting)
It started off as a specialty position (graphics), and I was well paid for it. But it turned into a position where I was responsible for a lot of other, varied things, like the intra-departmental website, and eventually my grasp of modern graphics technologies started slipping.
Now, because it started off paying so well, I'm still paid well... but now my raises are crap, not enough over cost of living to make any difference. I while I like the company I work for, I hate the location, and would take an equally paying job (adjusted for location) just about anywhere else.
The problem is that when I look at available jobs, the ones that pay even moderately close to what I'm getting now require a specialty.
This really kills me - because I'm sure I could get a great raise here if I threatened to leave, but I wouldn't threaten to leave unless I could follow through on it (I'm not good BSing with empty threats).
So, OK, I'm giving my annecdotal experience, but I find it's true elsewhere. I've had this conversation with my manager and he agrees, and he'd like to see me be able to get back into graphics 100% of the time, but the company won't budget for another programmer (I'm in a unique position here). I like all the things I'm doing, but I wouldn't mind dropping the variety and concentrating on being great at one or two things, I'd still be happy and I'd be able to demand more at a different place.
Parent
Re: (Score:3, Interesting)
Yes, but... (Score:4, Insightful)
If a shop is large enough to have an HR department (complete with screeners) it's hard to get a foot in. It's often difficult to get a position open to hire for with the designation Jack of All Trades. Uppers don't understand, and HR certainly doesn't. (Thats a common situation, but not a rule.)
If they do get that designation, starting salary for the job will be somewhat low, because that designation will be of lower status than an "expert".
And small shops tend to pay less than big ones in the first place.
This wouldn't apply at all for a shop consisting of just one or two people, but then, they tend to pay VERY low salaries.
For the record, I'm a JOAT, too, but have been involved in a bunch of hiring.
Parent
Re: (Score:3, Informative)
Jack of all trades,
Master of none;
But oftentimes better
Than master of one.
Tech Support (Score:5, Funny)
No seriously. BOFH is the field you're after.
Too many variables (Score:3, Interesting)
You then also have to look at not just region, but industry -- informatics is becoming more significant in some industries, but not in others.
Then there's issues with the size of the company -- specialization may be good for large companies with a massive IT workforce, but it's not desired in smaller companies with a small IT staff.
From the sounds of things, you need to look into systems analysis -- and review your organization, and your network of contacts. What's good advice for one person is most likely not what's good for anyone else.
Wrong Question (Score:5, Insightful)
Almost all areas are 'hot', but that doesnt mean anything. The one that will STAY hot for you, is the one that you love enough to continue your education throughout your career, and dont just pick someting to do for a paycheck.
If you love a particular area, your constant learning and improvement will lead you into related areas and keep you relevant throughout your career, you can move into consulting, writing and development within your chosen area and never miss a beat.
Never chase a paycheck.
Re:Wrong Question (Score:4, Insightful)
Parent
Re: (Score:3, Interesting)
I could do any of these things and be happy. I'm one of those guys who would stay up all night when I was a teenager just playing with code on my Atari 400 with the membrane keyb
Re: (Score:3, Insightful)
Oh, that must be why our economy is made entirely of astronauts! How does the view of Earth look from your space ship, Cytotoxic?
Good advice would be: Among career options with good economic outlooks, pursue the one you like most. "Do what you love" is terrible advice unless you just happen to love something with good economic demand (this is EXTREMELY rare). Most people would rather be making music or playing sports or inspecting bikinis.
Re:Wrong Question (Score:5, Insightful)
Sadly, no.
I went into IT because I love programming.
I evolved into Software Engineering because it made the programming easier.
I learned how to design because you can't do SE without it.
I became an architect because I had to design beyond my immediate system.
I got frustrated by the shortsightedness of the people giving me projects and became an enteprise architect so that I could influence the broader picture.
I expect to find I lack sufficient authority and move into IT director type roles to gain that ability to make the decisions I feel are necessary.
I still love programming. I just couldn't take a programming job any more. I'd get too annoyed at the crap development processes, the poor design, the inadequate architecture, the incompetence of the business and the inability to change things at a high enough level.
So find an area you love, yes. But expect it to change. Go with the flow. And remember the advice from Ferris : Stop and take a look around once in a while.
Parent
Doesn't matter (Score:4, Funny)
Cisco Voice (Score:5, Informative)
I work for a large company and we're currently in the process of a ~5 year migration from all legacy PBXs to Cisco Call Manager. Many other companies are doing the same. Just about all new offices are built with either Cisco or Avaya VOIP systems, but most companies go with Cisco since you don't have to be concerned with compatibility. (eg. A high-end Cisco router is also your telephony gateway where the T1s are converted to VOIP.) As you can guess, this calls for some highly specialized skill sets (eg. Call Manager/ICM/IVR + Cisco Networking/IOS, etc.) which not a lot of people have. If you're certified, you will NOT have a problem finding a job.
Pick something boring, or get lucky (Score:4, Interesting)
On the other hand, you can always pursue what you really love, and hope that you happen to get lucky and that your obscure interest is the Next Big Thing (TM). That's how the really great ones did it. Of course, if you did a better job selecting your parents (see: Paris Hilton), the career thing wouldn't really be an issue and you wouldn't be in this boat. So based on your track record, going with the chance part isn't such a good idea for you.
Re: (Score:3, Funny)
Avoid "hot" careers (Score:5, Insightful)
Loaded question (Score:4, Informative)
The one thing I do know for a fact is if you are diversified in a couple of "hot skills" your marketability goes through the roof. If you throw management experience along with that you can make some pretty hefty sums AND find a job you like.
My
AUDITING (Score:4, Funny)
My Faustian deal (Score:3, Insightful)
I personally prefer development over administration. Being a database administrator was a lot like being a firefighter. There were long periods of boredom where everything was running smoothly, coupled with late night crisis modes with huge pressure to get critical systems running again.
As a web developer, I get to do database work as well as creating web applications. I create a lot of things to make people's lives easier, some of whom are patients to our hospitals. It's interesting work and I get fairly generous praise heaped on me by coworkers and customers. The really crazy thing is that they pay me quite well to keep doing it.
Re: (Score:3, Interesting)
I was a developer for 10 years before I decided to work as a DBA exclusively. When I developed I was always the DB "go to guy" because it was always something that interested me. I wanted to make sure what I delivered performed well and the DB was a big part of that.
I enjoyed software development immensely but I got tired of the death marches and feature creep. One of my CEO's was nicknamed "Two Week Pete" because after visi
I am an IT Multi-Tool (Score:4, Interesting)
I have the following credentials:
Degree in Computer Science - No I didn't learn everything I needed to know in college, but that paper opened a few doors.
10+ years experience with computers in a networked environment.
Experience using and troubleshooting computers ranging from DOS to Windows to Linux, with a sprinkle of Unix.
Programming in C,C++,Java, VB and VBA
Knowledge of HTML
Experience in maintaining production servers for critical tasks.
Experience with peer-to-peer networks, hundreds of nodes.
Experience with Databases,MSSQL and MySQL know basic to moderate level SQL.
Experiences with Apache and IIS.
Command line scripting from DOS Batch to Linux Bash.
Tons more things I have just "worked" with as needed.
I have always been a "jack of all trades" in terms of computer work. Recently I have been specializing, not by choice, but by necessity in Phone and Data Networks. I have taken several weeks of training in ACD and Phone PBX systems. I have been setting up our phone ACD for about 2 years now. About to start working closer with the PBX hardware as well. It is an interesting niche.
If you are just looking for the latest "hotness" in computers it is security. But that type of job could well leave you stressed out with gray or no hair and a coronary in your early 40-50's. I see too many green newbies fresh out of college all excited about security and their careers. I don't know if I should find them amusing or scary. I guess someone has to do that job.
As for me, If I can keep learning and enjoying what I do, I couldn't ask for anything more.
Stupid question (Score:4, Informative)
A career in which you don't feel at home with will kill you before you get to retirement.
Must read today's dilbert (03-Mar-07) (Score:3, Funny)
Smart people are still in demand! (Score:5, Interesting)
Smart people will always find work. I've bounced all over the IT world...support, sysadmin, design and architecture, and it's really hard keeping your skills truly sharp. Someone who's truly valuable picks a few key areas to get really good at, and knows _something_ about the rest. If you're a network guru, learn a little about the machines you're connecting. If you're a systems genius, learn enough about databases to realize your DBA is BSing you.
Take the latest fads...SOA and security. You can learn everything about these two areas, but what happens to all that knowledge when it becomes a commodity? When the execs realize SOA is just a rehash of centralized computing with some XML and the web thrown in, where will you be? Keeping yourself open keeps you employed.
I learned through a really tough experience that management was not for me 2 years ago. Technical people generally don't make good people-managers. It's not lack of social skills, but management is a completely different job. You will never touch a machine again. You will be in meetings, answering e-mails, making phone calls, and "separating the kindergarteners" when they get into conflicts. If you burn out on technology, then it's an excellent career path. Otherwise, don't let people convince you it's a good move. Rememeber all the bad bosses you have/had? Just like some people aren't suited for IT, they're not suited for managing either.
One good overspecialization example I like to cite is OpenVMS system administrators. OpenVMS is still in active use, but it's really declining. Truth is, it's easier to write new applications to run on Linux/Windows Server than to pay for expert system administrators. One of the first IT jobs I had before moving on was VMS support. I don't know how DEC trained these guys, but they're some of the best, most vigilant admins I've ever seen. However, finding a paying job working with those systems is getting harder. I world love to have that kind of sysadmin in the Linux and Windows world I work in, but a lot of them are totally specialized and don't want to learn new systems.
One other thing...outsourcing is here to stay. If you're a developer, become a crack genius developer so you can get the contract jobs rewriting outsourced code that doesn't work. If you're a procedural system admin, become an operations wizard that designs systems that don't randomly blow up. In short, truly earn your money!
My advice (Score:4, Insightful)
Do what you enjoy. That's it.
Everyone I know in IT who really enjoys what they do (to the point where they would probably do it as a hobby for free if they were independently wealthy), ends up being successful. They are passionate and competent, likely not because they are inherently smarter than anyone else, just that they spend more time learning, experimenting, and playing around with the technology they like and work with.
I also know people who picked their IT career (and decided to go into IT to begin with) based solely on the job market. Will I make more money with
There are jobs out there for everything. If there is something out there that really gets you excited go for it. If you learn quick, really throw yourself into it and know your stuff, you will find employment. It might be more lucrative in the short term to trend hop, but if all you are interested in is the possibility of making big bucks then you should forgo IT and go into something like hedge fund management.
Me? I really dig identity management stuff. I've worked in academia with SAML, Kerberos, and PKI and in the corporate world with Oracle and Sun's IdM tools. A word of warning though: Find a field you enjoy, but do not get too hung up on a specific technology. I'm happy using my knowledge and experience in IdM to work with Infocard, SAML, PKI, LDAP, NIS, Xellerate, CoreID, Kerberos, AD, etc. I have my opinions as to what is best for what need, but I try to not be too much of a snob about it and limit my career that way. I've seen a lot of people go the "horse and buggy" way by latching on to a specific technology and refusing to let go when the world moved on.
Finkployd
Re:Choose a career you like (Score:5, Insightful)
One thing I miss about the good old days when anyone who even looked at a computer was considered a nerd was that you didn't get these kinds of questions. The words IT & career in the same sentance just bring a foul taste to my mouth.
Sure, if you just want to make a living IT is an industry that will probably always have a job for you. However if you aspire to become a master at something it has to be something you live & breathe. Just figure out what you like doing and roll with it.
You like organizing people become a manager. You like helping people work at a helpdesk. You like figuring out how computers work get a job making device drivers. You like php become a web developer... You get the idea. Doing something just because it's hot is a sure recipie for disaster.
Parent
Get out of IT (Score:4, Funny)
Go into the resturaunt business. run a mcDonalds. Get into the auto mechanic shop business. You can probably make better money herding 10 people cleaning houses. (That right there is a six figure a year job, for basicly managing a crew of people who descend on a house, clean, sweep, vacume and leave, repeat ad infinitum, scale as large as you want)
Of course, considering your lack of direction, you may not be the best person to run a business. Perhaps you should stick to help desk.
Parent
Re:No Future in IT in USA (Score:5, Interesting)
I was bitter once. I got laid off after 9/11, couldn't find a job to save my life
You have to bounce back -- if you don't, you shouldn't be in the field to begin with. Same thing applies if you can't find a job today -- you probably need a new profession. IT is booming, the Internet bubble was a temporary setback. Not all IT is INTERNET.
Not everything can be offshored -- I've seen successful offshoring, but I've also seen a large number of disappointed businesses who feel they were overcharged for sub-par return on investment in off-shored projects.
There is always a need for business analysis and system architecting. Someone thousands of miles away is going to have a very difficult time truly knowing a business, and understanding its needs. There is ALWAYS going to be a need for capable, creative people who know the technology AND the business to be local.
Parent
Re: (Score:3, Informative)
When you hire someone to program for you, communication is absolutely crucial to success. If the person you hire doesn't speak the same language you do (or doesn't speak it well), you're probably not going to get what you ask for. Also consider how bad communication will be if you are unavailable (sleeping) most or all of the time they're working. You can only communicate once per day. If they have a question, they have to stop working until the next day when y
Re:These aren't fields, and you don't need to choo (Score:3, Insightful)
It makes a difference to every HR person.
Re: (Score:3, Interesting)
Not as much as you'd think. A good portion of openings I've seen there are from headhunter agencies that put up phony jobs for clients that don't exist. This gives them a pool of resumes to boast to their own clients about.
Out of all the career books I've read, Ask The Headhunter is the one that struck a chord with me. His take on Monster/Careerbuilder [asktheheadhunter.com], while old, still holds true.