Which IT Careers Are Hot and Which are Not? 284
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?"
Good techies don't necessarily make good managers (Score:5, Insightful)
Domain Knowledge (Score:4, Insightful)
Being a manager... (Score:5, Insightful)
Seriously, if you like something, why stop doing it and start just watching people do it?
Oh, money.
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.
Depends on what you like. (Score:2, Insightful)
Again, you need to decide on what you feel is right. Obviously, money always come into play here, but it seems like you already have a wealth of information and a broad spectrum of experience that you have the capability of going into any IT arena.
Good luck.
Re:Good techies don't necessarily make good manage (Score:5, Insightful)
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.
Choose a career you like (Score:2, Insightful)
That's one of the better quotes out there. I've been in the Unix Sysadmin/Programming areas
for 10 years now and while I haven't found it all easy going and wonderful, I DO like what
I do, which is a huge advantage to quality of life in a career.
Pick something from the areas you listed that you enjoyed and work at it. Don't be too
concerned about "what's hot". If you have the fundamentals (such as a CS degree or equivalent experience) you will be fine.
Best of luck.
Avoid "hot" careers (Score:5, Insightful)
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.
Re:Good techies don't necessarily make good manage (Score:3, Insightful)
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.
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:Wrong Question (Score:4, Insightful)
These aren't fields, and you don't need to choose (Score:2, Insightful)
These aren't fields. They're roles. They're roles that will always play a part in IT. As others have mentioned, you should focus on what you like. At the same time, don't become overly-specialized -- if you pigeonhole yourself, you risk your job security in the long run.
Personally I'm a
"Web development" has become a silly term. Be an engineer, know the technology, and desktop vs. web won't make a difference. Be a "tech," and again, you're pigeonholing yourself, and putting long term job security in the pooper. Make sure you're proficient in current technology, but keep an eye to the future. Attend user group meetings. Attend industry conferences.
You shouldn't base your future on specializing in one of these roles you've specified, unless that's what you want to do, and nothing else, ever. You're better off exploring theory, being capable of applying practice. Improve your communication skills. Learn something new every month. Read the Pragmatic Bookshelf series, I think they might help enlighten you. Read well-known works, the classics, the new hotness. I can't say it enough: don't pigeonhole yourself.
Re:Pick something boring, or get lucky (Score:2, Insightful)
Re:These aren't fields, and you don't need to choo (Score:3, Insightful)
It makes a difference to every HR person.
How bout just answering the question? (Score:2, Insightful)
Re:Good techies don't necessarily make good manage (Score:5, Insightful)
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.
Re:Wrong Question (Score:3, Insightful)
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.
My Personal Thoughts (Score:2, Insightful)
First of all I will say that I have worked mostly in software development in my career, although I also have some UNIX system administration experience in my background. Because of that, this is focused mostly towards software development although some of it applies to other IT functions as well.
Next I want to clarify my own personal definitions. I define Information Technology (IT) as the group that provides technical expertise to a company in order to support their business needs. For example, if you work for a bank, you maintain the computer hardware software that allows the bank to make a profit by providing financial services. You aren't really directly contributing to the bottom line, since you aren't creating a product or service that the bank sells, but you are critical to their success.
The flip side of that would be Software Engineering or Technical Consulting, where you work for companies like Oracle or Microsoft or IBM. Although those companies have IT departments, the positions I'm referring to are the ones where you produce a product or service that is sold to customers to generate revenue. In this case you ARE directly contributing to the bottom line.
What I see in the industry is less of a demand for actual software development in the corporate IT world. In the past, companies needed a software development group, because they developed all their software in-house. If you worked for a tire manufacturer, and your company needed an accounts payable system, you would often develop and support it yourself. Now, that same company would be much more likely to purchase an ERP suite like SAP. If you needed needed technical customization, you hire consultants and/or contractors to come in and do the work on a project basis.
This is also true of help-desk and even networking/system admin functions. We're seeing more and more of those commodity-type positions being outsourced to third-party providers, especially in larger corporations.
So... my advice to someone just starting out in IT would be similar to what has already been said. If you really want to stay technical and go into hardcore software development or system administration or something, try to get jobs with companies who make that their focus, or else be prepared to work as a contractor or consultant, traveling frequently from project to project.
However, if you want to truly be successful in corporate IT, try to get as broad of an experience base as possible. Ideal IT candidates in the future will have broad experience in both hardware and software, and also the communication and people skills to help leverage technology to solve strategic problems. Working in the IT department of a big corporation will mean that instead of writing that accounts payable software package yourself, you will be identifying the requirements and coordinating with the different vendors to get the job done. You will still need technical knowledge, because you will have to be able to communicate with the consultants/contractors/vendors, and you will performing the integrations between the systems. However, you might not be slinging code all day.
Just as a disclaimer, I will repeat that this isn't a 100% rule. There will always be a need withing corporate IT departments for software development, because companies will always develop creative solutions to give them a competitive advantage over their competitors.
If you're just starting out, my recommendation is try several areas of the technology field and figure out what makes you happy. Being happy in your job is much more inportant than just money, in my opinion. If you don't like what you're doing, try something else. Having a broad experience base can only help you in the job market of the future.
Comment removed (Score:4, Insightful)
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]
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.
Re:Wrong Question (Score:3, Insightful)
Look at your list, and it would appear that in each case, you let others influence you into doing something other than what you wanted to do.
You love programming? Why the fuck are you not self-employed, so that YOU can decide what you do with your talents, instead of being trapped into making money for someone else by whoring out your time?
I dont get you folks who allow yourselves to be ruled by others, when you have the ability to pick and choose what you do, AND WHO YOU DO IT FOR.
Go with the flow, my ass.
If you are good at what you do, work for yourself.
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.