After College, What Type of Jobs Should One Seek?
Sushant Bhatia asks: "I'm coming to the end of my Masters degree, and I'm on the prowl for jobs. However, there are so many types out there it's just overwhelming for someone who's never had to go through the job-hunting process before. So, what should I do? Should I go for a full-time, contract, half-time, or something else? Also, what kind of position should a person with a Master's in Computer Science be looking for (other than dish washer)? I've been looking at senior software developer positions, but is that too high up the ladder for someone 'fresh' to cope with? My current manager (research lab) says that 'You should always find a job that is above your skill level so that you can learn and be challenged.' I think he's right, but is that something Slashdot readers agree with? What was your job coming out of university?"
I hear Wal-Mart is always looking for shelf stockers
Straight goods:
There's always a need for network people and sysadmins. With the shift from Windows/Proprietary Unix to Linux/*BSD you should concentrate on jobs in those areas, they're booming (I get at least 2 offers a month). If you stick to the Windows side of things you're going to be in a rut of helping users reboot and install patches. If you stick to proprietary Unix you can still do well in some high end research or data center work but cheap clusters are eating the bottom end out of some of that market.
Don't expect a senior position. Frankly too many hot-shot grads think they're The Goods; NONE are. If you can't translate your book smarts to real world work then you're destined to a life at a help desk.
That's how it is around here (I'm based in SoCal with work in 8 data centers around the country and 4 internationally) and I've been in the field since 1988.
Most people here are kids working at McDonald's or aging, overweight geeks living in their parents basement.
My advice, listen to all the +5 comments, and do the exact opposite.
It's "Master's," not "Masters." See wikipedia entry.
It doesn't look particularly impressive on a resume if you can't even write your educational credentials correctly. Yes, these are small things, but we are nerds, and for nerds small things like this matter. If we weren't obsessive about details, our programs wouldn't compile, and we wouldn't be who we are.
Of course, Slashdot moderation being what it is, the parent will probably end up with a +5 moderation, and then what do you do?
//Information does not want to be free; it wants to breed.
You're asking the wrong question. You should first sit down and ask yourself what interests you and what you would enjoy doing for a living. Maybe you dig airplanes so you want to get a job working on the computer systems on new planes from Boeing. Or maybe you like security software so go find a job at Symantec. You get the point.
After you've figured out what interests you, go talk to alumni from your school who work in the industry you're heading into. Ask them how they like their job, what salary expectatios you should have with your experience etc.
Whatever you end up doing, make sure you enjoy it. Good luck job hunting! I hope you land somewhere interesting and enjoyable.
why? i graduated in march with a BS in CS (math minor too). with a 2.5 gpa, no references really or any industry experience and only applied for jobs online. Now in june i'm an official software engineer making good money. The irony is how much i listened to slashdot's gloomy idea of the real world was considering doing something else outside the computer industry because there was no jobs for me (as you would believe by reading slashdot). Not that it was easy for me to get this job, but it wasn't the only response i got to my resume. Course I also think I got pretty lucky.
So my personal advice is to try and do what you like and not get disappointed over being rejected. And I think people in masses tend to be pessimists.. so take what they (slashdot) say witha grain of salt.
so, how's the weather in Calcutta?
My problem? I was perfectly gruntled, until some numbnuts came by and dissed me.
From a person who just went through a hiring phase for two programming positions (one senior, one junior), and wading through the over 200+ resume we did recieve, the only advice i can give you: 1. Don't assume you are qualified for a senior position if you don't have the experience to justify it. Most companies will look for relevant experience versus schooling (not always the case but...) 2. A full time position is always better (and will reflect better on your resume) than any amount of contract work or part time work you did (assuming what type of contract work of course). Companies like to see long term employment. 3. From a lower end position, a master's degree won't help you versus a normal bachlors degree. What you should look out for is the chance to really have an opportunity to make that masters degree work for you. That usually wont happen right away. 4. A position in a researching environment has really good potential of rising up that fabled "ladder" with a masters degree. Of course, a reseraching position will never pay as much as one in the "industry". I'd honestly, like pete said, get your foot in the ladder, and start climbing. Just find a ladder you actually want to climb is the most important thing :)
...believe it or not, real-world experience is very different than academic experience.
I have a great deal of real-world experience now, and a degree as well. When I graduated, I started at entry-level positions and worked my way up. It works.
Recently, I worked with a guy who had a masters in computer science from a well-known accredited state college. And he wasn't an idiot. However, he also wasn't ready for the real world. His troubleshooting thought process needed a great deal of refinement, and his ability to deliver the kind of requirements necessary in the kinds of time-frames necessary just wasn't up to par (yet). During the year that I worked with him, I saw his skills improve (as one would expect). In another several years, he may be senior-position material. But not until he has the experience under his belt.
I am not saying college is easy, nor that the education is valueless. I AM saying that graduates, precisely because of their lack of experience, have an unrealistically high opinion of their own abilities, and often make the sorts of costly (and embarrassing) mistakes that more experienced programmers don't make.
So there's my opinion.
Let me apologize up front for how vehemently I'm going to disagree with you.
No. I mean no. For the love of God, No! Have you lost your bloody mind?! NO!
Don't. Ever. Work. For. Free. You might as well wear a sandwich board that reads "My time is worthless and I'm so naive that I believe an idea put forth by suits looking to recruit cheap, easily-abused labor. I'm beyond desperate, so please, pay me some lowball chump change."
Take a lesson from the marketers. People honestly believe that a thing is worth what you paid for it. If you ever work for someone for free, you'll never convince them to pay top dollar for your services.
You wouldn't believe how much my life has improved since I learned to look them right in the ye without blinking and say "You're right. I compete on quality, not price. To be honest, these are my prices if I design and implement. If I have to go through the headache of fixing someone else's mistakes, I charge a 20% premium."
You'd be amazed at how that one little statement/attitude improves your world. You never have to deal with those neurotic not-worth-the-trouble PITA clients, and the rest come to the job with a "he's expensive, he must know what he's doing" mentality.
So long as you can deliver the goods, it's a far more satisfying way to run your business.
He put his boots up on the table and made a face. "The sig," he smirked. "You can waste your life in search of the sig."
http://news-service.stanford.edu/news/2005/june15/ jobs-061505
The only thing cheaper than french fries in a resturant is the soda pop.
Depends on whether it's bottled, premix or postmix.
Some very small restaurants purchase their soda pop in either single-serving cans or bottles (quite expensive) or 2 liter bottles (slightly cheaper).
Most restaurants use either premix or postmix. Premix is, as the word suggests, pre-mixed with water at the bottling plant. It costs about 10x as much as postmix but it tastes a lot better. Chain restaurants and whatnot use postmix where a syrup is mixed with water on-site. This is the cheapest but least "tasty" option. The contents of cup of postmix costs very little; the cup costs something though.
If you're a zombie and you know it, bite your friend!