Q. In I.T Infrastructure related careers can be stressful bit and also help desk or software support that involves dealing with customers and fault resolutions a lot, is software development sitting quietly and developing in .net programming or something stressful ?
A. Well it really depends.. depends on the complexity of the design of the software specs. It can be as simple as coding a few lines, to a project that never ends (upgrades, add ons) etc.
From a social view, yes software development don't deal with much people, but they still do - you gotta talk to someone to understand what are their requirements in the software, you gotta make sure what you design fits those requirements, you gotta do quality assurance with the customer so that the end product is what they wanted. etc. You're bound to be in projects that require other team members with time lines, you will have to interact with other people albeit not as much as helpdesk would.
The more stressful and complex the job is, the more money you are bound to make. May I suggest if you worry about stress, to speak to a doctor or a therapist to teach you skills that can help you cope with stress.
From a social view, yes software development don't deal with much people, but they still do - you gotta talk to someone to understand what are their requirements in the software, you gotta make sure what you design fits those requirements, you gotta do quality assurance with the customer so that the end product is what they wanted. etc. You're bound to be in projects that require other team members with time lines, you will have to interact with other people albeit not as much as helpdesk would.
The more stressful and complex the job is, the more money you are bound to make. May I suggest if you worry about stress, to speak to a doctor or a therapist to teach you skills that can help you cope with stress.
How should I approach entering the IT industry?
Q. I'm about to graduate with a BS in Computer Science and every time I stumble upon a listing for entry level positions the requirements are somewhat confusing to me. I'm confident in my computer skills but they ask for certain knowledge on things that I've never heard of and no idea what they're about. I know they won't teach me everything at school but how should I go about job hunting?
A. In career coaching IT students, i have learned that colleges don't always do a great job of preparing students for real world IT jobs. Broadly speaking, there are four paths in IT:
1. Software (programming)
2. Database (architecture)
2. Hardware (helpdesk)
3. LAN/security
Only in very small companies with one IT person would you wear more than one of these hats. Since you probably already have a path in mind, and chose your courses accordingly, hopefully most of the requirements you don't recognize aren't part of that path.
Another thing to know is that employers are being very silly these days about how they define jobs. So they are probably often at fault for including requirements (such as knowledge of arcane software) that simply aren't realistic for an entry level position. You will rarely be a perfect match regardless -- apply for the ones that you seem to be the best fit for.
Also, use this as an opportunity to network. Find some organizations like the one I linked to below (which is best for help desk & LAN/security peeps), go to meetings and ask questions to learn about these unfamiliar requirements. Good luck!
1. Software (programming)
2. Database (architecture)
2. Hardware (helpdesk)
3. LAN/security
Only in very small companies with one IT person would you wear more than one of these hats. Since you probably already have a path in mind, and chose your courses accordingly, hopefully most of the requirements you don't recognize aren't part of that path.
Another thing to know is that employers are being very silly these days about how they define jobs. So they are probably often at fault for including requirements (such as knowledge of arcane software) that simply aren't realistic for an entry level position. You will rarely be a perfect match regardless -- apply for the ones that you seem to be the best fit for.
Also, use this as an opportunity to network. Find some organizations like the one I linked to below (which is best for help desk & LAN/security peeps), go to meetings and ask questions to learn about these unfamiliar requirements. Good luck!
What is the job of technical helpdesk?
Q. I have got a job in technical helpdesk.I am btech.Please tell me,is the job suitable for a b-tech?What is the actual job profile,what i have to do?What will be the yearly income and if the work experience may shown for a software job.Please tell me the details.
A. There are no standards. "Technical helpdesk" is used for a very wide range of jobs and tasks. I've never heard the term "b-tech" before, so I can't comment.
"Technical helpdesk" could involve taking phone calls, reading faxes and emails, talking to walk-up customers, walking around to people's desks, driving out to client sites, or all of the above.
You might be serving the general public, school or university students, employees of any industry or type, in-house staff, company customers, third-party requirements, or any combination.
It might involve technical troubleshooting, diagnostics, repair, training, learning, teaching, escalating, writing, logging, liaising, analysing, systems administration, network administration, workshops, classrooms, speaking in front of groups, report generation, monitoring, installing, decommissioning, cabling and recabling, equipment transport, equipment relocation, editing, wiki maintenance, newsletter production, attending meetings, setting policy, user admin, password resets, IT security, configuring, tuning, tweaking, reading, and being at least partially telepathic and psychic.
The actual stuff you will be responsible for can be anything at all. If it's got lights, buttons, keys, a screen, goes "beep", uses electricity, has wiring in it, has metal or plastic in it, "looks technical", or is just something that no-one else above you on the corporate ladder wants to do, you might find that you have to take care of it. This can be anything from hand-adjusting the regular expressions making up the corporate firewall rules or brainstorming on the new version of the SOE, through to endless, mindless data entry off grotty bits of paper and people asking you to repair the broken electric kettle.
And yes, I have personally done or sat next to the person doing ALL the above things in various "technical helpdesk" positions.
The only way to find out what it's going to be at any given employer is either to work there for a while or to ask someone who's already been there six months.
If you want a very rough approximation, though, the bulk of work at the majority of helpdesks, most of the time, involves taking phone calls and emails from people who are having problems with their PC, trying to figure out what the problem is, and walk them through fixing it, preferably in the minimum amount of time. Sometimes you're lucky and you get documentation covering the most common problems and how to fix them.
However, in any helpdesk job there will always be a couple of problems or tasks which will make you ask "What the flying moose ears are they on about?" Only the details vary.
"Technical helpdesk" could involve taking phone calls, reading faxes and emails, talking to walk-up customers, walking around to people's desks, driving out to client sites, or all of the above.
You might be serving the general public, school or university students, employees of any industry or type, in-house staff, company customers, third-party requirements, or any combination.
It might involve technical troubleshooting, diagnostics, repair, training, learning, teaching, escalating, writing, logging, liaising, analysing, systems administration, network administration, workshops, classrooms, speaking in front of groups, report generation, monitoring, installing, decommissioning, cabling and recabling, equipment transport, equipment relocation, editing, wiki maintenance, newsletter production, attending meetings, setting policy, user admin, password resets, IT security, configuring, tuning, tweaking, reading, and being at least partially telepathic and psychic.
The actual stuff you will be responsible for can be anything at all. If it's got lights, buttons, keys, a screen, goes "beep", uses electricity, has wiring in it, has metal or plastic in it, "looks technical", or is just something that no-one else above you on the corporate ladder wants to do, you might find that you have to take care of it. This can be anything from hand-adjusting the regular expressions making up the corporate firewall rules or brainstorming on the new version of the SOE, through to endless, mindless data entry off grotty bits of paper and people asking you to repair the broken electric kettle.
And yes, I have personally done or sat next to the person doing ALL the above things in various "technical helpdesk" positions.
The only way to find out what it's going to be at any given employer is either to work there for a while or to ask someone who's already been there six months.
If you want a very rough approximation, though, the bulk of work at the majority of helpdesks, most of the time, involves taking phone calls and emails from people who are having problems with their PC, trying to figure out what the problem is, and walk them through fixing it, preferably in the minimum amount of time. Sometimes you're lucky and you get documentation covering the most common problems and how to fix them.
However, in any helpdesk job there will always be a couple of problems or tasks which will make you ask "What the flying moose ears are they on about?" Only the details vary.
Powered by Yahoo! Answers
No comments:
Post a Comment