Go For a Masters, Or Not?
mx12 writes "I'm currently an undergrad in computer engineering and have been thinking about getting my masters. I have a year left in school. Most of my professors seem to think that getting a masters is a great idea, but I wanted to hear from people out in the working world. Is a masters in computer engineering better than two years of experience at a company?"
Work Experience for sure.
And you should be getting some NOW.
But if you want to hang around uni, maybe become an academic, then sure, do your Masters.
You can tell how powerful someone is by the magnitude of the crime they can commit and be able to get away with.
spend the money on partying and living like a gypsy for 2 years instead.
I know a lot of people who don't work in the area which they studied for their masters. Thats a waste of time IMO. I think you should decide now what type of work you are going to do after university and make sure you can directly benefit from the extra time you spend on your education.
http://michaelsmith.id.au
when you are considering taking on a masters/Ph.D/etc, its not really about money. Its about you, how much you are enjoying academic life, and how far you want to pursue it. if the only reason you are considering postgraduate courses is that it might increase your employability, then you shouldnt be considering them.
Normally I'd say "get a job", but there's not as many of those going around as there used to be. (Damn banks and their irresponsible lending.) What are the employment prospects where you are? Doing a masters is more productive than being unemployed, and much better on the CV....
HAL.
Got them moderator blues I blieve I walk out the do', With these mod-points I been gettin', I 'most never post no mo'
As someone without any education at all, I'd say go for the Masters, then get your experience after that. No?
Yea, we haven't heard this question verbatim before, but the:
I want to go to college and get my BS in IS - what should I do?
or
I want to get out of IS and pursue basket weaving - what should I do?
or
Do I need a degree to be a Tape Monkey?
type questions are pretty much the same.
Though the questions aren't the same the answers will be.
The IT industry isn't so great at the moment, and as soon as job cuts come about in a company, the IT people are always the first ones to have their heads put on the block, then get chopped.
Companies seem to think that the IT dept is the most expendable for some reason. Now things are so bad that when a vacancy does crop up, there are more jobless candidates applying now than ever before. It's ridiculous until the economy gets better and God knows when that is going to happen.
My advice is to spend another year in study and sharpen your skills and knowledge. You really haven't got anything to lose until things get better. Except money. But there are always ways of making money, eh? Websites, your own ventures, freelancing while studying, part-time work in other industries like retail. The pre-bubble era of plenty in the early 2000's is long gone, but it happened once and I can easily predict it will happen again as more turn to online purchasing to save some cash in these troubled times. So such plentiful times will come again. Enjoy your studies if you decide to carry them on.
Depends on the situation. If you can get a good coding job in a good situation where you can learn a lot, then the master's degree isn't worth it.
I'd continue with education if I couldn't find a decent gig. There's something to be said about doing and open source project as well to get experiences that you can't get in either college or a job situation.
These days, if you have the raw skill, say for kernel development, going through a master's degree program at a University of California minimally would be a waste of time even for Berkeley or something like that.
You can even cut that off sooner than that in that a wide variety of folks drop out of college to do the same thing and just do not suffer from not having either degrees.
It's situation sensitive however.
I ended up getting employed full time right out of college. I accumulated 4 years of good experience, at which point I decided to go back to school part time.
The great thing about this is that if you can find an employer to help you pay for your higher education, that sweetens the deal. The downside is that your work obligations always come first, no matter what, especially if the company is paying. This is especially true if the job requires travel.
I can tell you working full-time and going to school part-time is not easy, especially if you have a family like I do. But it's definitely doable if you are dedicated and have a wife who is willing to put up with it for the next 2-3 years. Just don't count on much of a social life.
Change is inevitable, except from a vending machine -- Robert C. Gallagher
I took a Masters in Software Engineering - back in the 90s. My masters was specially setup so that an industrial placement with a company was an integral part of the course. By all means take a job now - if you can get a good one - on the other hand - combining your masters course with an industrial placement at a well known company will get you the best of both worlds - and usually there are several bigname companies interested in taking on a motivated masters student as an industrial placement.
I am pretty torn on this question...
On the one hand, it will never again be as easy to learn as it is now. The older you get and the more time passes between having been in school and then doing it again, the harder it will be. Not only to find the motivation (unless you really do like school), but also to get your brain into learning mode again. Not to think about actually fitting school into your budget, especially if you already have family.
On the other hand, I'd expect you lack experience on what kind of jobs are out there for you and which of them suits you best. If what you like to do best falls into your current degree, then getting a higher degree will make it harder for you to find employment in this field. Wacky companies aside, it is usually not a good idea to hire people with too high degrees for a certain job. Bored people are just as detrimental to your overall success as people who are overworked.
Frankly, without having any idea what you actually LIKE to do with your life, this question is a pretty tough one. As unhelpful as it may be, you should try to match your education with the profession and amount of responsibility you target. The closer you get, the easier things shall be for you.
If you can get a job do so, if you can't (because of the "current economic climate") get a masters. But whilst you are doing your masters, keep looking for a job.
Given the choice between two candidates for a job: candidate A has 2 years experience doing the job they are going for, candidate B has zero experience of the job they are going for but has a piece of paper that says they have a masters, which would you choose? The guy that can do the job from day 1 and has a proven track record, or the guy that will need hand holding for 6 months to get him up to speed?
I have friends that have gotten very good jobs after their masters and others that haven't. If you're going to play probability than masters will offer you better chance for better paid jobs. But in the end, it'll be up to you on how you present yourself and the experience and knowledge that you have. If you think the master degree for whatever field will present you with more options, than definiately go for it. Else, get a job, get some proper experience. You can always get your degree at a later date when you know what you're doing.
Get it out of the way now. I believe there is a trend for upper-level jobs requiring a masters or MBA, so if you get this out of the way now, it'll be worth it down the road. My mother pressed me to do the MS after I finished my BS and it was good advice because it would be difficult to do it now -- I simply have too much going on. Of course, you need to be practical about this. I'm assuming you have the time, interest, and money. If you don't have the money, one way to get the university to pay for the MS is to apply for a [funded] PhD and then quit once you get the masters. And you never know...maybe you'll finish the PhD? Or start a company? I think there's so much opportunity to be creative in academia. It's almost altogether absent in the corporate world though, which is one reason I tend to work at startup companies. Hope this helps, Thomas
All depends on the job your applying for but generally as long as you have a basic qualification, real life work experience is what is valued the most. Best to decide which area of IT you like most and try to find a position that will give you some nice projects, etc to put on your resume. Employer love to see potential employees who have broken new ground in the area that they want to employ them. Qualifications are more valuable if your applying to a large corporation that's more interested in what's on paper and usually suck to work for anyway.
Those who can, do. Those who cannot, sue.
"Most of my professors seem to think that getting a masters is a great idea"
Of course they do, that's how they get paid.
A taught Masters (eg two more years of lectures) is a waste of time compared to two years experience, but a research Masters (two years of independent research under a mentor) is a good opportunity to make a name for yourself in a computing niche. The research one is more difficult, more expensive because you'll need to get to the right conferences and 'market' yourself, and only worthwhile if there's an aspect of computing that fascinates you more than it interests other people.
But...
The economy is shot. There's a chance that you won't be able to get a solid two years of work experience. If ever there was a time to not be in work for a while and take some time to improve your skills and get some "me time" where you're doing what you want to do this is it. If you do a Masters when you finish you'll be entering a work environment where there are lots of people who've graduated with you and then been unemployed for a large proportion of the past 2 years. You'll have an advantage over them.
http://twitter.com/onion2k
Look at the kinds of jobs people have gotten with a bachelors. If some of them have the kind of job you want, look at what it took them to get it. Do you have that? If not, look at the kinds of jobs people have gotten with a bachelors that you don't want. Are you willing to settle for that?
If you have a masters you can have the kind of job you wanted in the first group whether you have what they had or not. You can also repeat the process above for jobs people have gotten with a masters.
"I may be synthetic, but I'm not stupid." -- Bishop 341-B
I'm not a professor, I do computer support for an engineering department so I see an academic environment, but I'm not an academic. That said:
Don't get a masters just for the sake of getting one. You will not get yourself any sort of real leg up. The reason to get a masters is because you want to do research. If there is something that interests you, something you want to study, particularly a research professor you'd like to work under, then it is a good idea. Education for its own sake is never a bad thing. However to just get a masters just to try and get a better job, nah not a good idea.
We have all kinds of students like that in the department where I work. They are hoop jumpers. They see a masters as just another hoop to jump through. However they don't really learn anything from it. They don't do any research, just take a comprehensive exam, and still go out in to the world with a ton of theoretical knowledge and no ability to actually apply it.
What you see is the opposite of what you'd think: The bad students go on, the good ones don't. The top students go and get a job. The bottom students go on to get a masters since they can't find a good job. However the problem isn't education.
Also, if your company wants you to get a masters, they'll send you back. My cousin did this. Got his bachelors and went to work for Boeing. After a few years they said "Hey, you are doing well on this, how about go get your masters?" So he did.
Now the one confounding factor right now might be the crappy job market. If you can't get a job, then maybe staying in school makes more sense. That's a question of finances, and I can't answer it for you since I don't know your situation. However if the option is no job living in poverty or full scholarship living as a student, well then it isn't hard to figure out which you should do.
So, reasons to get your masters:
1) You have something you are really interested in researching, or you know a professor who you are really interested in working with. You are getting it because you want to learn more and enrich yourself.
2) You have a good financial incentive to get it, like a scholarship, and poor financial incentive to go work.
3) You are working in a field that requires a masters. Computer engineering isn't generally one of those, but there are some exceptions. There are some subfields that a masters or PhD is necessary. If you wanted to be a professor that would be an example.
Now these are NOT reasons to get a masters:
1) You want a better job. Probably not really going to help you. It might, and I emphasize might, get you a better entry level position, but work experience counts way more than education after that. So you might find that in 5 years, you were better off getting more work experience than education.
2) You want to put off working because you aren't sure what you want to do. Bad idea. Only way you will know what you like is to try it. So get the job, and if it doesn't work out get another. Don't use school to avoid work, because that doesn't solve anything since work is coming at some point.
3) You "need it to compete." No, you don't. Most CE people don't go on to get a masters. It really isn't needed. If you find yourself unable to compete, the problem is likely not a lack of education, but something else. I mean if you are the sort of person with no problem solving skills (something engineering requires) no amount of school will teach that.
So I can't say if it is the right decision for you since I don't know you or your situation. All I can say is that it is the right decision, so long as it is made for the right reason(s).
Two years of work experience will do more for you in the long run. Plus, you could always take the masters at some later point in time.
Also, if you're up to it, there's plenty of colleges that'd let you do your MBA on a part-time basis, or at least schedule your classes around your work requirements.
Back when I was doing my Bachelor's degree (full-time course), I also had a regular 40-hour-per-week day job, and was also raising a baby daughter at the same time.
Two words: time management.
The Wknd Sessions - Malaysian and South East Asia independent music
I would be careful of the Masters. (coming from someone with one and going for a Ph.D.) I would say yes get one, because later in life it's a check mark for higher positions in engineering.
Now here's the choice, you can get a professional masters (online and/or course work only). This pretty much shuts the door to going on academically. Or do an in residence thesis under an adviser. Yes it will be harder, but it gives you flexibility if you so choose later on.
Please don't do online.. yes it satisfies the checkmark for management positions, but not for engineering. You miss so much of the learning not being around other people going through the process and having alternative ideas proposed (read lab mates calling you out on retarded ideas)
There's no real point to a masters in CS. If you want to do research, you need a PHD to get a good spot at a uni. If you want to teach collegiately, you need the PHD if you don't want to be treated like shit by the administration. If you want to do heavy duty research while hired by industry, a phd is respected, anything else has a huge burden of proof, usually in the form of similar experience in the real world. If you want to go into the real world and work, a masters won't make you extra money and won't get you more respect than a BS- a masters with no experience is treated just like a bs with no experience.
So what do you want to do? If it's research or teach, get a PHD. If it's go out and program for a living, stick with the BS.
I still have more fans than freaks. WTF is wrong with you people?
Most young professionals work on a masters part-time. A good employer will pay the fees.
more money..
I'm actually in a similar position (about to graduate in CSE, deciding where to go next). I probably have a job lined up, thanks to an internship program that I've been in, but in this economy you shouldn't count your chickens before they hatch. On the other hand, universities are also raising tuition and cutting back on incoming class sizes, so a good grad school isn't guaranteed either. Consider the pros and cons of each, though:
The advantages of working are substantial - you get an income, real work experience (different from classroom experience to be sure), networking for future jobs, and corporate seniority (useful for promotions, or for resume building for later jobs).
However, most people don't get to really experiment and push themselves the way they want to in the workplace - to do that, you either need to be in research (meaning you already have a graduate degree), highly placed within a successful company (you're not, I take it), or an entrepreneur with cash to burn (see above comment). Work is mostly doing stuff that other people want you to do. You may (hopefully do) enjoy the work, and you will probably learn from it, but you have fairly limited control over your own path within any given company.
Grad school allows you to explore the topics that interest you most. Take a few advanced courses, then do some research. Become an authority in a specific topic, or know enough to tackle anything in a given subfield. As for money, you won't earn much while in school that doesn't go into student expenses, but you can probably support living and tuition by working as a TA and/or getting a research stipend. After you graduate you can get a substantially better salary.
Don't forget internships, either. They carry many of the benefits of starting a career (CSE internships pay better than many full-time jobs, if you haven't learned that already), while still letting you carry on your studies and/or research the rest of the year. They can be hard to get in a down economy, but if you can, grad school plus internships give the best of both worlds. You'll have knowledge, experience, money, career options, high employability, and the chance to do whatever you really want.
There's no place I could be, since I've found Serenity...
If you can afford it, go for masters.
Let's compare yourself to someone of your age and education but without a masters degree.
In two years, he is in great advantage (you have 0 experience, he has 2yrs). Two years later, he is still in the advantage (masters + 2yrs against 4 years). At this moment he is, unlike you, a candidate for getting a promotion etc.
But in a moment when you get ~4 yrs of experience, i.e. where you have to compare his 6yrs against your 4yrs of experience, his advantage is not that big. Four years later, 8yrs vs. 10yrs of experience does not make any difference. But your degree will remain an advantage.
Assuming that you'll work in IT for more than 2 years, I would say that your master will be an advantage for longer period that his 2yrs of more experience will be the advantage for him.
And as something possible in CS/IT, you can get some real-life experience during your masters course, which means that in practice you will have 2yrs spent on masters with some experience, and he will get only the experience.
Also, on a plus side for you, the larger company becomes, it takes more into account formal training. So if one day you want to work in some large system, it's better to have higher qualifications. In this moment you may not want that, but do you know where would you like to work in, say, 15-20 years?
No sig today.
Try for a research masters degree on some topic you find interesting, and try to find a way to monetize it. :-))
Create a small company that you own if necessary (take care of not being carried away bankrupcy is no fun
And either do some consulting,or try to monetize whatever you have developped.
So on your CV you'll have the Master AND the Experience...
At any rate, having the master's degree will make your life much easier, particularly when you'll be a "senior"...
(it might seem counter intuitive that a diploma that you've done or not 25 or 30 years ago has any impact on your career, but in reality not having it means needing twice the "support" from insiders...)
unless you're absolutely sure that you'll be running your own company when you're 45..50..
(and actually no you cannot be sure....)
Yes, it's worth it.
Two years of work experience may sound great now, but in reality, they won't ultimately make much of a difference - once you've worked for five or ten years, it'll be entirely irrelevant already. A degree, on the other hand, will stay with you forever.
Also, consider that work experience is something you can always get (and in fact *will* without even having to do anything for it, other than being employed); a degree is something you won't be able to get as easily in the end once you're not at your university anymore.
That being said, I also agree with what others have said and suggest not stopping at your Master's and getting a Ph.D. instead (well, in addition).
Right now, you've presumably got non-zero earning potential. Earning some money might feel good. Getting rid of some student loans might feel good.
Sooner or later, maybe you'll start spotting jobs that you could get if, on top of your natural talent, you had more education. When you start thinking that, go get more education.
I spent about 15 years in IT (went from $18K to $100K+) and never needed more education than I had. If I had more education, I suppose I might have been pushed into management... but I don't really like managing, I like doing.
5 years ago, took my IT skills and went into scientific and policy fields where I got to apply my IT skills, but got to learn a bunch of entirely new stuff, and do completely different work that made my old cubicle-dwelling buddies extremely jealous. Of course, it did put my pay back down to $18K... and I realized that everyone around me had a PhD or JD or something similar! So after racking up some experience, I'm now taking grad classes... and in these fields, just being in grad school makes people take my job applications a lot more seriously.
Village idiot in some extremely smart villages.
I did an MSc directly after my BSc. I believe it was time well spent. When it came to looking for a job I found that the MSc got me several interviews, it also meant being offered the maximum salary for a new graduate.
Hi,
I was in the same situation in 2001. I could have gone straight to work (many and some fun possibilities) but instead I chose to do two more years. It was the best choice I've ever made. Do not hesitate. If you have energy: do it. You'll cover a wider spectrum. Besides, you can ALWAYS make up for the "lost" working experience. Overall, there are more advantages than drawbacks. In addition, you get to put many "I-know-everything" people back on track by just pulling rank. :-)
Captain America
The job market is tough right now. This makes it attractive to stay in school. Rather than getting a MS in Computer Science you should consider getting an MBA and focusing on your communication skills (writing and presentation). I have a BS and an MS in Computer Science but have observed those with a BS in Computer Science and an MBA. I believe increased communication skills and general business knowledge will open more business areas to you and once there will help you to excel.
Academics live in their own little world, where GPAs and degrees and such rule the pecking order. They are very focused upon the idea that success equals education. That is not true. Education can be part of success, but there are far more factors than that, and almost all of them are about you. Being eager to learn new stuff and being easy to be around triumphs a double Ph.D. and being an obnoxious arse.
Also, I've never been asked about my grades nor my education (B.S. in Software Engineering btw) but very often about experience and getting hired seems more about buzzwords than you ever wish it was.
So some of your more obvious options are:
1. Get a masters because you think that it is fun and rewarding. That you are asking the questions you are makes me feel like you might not think that it is the most funnest evah.
2. Jump into the work market. Could be tough, prepare for it well.
3. Start your own business. This honestly seems easier than getting a job these days. The internet and stuff like the Apple app store has made it easier than ever to sell software to others, and there is always consulting. Will give good experience, might give good money, will have a degree of freedom to it.
4. Do the masters and start your own company, combine the to if possible. More work, but might be a better combo.
5. Bum out, quit school, go on welfare, play computer and video games like crazy and get all the loot. Play the lottery, hope for epic failure to avoid you. Code perl once a month for a few minutes to give yourself the illusion that you still go it.
6. Surprise me!
I've started my Masters this month. I'm doing Masters in Software Engineer at University of Oxford, UK. I have 3.5 years experience and this Masters is a part-time, so, I can do both. If you have this option, better. You can add years to your experience and at the same time update your educational background. But, the industry, in my point of view, needs more computer scientists and software engineers. The bigger educational background you have, better. Just one thing: go for the subject you most like, otherwise you are going to face a very tough post-graduation course.
If you want to go deep and become an expert in your chosen area, I would (perhaps surprisingly) recommend getting a job now. Best learning is learning by doing.
If you want to keep your options open, being able to switch not only jobs but perhaps even specializations or industries, I would say go for your Master's. It will train your thinking rather than your skills.
This from someone who has done a BC in electrical engineering, Master's in IT (signal processing) Ph.D. in IT (object databases), then worked as a security and financial auditor, now teaches financial management, and is certified in all these fields :o)
The question you should have asked, is not "Is a masters in computer engineering better than two years of experience at a company?"
Indeed, at that point in time, the two years of experience will put you in a better place than your masters.
What you should have asked was: "Is a masters in computer engineering + 2 years experience better than 4 years of experience?"
After masters + work experience will be more valuable, however, the masters cannot be a replacement for work experience.
Then again, I am doing my PhD in chemical engineering, so what do i know about a masters in computer engineering and your employability in the IT world...
It might be a good idea to take masters if u are final year student right now. Why? In order to sit out the economical crisis. But it mostly goes for those doing Economics or Finance. However, it might be good idea not to take it right now if u want to start or already have your own business. If you are in the UK. Try to change/choose your course so that you would have joint Masters degree with BSc this way you will spend only one year doing Masters and you will be applicable for the government student loan which you are not if you do Masters separately. Then try getting a year internship between last bachelors year and first masters. Internship say at IBM will look so much better on your cv then plain masters degree. Finally, if you have a research field you are interested in go for the masters and then maybe phd. If you invent smth new that might serve a good head start for your own successful business. But if not that into research find a job for now. Seek that your employer would pay for your masters and if he does: well it couldn't be better to be a freshman once again =] ps. masters do not have to be in your field (you could argue), try to broaden your perspective. Study economics or a language. In Computer Science there are so few girls, not in arts tho,no.....
It also depends of the college you're going to. If the school is good and reputable, then a Masters might be a good idea as it will increase your salary. If you can't get into a good college to do it, it's probably better to get a year or two work experience, and then apply in a good college.
I'm on my third year of a Masters course. The third year is a year out in industry. So I've spent the last 11 months as programmer for an ISP. It's been great experience and good to take a break from university. You should see if you can do a masters with a year in industry. Personally, 5 years is a long time to stay in one place. What I've found is that a few of the students on the same course have now dropped out of the masters to a shorter course as they have been offered permanent jobs by their industrial year employers. I like studying but don't want to end up an academic, so I chose the masters to give me a couple of extra years. Now, my reason for sticking with the masters is the economic climate, many of my friends in computer science and other fields are finding it difficult to get work at present. Good luck to you, whatever you choose.
How old are you? Think about this: you are going to die. You can go to grad school when you are in your 30's (apostrophe nazis can fuck themselves). If you are still in your 20's, make a dream list if you don't get into grad school. Here was mine at 23:
Now pick one and do it. In a few years when you can't take the painful vagabond existence or high pressure of your dream career, go to grad school. After I made my list, you know what happened? I got into grad school. Worst thing that could have happened to me.
Just callin' it like I see it.
Finished my masters a few moths ago. Then I had to sit down and ask myself why, why was it worth all that effort and what would it enable me to do. And all I got was emptiness. Then I realized I had been sold the useless widget that you see on tv and that once bought you don't touch it again but occasionally look back at it and wonder why, why did you waste your time and money with it.
The higher education marketing got me too :(
Now here's the choice, you can get a professional masters (online and/or course work only). This pretty much shuts the door to going on academically.
I can only speak for my personal experience, but working on my online professional masters helped me get into the PhD program at the same school. I came from a 4-year school that ranked waaay down there near the bottom, and I'm not sure that I would have been accepted without the higher-ranked graduate school having a year of decent graduate classwork at their institution to include in the evaluation.
I will however agree that a "real" (i.e., you wrote a thesis) masters is probably going to be viewed by technical recruiters as a lot more solid qualification than a professional masters.
[b.belong('us') for b in bases if b.owner() == 'you']
There's already some great advice about why or why not to get your Master degree now.
However, the people that are suggesting that this is a poor market to get your first job are wrong.
First off, hiring is not down that much (and in many instances it is up)
http://finance.yahoo.com/career-work/article/107040/Bright-Spot-in-Downturn-New-Hiring-Is-Robust
And I speak from experience, I finished school in early 2002, during the previous IT downturn.
You might not get the same starting wage as someone did 1 or 2 years ago, and you might need to relocate, but when the market takes off again, you will be much better positioned to get a better job (either in an area you care about more, or something just for more money), if you have 2 or 3 years of experience, vs. having a Masters Degree.
My suggestion is, regardless of whether you decide to get a Master's degree, get an internship or a Co-op over the summer. Especially if you decide not to get your Masters. Even that 1 summer of experience will help to differentiate yourself from any other graduates that have no experience.
As someone who is a few weeks off submitting a Masters thesis, my advice is: do a PhD.
The writing up process for a Masters is as arduous as a PhD, though the actual research is easier because it doesn't have the "original contribution" requirement. For a little extra grief though, the PhD will open more doors into the world of research.
From a career perspective it's probably a bad move. It's the worst of both worlds. It labels you as a "theoretical" person or a "student", whom people with limited vision will not want to employ. As the same time, doors to serious research positions stay closed as PhDs specify more PhDs when writing job descriptions for research.
Do it because you love it, not because of what it will do to your career.
I started with a "change the world" view, but it eventually became a "get the #%^$ thing submitted" view. A minority of higher degrees are about changing the world. Most are about jumping through the necessary hoops to say "I'm a researcher".
This is written from an Australian perspective.
First question - are you just in it for the money or in it because you like the technology and money is secondary?
If the former, get your masters, without a love for the tech you will not be an over-achiever, at least not long-term. So a masters degree will help bolster average performance and keep your earning power up better than a regular clock-puncher without a masters.
However, if you are the later, skip the extra degree and gets your hands dirty. If you haven't done so already you need to be interning as part of your bachelors program. The most learning you will ever do is in the real world, so the more real-world experience you get under your belt the more you will be able to excel.
Incidentally, excelling at the job (and keeping your eyes open for opportunities) is the best way to make good money. It is, however, not usually an option for most clock-punchers.
When information is power, privacy is freedom.
I think at this moment in time you should go for the masters unless you have a good position waiting for you after graduation. The job market is not looking great right now but should be looking good in a year or two when you'd be getting out, and a masters degree will set you apart from the crowd who didn't get one and spent 2 years doing their level best trying to get people to super-size their meals while desperately hoping for their first real job.
When I graduated with my masters the tech boom was in full swing and if I'd gotten my masters I would have missed it, so back then I would have said get straight into the job market. Now in a market contraction it makes sense to go for more qualifications.
I personally think that for the majority of tech jobs a masters degree is irrelevant as the vast majority of what you will do you will learn on the job. You can't learn realistic project management in school, or how to deal with management. These things you only learn in the trenches.
would you rather try and find a job now? or in two years when the market may have bounced back a bit and you're better qualified (and could have some part-time experience on the side).
~/ One man's opinions is a lifetime of pain.
As someone who was in your shoes two years ago, let me tell you this:
You need MSc basically only if you're going to continue in the academia, or if you're serious about research (more or less the same thing). I went that road, and am at the beginning of a research gig that will last for some time right after I finish the thesis this month.
If you think that MSc will somehow magically open the doors for you, don't. This is more valid for CompSci than Engineering, for example. The knowledge required in the field changes so much through the years, that one or two more will probably leave you with a stale skill set. Not so for research, especially if you're working in a specialized cutting-edge area (I'm at AI).
But if you're a generic Java/C#/C++ guy, with no specialized knowledge or interests, you're the same as a million other people looking for a job that (probably) have more experience than you in the field. You need something to differentiate in this case, and that is either a more specialized skillset, or a more diverse skillset (e.g. MBA).
Good luck, on any occasion.
+ 3.14 Transcendental
I'd say it depends on what you see yourself doing. If you want to be a deep thought thinker in an R&D department, or if you want to stay at least semi academic, get the Masters.
If you want to be a programmer, engineer, or whatever you want to call it, I'd say get the experience. I've been directly involved in any number of hiring decisions over the last 20 years, and I can't recall a single instance where the existence of a masters degree made the slightest difference in our decision.
And I will add: if you aren't interested in research, you are wasting your time doing a PhD. Unless they actually specify "PhD" in the job ad, employers will actively discriminate against a PhD on the basis of "over qualification" or "being in an ivory tower".
If starting a business, PhD can impress some people you talk to. The time spent on a PhD would probably be better invested in building the business though.
While it might not be a consideration now, your formal education can have a big bearing on your future immigration opportunities. For example the UK now requires anyone applying for a High Skilled Visa to have an equivilant of a UK Master's degree, irrespective of your field.
D.O.U.O.S.V.A.V.V.M.
I lost a great opportunity to work in a huge data centre because of my Master course. Even though I'm just part-time student they said the course could affect my availability for shift work and on-call duties, so they didn't accept my application. Anyway my experience with hunting for jobs shows that what matters for employers is the employment history rather than education. But I'm still saying it's always good to have both.
Go for a Ph.D. In most US programs, Ph.D. programs are subsidized and Masters programs are not. If you go for a Ph.D., you get a masters for free along the way. At that point you have a free masters and can then move on.
http://online.wsj.com/article/SB124181970915002009.html
This article in the Wall Street Journal talks about the long term salary affects of graduating in a recession. If you're sure you can find work in your field then you should be okay. If not you might want to consider getting that degree, at least according to the article.
Cheers,
Greg
For a start, education is worth more than your final salary. Your time at university should be more about expanding your horizons and using the spare time that you will not have in the working world to pursue your own projects. Savour it whilst you can.
Secondly, if you hadn't noticed, it isn't a great time for anybody to be graduating with anything right now. Staying in university longer will, hopefully, save you from having to look for a job in the middle of a crisis where companies are having to cut costs.
Thirdly, the idea that you must find work as soon as you graduate often leads people into jobs they dislike, jobs they feel trapped in, and jobs that are considerably below what they are capable of. This will, I speak from personal experience, make you very unhappy.
Forget the work ethic bullshit you've had thrust upon you. The purpose of life is to enjoy yourself and to fulfill your potential in the way you choose. Work should not be a means to this, but a part of it. Poverty is preferable to drudgery.
Don't look for money. Look for a vocation that really appeals to you, rather than just a job, and let the money sort itself out later. Don't think about getting a mortgage and a pile of expensive crap as soon as you graduate it because you'll end up making yourself little more than an indentured servant.
If we can put a man on the moon, why can't we shoot people for Apollo-related non-sequiturs?
I have a year left in school. ... Is a masters in computer engineering better than two years of experience at a company?
Marty! Accelerate to exactly 88 mph!
Academia, then go for PHd.
Workin' for the man (even if you plan to be the man) then...
C E R T I F I C A T I O N S !
As a close-to-30 completely uneducated (effective high-school dropout) developer, stick in there and get your masters, easily.
Like people have pointed out, when HR compares a masters with 2 years of work experience, the masters will win.
And if I were in your position, I'd wager that the economic funk we're in is a little less depressing in 2 years. If you're right, two years well spent. If it goes downhill, well, then you'd be pretty much fucked anyway (last in, first out).
Masters and whatnot stop being relevant after a couple of years (it's not like anyone even bothers to ask for my grades anymore, having worked for over 10 years whereof 8 "in the business"), but it'll give you a good head start when you're compared to people like me ;)
Given the current state of the economy, any job you apply for will likely also see applications from professionals who have had 5 years of experience or more. In other words, you have slim chances.
In light of that, my suggestion is to do a master's degree but not in the US. Tuition in the US (and Canada for that matter) is far beyond what its actually worth. Go go a European country where tuition is subsidized. The "worst" part is that you have to learn a new language (unless it's an international program in english), and that's actually a very marketable skill.
On the other hand, if the economy were better, I would say that you should get a job; good work experience is exponentially more valuable than academic "training".
However, when you do begin your career and start looking for employment, and I can't stress this point more - do not apply to a lower-level position in hopes that you will one-day get a promotion. Internal promotions require at least twice the time and money of retraining and rehiring that an external hire requires. In short, don't take the first job that comes your way. Hold out for one that seems challenging and dually rewarding.
If you really want to gain some experience, port Linux / Android to a new device while you're doing your master's degree. You don't necessarily need to be employed to gain some practical, modern, and highly valuable experience. There's a whole world of open-design out there waiting for you - take OpenMoko for example. Why not redesign their next handset and make some major improvements?
" Is a masters in computer engineering better than two years of experience at a company?"
No, but you should get a masters degree anyway since it'll make it much easier to get your first job and it's actually "proof" of knowledge much more so than work experience. That said, you'll probably learn a whole lot more during your first two years working than the entire time studying.
Speaking from experience here as a recent grad (BS in Math/CS in 2000, MS in Telecom in 2004), I was faced with that decision for a while, and seeing it in hindsight there is one thing you need to realize. The Masters is only going to get you into the door a little bit easier. It might get you to the top of the pile for interviews, but it by no means makes you a shoe in.
After that, you must deal with the fact that it's hard finding an IT company who wants to hire someone as 'green' as a new grad. Use your masters to get contacts in the industry, work your tail off to get a great summer internship if your program is two years long. I was lucky enough to go full time for two years, and wrote freelance for a well-known computer security magazine. Bolster your resume.
Use the masters to bolster your chances of convincing future employers that you are more than just a naive college grad.
If you have little or no debt load and will be able to pay for the degree as you go, I'd say absolutely go for it. By the time you get out the economy should be good and healthy again and most of the companies that dabbled in outsourcing will have been burned in their projects. Delaying entry into the job market by a couple years right now would be a decent strategic move.
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
Master degree may not counts at the entry level positions (you will be treated just as BS for entry level positions)... but it does count when you get you a senior position in 20+ years. Seniors with master degrees definitely earn more than seniors without master degree, and I'm telling it from the personal experience (i have master).
However, it's not always an Either-Or forever.
I began college in the early '90's, and after decling Pro Science, set about for my career.
I was just luck enough to have this feeling that computing in 1994 really wasn't mature enough to waste a full degree in, so I got an accounting degree with some PHB icing.
Wall Street adventures in the news aside, accounting is still accounting. But now were I the CS type, a CS masters in this environment is "still the paper", but far fresher and full of much more useful topics. I think What To Do Post Microsoft will be the topic of the decade.
Meanwhile, I have some grade B work experience, but a hulluva lot more real context. My current position is a hybrid I invented for myself, that no straight degree will ever describe in a course catalog.
My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
Back in 1998 instead of listening to my lectures at college I decided that I wanted to go to University and get a CS degree. This was a foolish move as I could have made mega money on the Y2K crisis. I ended up leaving uni just as the bottom was falling out of the UK IT market. What I should have done is got the work experience and then gone to uni when the IT market fell after 2000. That said you are currently in the reverse of the situation I found myself in. If you can do both you are on a winner. If I could only choose one I would go for the Masters. That said I am not you. What is right for one person isn't right for another. Good luck what ever you choose.
-1 disagree is not a modifier for a reason. -1 troll, flamebait, redundant, overrated are NOT acceptable substitutes.
Go for Masters, have fun and enjoy your days as a student. You can work for the rest of your life (I'm not saying it'll be boring, but it surely won't be the same).
If you find yourself low on salary, you can always take some smaller projects to work on, get a part-time job or take a break from studying and go to work.
That's a good way of putting it... Starting with zero experience in the current climate is going to be *hard*, so a Masters is a good way to pass the time until things pick up. Either way, you'll start at the bottom (when we're looking for candidates we grade according to experience - not qualifications - and someone with zero experience is only going to get a code monkey job no matter how many bits of paper they have).
I don't know much about the educational system in the US as I live in Europe. But from my experience (I've had both day classes and evening classes) it's a lot harder to get a degree outside the normal 9 to 5 classes and it takes a whole lot longer as well.
Going back to school after several years of working isn't that easy either. When you leave school, your life changes and unless you have someone willing and able to support you for several very costly years, it's not going to happen.
IMO get the masters, chances are it's the only chance you'll get to get them. To give you an idea: I'm working to get a bachlor degree through evening classes and taking exames for a number of classes in college. In total, combined with a full time job, a mariage and a child, I'll have spend about a decade on this. Compare that to the 3 years in day classes it normaly takes.
On the other hand, now I've got several years of experience, which builds self confidence and teaches some things you won't learn in school.
i just started a cs masters program and am loving it. the general trend i've seen is that most people intersperse internships into their program to break the monotony and get some great experience. so you shouldn't worry about work experience. personally, i've met a ton of smart people who love to hack away at cool projects and met some great career contacts through internships. my general strategy when it comes to the future is to do what makes you happy and make 'option maximizing' decisions. a masters in computer will only better your understand of computers, programming, networking, compilers, etc. and if you ever got the itch to teach, you could absolutely do that as well. i've had several professors start in industry and migrate to academia after 20 years. nobody in industry is going to dog you for getting an advanced degree in a field you really enjoy. i'd totally recommend it.
Work for a couple of years first and then do your masters. You will be more mature and also take full advantage of the master's once you've experienced first hand the mediocre approach most people have to their jobs. Having seen this, you'll appreciate why the practices taught in your master's are really worth it.
I did it the other way around (undergrad->masters->work). I wish I hadn't.
Read the Daily What-the-Frel http://thedailywtf.com/ This will teach you more in a day's reading about the real world of computing than you will learn in a year on a Master's. And you will enjoy it or be horrified, either way you'll have more fun thn writing a Master's thesis.
"Cock Up Your Beaver" does not mean what you think. This sig is intended to clog filters and annoy do-gooders
Also: the MS is good for another reason: contacts you keep for a Long Time. Like in Undergrad, the contacts you make in MS degree will help you later in life.
Good luck!
rs
Shoes for Industry. Shoes for the Dead.
I do think I disagree here.
The pay curves from 0 to Bachelors are far steeper than Bachelors to Masters. While "many" can, that kind of success does take an odd brand of insight to make it work. For those who don't have those flawless instincts, it's all too easy to miss the window a few times, then end up serving cheese subs.
At least a degree lets you usually finagle some entry level stuff, just to avoid gaping black holes on your resume. Now multiblended careers are standard, so "just working usefully" is good enough even if it's not a straight line up a field.
My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
In my experience, employers prefer years of actual experience.
Having a masters degree says nothing about how well you can withstand the pressure of the real world, and how well you can work with others, two things that most IT companies value highly.
I know a lot of people who have done both. It depends a great deal on 1) what the masters program is, and 2) what kind of work you can get right now.
If the masters program consists of taking a few more classes, doing some problem sets, and a few small programming projects, skip it. Employers will (rightfully) lump you in along with every other undergrad or BS + MS who finished simply by following a pre-planned track.
If, on the other hand, you're actually doing independent work- working on some large, independent/group projects, doing real research, maybe getting your name on a paper or two and building some decent prototype/POC systems, then the masters may give you a real advantage, because you'll be able to talk about real experience working on projects, but still have a wider theoretical base than a lot of people fresh out of school. A really applied, hands on MS program gives you the best of both worlds, in a way. At some large companies, a MS is a gateway to higher-level work as an architect or other high-level designer/developer- whether by policy or by happenstance, most of the people you compete with for those positions will have post-grad degrees.
What kind of work can you get? Keep in mind that the hiring market is very competitive right now; you may see yourself dumped into a support/low grade technical positions as a fresh grad that doesn't provide great experience. If you can spend two years actually writing real code that gets used in a production system, the experience might be more valuable. If you're going to be doing tech support or fire-and-forget CGI forms for two years, the real world work might be much less useful to your ultimate career than doing the MS.
I came out with a BS and started working, but I had a degree from a well-reputed school and good internship experience. A lot of the guys I knew in my office had bachelors degrees from local schools, and they started out doing support and incidental minor scripting. My starting job was as an engineer, on the other hand. The lesson for me was that a solid education (which the MS can be a big part of) can leapfrog you past some of the duller entry-level busy work.
My advice would be:
1) Talk to people who have done the MS program. What did they do? Are there opportunities to do real research or project work that will set you apart from other people who took a ton of classes?
2) Apply for a few jobs and see what you can get. If you can get a job at a good company that will take an interest in your career development (usually means a larger company- small companies are very friendly, but often lack the resources to really develop their people) and will pay you well, that might be convincing for you. If you're going to be punching a clock doing work that doesn't advance your career (there are plenty of people with BS's in Software Engineering and Computer Science doing what is essentially tech support that could easily be done by someone with an associates degree or a self-study with an A+ cert), the MS will probably offer you better options.
3) Make a real assessment of what you're like as a student. Getting the most out of a MS program will require that you are able to manager yourself and challenge yourself, and take on big commitments without someone standing over you forcing you to do it. If that sounds like you, great. On the other hand, if you sat in the back of every classes and did fine while avoiding notice and not getting involved in much (frankly, I was this type of student!), a MS might end up just being a few more lines on your transcript without much to contribute.
What is your specialty--hardware or software?
If software, I would agree that work experience is far more significant, if you have a choice between one or the other.
If hardware, it could be quite different, as either a Masters or PhD may be the entre into the most meaningful career opportunities...again, depending upon your primary interests. Even there, though, work experience of some sort is extremely valuable. However, a PhD candidate can often do projects with industry that would qualify as valid experience--and don't forget that professors are often well plugged into the industrial world as well and can help with placement for the most promising grad students.
As others have said, it depends on what you want to do. If you just want a job as a systems administrator, get a few certifications and lots of experience. If you want to be a software developer, experience is a must. Start doing cheap freelance stuff. Take a look at the job market out there, and look at the requirements for the job you want. The majority of them only require a 4 year degree, but ~5 years of EXPERIENCE. Getting experience is the tough part. You'll probably have to find a job on the lower level than what your post-graduation expectations were, and put your time in. Even with a masters, this is more than likely.
Some places of employment offer full tuition coverage while you're working. The downside is that you'll only be able to pursue your Masters degree on a part-time basis.
Personally, though, I'm looking to exit the work force after 3 years to pursue a research masters/PhD. My recommendation is that if you find an interesting job and are willing to do a part-time masters, it may be a way to get the best of both worlds.
If you *like* being at university, stay and do the master. If you don't particularly like it, go looking for a job. Too many people see the master (or university as a hole) only as a means to an end. A painful experience you have to get through until you get a job. My view is different. I believe that going to university should be a rewarding experience, and not just as some diploma on the wall and potentially a higher salary. The act of going to university should be fun, otherwise you have nothing there to do. You can't possibly expect to benefit fully from something you hate doing, if you're doing it every day for several years.
I have a master's degree. I got it in a different country than where I got my bachelors degree. I thought doing my M.Sc. was well worth the time and effort I spend. I honestly don't care if it makes me more attractive in the workplace or not, but I suspect that it can't really make me less attractive. Compared to the two years of working experience, that depends entirely on where you work. 2 years working experience can be several times more rewarding and interesting than 2 years of master study, but it *can* also be utter crap if you do it at the wrong company, or if they are not taking care of you properly.
In the end, since neither path can *guarantee* that you get what you want, I would recommend that you choose the path that seems like the most fun.
Move sig!
If you are into status symbols then get a Masters Degree. If you are into education then home schooling is more efficient (assuming you have the discipline) than a traditional classroom university education and saves you money and opportunity costs.
In terms of HR hiring departments (I would think) a Masters Degree gives you a slight edge over people who don't have one, but the intelligent recruiters would be more interested in knowing what you can do, and not what degrees you have earned.
Get real work experience first, then get your masters. Not intern/co-op stuff, but some real world work experience.
I'm have a BSME, concentration in controls. If I went to masters program straight out of by BS, I wouldn't have known what I didn't know nor what I wanted to learn.
I've worked for 2.5 years so far at a company and love all the work that I do. But there's definitely a 'glass ceiling' of knowledge that I want to get past. I'm looking at going back in 2010 for my masters.
At the same time, 95% of the people I work with are perfectly content with their position and the work they do. You maybe too. Get out in the real world, see what you know and what you don't and then make the decision after a year or two in the real world. After 2 years you may come to the conclusion that 2 years in the work force taught you everything you wanted to know about CO and you'll have saved yourself 2 years of your life.
a) Don't go to grad school unless someone is paying you to be there. Medical and law school are exceptions. If the school doesn't find you a job, they don't really want you.
b) Don't think you will be able to go back later. Yes, it does happen, but "life" gets in the way.
c) You will never be in a better position to live cheaply than you are now. If you start working, your lifestyle will expand to use the income.
d) Image you are 90 years old. When you look back on your life is "having a Masters" on the list of best things you did? Most men probably have "wife, children, grandchildren" on that list. Very few people have some job ... except doctors, I'd guess.
e) Don't go to grad school at the same institution you do your undergrad at.
In short, you'll never be in a better place to go for a Masters, but it needs to be your decision. My daughter was working on her PhD at CalTech then just walked away a few years ago. No reason was provided. She had always excelled in everything - sports, academics, friends, life.
Each of us need to find our own way and be responsible for our decisions.
I think the Masters / PhD will be more valuable later in your career. Experience will open doors at low levels for you. The Masters / PhD will open doors in academic and high management levels for you, more specifically rule, the more you see the "public" in your job, the more valuable the Masters and PhD become (company bragging rights, and proving you are an "expert"). If you are thinking of a work, management and retire/teach, get the Masters now and the PhD later, if required to teach.
My answer to the OP question is no...a Master's is not better than 2 years in the field...especially at the beginning of his career. Companies tend to want to know you can do the job for which you are applying...not whether or not you can take classes, pass tests, or even write a thesis. Can you deliver that all important webpage/application in on time and under budget withh all the bells and whistles the end users demand? Can you provide the business with a solutio to an existing problem without costing them an arm and a leg? If after years in the field you want management, then yes a Master's will do you well then. If I were the hiring manager, I would hire an experienced professional with an Associates and real job experience over a newbie with a graduate degree and no experience...all other things equal.
Why not find a good part time or distance learning Masters? Then you can get a job after leaving college, work at that a while to make sure you like it and then study a Masters part time. You may even be able to get your company to pay for it. That's what I'm doing and I think that if you do it this way, your company would be more inclined to give you a promotion upon completion of the Masters as they would be looking for a return on their investment.
There is no one answer to this question. The field of software engineering is broad. For some jobs, perhaps most, work experience is more valuable for sure. But in certain fields, a masters is a must. Government research labs and the financial industry will only consider you for some positions if you have a masters or even PhD, but if that is the sort of job you're aiming for, you'd be better with a maths or perhaps physics or economics masters than a masters in computer science/engineering.
I guess that might also depend on where you live. I'm from Croatia, I've got my Bachelor's degree and right now I'm going for the Master's degree (pretty much, I've got no other options, I'm the first generation studying according to Bologna process and I figure it's better safe than sorry).
In a few conversations with potential employers (Ericsson for example), most of them said they would rather employ someone with a Master's then with Bachelor's degree.
Then, there is also the self-motivation and probably self-reward in a higher degree.
There is no way I would have appreciated a master's degree, or even learned as much from it, had I done it right after of college compared to after 2-3 years of work experience.
And you can save up to pay for your tuition that way, too.
Job experience teaches you to be confident in your code, to work with standards and within an office with actual structure to how they code. But you learn very specific technologies. I went into a job writing a 3d Rendering engine after specializing in computer graphics in college - I've learned so much more about actually being a programmer by being in this job, but I learned way more about computer graphics in college. You narrow yourself a lot in what actual textbook type knowledge you gain, but you develop much more as an adult and as a computer science professional by being out of school.
Let's put it this way - you work on a bunch of interesting project in college, but every one of them was completed in less than a semester. You could be working on the same project for years in a job. The scale of everything is tremendously different, and you grow so much by learning that you can handle that scale and work within it.
After you've had that growth - sure go back for your master's if you liked the learning and want to improve yourself, and you'll appreciate it so much more from seeing what the "real world" is like.
"I'm currently an undergrad in computer engineering and have been thinking about getting my masters. I have a year left in school. Most of my professors seem to think that getting a masters is a great idea, but I wanted to hear from people out in the working world. Is a masters in computer engineering better than two years of experience at a company?"
In the workforce experience trumps just about everything. Having a Bachelor's degree is great, and it's an important tool to get your foot in the door, but it's what you do once you get through the door that really will make the difference. Your professional reputation and work experience will take you farther than any piece of paper will.
That being said, having a Master's degree will no doubt help you long term, but I think that it's of dubious usefulness without some work experience behind it. If you roll straight out of a Bachelor's program into a Master's program and then into the workforce, people are going to look at you like you're all theory and no practice.
My advice would be to find a decent job (easier said than done these days) and develop work experience and professional contacts. Learn how things are actually done and truly understand the challenges of your field. Then after a year or two of working full time, start working on a Master's program. You can do it part time while working, and while that will take a little longer you'll finish your Master's program with more years of experience under your belt too. On top of that, you might be able to get your employer to cover some of the cost of your degree.
In summary, a B.S. and an M.S. are great tools, but if you have no experience then people aren't going to look at you much differently than if you only has a B.S. A B.S. and an M.S. with significant work experience makes you much more valuable.
Do you have a job now?
No? go for a master... make yourself more educated...
Yes? go for a master... make yourself more educated...
Maybe... There is no maybe...
1. If the work you do allows you to dabble in a few areas and enables you to get a lot of experience in a couple of them, then your work experience may be just as valuable or more valuable than master's studies done for the same period. 2. If the work you do is basically mundane, run-of-the-mill stuff (say maintaining a very stable project with limited scope for engineering work and/or development) , it certainly won't give you the depth of knowledge that you could possibly be getting if you go back to school. 3. Someone else has also said this a while back - a master's degree is sometimes a pre-requisite for some jobs and certainly helps if you ever think of migrating to a different country for work.
Here in Europe (and more specifically the Netherlands), people who didn't do their Masters are regularly considered lazy guys since we have come from a system where you always did your Master, and now you "drop out early" if you don't.
Also you can get a BSc from a school which is definitely not an University, which basically pollutes that title.
I've been in the IT sector for over 14 years, and it's the education at the master's level that really helped me in my career. But then again, I never sat idle when I was in school - I got my first developing job at a large insurance company when I got my AA degree, and I continued studying till I got my B.S. and then I went for my masters.
I've worked from financial companies to, currently, with a large contractor for the defense sector, from pure development to IT operations, and, overwhelmingly, every almost single person I've worked with THAT IS REALLY GOOD AT WHAT THEY ARE DOING either had a masters or at least had pursued a good amount of graduate studies.
Graduate studies, that is, good graduate studies teach you how to research and troubleshoot things - in particular if you focus your grad studies to practical research in software engineer, distributed systems, embedded systems, enterprise computing, or biometrics/robotics.
It won't help you for making web apps, but one doesn't need a B.S for that either.
Some of the best programmers I've known didn't even had a degree in computer science, and OTH, some of the worst I've known where Ph.D. candidates.
So it depends on the individual. If you are the type of student who thinkers with stuff, who isn't afraid of working from the command line, or doing C or Assembly, who knows how to work with pointers and who had a really good grasp of algorithms, theory of automata and software engineer, then by all means, go for the masters and then get a job.
Depending on where you are, having a masters will open more doors than just a BS. But that depends on the location.
On the other hand,if you suck as a programmer while being a student, and by this I mean that you suck not because of inexperience, but because you suck at a very fundamental level, and all you do is point-and-click programming, then you'll suck whether you have a BS or a MS.
My suggestion is to go for it immediately after you get your B.S. degree. Use that opportunity to contact potential companies that might hire you after graduation. See if they can give you an internship during summers or work on a master thesis related to some industry-funded project or topic.
For example: when I was in grad school, I was working on a project that dealt with security on distributed systems for medical records funded by a large hospital network.
When used wisely, a grad education will open far more doors than just a B.S. degree.
Of course you want to go to grad school! Isn't it the ultimate escape from reality?
I don't know that I'd say 'most', but there are quite a few that do.
My recommendation would be to look at the potential employer's education benefits packages ... some go by dollar amount per year, some by number of classes per semester. Almost all have a clause that say you have to repay any benefit if you break employment within 1 or 2 years after finishing the class, but some universities take the reverse approach that you have to put time in before you're eligible. Some pay before the class, others pay after you've passed the class. (I was under three different benefits packages while working on my degree ... and the company got sold, so I don't know what my current situation is)
Once you're on the job for a while, if you like the place, you can look at what would actually be of use to the company (not entirely altruistic -- it makes you more valuable) and you find interesting -- sometimes, it's cross training in a different field. My master's is in information science, not computer science. (of course, my undergrad isn't computer science either, so I'm still debating on a comp.sci. degree, but I have a comp.sci PhD/part time faculty to bounce questions off of.)
And *always* talk to HR before starting classes -- I had one employer tell me that I'd get reimbursed if I got an A or B, and only had to get special permission if I took more than two classes per semester. What they didn't tell me was that I had to get 'regular' permissions before taking ANY class -- so the report cards come in, I turn them in, and they ask me why I didn't file the pre-class paperwork to justify that the course was related to what my job. And of course, by then, I'm already into the second semester, so had to eat the cost of two classes.
Build it, and they will come^Hplain.
I'll tell you the answer, because I've done it myself: he should get the degree, THEN pursue basket weaving. IT isn't the great job market it used to be (unless you're willing to move to India), and you'd be surprised how much money and how satisfying a career you can get in manual jobs.
I myself have a 4 year degree in computer science, and now work as a gunsmith. All my pals who stayed working in computing are looking for work, I don't. And on the plus side, if gunsmithing tanks, I can always go back to computing.
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
As someone who interviews candidates for software engineer positions then what I find more valuable than a masters is finding someone with the demonstrated ability to do the job, enthusiasm and love of the subject. This is because, in my experience, a graduate who only took the course to earn more in the industry is not really going to understand the subject and not really going to perform as well as someone who is a "hobby programmer" who has discovered how to research their own solutions due to loving the subject. So if you really love the subject then opt for work experience, i.e. do the work you love. If you want to learn how to teach other people then a masters. You'll learn far more from three months work experience than you ever will during a two year masters course. The most important thing is to figure out what you want or love, is it the programming or is it the thought of being able to earn tons of cash? Because I know I could and have programmed for free because I love the subject. Which is what sets me apart from those who don't love the subject and turn up for interviews thinking they can get a highly paid job just because they passed an exam.
Martin Piper
Owner - ReplicaNet and RNLobby
One thing I regret is listening to the advice of so many people. If you feel like you will learn more, and be able to do more of value for others with a Masters Degree, then get one. Even more important, make sure that you will enjoy earning the degree.
Money is not the most important thing in life.
-- $G
well, 10 years later, you have the same candidates.
Candidate A has 10 years experience
Candidate B has 8 yesrs experience PLUS a Masters degree
Wo which one is it now?
...so I will post the same answer: For me it was useless.
I did my Masters (in Engineering, not Comp Sci, but my example might still be relevant) and discovered that, although I enjoyed the program, as far as my career was concerned a Masters degree was worse than useless.
After I graduated I was hired at a starting salary. My Masters' experience counted for nothing. I was therefore making less money and had less seniority than my former Bachelor's classmates, and was essentially doing the same work. When I was looking for a job, some employers were openly suspicious of my intentions, saying that since I had a Masters degree I would probably quit after a couple of years and go seek a Phd (so why hire me?).
Would I do it all again? YES! Because I really enjoyed doing my Masters and was very very interested in the research that I did. That is the most important thing. If you don't love the subject, you will hate doing your Masters.
I know many people who have done Masters degrees, and the only ones who benefited career-wise were those who continued on to their Phd and those who did MBAs.
Life is like a web application. Sometime you need cookies just to get by.
If you have to fund it yourself, how do you know anybody wants the result?
If someone will fund you to do it, a third party outside the University thinks it is a good idea and worth something to them.
It's like MBAs: if you have to pay for it yourself, you're probably not MBA material. If your company wants you to do it, somebody thinks you are.
From scarped cliff or quarried stone she cries "A thousand types are gone, I care for nothing, no not one."
Do I need a degree to be a Tape Monkey?
Absolutely! And for only $29.95 I'll be happy to send you one.
Regardless of whether you choose to do a masters or start working right away, it's not likely to penalize your career. So how about you do what you feel like doing? It's really important to feel comfortable in what you're doing. If you don't like your masters, it'll be useless, but if you really like it, then I'm sure it'll be very valuable. My only advice if you want to do a masters is don't do a "course masters", do a research masters.
Opus: the Swiss army knife of audio codec
You can get work experience while you study, and probably get your tuition paid to boot. It's called a Research Assistant position. Don't assume that Computer Science departments are the only place to look for one. Other departments like Astronomy, Chemistry and the biological sciences all have computing needs.
#1 priority is get the job. Once there, you can think about part-time / night school to get your Master's.
I was in the workforce for three or four years before I started my Master's program. I found it a much more rewarding effort because I had real-life experience to apply to what I was learning. I had lessons-learned to bring to classes, and if your classes are made up of people who are working (nighttime classes will be like that) then you are more likely to get better "war stories" and come away with good info and considerations of things you had never thought of.
And at the end you'll have a Master's plus work experience... an advanced degree plus a portfolio of success (or at least experience) on real projects.
Some say certifications are the route... somehow I think a potential employer is going to be more impressed by my Master's plus years of experience and examples of work over the cert-of-the-year I could have gotten back then that is useless now. Certs have their place, but in my view (and career experience) there is much to gain by hitting the workforce for a couple of years and then starting the Master's program.
IT may or may not be expendable. However, there is a big difference between Computer Engineering and IT....
Computer Engineers actually understand (and often use!) basic Calculus... But those in IT can tell you how actually to deploy security policies across a network. Other than being two professions centered around computing, they have little in common.
Equating the two is like equating a professional chef to someone who flips burgers. Yes, they both deal with food, but there are major differences...
I'm a firm believer in staying in school as long as possible. It can't hurt.
That being said, any degree or certification will only teach you how things work in the lab. That's not real world. Everything always works wonderfully in the lab. However, once you dive into some corporate abortion of a network, it's sink or swim. That's real world.
I have a Master's in English. I've been working in IT in one form or another for just over twenty years, most recently as the network/server administrator at a university. So, I guess my point is that it doesn't matter what kind of degree you have. The experience of actually working in the field goes a long way.
Best of luck in whichever path you choose.
SiO2
Easy answer...
The job market sucks right now... So, do the MS as fast as possible (1.5 years or less if you work hard this summer)! ... and the reality of the situation is that the MS is just an extension of the BS...
Just don't flounder .... finish it quickly!
Of course your professors think grad school is a great idea. That's what they do for a living.
I've been there and done that. Got my degree, went out in industry for five years, then went back for a graduate degree.
What I found is that I knew more about my field after five years working in it than the professors I had trying to teach me. And grad school ain't no place for people who want to argue with, or correct the misconceptions of a professor. Because as a grad student, you are their slave. Literally. So instead of a Ph.D, I opted out with a Master's.
And that Master's has been nearly worthless. No employers cared. Didn't net me a dollar more, or another gram of respect. What earns you the money and the respect is real world results.
Something else to consider. For some fields of study like English, the highest and best use of the degree is university professor. That's the top of the line. Is it for engineering? No, not even close. So... who are the professors of engineering? Why are they there and not out in industry making twice the money generating real results? What exactly do you think you can learn from these people? I'll tell you want they are good at -- writing grant proposals and running roughshod over grad students who often know as much or more than they do.
Think carefully before you decide to get that degree.
It's a fair comment, but not many managers can see 10 years ahead when sitting in the interview room. They want someone to fill the vacancy NOW, and there will be no shortage of applicants.
Sir, I am not going to repeat the famous Slashdot opinion that you must follow your passions or any such crap. The only thing I can say to you is Give up!Get a business degree no matter how much ever you loathe doing it! There are an army of programmers/engineers in the third world willing to replace you with just a tenth of your salary. Do you *really* want to be in a profession where your job is constantly threatened by these people?
I've been in the tech business for 30 years. I can tell you this much - you're obviously going to get a lot of conflicting discussion here, but keep in mind that's because each of the respondents has different job goals.
/. and you will see that your brain develops and learns faster while you're still young.
Generally the master's pays off in the long run. It can get you an additional $20k/year initial salary, but it's more common to see around $5-10k. So you may or may not see an ROI in the first couple of years out of school, and that's a goal you'll have to consider. But you will see an ROI if all other things are equal, and it will make a bigger difference in your future, everything else being equal.
More importantly, it opens doors. Many jobs at the supervisory level require or highly prefer a post-grad degree. This does vary by region, so doubtless you'll get arguments to this. Public sector, such as government jobs (NASA, state and federal jobs, military civil service, and public sector colleges, for example) typically require master's degrees for higher level positions. Notice I said "typically." Some require Ph.D.s.
So the question is more one of what do you want to do with your life? If you'd like to be in management some day, you better your chances with higher degree. It's much easier to get the degree while you're still in the college routine, and it's much harder to fit it in later in life. I got mine right after my bachelor's and my wife got hers 20 years afterwards, even though we were in college together. It took me 1.5 years to complete, and it took her 5 years. Evening and weekend classes, much tougher when you have a job and kids. Plus, read back articles in
Finally, getting the advanced degree will teach you things you won't learn quickly in the career field. I've had lots of young grads come to me with wonderful new things they had developed, which were really nothing new. How new can round-robin process scheduling be? I have to hand them a book and a reading assignment to show them that they're 40 years behind the times.
My advice, is much like the advice I've heard all over the place when it comes to getting a Masters. After getting your undergrad, go to work, and head to school part time to work on getting your MBA.
In my field we have so many Computer Engineers and Scientists it's ridiculous, and every year we hire some more from college. Everyone is looking to get a foot in the door, but most don't realize what it takes to get a leg up. Understanding how businesses work by getting the MBA will make you invaluable to the company and will open up leadership positions to you that were once closed off. Now when I say leadership, I'm not talking about low level management or even mid level management, but positions in which you might actually create change within the company.
Many of those same people who get the MBA, continue on to getting the PhD in Computer Science or Computer Engineering to solidify their hold within their field of expertise. Continue to strive for excellence in productivity, never forget education, and you will go far. It may not all be about the money, but it will make many of your other decisions in life easier to make when you're well off financially.
Unless you're in the top 5-10% of your class, you should go for the masters, however you're not going to like the reason why.
WSJ.com had an article on how the class of 2009 will be behind other earners for the next 15 years. Basically, it's like this: others in your field have been laid off and are more qualified than you so you'll have to settle for something less than you "deserve". Having settled, you won't land in get a great career advancing job. Career wise, you'll be continually 5 years behind where you "should" have been had you graduated in normal times. Unfortunately, according to WSJ, studies show that it will take you 15 years to catch up.
The article is about the Class of 2009, but with unemployment expected to be high again next year, you're in the same boat.
I'd say get a Master's and avoid the job market for 3 years if you can.
http://online.wsj.com/article/SB124181970915002009.html#mod=rss_Page_One
Aside from the work now vs educate now, there's another consideration. You'll never have this much freedon to choose again in your life. Every year out of school, you'll take on more and more obligations that limit your choices.
Personally, I believe that grad school if best served after a few years in the work force, but many people never go back to grad school because the obligations they take on (house, family, job...) won't let them.
Getting two years of experience right out of school is a great thing, but its easier said than done. A lot of companies would prefer the experience to start, but will look for someone else if you don't have an advanced degree or the experience. Its a tough job market out there and I found that my Master's degree opened up a ton of doors that were otherwise closed. I got numerous job offers because of my degree and your salary will be slightly higher. If you can get it out of the way early, either part time or full time, do it. Master's are the undergrad degree of our parents generation. Everyone has an undergrad degree and to a large part, there now relatively worthless for setting you apart from the field.
so the extra education would probably be lost on you!
if you weren't an idiot, you'd know for your first few years (i.e. when you don't have experience) the experience is worth more, and after that the masters would be worth more. you'd also know that now isn't the best time to be looking for a good job so it is a good time to stay in school.
most "real" jobs allow you an opportunity to continue your education and get the masters. if you can find a "real" job in today's environment this is a good path to take.
Why not work and get your master's part time. Usually you can get your company to pay for it, and you get the best of both worlds. You should also be getting experience now (internships, apprenticeships, etc.) Experience is vital and it gives you the opportunity to make important contacts when you are looking for your full time job.
By "better", do you mean how will you learn the most; or do you mean what will the administrative types (guess which path they took) who will pigeon-hole your career respect more?
/o Tape monkey get up, get coffee, tape monkey go to job... o/
Lead devs: Master + Experience (not necessarily work experience, doing personal projects or contributing to OS also works).
Monkeys: Work Experience.
Do you want to be a monkey or a leader?
The brutal truth is that you have to pass that first fence: HR.
From my experience, those people tick boxes. They will not look at intelligent things you've done (even when you're many years in the market) - they are just about qualified enough to see if certain keywords appear. Only when you cross that barrier can you expect someone to ask questions about ability and ambition.
This means you have to stand out. An MBA will do that, plus it will build that vital understanding of how a business actually works, which means you'll be able to translate between the two worlds.
Unless, of course, your aim is not to work in industry but in the academic world. In that case progress as suggested :-).
Good luck either way!
Insert
No. In fact I'd go as far as debating the value of a batchelor degree - I have one, and it's mostly irrelevant for 95% of IT. I've done well as a result of having one, because it looks good on my CV, and it set me up for meeting my first employer.
It's also given me an overview of a lot of concepts that my colleagues just 'don't get'.
But for actual hard experience? 2 years in the industry counts way more.
Get into one of these:
* Clean/sustainable/renewable Energy and transport
* Nuclear energy, quantum physics
* Aerospace - all the "rocket science" stuff
* Consciousness studies -- *very* fulfilling, "The Light Side of the Force"
* Genetics -- be careful not to work for evil pharma companies that use entire populations from third world countries as guinea pigs to test bio-weapons and cures for pandemics - eg SARS, bird flu - they release the virus and then sell the medicine at very high prices.
* Robotics + AI -- you must "guard not go to the Dark Side" (a la "SkunkWorks")
Make sure you don't end up being a zombie academic pedantic professor - so tie up with cool folks like MIT media lab or the Californian masters to make something awesome for common people to use too.
Google, Wolfram Alpha, The internet, the www, email, p2p (torrents), Java, multi-touch, holographic projections, video conferencing, flying cars. Lot of cool stuff to work on and get a PhD in the process too.
However, make sure you don't behave like a selfish evil dick and go work for the US Military Industrial Complex - you may have to give up on Robotics and/or Genetics to avoid that.
If you read Slashdot regularly and work for the US MIC, that's the best example of "conflict of interest" out there.
Work on something that eradicates poverty, hunger disease and social injustice en masse - a la internets.
Google, Amazon, Facebook, Twitter, and obviously open source and free software, and the web itself, all have levelled the playing field between commercial entities and talented individuals. They have brought the evil corp-driven media under check and have given hope and revenue to many peoples and many lands.
That kind of stuff. Really awesome stuff.
There was once a time that a scientist would brag about the fact that he worked on or led the team that made the most powerful machine, the most deadly bomber and the most powerful nuclear weapons system.
Contrast that with the wide array of opportunities to become famous as the guy who helped eradicate disease in Mexico, or the guy who made genome analysis and choice of genes available to the common man. You'll be stuff of legend for centuries, an immortal part of the history of modern science.
In one sentence:
Do something that makes TED invite you to give a talk on your field of expertise.
That's what you should aim for.
Bill Gates did not finish his studies... Linus did!
I've hired 40+ engineers over the last 4 years, and here's my take on a Masters degree.
Best option: combined 5-year Bachelor's + Master's program. You get more technical depth and a Master's on your resume for very little additional money. Your starting pay will be higher, and you can expect to break even in 3 years.
Next best option: 2 year Master's program at a top 5 or top 10 school in your field of interest. If it is not a top ranked program, or you're not changing your field of study (e.g. EE to CS or CS to Robotics) it's not worth the money.
Otherwise, get a job and work on your Masters part-time. Either negotiate an accelerated career track while you're working on it, negotiate a pay increase after you get it, or switch jobs for more pay / more relevance to your new field of study afterward.
-- Hiten
It really depends on the Masters itself - the course content and the experience you gain from it.
It may not be so beneficial if its entirely CS theory work.
My CS Masters was only an extra year added to my 3-year course.
The Masters I took included a module which was also real-work-experience.
This helped no end, it was vital in helping me secure jobs.
Employers want experience, graduates don't really have this aside from "well, on my course we did a project where...".
Everyone does development projects, they're not unique, they do NOT make you stand out.
If you're struggling for real-world corporate experience, pick an Open Source project and get stuck in.
[This is for 'real' employers, if you're going for a Graduate Course or Scheme, it's not so important....but still helpful]
BUT!
My Masters is a .NET Masters, and gave me masses of high-level .NET experience on top of my 3-years experience, that really helped me out in the real world and helped me secure a great salary.
The main thing I got from my Masters was the *experience*, both work experience and development experience.
There was no 'general' CS theory, only .NET theory related to Design and Development.
Hopefully have a Masters will also help me later in life when it comes to pay scales.
*Although in saying that, only 2 years out of Uni and I'm earning two to three times what other graduates earn....
So really it depends on the course!
Masters + Experience = Salary Ownage.
Also if you're in the US and planning to move countries, be aware that a US Masters is not always considered equal to Masters in other countries - just like with degrees.
Sometimes its >, sometimes .
When I read the "article" (why this is not in "Ask Slashdot" in the first place), and my eyes were rolling at 7200rpm.
The person apparently can't clearly describe the problem. What is his goal? What kind of "experience" is he trying to get? Did he check if there are any jobs available that he is interested in and qualified for? What is the result that his friends use to judge "better" or "worse" of his options, and how does it correspond to his own goals. Last and most puzzling, what are the actual options he believes he has? Is he expecting that he will work for less than two years after getting Master degree? (And then what, die? retire? leave Computer Engineering forever?)
I assume, the actual question was supposed to be "Would the next two years be better spent working on Masters degree or should I jump out of school two years earlier and go looking for a job?" Obviously if the optimal answer for everyone was "Just get a job two years earlier", no one by now would have Masters (or Ph.D) degree, and if such universal answer was "Get a Masters degree", there would be no people with Bachelor degree anywhere outside of school. Therefore there is no point asking without providing some explanation of goals, criteria, or other details that give an idea what would make either choice preferable over the other.
And if a question was asked in such manner I would try to answer it. However faced with a failure to state the problem clearly, and lack of understanding of the basic logic behind it, I can make only one recommendation:
Find a job in something that has nothing to do with engineering and computers.
Contrary to the popular belief, there indeed is no God.
Find a company that will pay for your masters degree. Some will even give you time off.
Where I differ from the above comment is that I don't think it's harder to get back into learning later in life. I went into the work force for 10 years writing software code in a decent environment and discovered I loved the process. Now I'm working on my Masters in Software Engineering, half of which is being paid for by my company, and finding it extremely easy. In weekly discussions, I have all my work experience to contribute to the class, which earns my high marks. When I write papers, I have the additional insights of having been in the trenches, and when I go back to work on Monday morning, I have new ideas to bring to my coworkers. It's been a fantastic experience.
Get in the workforce now, but make sure you get into a good working environment. Don't be afraid to look for work elsewhere if you end up with a company that isn't following an established SDLC. Work experience is important, but make sure you are getting the right kind of work experience, where you are perpetually challenged and advancing in knowledge. Then, after a few years, you can start taking two classes a quarter towards your Masters and earn one in two years.
And then you can start trying to figure out what interests you for a Ph.D. : )
i ~ Celebrating Science, Cyberspace, Speculation
It probably won't make any difference immediately but long term it does put you ahead of others. I'm doing a CS degree part-time while working and the full-timers are mostly foreign students from countries like India. If a Master's degree at a respected uni is something people who want your job are getting, then I think it's a good idea to get one too. It is probably worth choosing your master's carefully and looking for one that is at least part research based. Make sure your research relates to an area you want to work in and you do really, really well at it. It might not get you in ahead of Phd's but it could get you close enough without the years of research.
But in English Lit. Or Music. Or Math.
You are welcome on my lawn.
Oh, just noticed the rest of the post. I thought you wanted to play golf at the Masters tournament. Silly me.
Well, if you can't play golf, then keep going to school. It puts off the real work to some later day.
This was my plan but with the downturn it's a hell of a lot harder to get a job straight out of college so I'm thinking of going for a masters and hoping that either it will help me get a job or that things will have improved a little by then.
I was lucky enough to get a fellowship from my company when I first graduated. I had some intern/co-op experience and waited a year before getting into a Master's program. Most companies have a reimbursement program for advanced degree course work. You may not have enough experience to really determine which path you should be on for a good future. Best to take a year working and decide if you really want to do what you are already doing even more or if there are changes you want to make in that path.
I'll never be as good as I want to be. I can only be as good as I am.
I am pondering the same question lately. I have a B.S. and I have 10+ years experience. My salary is ~10-15% above the norm for a senior level Linux engineer in the area where I work. What I have found is that many companies use a table to calculate what your salary/hourly rate should be. In my case, because I don't have a Master's, I have maybe 10-15% more room for salary increases before I reach a proverbial "cap" on how much I "should" make, according to the table. My options are simple: 1 - get a Master's and "qualify" for higher salary 2 - branch out on my own and go into full-time consulting 3 - accept my fate and wallow in mediocrity I am leaning towards option 2 above, but I have done some casual inquiries with regards to number one recently. Number 3 is out of the question. In conclusion, if I were you, I would get 3-5 years experience and make a plan NOW for going back in that time. Stick to the plan and by the time you have the Master's, you will have some experience to back up what your resume says you know. Hope this helps.
Benefit/not depends on many things: 1) Your values 2) Your employer 3) Your career path So best to get both, work experience while studying masters, that is. You get also extra points because you look so hard working while doing both same time. Also, as many people have pointed out, you might benefit a great deal from it later. Check out the management ladder in many companies, many times there are not a single guy without masters degree.
A Masters degree is worthless in industry. A PhD is valuable but primarily only if you are staying in academia. My company pays a miniscule premium to new grads who have masters and it doesn't come close to compensating you for the two years of lost career. Any difference in salary will disappear within a few years anyways. Practical experience is more valuable. So, unless you are aiming for an academic position, go out and get a job.
Own it. Built it. And Sell it. When you succeed hire others to do the pieces you do not enjoy or have time for anymore.
If you are hired to do these things, for others, you can spend the rest of you life working for someone else, Or not. Based on the success of their dream not yours.
Get the Masters. You're used to living like a student -- poor and with homework. After you've been working for a few years you'll be used to living with money and free time.
You're still used to taking tests. You still remember the mathematics.
I found it is very hard to go back to school after you have been working. Getting my masters involved working full time and taking classes, so I spent a huge chunk of my free time doing homework and writing a Thesis over a period of years.
The only advantage I had by working first and returning to school was that I had a much better view of why school was important and what I wanted to get out of it. Being an older student also gave me an advantage understanding the perspective of my professors.
As far as your career goes, if you ever plan to get a masters, getting it earlier is better than getting it later.
By the way, when I review resumes, I count a masters degree as two years of experience towards any time we required for the position.
Extrapolate from there...
Yo dawg, I heard you like the Ackermann function, so OH GOD OH GOD OH GOD
The BSEE's I've interviewed earn about $5k less than the MSEE's. I'm pretty sure that MS cost quite a bit more than $5k in both time and tuition but there are certainly people with masters degrees that are willing to work for that.
Two years of school costs you 20K AND you miss out on two years of income, totaling 140K (ish). If your masters then gets you 65K instead of 60K, it will take you 28 YEARS to recover that initial cost.
As an ex-University teacher, I am not surprised that your academics favor straight-through, do not follow this even if you intend to become an academic. We already spend too many years learning, or rather being taught, and most need to learn to apply what they know.
Unless you are very young or prodigy material take two years out between first and second degrees. Be very careful what you choose to do in your masters, since, unless you are a frustrated pure-mathematician there is a lot of pseudo-mathematical cruft in masters programs.
One advantage of the time out is that, hopefully, you will find out what interests you.
Do you ant cold hard cash ? Well make your choices in the real world, academia will might even harm you. Now you have an all round foundation. Get some experience and move forward and network with $ as your guide.
.. academia is the way.
You enjoy programming both the real world and academia can give you that.
You want to explore something specific
G
The answer is yes and no. A masters likely wont pay off right away at the lower levels. A masters will really start to pay for itself when you get into the highly specialized jobs and management (if you ever go that direction).
If it were me, I would wait until you've been in the job force for a few years to go back. That way, you know exactly what you want to get a masters in, and also your company may pay for it. Why pay yourself when you can easily find someone else to pay for it.
FYI, my opinion might be a little bias. I am currently working on my second masters degree.
I haven't read the whole thread, but here's my take:
Do a Masters if you want to learn more.
Go straight into employment if you want to earn more.
Personally, in 2 years time, i'm going to be doing a Masters or a Ph.D, simply because I love learning - contrast that to a friend who left this year who suggested not even doing honours because all she wanted was a decent paying job.
Different routes suit different people.
There's two ways you can achieve this:
1) The lazy method: Look for a job that will fund you and give you time to do your masters
Pros:
- Cheap (although possibly offset by lower pay vs. method 2 below)
- Easy
Cons:
- May have to accept lower wages
- May be tied to company for x number of years
- May be more competition for such jobs
- May be harder to find the job you want that also supports this
2) Fund it yourself in your own time and also work full time still
Pros:
- Having the commitment to do it in your own time will put you ahead of other masters students at CV/interview time
- Not limited as to what jobs you wish to apply for/choose
- Will not be tied to the company you work for
Cons:
- Requires you to be good at managing your time and money
Don't limit yourself to one or the other when you can do both, when you go for interviews mention you're interested in doing your masters and ask if they would be willing to support that if you were successful in getting the job. No company you want to work for would look down on you for asking and showing enthusiasm to continue learning.
But more importantly, ask what masters you want to do and ask if you enjoy learning. You need to do something useful and that you will enjoy else there's no point. It's easy to overlook what qualifications bring you - it's not just a peice of paper, you have the chance to get skills out of them that make you a better employee. If you're doing it for the extra peice of paper it's not going to get you much further in life than if you didn't have it. If however you do something you can learn lots from and you take the time and effort to figure out how to apply and use what you've learnt then it'll get you much further in life. This is why I chose mathematics because as a subject, it has so much scope for you to go and figure out how to apply the techniques for yourself and come up with truly efficient, accurate and innovative solutions to problems that often otherwise are just left unsolved or worked around with tacky, half arsed band-aid fixes.
I have always thought that experience will actually lead into making a better decision as to what grad degree one should pursue. In this economy, your best bet is to work through the last year of undergrad in your field of study, maybe take another year of work after school is done to make decisions as to in what and where you want to pursue a graduate degree. In any case, a Masters does NOT assure you better pay these days and experience will always be a must for ANY kind of well paid job.
I did Computer Engineering and chose to undertake a Masters. Cost me 8 years of Uni all up (4.5 for the undergrad, 1.5 for working as a research associate, and then 3 for the Masters - in that order obviously).
During my Masters I did extra research associate work, as well as tutoring/marking and other Uni work. During the final year of my Masters I spent time looking for jobs. What did I learn? The industry doesn't appear to give a shit about the extra study, only experience matters. I thought that the Masters would show that I was prepared to forgo the easy path of getting a job in the persuit of hoaning my skills, but as it turns out, the private sector cares more about industry experience. I thought that once prospective employers saw my Masters (or at least Masters in progress at the time), it would be a beacon for attention. Didn't seem to turn out quite like I expected.
Eventually I got a job working in IT (go figure, but at that stage I was pretty happy to get something at least), though I'm FINALLY on my way to working in the defense industry as a proper engineer, once my clearance comes through. Perhaps the Masters itself will make more of an impact in the long term, but it sure as hell didn't help me in the short.
That's my 2c.
I have been working in IT at multiple levels for 10+ years now, and I just recently finished my M.S. in Software Engineering. I cannot stress how much the work experience assisted me in getting through the program and giving me a better way to relate to some of the course material.
Without a doubt, I have a better understanding of why some of our wins in the workplace were wins, as well as why some of the failures took place as well. For me, the context of the workplace made the degree worth it.
From the payscale side - I am an excellent developer and architect in the area where I work. The MS is a blurb on my resume that will probably never get me another dollar in salary, but I know it does make me better at my job - indirectly, I am sure that I will see a benefit down the road. However, do not expect anyone to break out a checkbook and start asking how many zeros you want in that salary just because you have the degree. Get the work experience first. Make sure you love the field, because it will rarely love you back. Then decide to invest another two years of your life in another degree.
I personally know a CIO of a major national retail company that only has a High School diploma and a few college classes under his built. He built his entire career on experience and being the best at I.T. He makes over 6 figures and gets bonuses and raises every year. Book smarts aren't bad, but they aren't the end all be all that the academia makes it out to be.
Doing a MS degree can give you a couple years to specialize in a specific area of computer science like graphics, HPC, AI, compilers, etc. This can open doors for you when you get out in to the real world. Its like having a couple years experience, and you can focus on an area, so you aren't stuck looking for entry level jobs.
Well...
In a bad economy, you might as well proceed with a masters or even a Ph.D. The alternative is to be outgunned by experienced people who will beat you almost 100% of the time.
When the economy is cold, even a Ph.D will get an endless stream of excuses instead of job offers. In such a climate, school is a good option.
When the economy is hot, even a non-grad can get a job and use work experience to propel a career. It worked for me, and I have been doing this for over 20 years. I am probably not the wealthiest Slashdotter, but could easily be in the top ten. Timing is everything. Some very famous people quit college because it was the right time for them to start their careers. Perhaps you have heard of them: Bill Gates, Larry Ellison, Michael Dell, Steve Jobs.
Don't get me wrong; a BSCS is quite helpful in the computer industry. The MSCS is primarily for college profs working on their Ph.D.
In the world of direct computer work, there is no degree that places you ahead of than those with solid experience and references. Do not confuse the HR screening process with the actual hiring process. HR simply thins out the applicant pool. They generate excuses, not offers. There are ways to bypass HR, but not the hiring manager.
To provide a counter-argument, my wife has a BS in ME _and_ a MS in ME, which she got in rapid succession. Her work in graduate school is _extremely_ relevant to her current job, which she got shortly after finishing up school. Your generalization that intern/co-op experience isn't good enough is almost hilarious - you don't think employers care that you worked a few summers for a major aerospace or electronics firm? I rather think that they do, because those references can be _very_ helpful in determining the quality of an applicant.
Now, let me provide another bit of advice from personal experience: going back to a good school full-time once you've started working is extremely difficult at best for most people. I'm not saying it's not doable, but if you've got a spouse and possibly kids you need to help support, the option is difficult to exercise. _If you want a graduate degree, best to do it up front._ You may not have the chance later.
Personally, I didn't care to go for an MS in CS (or an MA in Economics), but I did wind up going part-time for an MBA. It is not a ton of fun to back to school at this stage of my life, useful and interesting as it may be.
Plausible conjecture should not be misrepresented as proof positive.
Why can't you do both? Graduate and then find a job. Once you've got the job, go back for your Master's degree. If you're with a larger corporation they often have tuition assistance programs (which require you to stay with the company for 2-3 years after getting your degree otherwise you have to pay back the money). You may not have much of a social life, but you're getting real world experience at the same time as furthering your education.
And if you want to get your Master's, don't wait long to do it. The longer you wait, the harder it is to go back.
"Action without philosophy is a lethal weapon; philosophy without action is worthless."
For the record: I've got a BSEE myself, working on the MBA.
The thing about master's degrees is they're generally most effective when you have a fair idea about what you want out of them. Are you looking to broaden your expertise? Focus on a particular topic? Change careers altogether? That will help you choose the right program (school, full-time vs. part-time), the right course of study, etc. You'll be much more motivated and enthusiastic, and you'll get more bang for your buck (and it ain't cheap).
Go get a job, earn some money, work a bit (and don't stress too much about the 'harsh economic climate'). You'll learn a lot about what you want and don't want in a career, what type of work makes you happy, what management style and company you prefer, etc. You'll also have some fun building your life and putting some money in the bank (it's quite rewarding).
Look up in about 2-3 years and see what you think of graduate school at that point. See where you really want to go/what you want to do. Most of the engineers I've known get master's degrees to manage groups or move into senior or even principal design positions (though the later leans more towards a PhD, in bigger companies). Some have done it to shift industries (e.g., telecom to biomed). Depends on what you're after, and you won't know that right out of the undergraduate gate.
Try and get it done before marriage and kids/partnering up. As a collegue once told me, three drinks down: 'changing the world is doable after a wife and kids; it's just a helluva lot harder.' You'll have more energy and focus, and it's easier to live a poor grad student's life when there's no one else to be responsible for. If the timing doesn't work out that way, don't despair, just talk it out with the wife/partner.
Above all, just enjoy it. Life's too short to stress it overmuch.
A masters would be nice on the CV and does up your value, but I agree with some of the commenters - long term, experience is worth about as much as a masters, plus, you're gaining work experience and earning money along the way. This is of course assuming that there's a job waiting for you after your course finishes. I'd had a discussion with HR about salary calculations recently and was informed that a 2 year masters course from a reasonably good univ is counted as 1.5 years of work experience for the salary calculation in our organisation. If it's an A rated institution it goes up to 2.5 years + premium (upto 30%) - at least this is what I understood from the conversation :)
A lot of wonderfully super-geeky people get into computer science because it's fascinating, not for the paycheck. The paycheck is an AWESOME byproduct. One reason to do the MS is because you love what you do and want to know more. A good MS is bringing out the heavy duty geek tools. Don't settle for less.
Get a masters. I have been in the industry as an engineer for 12 years, and last year started going back to school part time for my masters.
It's true that experience is huge. I got my first job with no degree at all, and was making around 75k (in a city with an extremely low cost of living) with only a couple years experience and no degree until I decided to finish it up.
But the thing I learned in all this time is that there are certain jobs that will just never be accessible to you without an advanced degree. And if you're anything like me, the longer you're in the industry the more you'll aspire to these jobs, because they are the ones with the really interesting work, working for major corporations and designing cutting edge things.
Most jobs without an advanced degree will have you designing things that have already been done 1,000 times before, but they just need a slightly customized version for their purposes. Or you'll be thrown into a project that's already been mature for a long time and you're just extending it. These are all great, and it's definitely the way to go right off the bat for experience, but after a while you're really going to want to be working on the cutting edge technologies, working on a project that is the first of its kind, or really novel in some way. For >95% of these projects, you flat out just need an advanced degree. And it's not just because they only recruit people with advanced degrees (although the more elite the job, the more that will be the case), but no matter how much you learn on your own there is a certain aspect that you just lose out on without having learned the material in a formal, academic setting.
I was programming in 4 languages before I even got to my freshman year as undergrad, had started playing with electronics and programming when I was like 10. I still keep up on my learning by reading all the books I can get my hands on. But still, in my first 2 semesters back at University working on my Masters I've learned a TON. I'm only my second semester in and already I know it was an excellent choice, and will really be worthwhile in the end. If not for my job, for myself.
Absolutely go for masters, but consider part-time while you are working. I started masters in my second year at work and it took me about three years. It was pretty hard but it was very beneficial in every way.
I went through the same thing a couple of years ago right before I graduated. I can't tell you what is best for you, but here is my experience.
I decided to work full time and get my Master's part-time starting the next fall. As a bonus, the company pays for it so long as I get a B or better. I figured it was a pretty good deal: work experience plus an essentially free Master's degree.
I, too, majored in computer engineering as an undergrade and am doing computer engineering for my Master's because I wanted to learn more about it. What I've discovered, though, is that graduate school is nothing like undergrad. You might think "hey I've been at this for four years and it's not so bad, I can do two more." But as a grad student, I have spent most of my classes reading academic papers, usually about some really dry and boring stuff. So far I've had no labs and only one class (a math class) where I actually had to solve problems that didn't consist of parroting back points from a paper or making unsubstantiated guesses about things. Plus, as a part time student at a university's satellite campus, you will really get shafted in terms of course availability.
Finally I have to admit that part of my motivation was to be more competitive a candidate should I decide to switch careers. I can't say if this has or will pay off since I've only had one job though.
Bottom line: as many have said before me, I think you have to really want to learn more to do your Master's. I am still interested in finishing my degree and learning more about computer architecture, but it is nothing like I expected. Work experience is invaluable; I have learned a lot in about 2.5 years on the job that they don't even touch in school.
a few things. - What school are you planning to do your Masters from - Is it a place where you will have a chance to learn something you don't already know - What job opportunities do you have available - Is it at a place like Google? Then take the job - How good do you think you already are in Computer Science (or how much do you think you have learned in your Undergrad) - Do you want to concentrate on something special like linguistics or NLP? Then a Masters in a school good in these disciplines may make sense (if you do a Masters Thesis, even better) Hope this helps.
Life is about being a Phoenix!
Ultimately, getting a masters or not depends on what you want to do. While statistically you'll make more money over your career don't do it for the money. People who do it for the money are typically miserable. If you want to be a coder who implements existing concepts then a masters is not necessary. If you want to be more than that then it will be necessary at some point (although not necessarily right away as others have noted).
While a good employer will pay for your masters degree most universities (especially the decent ones) will pay you to get a masters as well in the form of a stipend. It's not enough to be sippin crystal, but typically around $25k/year with them covering tuition which if you're used to being a student is plenty to live off of.
If you're looking for a litmus test of should you get a masters here's what I think it is. Did you like assignments in school where you could easily find the answer on the net, or assignments where there either wasnt an answer or it required you to figure it out. If you liked looking the answer up don't get a masters otherwise it might be for you...
PS To acknowledge any existing bias I may have I have a masters....
In the business world I have work individuals with any higher degrees Master, PHDs, etc are not typically liked.
I have worked along a computer guy with more education than most doctors... he was very slow to work with. He took for ever to make a decision as he spent way to much time analyzing each possible choice. He may have had the papers but could not make good business decisions in a timely manner.
I have talked to lots of executives and most hold the same opinion. The highly educated people are good if you are doing research (R&D) type of work or if the client requires it. Other than that they take longer to do the exact same task as someone with a lower education (3or4-year university/Collage degree).
So if you want to be a research or a teacher go get your PHD or Masters. In the computer business development world it will not really help.
Leaving college is a major change in your life. It is likely all you really know about in any detail and change is a bit scary. I saw this influence several people I knew to stay in school. Think on this and be sure to understand your motivations.
Many of the posts I skimmed were addressing the effect of having a master's degree in a large company. Do you *want* to work in a large company? Small companies are going to be much more interested in who you are than what letters you sport after your name.
Steve
I graduated with bachelors in Computer and Electrical Engineering with a master's in Communications. I found that once I was out looking for a job no one cared about the masters but the second bachelors really seemed to impress. Now that I have been in the industry for more than a couple years, the general consensus is that masters are too specialized and aren't usually worth the money to pay them.
Wouldn't this be simpler with a poll? I agree with those that said a technical Masters doesn't get you much, fresh out of college. Find a good job, then (after a year or two) get them to pay for your Masters. You will be getting something for nothing (perhaps obligation to work a certain period), and you'll have time to consider exactly which Masters degree you want. I waited 10 years after my BSEE, and I wish I hadn't, but I'm happy that I realized an MSEE is not my preferred career path. I got a MBA, and I think it was the best choice :)
Since you have not told us what it is your really like we cannot give you advice that is appropriate to your likes and needs. With that said here is some general advice which is worth exactly what you have paid for it.
I have made 6 figures for more than half of my career, have no degree at all, am in and have been in management (line and executive) and am a hiring manager. I have also worked for majors like IBM/ATT and minors so small you have never heard of them.
1. I strongly suggest you finish your undergraduate degree. I do not have mine and have had to fight much harder than those around me to get where I am. I will hire someone without a degree but they have to work very hard to prove themselves to me and/or need to have been in the military.
2. Graduate degrees hold no weight in in initial levels of hiring unless you are at a very large company. For example at IBM if you had a graduate degree in anything they would hire you. At my current company it gets you no points. So your mileage will vary according to the job and where you are looking.
3. If you would like to eventually be in management get a graduate level business degree. This will put you on track faster than any other. Passably an International business degree. Or get your law degree pass the bar and you can write your ticket to guaranteed employment starting 20 to 30k over your peers...
4. If you want to stay technical (this will eventually limit your income potential but you can still make a very good living [AKA about 200k right now]) then do the graduate degree in your technical field.
5. The economy is not that great right now so if you can afford to stay in school do. And when the economy picks up people like me will be looking to hire you.
6. No matter what you do get some experience in your field. This will get you your first job faster than anything else you can do. Join a team creating some open source software and write some code in a team environment. And yes even if you have no interest in coding do it.
Most of all have fin and good luck!
I think that perhaps you're asking the wrong question. Money counts, you can't pay the bills with fairy floss. But happiness counts for something.
I'm 28 and graduate with my PhD in a week. You can't wipe the smile off my face with a sledge hammer. I wear my bonnet around the house.
Some random advice:
- You should compare industry certification with academic qualification. Knowing ~why~ and how routing algorithms work the way they do counts more than knowing what commands to plug into a device and calling support in India anyway.
- Irrespective of what anyone says APPLY ANYWAY. But for PhD. If you don't get PhD, departments often offer masters. If you apply for masters, you might not get it. Once you're foot is in the door, options are open, you can trade up (or down).
- Apply for scholarships, you can't loose.
- Seek a supervisor for hons/masters/phd early in third year. You'll get a better name by being known earlier. This counts when applicant rankings are done.
Ultimately:
Seven years of stress. Expensive.
Traveling the world to present at conferences. expensive.(Ok, not really a negative).
Slogging it out in a job on the side to pay the bills. expensive.
Spending far too much time away from friends and family (and the girl). expensive.
But.
Having all arriving mail and correspondence land with 'Dr.' in front of your name. Fucking priceless.
Telling your old school teachers you have a PhD and asking your old class mates who thought they were better than you to call you 'doctor' at the 10 year reunion. (You just can't buy this). Yep. Fucking priceless.
Making a meaningful contribution to the advancement of science and society. Fucking priceless.
Long after you're dead and buried, people have upgraded to better software and tossed out your code, you're thesis will still be in the library and papers still on the web. Priceless.
In the end:
Do what you think will make you happy.
I am not sure the comment was directed at the manager's log term outlook, but rather the student's. Put differently are you going to be better off in 10 years with a Masters degree, or two extra years of experience?
I say go to work immediately, and work on a Master's part time, then you get the best of both. You also get additional time to find a MS program that fits your career path and interests, which will make the program all the more rewarding.
I've been working IT professionally for the past fifteen years. I started as a junior level programmer and moved into customer support (outside) doing systems integration as well as programming and configuration. I went for my master's but - due to the fact that I was flying at least twice a week - never finished.
That was 1998. Now - 11 years later - I don't regret not finishing. I am now a departmental-level manager in charge of some 30 staff members and an $8M budget. When I go to hire people I don't really look at their degree. I want to know what they can do and how well they apply themselves.
What I understand is this - a masters works great in academia. My wife is a professor and a teacher (elementary) so she hears about the degrees all the time. My area finds a degree a great starting place but something that loses value after about five years.
In fact, my boss' boss has no college degree. He got the job not because of his degree (or lack thereof) but because of his skills and what had had done previously.
I actually don't even have a CS degree. I have a degree in German with a minor in PolySci. Does it matter? No. Keep in mind that I graduated college in '92, when PC's were still mostly running DOS and most business computers were running either mainframe, unix or VMS.
The Kai's Semi-Updated Website Thingy
What would you be learning to get your Masters degree? How quickly would you learn it? How long would that degree be relevant. I have a B.A. in Computer Science, received when COBOL and Pascal were the languages of choice.
Working for a company there is no time frame or pace on learning something new, it's just ASAP. Or sooner if there is an approved project.
Android 1.5 OS just came out, iPhone 3.0 OS is coming soon, are there courses for these? Even if there is, it would be a semester long course? In a company, taking 2-3 months to learn something new is unacceptably long. 2-3 weeks may even be considered long.
A masters degree that would be worthwhile would be one geared more towards business and/or management of information systems, not technical.
I had a very wise college english teacher once stress:
"If you're going to get a masters or a Ph D. For the love of God don't pay your own way through it! There are piles of companies willing to pay you to get them!"
He even had a little jingle.
You don't pay them for your masters. They pay you. They pay you! Or else... you don't... go through!
Seriously though. As an engineer with a BA in CS I currently have 10 years of real world experience under my belt and am nearly complete with my 100% paid by employer Masters Degree in CS.
Once I land it I get a manditory raise!
As it stands I am already making more than folks around me that came in the door Masters Degree in hand. While the Masters is nice the real world experience is frankly more valuable to most employers in the near term.
If you're good at what you do and the company is worth their salt. They'll be more than willing to invest in you furthering your education.
Thing of beauty!
I have a combined 10 years doing everything from it support to systems administration. I just happened to be in the latest rounds of layoffs from Microsoft (dont hate me). My problem is I have no higher education at all. I am kinda stuck on going back and getting my 4 year degree, hopefully in 2.5 years, or trying to find another good paying job in this economy (Raleigh NC area). What do you guys thing?
Sad thing is I registered to go back to school part time a week before the layoffs.
5 years of experience and a BA/BS on your resume/CV will be much more valuable than a 30 year old man/woman with 7-8 years of schooling and only a couple of internships or part time jobs.
From what I've seen (11 years experience, BS, working on my MBA part time), a masters will really only help if you're looking to jump into management. I was able to get into a management position by virtue of pursuing my MBA, along with my broad range of experience. Heck, my company is even paying for the MBA.
Later, if you decide you want to get into a management position, you can always go back to school for a MS or MBA.
I'm not cool enough to have a
But then the manager the guy would have to work for would want to interview the OTHER guy, too.
I've interviewed too many people with a master's and no experience who couldn't write a fizzbuzz. But then, I've interviewed people with a master's AND experience and couldn't write a fizzbuzz.
A master's may not be a badge of disgrace (went back to school because he/she wasn't doing well in the workplace and thought "I know! I need more school!") but it's not a reliable mark of excellence either.
It is an unfortunately reality that changing employers at a reasonable pace is the only way to get yourself on a good raise schedule.
Get out in the work force, get your experience, and let your company help pay for your masters. Many large companies have a master's while you work program.
Finish your degree, work for a while, then do your masters. Why? So you have field experience before you do your masters.
Why is this important? Because as a norm, you are a less attractive candidate if you are over educated for your experience level. You are in reality a paper Tiger, you have two pieces of parchment that say that you have spent a lot of time in school, but the only practical experience that you bring to your new employer is whatever little you could pick up during school.
Your competitors, on the other hand, got their bachelors degree done, then worked for a few years, and finally got their masters done. Most of them got their masters completed while still working.
When I, either screening resumes or running the interviews, compare you to them, what I see is that for basically the same amount of money I can get an employee with the right education and with some relevant experience, instead of a guy with just the education and still needs to be trained on the job.
Education is awesome, get as much as you can get away with it, but pace yourself. Your school probably isn't going anywhere. Your masters program will be there for you whenever you are ready to go back to it.
Pedro
----
The Insomniac Coder
You'll get different benefits from each. Right or wrong, having a Master's degree, especially from a top school, will get some people to consider you for positions that might not otherwise have done so. It's like a little asterisk on your resume that says, "This guy is really smart" in a way a B.S. just can't. That benefit will stick with you the rest of your career.
That said, if you're only considering the situation three years from now, i.e. right after you would earn the M.S., then you're probably better off with the two years experience. All else being equal, "two years experience + B.S." probably beats "0 years experience + M.S.". But if you consider the situation 10 years out, the difference between 10 and 12 years experience is much smaller, so the M.S. would probably count for more.
The other thing to consider is whether there are aspects of the M.S. that aren't related to "career" that might motivate you to go that route. Maybe you just enjoy being on campus and being a student? Maybe you just enjoy the material, and would find it intellectually stimulating to explore some advanced topics? Maybe you really like to surf, and two years at UCLA would let you get in a lot of surfing? Etc.
Years ago, I asked the same question and my Manager at the time made a comment to the effect of "Once you've been in the industry for a couple of years nobody is going to care if you a Masters in Computer Science (I was going to to do it part time) Why don't you thinking about widening your experience and get a Masters in Business Administration"
Best thing I ever did, gave me an excellent base of business knowledge that I still apply today as an Enterprise Architect.
I am working on my M.E. degree and my C.E. at a highly rated university. I figure the two degrees allows me to be highly flexible and they fuse together well. A downside is that it takes about a year longer than getting a Masters.
How does this compare to say getting a masters in either one of these degrees?1
It depends on which route you prefer. If you prefer to practice in your field then I would say go for the work experience. If you academics, or want to become a professor go for a Masters (and get an MASc). I'm not sure where you're from, but if you have a professional designation requirement like Canada (where I'm from), and wish to practice sooner rather than later, then I would say get the P.Eng and go for a Masters later on.
If you get that masters in the evenings, then the question is Candidate A with 10 years and a MS, or Candidate B with an MS and 8 years. If the entry requirements are a BS, you may as well start working. Unless, of course, you're independently wealthy already and are just looking to fulfill your personal goals for challenging work and don't really need to worry about a "career" or paying bills short term. In that case, go get the degree.
Is it just my observation, or are there way too many stupid people in the world?
In my case, going for a master's let me get a 30% increase in pay over the job I had with an undergraduate degree, and to work in a field more closely aligned with my interests. I consider this to be a good use of two years of my time, but I was also under a sizable scholarship (about 25% of the undergrad degree pay, tuition waived.)
It really depends on how research-oriented your job is going to be. If it has a lot of algorithmic work, then there are probably a lot of former academics in the company who would look highly upon a graduate degree since they have ones themselves.
Contrary to others, an MS in Computer Engineering directly translated to both a higher job rank and salary over people hired at the exact same time at the same company. Regardless, I got my MS because it was a 5 year BS/MS program, and I felt it would be something additional to help set myself apart from everyone else. Used to be a college degree set you apart, but I didn't feel that was quite the case anymore.
On a more practical note, consider the job market and economy at the moment. If you believe things will improve, then why not hide out in academics and learn more, especially if you think you'll want a MS. You don't want to come back in 5-10 years, have to take the GRE, and change your lifestyle from that nice cushy salaried life to going back to ramen. Plus you could have a family by then further limiting your options.
As for job experience, co-op education and interning are great for that (but you may be a bit late). What you don't want is to graduate and waste a year looking for a job. Or getting a job an getting laid off a year or two later. I, for one, would not want to be entering the job market today.
Speaking from personal experience, I had neither the grades nor decent research experience from undergrad to garner me a decent job (or any job for that matter). All that changed during the course of my Masters. Employers like graduate degrees and are likely to pay you more and offer perks like covering moving expenses. I emerged in 1990 when the tech job market sucked. In two years time, things should be improving once the dust settles from the obscene corporate taxes and companies need people but are less willing to hire undergrads than they are grads.
Even fresh out of school with a B.S. you still have no experience. When applying with a B.S. you'll still be competing against other people with experience.
Ph.D. is a different deal than a Master's. It does carry some clout in the job market. It's not really worth (in $) the time you'll spend getting it but it could give you a wider range of career choices and might get you slotted into a different level than you'd be at with a B.S. (I speak from some experience, having been on the hiring end of an interview hundreds of times).
In general, and this is based on over a decade and a half of direct experience as well as those who have worked with him regularly re-validate this, those with Masters are rarely as valuable as those without. Those with PhD's can lead to down right project disaster. The reason being a general default attitude that additional education trumps direct experience, and the idea that a better, more complete idea is invariably the correct solution.
In the product-company space there is likely value, but everywhere else that I've worked it has been a detriment to the team and ultimately to the individual. Certifications are of better value from a career perspective. That's my 2 cents.
While I was finishing my bachelors in EE I was having this exact same conflict. One of my professors told me that if you're a good student that generally gets good grades you'll probably eventually want a graduate degree anyway. You can do it now while you're still in school mode or you can wait until you're trying to do the full-time job and family thing on top of it. It's easier to to do now.
Having a masters degree does make a difference. Anyone who says otherwise is fooling themselves. I've been out of school for 5 years. In a recent job interview I was up against a guy without a degree but he had 20 years of experience in the field. I didn't get the job but I was at least able to be competitive. Without a master's degree, I probably would not have even been interviewed.
When in doubt, do it. It can only help.
A Masters is not going to help you get a coding job. A Master is going to help you get a research job.
There are companies out there that do research in the field of computer science -- large companies that might have a dedicated research lab or two, or small and mid-size companies that can be fully dedicated to research.
So figure out what you're interested in:
1. Strictly coding? Go out there and grab job experience. Maybe look into some sort of applicable certification, by Sun or Microsoft or someone. Get OpenSource experience. Code recreationally.
2. Research? Look into a Masters or PhD. Wondering how to find companies that do research? Google around for institutions like NSA and DARPA that grant research contracts, and see what companies are winning them.
3. Academics? You'll want a PhD -- unless you're interested in teaching below the college level, in which case you'll need to get teaching certified.
4. Management? A Masters could help, but so could a MBA (try one with a specialty in IT). Or work you way up the food chain (you'll have to do that anyway) and look into some sort of program management certification. Google around for something like 'PMP certification' and you'll read about them.
The good thing is you don't have to decide now. The better thing is, you can change you mind. I thought I wanted to do academics, did a year of PhD program at Georgia Tech, decided it wasn't for me, then decided I wanted to do research, joined a small research organization, then 15 years later decided to go back and work on my Masters. Even better? Where I work is paying me to pick up my Masters part time. I might also work on picking up my PMP certification, since I seem to have most of the requirements anyway.
Just remember, you can change your mind later.
Try to get a job that will pay for some portion of your MS. That way you don't miss out on the experience at work, and you get the MS. And, sorry, I hate to break it to all the naysayers, but, it does matter. The MS will open up doors for you **but you have to leverage it do so!*** You can't just bang out an MS and expect offers for 150k to be flying your way, you need to do the work. You need to market yourself, make sure you have the right real/technical skills, and then most important *go somewhere that values the education* People make the mistake of getting the MS and then going somewhere that would hire the guy with the BS. Go somewhere where the majority of people have advanced education (be it a big or small place). Don't cheat yourself by not doing this.
... to do over I'd have stayed in academia. Get your masters, get your doctorate, and get a job in academia somewhere. There is no better job when you factor in wage, stress, and vacation time.
Shadus
Wonderful post.
But as someone who used to work for a University, let me add this:
Let's say you decide you need a masters, or at least want one. Be VERY careful about where you go to get it. Many departments in many schools see a master's program as a way to generate revenue. That's very different from the way they see undergrad and doctoral education. Those are what they REALLY do. Master's candidates come in to piggyback on the two core reasons for the department. That means that many master's program's are just a repackaging of the undergraduate classes at a high price.
That's really not going to help you, except to hand you a piece of paper. Other posts here have made a good point: You want to do a master's if you are fundamentally changing your approach. A good master's program should not be on how to program. It should be on how to lead programming teams. It should not be on how to read requirements. It should be on how to move into a company, establish the needs and goal of a company, come up with specs, and code the solution. It should feature engagements with local companies. It should change what you are and really teach you something.
Many (perhaps most) programs have no desire or intent to do that. They just want to move you through the existing resources they have at no (or very little) increase in cost to themselves. Do NOT wind up in such a program. Talk to a lot of people. Do not assume that a good name of an institution means they have a good program.
It depends on a lot of things. In the current economic climate I would think that using the downturn to get ready for the next upturn is probably a good idea. It depends on what you want to add in your masters degree.
Going super theoretical may give you some interesting opportunities if you are really good.
That sort of specialization could get you into interesting territory.
If you are only an average student then I think doing the masters degree as practical as possible could still be a big help.
Parts of the masters degree can be done in conjunction with some kinds of real world companies as well, so that gives contacts and experience.
Just approach contact building and experience gathering as an ongoing project and you should do fine.
At many large companies having only a bachelors degree will limit your advancement. If you specialize in an area that you really like and are lucky enough to get a job in the same field a Masters can translate into a lot more money and opportunity. The company I work for hires Masters graduates a full job grade above Bachelors. If the Masters student has specialized in the area they will be working on when they start, they are hired two job grades above the Bachelors.
more cowbell
Do both... work full time and go for your masters part time.
Many companies will pay for some if not all of your tuition anyway.
3 years later you'll have the experience and the degree, and you'll be way more valuable.
A few years ago I'd have said no, but if you look around now, particularly in some of the more prestigious companies, a lot of them are now asking for an MS in CS, CE, or EE for certain positions. But it's by no means universal, so if you're sick and tired of school or drowning in student debt, you still have the option of a going into the work force (well, assuming this recession gets over with). If it's the theory-heavy stuff you like, the masters is probably the better bet in the long run.
You'll find that once you start working that there's nothing you
can't pick up by reading a few books. Unless you want to be an engineer
forever (it's a burn out industry), I'd suggest that you start working
on your MBA after say 4-5 years in the field. By the time you're finished
you'll easily have the chops to be a project manager (at the very least a team lead) and then something more.
That is unless you have some idea you're passionate about that you want to pursue a thesis with, in which case you should pursue a PhD and not a Masters.
www.alphalinux.org
I'm graduating in less than a week with a BS in CS and personally have decided to stick with an MS program, although in Math and not CS, but that's a different story. However, having gone through the absolute garbage that is the job market (and been offered a $75k/year starting salary) I'll offer up my perspective on the issue.
My impression from any places I interviewed, which were basically all positions where you do nothing but churn out code, what people are saying about experience is very true. My interviewers weren't interested in my degree, my GPA, etc. etc. Hell, they didn't even request a copy of my transcripts before offering me the job. Instead of focusing on what classes I took and what grades I got, each interviewer ran me through a rigorous technical interview--Data structures, OO design techniques, C/C++ code debugging, very basic algorithm design (not even as complicated as optimization), etc. etc. They're much more interested in what you can do when you get there than what you have done in academia.
Honestly, I've been crawling monster/dice/career building/school job networks/etc. for months now looking at various job postings in the realm of CS and what I've seen posted as requirements for a job which requires a BS in CS really need nothing more than the knowledge you gained during your undergrad mixed with a little real world application and know how which can easily be obtained through internships, joining open source projects or personal projects. These companies basically want someone who paid attention in their data structures & algorithms, programming languages and oop classes. Going through a masters program in CS as far as I can tell isn't going to really improve on these skill sets as any MS degree program is going to assume (as they are the basic building blocks required for any theory or programming classes you will take) that you have already acquired them.
The jobs I saw which required an MS to even be considered as a candidate were much more academic positions usually dealing in more theoretical research at places like national labs, universities, etc. Granted, they're generally higher on the pay scale and the masters will undoubtedly open up doors in terms of pay scale caps, etc. I wouldn't go for a masters in CS straight out of an undergrad unless you plan to stay in academia. If, however, when you graduate the job market is still in the toilet, an MBA is always a great way to up your earning potential as long as you don't mind dealing with bureaucratic bs and management.
A Bachelors in Computer Engineering will get you exactly the same place a Bachelors in Engineering Physics will get you; a Programming position.
If you ever want to do any real engineering work, get the Masters. If you actually want to get into R&D get the Ph.D. and start building industry relationships.
And most companies aren't going to pay for a Masters in Computer Engineering since it isn't related to your job; but they'll pay for a Masters in Software Engineering.
If someone is passing you on the right, you are an asshole for driving in the wrong lane.
In our country, people usually do both at once: masters and work experience. Anyways, masters is not something you would do later, that's something, you should do now. After going to work, I guarantee you, you are not going back to the university.
So go for it, the worst that could happen is that you don't finish it.
Maybe try abroad combined with some work experience.
Go for the Masters, it will benefit you in the long run, and you will find it easier to keep going now, while you are in school, than go back later, when you have bills and life stuff. I say this as one who knows.
If you are not sure, then try an internship. That will give you some experience while you figure yourself out. Also, with the economy in the toilet, it's a better time to stay in school, rather than look for a job. If you can hold out for another year or two, improving economic conditions will make finding a job you want much easier.
If possible, I would suggest getting your MS in a field outside your BS to diversify your education. (My BS is in Physics and my MS is in Applied Mathematics.) I would also suggest that if you have to pay for your graduate degree out of your own pocket, you are doing something wrong. Many employers have continuing education programs that will pay for a graduate degree. I think you should only stay within the University system if you have a TA position that pays for tuition.
Going to work right away could really be the best of both worlds. You can earn work experience and get your degree through an employee continuing education program. My suggestion, when the time comes, is to apply for graduate school and commence the job search. Grad school will act as a safety net, but it also looks great on a resume or during an interview. I would also talk to those professors and see what the chances are to getting accepted to a program and getting a TA position.
The cancel button is your friend. Do not hesitate to use it.
Two years of experience is not weak, by any means, but academic achievement is externally-verifiable.
For any international thoughts, go with the degree: Minimum degree for British Tier-1 Visa is Masters. Chinese see Ph.D as we see Masters, and a simple B.Sc is "well, OK, but weak".
While you're in the academic mode (no sleep, lots of study, brain like a sponge) use that to soak up a few more diplomas.
When I started at my current engineering job after finishing up an MSEE, my starting salary was equivalent to someone who had been at the company for two years - exactly how long it took to do the masters. I also started with two years of work experience credited towards my retirement date.
Going to grad school was worth it for the chance to travel to conferences on the school's dime, to work with an internationally renowned professor, to meet incredibly bright people, and to do some fascinating original research.
I'm aware that the situation might be different in the US (assuming you live in the US), but if you really like what you do, I see no reason not to do both at the same time.
I'm about to graduate as an Informatics Engineer (in Argentina the Engineering degree is between a Master's and a Doctorate) and I've been working full-time in this bussiness since I started my studies.
Far from being an isolated case, this is actually a common situation among undergrads. It helps to pay college, get experience, and make contacts.
Isn't getting your Master's and working at the same time an option in your case?
The world is a tragedy to those who feel, but a comedy to those who think.
Like it or not you are in school mode. Stay in school, wait out the economy. Once you are in the job market, life will present too many distractions. Get the degree while you can.
I got my MBA straight out of school, went into pre-sales and now make more than most engineers.
Sales Engineering is challenging, a lot of fun, and can be very lucrative.
depends what you want to do. you can earn loads of cash writing generic business logic type programs in e.g. financial sector: no MSC required. if you want to do real computer science i.e. development of algorithms e.g. partitioning or searching or scientific computing then more education is essential
If you have the means to get your Masters there is no reason not to. It can only help you.
There is some serious ignorance on this thread. In all my years reading /. I have NEVER seen such blatant stupidity here.
IT != CS != CpE.
Most of you guys don't even know what a Computer Engineer is which invalidates 95% of the advice given so far.
A Masters degree at a REAL company that offers you a REAL future is INVALUABLE. You cannot and will not move forward in responsibilities and/or management options unless you have a Masters.
PhDs do not necessarily put you only in academia. Many larger companies need PhDs to run their R&D departments. Since you are THE expert in your field (instead of riding someone else's coattails in for a Masters), if the company you are hired for needs THE expert in that field; they will hire YOU and pay you a LOT of money. You will be put in charge of people that only got a Master's degree as members of your team.
If you enjoy R&D on cutting edge stuff (CpE has great options upcoming for many major autonomous robotics projects, the private space industry, and the forthcoming moonshot by NASA and several other countries), then get your PhD. It takes the same amount of time as a Masters degree and you can skip the Masters altogether if you go to the right school.
However, it all depends on what you want to do. At the very least, get your masters degree. It makes a huge difference. Your work experience will come on its own. But you will set yourself apart from your colleagues by having a better education and more thorough understanding of the subject of your career.
These are all great responses.
I have a BS in CS with 8 years experience between the U.S. and Russia. I've participated on panels which have interviewed candidates from a variety sources: PhDs from NASA, Boeing, Microsoft, MS/BS graduates from China, the Ukraine, the U.S., etc... While the credentials looked nice on paper, our topic of conversation ultimately reverted back to work experience, demonstrations of problem solving, and people skills. Those three things seemed to take precedence over any academic qualification.
I personally will finish my MS at some point strictly because I enjoy the coursework. But so far in my career and chosen profession as a Software Engineer, I haven't seen a great incentive to obtain an MS strictly for advancement purposes (although, as some posts indicate, this largely depends on corporate policy).
My 2 cents is education is never a waste. If you have the desire and means to engage in furthering your knowledge you'll be making an investment - this includes but is not limited to a Masters.
Do you have good expectations of finding a job right now? If so, I would say go get the job and then work on masters in two to three years.... But, if you have the ability to stay in school or think that you might get lazy and not go back to school, then get the masters now. Perfect thing to keep you busy while the economy turns around.
GENERATION 25: The first time you see this, copy it into your sig on any forum and add 1 to the generation. Social exper
One important thing that a Masters degree says on your resume is the fact that you are willing to go the extra mile. No many people go for it, therefore the Masters degree shows discipline and commitment to long term goals.
On the knowledge side, well, in the IT field you ALWAYS need to keep studying in order to be up to date, so academy is always praised as a trusted an reliable source of knowledge.
Go for it
I'm 50, earned my MS in CS 20 years ago, and have worked in CS R&D for the past 20 years.
Here's why a MS in CS is a good thing:
1) You can take 10 more courses and learn 10 more subjects that you didn't have time for during your BS. Examples: intelligent agents, robotics, machine learning, compiler optimization, virtual machines, advanced graphics, image processing, signal processing, parallel computing, quantum computing, microarchitecture, computer security, computational biology, advanced networks, mobile computing, pure math, applied math, advanced statistics. For many employers, the presence of the right combination of courses in your resume can be very important, and very likely will make the difference in preferring you to another job candidate.
2) Employers value credentials. When it comes time to promote the next staffer into management, they will consider your education. In the first decade of your career, a MS will definitely help you get the more interesting assignments or step up into management.
3) You are less likely to be at a competitive disadvantage to your coworkers. For the first 5 years of your career, almost everyone in the company will have more work experience than you. If you also know less than they do academically, then you lose.
4) Everyone values a MS more than a BS. Knowing more is always better than knowing less.
5) If you want to work in R&D, don't. Not without a PhD. That said, the (optional) research component of a MS may have more value to a R&D shop than would the alternative -- two additional courses. The thesis shows your ability to do (some) research. That said, most non-R&D employers would prefer the courses anyway.
Randy
Be careful about this plan if you really want the degree. This was my idea and its amazing how real life will keep you from going back for a long time. Especially if you get married & have a kid, all of a sudden the good pay check you're earning now will be much more important that the possibly better paycheck you'll earn tomorrow. Even finding the time /money to do an online masters later on may be rather tough while taking care of your other responsibilities
Shop smart, Shop S-Mart.
After that, you'll have a PhD in everything.
Of course your professors think it's a great idea - they get funding based on post grad numbers. In 20 years of working in IT I have yet to find even my bachelors degree of any use. I have worked alongside people with PhDs and people who never went to university - none of it is important - all that matters is your skills and experience. So forget the masters and get experience!
Seriously instead of asking the slashdot crowd about career advice (brave). What do you want to do? Do you like your field of study? Do you think the CS master at your college is interesting? Worthwhile?
What i'm trying trying to say is this: Is your life about making money? More money than the idiot who spend two more years in college? If so good luck on your road to happiness. If not then you know the answer.
in the normal industry, sooner or later your big boss will decide to hire an Indian company, and some guy who claims to have 15 years experience in any technology, even the one that came up two years back, plus any degree one asks for, all backed up with experience and references (all from India) will have your job.
I had been told when applying for a Masters, they would look more favorable to approval if you had more than 5 years of work experience. Right now, I don't feel a Master would really give you anything more than a bigger loan and maybe a slightly higher salary. Work experience is much better in my opinion because you may not know what you like or what you want to focus in your career. If you work for 5 years, you might find that you would like to focus more on Databases, Web, Graphic Design, Middle-tier architecture, etc etc. I think it is best to find a job that your company will pay for the masters, work a few years, then have them pay for it. You might owe them 5 years of work for them to pay for he education but it is worth it.
Given the choice between two candidates for a job: candidate A has 2 years experience doing the job they are going for, candidate B has zero experience of the job they are going for but has a piece of paper that says they have a masters, which would you choose?
Now try this choice. Once candidate has 10 years work experience. The other has 8 years work experience, and a master. Which one would you choose?
Let's be blunt: if you're talented, a masters degree is easy and quick to do, and is probably your best bet regardless of any other considerations. Provided you complete it on schedule, it also proves that you are not just able to passively absorb and reproduce a lot of information, but also (depending a bit on what school you go to) that you are capable of independently applying the theory that's around in your area of expertise to a specific problem. That potentially makes you more valuable than someone with just a bachelor's degree, even if you have a little less on-the-job coding experience.
Unless what your prospective employer needs (or thinks he needs, or rather what his HR department thinks he needs) are straight-up coders who work hard and don't ask questions. In that case a BSc with more coding experience will be preferred.
In order to advance in the field you'll need to build a resume with successfully completed projects, in which it must be clear what *you* did (as opposed to the team you worked in). Writing a Master's thesis gives you such a project, which you'll have to do all by yourself (not counting all the advice and supervision you'll get). The point is that a Master's course is designed to allow you to shine, while work-experience is not. If you are really talented, you can show that in your thesis. What you will get in a workplace is a lot of simple tasks which, if completed in time and to-spec show that you're a solid production worker who may be ready for some more difficult assignments. In addition, if you're not the shiny type, your Masters work will still be a solid achievement.
If you think it would be hard to go on, then getting into the workplace is probably best. However, unless you show outstanding talent and/or managerial aptitude, your BSc degree will more likely slot you in a career as a coder than as a designer of software.
Last but not least. I don't want to scare you, but low-added-value work like pure (low-level) coding can easily be outsourced. To India for example. More complicated work, and especially work that involves a little thought and local knowledge is less easy to outsource.
Most of the replies are irrelevant as they address different fields. While an MS is less useful than work experience in many fields, that's not nearly as true in Elec Engg, or Comp Engg. or any math-heavy fields.
I've done my MS in the Elec. dept. If your MSCE is like CE at my school, then it's going to be a lot of Comp. Arch., VLSI, Solid State, Analog Elec., Signal Processing, etc. which you CANNOT learn on the job. My rule of thumb - heavier the math in a course, lower the probability that you can learn it on the job. Very few employers let you learn on the job - and math-heavy stuff is far easier to learn at school.
An MS is a minimum qualification to get into the mid-level of places like Qualcomm, Analog Devices, TI, Intel, AMD, etc. So my advice? Do an MS CE, make sure you do interns at every possible opportunity. Or if you're near a school which lets you do a part-time MS, start working, and start your MS too. Not doing an MS will get you stuck very soon!
All bow to his Noodliness!! His Noodle Appendage has touched me!
Is there some sort of corollary to the old "all on the internet are male unless proven otherwise"? All on slashdot are of the Computer Science type until proven otherwise. We're all CS after Singularity.
Here's what I wish to tell you in this discussion. I graduated several years ago and my plan was to continue the studies without pauses. However, the planets aligned in such a way that I decided to stay where I was - a company where I started working when I was half-way on my path towards the BSc in Computer Science.
It has been almost three years since then, and throughout this time I felt that I still wanted to study something. "Hunger for knowledge"? Maybe, but I've been exercising my brain all this time - reading books, researching various fields, writing essays, helping people - I learned many things but I still wasn't satisfied.
Recently I was contacted by one of my university professors and asked whether I was interested in a teaching position. I thought that was a great idea because it would bring me back into the academic environment. I expected this to have a positive effect on me and somehow supress this "need for more".
It did, I enjoy the process very much, I get along with the students... but I still have the feeling that I want to learn more, that there are several fields in which I am not yet sufficiently advanced, etc.
I must also point out that in the meantime I became the CEO of my company.
Today I don't regret not taking an MSc course back a few years, but I am considering getting one in the near future. In the years since graduation I sharpened my skills, I got a better idea of what I want to do next, and I became a more mature person.
Immediately after graduation I was thinking about an MSc because "it's the next item in the list, everyone does it and MSc is better than no MSc". Today I know exactly why I want it - improve myself in order to be able to do better, plus I have a list of features which need to be improved.
I make more than I actually need, and I believe that many other people would choose to change nothing if they were in my shoes; but the thought of continuing my studies never leaves me.
If you are like me, then consider not getting an MSc right away, but spend some time working in the field. After a couple of years think about the problem again and figure out whether an MSc is what you need or not.
The saddest poem
From the question and all the comments above, it is clear that the focus of one going to university is not education or knowledge but ROI. If you really want to make great returns you don't need any degree, many of the business owners I know dont even have high school. But, if you are really interested in gaining more knowledge then go for your MS. MS degree should add more weight when when you apply for a job, and when you switch jobs. Also, it will help you when you see a leadership position within any large corp. Also, some of the more influential friends I made were my classmates from my MS program :)
So go for it if you genuinely feel like you need to learn more, its not all about ROI, it should be really about knowledge and experience you gain from your MS program.
Don't just blame the HR departments--the teachers' unions have a vested interest in maintaining the status quo.
Some school systems were breaking out of that mold and hiring people with degrees in other areas, at least in Massachusetts
JoeB
http://layoffsupportnetwork.com
I work in an IT department that works with a university. Not so much for the university as much as handle IT issues from outside university clients (foundations, privatizing research groups, etc...). We are housed at a university, but not part of any faculty or teaching program. In other words, we are not academic in any sense of the word except that we are housed on university land. For years certifications from Novell or Microsoft were shoved down our throat as the only way to get a promotion. When one of our "certified" employees failed to solve fairly simple issue for the VP, certifications were dropped as a mandate for promotion and emphasis was placed on real world learning. This was a good thing. Now several years later, new administration has turned over that policy and is requiring Masters degrees for promotion. Admin does not care what type of Masters, just as long as you get one. As it works out, this is also right before many of us would be eligible for a promotion. Because it happens during a bad budget time, this is seen as being done for a few reasons: 1. More Masters requirements equals more student enrollment (yes it is from within, but they do not care.. a student is a student as far as rolls go). 2. More money going back into the university. Getting 4 hours of classtime free a semester is a drop in the bucket when you consider your time and money that you will spend to meet your Masters requirement. 3. The Masters requirement is used as a tool to keep the salaries down of those who would normally be eligible for promotion based on time, effort, and accomplishment. Because the rules of the game changed mid-stream, this has really ticked a lot in the IT groups off, but given the economy, many of us are stuck. Most are in their 30's and 40's and have a family (myself included). Leaving at 5:00 (more like 6:30!) from work to then go home and work on a Masters "requirement" considering how much effort is already put in, is just not sitting well. One of the guys looked into a 12 month program from another university. He was willing to pay out of his own pocket to get it done quicker, but our university said they would not honor it EVEN THOUGH they honor the same degree from that same school for other programs. This furthers the idea that the Masters requirement is being placed on us to make money for the school and not as part of a realistic plan for employee advancement.
The chair of the department I graduated from in school made a good point; if you're wanting to get your masters, go to work for a few years after you get your undergrad, then go back for your masters. This does potentially 2 things for you: 1.) you get a few years of real-world work experience under your belt (I don't care what anyone says...relevant work experience is much more valuable than academic experience, if you plan to work in the real world), and 2.) if you work at the right place, you just might be able to get your work to foot the bill for grad school.
Where's the "+1, Hell Yeah!" option when you need it... :-)
My mother has a doctorate in education. She has 15 years of classroom experience in K-8 and another 10 in administration (principal and curriculum development). She spent over 6 years teaching for Vanderbilt University's graduate school of education after retiring from her real world experience.
How things are at the school you attended does not extend to the world at large. There are universities out there who hire professors with real classroom experience. Perhaps you should find a better school?
The Master (Angelo Rossitto) in Mad Max Beyond Thunderdome, "Not shit, energy!"
I did my undergrad in Computer Engineering at the University of Toronto. I had a strong interest in architectures and compilers, but undegrad left me woefully underqualified for jobs involving either. I could have gone into the workforce, but I don't think I would have gotten a great job. After two years, I don't think I would have had the opportunities I wanted.
I did my Master's in Computer Engineering on parallel architectures and pipeline multithreading. It was a great experience, got to co-author a paper (free trip to Europe) and author another coming up soon. I learned a lot from the courses but mostly from thesis work. You get to explore a lot of interesting ideas that you may not have time for when working, but will enhance your job. And you aren't rushed as much as you might be in the workplace. A lot will depend on a thesis topic and your supervisor, though.
I finished my degree recently and am now a Java JIT compiler developer at IBM. It's a great job and I'm definitely being tapped for some of the specialized and cutting-edge knowledge I got while doing my thesis. I didn't actually apply for this job, but since there was a relationship with my research group and this department, I just got a phonecall from my current manager asking me if I would like to come in for an interview.
I slacked of a lot in my master's program, and I regret not putting more into it. However, on the other side of completion, I am definitely glad I did it. I have only been in this department a few months, but already people come to me for help with processor architecture questions. I am treated as an expert, and feel quite happy about that.
I always have a PhD in the back of my head, but I don't think it is something I really want to do. It is a much longer investment, and the return on investment is actually worse from what I hear from my PhD friends.
New slang when you notice the stripes, the dirt in your fries.
Getting a Masters Degree in CS is a waste of time as far as the work world is concerned. They may pay you slightly more starting out, but that's just for the prestige. If you are not going into academia, its better to start working now.
IMHO, the disjunct between "Ivory Tower" Comp. Sci. and real world programming grows more and more the higher you climb in academia. Most comp sci. profs are producing the computing equivalent of figuring out how many angels can dance on the head of a pin - i.e. things of no practical value. For example, if you mention something like mathematical proofs of program correctness anywhere outside of academia, they'll look at you like you have two heads. And rightly so - it has nothing to do with how code is written and done today.
You're better off figuring out some area of computing that you like the most (databases, web, networks, etc.) and chosing between Microsoft based tech and UNIX based tech and immersing yourself in that than getting a Masters.
I am currently seeking two undergrad degrees.. CS and SE with a focus in Information Assurance. I've been in the field for over a year now and having been through several interviews and making friends with hiring managers in the area I've learned that as long as you have an undergrad degree it shows you are able to learn and focus somewhat. But they much rather you have the work experience, and prove yourself worthy of being their employee. I say getting a masters is never a bad idea, it won't hurt anything by any means.. but why can't you work and go to school? I'm slightly annoyed with people who think all they can do is go to school full time and not work. Trust me dude, if i can do it, you can too :)
They rank candidates on a merit system. A masters has more merit than a Bachelors, but ~2 years experience will cancel that out. But a Masters will give you more opportunity to advance, basically all management (read: do nothing) jobs in the government require a Masters.
This is Canada, US or whereever may be different.
and you'll get a Masters degree if you stay alive for three years (because you're "assumed to have been studying" in that time).
OK, so that means that the MA itself isn't actually worth anything - except to annoy people who've actually worked for the same qualification and to question the value of all such qualifications.
My advice is to follow your nose - do what you think you'll enjoy most. That'll depend on what job options you've got and what Masters options you've got - an "is X better than Y" question makes no sense without knowing the details of X and Y.
- Anonymous Cantabrigian.
I never said that employers don't care about internships. Internally, internships didn't do much to point me to the direction of what I wanted to know (other than stay the hell out of the Auto industry, and this is when things were 'good').
My biological clock isn't ticking. Say you graduate with a BS at 23. Go back for your MS at 26. What better way to spend 26-28 than picking up 18 to 22 year olds while working on a masters :).
I have a master's degree in computer science.
I believe that it depends on how strong and detailed your undergraduate experience is. The coursework for a master's degree provides one with a very good education, with deep knowledge in specific topics. Many undergrad programs just scratch the surface.
In the computer science field, many employers would rather outsource than hire an entry level graduate. A master's degree and the knowledge that comes with helps you out against the competition.
This is why I - an engineer costing my employer $250/hour - am doing IT work. Someone in corporate thinks the company will save money by laying off IT workers. Instead, it usually works out like this:
The society for a thought-free internet welcomes you.
After more than 20 years in the industry (13 or so as a software engineer/programmer, a few years manager, a few more as a systems architect) I can unequivocally say that a Masters Degree is nearly useless.
A post-graduate degree means nothing compared to another candidate with a few years more of meaningful experience related to the job. Even if the experience is not directly related, if they can demonstrate their problem solving skills and ability to adapt through that experience I am going to be far more interested in them.
I realize that this is anecdotal, however it seems to me that there is a huge representation of non-post graduate degrees in the higher paid levels of jobs related to computer science.
Other disciplines may make sense, but post graduate (and in some cases baccalaureate) degrees are a waste of time and money.
KK4SFV
Internships are extremely valuable _once you know what you want to do_. They're less so when you're still feeling around (eg, freshman and sophmore years). People who have their BS probably fall into the former category, or at least I hope they do.
Your biological clock might not be ticking, but life seldom goes as people plan it will.
Plausible conjecture should not be misrepresented as proof positive.
No offense, but there seems to be a lot of teachers, IT folks, and programmers from big dumb companies giving you advice. If you want to work as a teacher, an IT administrator, or a programmer at a big dumb company, by all means, listen to their advice. But my guess is you didn't start the CS program to have boring job...you started it to make cool things and hopefully make a lot of money in the process. None of the above qualify so ignore it. The most excited CS guys are usually the ones working for Google like companies. I say "Google like" because what you really want is a pre IPO Google. One that is still small and growing rapidly and building amazingly cool things, and oh yeah has the chance to go public and make everybody a lot of money. CS guys at a company like that aren't overhead, they are the lifeblood of the company. What does that have to do with a masters? Because cool companies like that are often (rightly) led by tech driven management, not lame HR. And tech driven management likely puts a premium on CS degrees, especially if it's a grad degree from a good school. How do I know? I run one of these companies and I have two open recs right now where I'm not even looking at your resume you unless you have a *Masters in CS/CE*.
My own experience is only slightly applicable: I was in a Ph.D. program in Physics and left with a Master's. I'm now a programmer at an R&D company. You don't generally get hired here without an advanced degree. (As a Ph.D. student in the hard sciences, I was paid to go to grad school.)
I disagree that a Master's is worthless. If you're really interested in the subject and can do a research-oriented program, it's invaluable. It's a significant qualification point at higher levels -- to the point that it's common for people to go back to school to get one.
If you're not that interested in the subject, though, you won't get much out of a Master's, so I'm not sure it would go well for you.
I recently hired a CS masters graduate. He's really bright; otherwise, we wouldn't have hired him. He's doing the usual new guy "toilet-licking" tasks; massive integrates of required-but-unpopular technologies, whitebox testing, automation and application profiling. Someday, he'll get to work on tasks specifically related to his masters. Hopefully, his masters will prepare him for success in those pursuits. For today, he gets to earn his stripes, like any other recent hire.
A masters in CS is worth doing, particularly if you want to do more than be a code monkey (design work, project management, ...). Programming is a skill. You can learn a lot from books and classes, but ultimately you only learn by doing. So, if you are going to go down the rout of further structured learning, pick a course that is heavy on coursework and projects, and get yourself work experience placements during the holidays.
PhDs in CS are well worth doing if you wish to stay in academia. The focus in academia is on the theory of software, not on making things that really work. This doesn't suit everybody.
Above all, don't stay in academia or in a programming job if you don't enjoy it. Life is short, and there is plenty of crappy code written by people who hate programming and their job. If you get it right, creating software can be a hoby that you get paid for. What else can anyone ask for?
Exceptions are like STDs. You really don't want to catch the ones you can't recover from.
In a hyper-competitive global market, you want the masters degree and any other edge you can get. This is especially true if you want to do anything that's remotely interesting. For example, a lot of software start-ups come out of graduate research.
As someone who got a Masters before going into the field, I can say one disadvantage.
My school focused heavily on software engineering, and every step of the way, you would hear "it works nothing like that in the real world". After getting out of school, I can say that software engineering is like a cluttered toolbox. 75% of it is stuff that you do not need for what you're trying to do right now, and some of it you will never need again.
The problem is, that you may find yourself swapping out parts, as you move from project to project. I personally feel that, had I walked into those higher classes with a foundation of education combined with experience, that I would have paid more attention in some areas, and would have seen some of the lessons not just as a bulleted list to memorize by 5pm, but as tools that can be applied in a practical way.
So, my suggestion is to work, if you can find a job, and wait on grad school.
First, if you don't enjoy school, don't subject yourself to two more years. I'm glad I continued for an MSEE after my undergrad CompE degree, but kept using summers for internships. The breadth and depth of additional coursework gave me a knowledge base I draw upon constantly. The teaching assistantship has helped me be a better mentor. The research assistantship wasn't too relevant, but it certainly paid tuition! I went to a top-tier school, and I'd recommend that experience. If you're planning to go somewhere else for a graduate degree, I can't judge the value. Especially in Computer Engineering (chip design) advanced degrees seem very prevalent among my co-workers. At one chip start-up, all dozen people in my role held an MSEE, except the boss. If you establish a connection with industry (internships), gain practical skills (programming), engage in your classes and research, and don't accumulate too much debt, I think you can come out ahead.
If you just want to code... even to the point that the thought of getting your hands on a really messed up algorithm makes your shorts tight... your bachelor level degree is sufficient.
If you want to teach or manage you should go for the masters.
If you're one of those really out there theoretical geeks who substitutes lab time for E there should be a Ph.D. in your academic plans.
My office has been taken over by iPod people.
I'd recommend trying to get real world experience. If you can't find a job, or have worked a few jobs and don't like your work then you can start looking at Grad school. Sadly most people in academia will always suggest getting more education, and those in the workforce will always suggest more experience. So you never really get a good stand point especially from academia since many don't have a lot of workforce experience.
I asked myself the same question. I decided to take 1 year out and gain some work experience before finishing my degree. I have been working for Microsoft Ireland as a software development intern for the past year now and I hate it. I cannot wait to return to college. Large software companies are not the place for students interested in solving interesting problems and changing the world. Large software companies crush innovation and imagination, the attitude here is get it done, fix it tomorrow.
It all depends on what kind of career you want to have.
Take my brother-in-law for example. He got his Mechanical Engineering BS and started interviewing. Most of his job offers were for Production Engineering type jobs. When I was working on an Engineering degree, I found the same thing. 80% of the Engineering jobs in manufacturing are Production Engineering.
But he didn't want to do production engineering. So he stayed and got his Masters. Instead of doing a bunch of classes he did research. He designed tested and wrote a thesis on a pollution control system for diesel engines.
When he interviewed after that, he was interviewing for R&D jobs. No one wanted him for a production position, They wanted him to design solutions for them.
Your mileage may vary. A Master's Degree opens doors you may not have even known existed.
Get out while you can. IT is going to hell in a handbasket fast. Your master's and Bachelors degrees won't mean squat when they can outsource your job to someone in India with a fake degree for 1/10th the cost. It's a race to the bottom and I don't know why anyone would try to make a career in such a pathetic, cutt-throat industry. All these people who say all this crap about hiring are full of it. They always say "Well if you can code you can get a job" but they don't even define a good coder nor would they know one if they saw one. If you really want to work in IT, just lie your ass off, use a fake degree, take the money, and run. Soon you'll have an impressive resume with big name companies on it and you can sit on slashdot and brag about how you're a real hard-core coder...
In Australia, you can do a "Masters (by Coursework)" degree that will be vastly easier
than your undergraduate course.
They are aimed at fleecing international students.
Education is Australia's third-largest export income earner.
Get the MS. It will never be easier or cheaper. Both a BS and an MS are simply credentials that prevent your resume from being rejected early. Where I currently work, they don't consider candidates without an MS. Play the game, get the degree. Make contacts, never burn bridges...
-- My brain is just a BUNDLE of nerves...!
Real-world experience is the most important, but sometimes that degree gives you an edge in the job market. So if it is work or school, choose work.
If you can get a job at the same time, go for the masters while school still fits into your life. It is hard to go back to staying up all night and eating ramen noodles when you have a wife and kids.
Agreed. The best way to increase your income is to get a certification in some high-end "corporate-sized" tool, such as Oracle, DB2, Java server tuning, network security, etc. In other words, specialize in some specific technology product used by big co's with deep pockets.
This condition is one of the reasons why US citizens tend to be scarcer in higher-end degrees. Masters and PhD's are valued more outside the US. It's not that US students are "dumb", as some work-visa lobbying firms claim. It's just a culture difference. US companies continue to favor "practical" knowledge, and masters generally don't provide this in their mind[1]. They'd often rather rent consultants for very specialized analysis projects rather than have internal staff anyhow.
[1] Whether they "should" value more theory is another long and messy topic.
Table-ized A.I.
Well, first, what do you mean by "computer engineering"? Do you want to design graphics boards, or set up data centers? If you're really going to do serious electronic design, you need both the degree and the experience. If you're mostly going to install big systems, the theory may not be that helpful. An MBA might be more useful.
Forty years ago, being an EE who designed serious hardware paid about as well as being a lawyer. (The IEEE has numbers on this.) That is no longer the case. Hardware design also isn't as much fun as it used to be. You're constrained on all sides - size, power consumption, cost, and schedule. There's less opportunity to be clever. Most electronics design work is now done outside the US now, anyway. When the manufacturing goes, the design work follows a few years later. Aerospace is much smaller than it used to be, too.
If you really are interested in how it all works inside, though, go for it. Computer engineering is far less superficial than IT. You're less tied to whatever fad is up this month.
The answer to this question is pretty simple really. It depends entirely on if you are positively sure and passionate about a specific aspect of computer engineering. A BS is designed to get you a wide breadth of knowledge whilst your MS is designed to focus on one aspect. If you know exactly what you want to do then go for your MS. Get on a research team and make a name for yourself. The contacts you will make in a masters program are invaluable. You will also be able to have published articles and earn fellowships which will only bolster your resume and more importantly your exposure. It will be much easier to get your masters now then to wait. The economy is not that conducive to getting a good job now anyway.
I don't know you, but I don't have your best interests at heart. Someday you could be competing against me for a job. It's in my own interest to make sure I get the job over you.
With that said, don't bother obtaining a Masters. If anything, you should have just gone to a community college.
I work in a company where almost everyone is either a CE or an EE. Here's what I can tell you.
1. Don't do a Master's only for the money. You will hate your life.
2. A Master's degree is practically required to be hired in my company and it will get you a higher salary right off the bat. It also enables future promotions that would come slower without a Master's.
3. When you're a Master's student, you ABSOLUTELY NEED TO get an internship so that you get private-sector experience while studying. You need it in order to have the maturity associated with 2 years work experience and you will have a foot in the door for getting a job.
4. Don't get a cheesy MS. Get it from a good research oriented University if possible. You will notice the difference compared to people who are just after a piece of paper.
5. Nobody cares whether you enter the company at 21, 25, or 30. Things happen in peoples' lives, people were in military, whatever, employers understand this.
I think professors will almost always think doing grad study is good, but the answer gotta come from you evaluating pros/cons. I wouldn't say 2 more years of working experiences is definitely better, but the bottom-line is that, getting a grad degree is definitely NOT additional 'job/work training'.
In Poland, at my university, we're getting a masters degree and during that time (5 years) we have to get minimum of 1 year work experience. I think, that's a good way of learning both practical and theoretical skills.
I'll throw in my two cents having been in an Master's program and dropped out to change programs due to little or no opportunities in the field I was studying.
Since you have a year left, start studying the job market and make a decision for yourself whether or not your BS in CS will get you a job. Look at the amount of opportunities you have available and the qualifications they are looking for in an employee. For most (if not all) graduate programs you won't have to start applying until your last semester of your undergraduate studies so you have a few more months to really look into things. If you don't think you will be qualified enough (or even have a chance) for the jobs available then take your time and get the MS. Should you decide to go for the MS the worst it will do for you is add on to any loans you may if you have to borrow, the best it will do for you is keep you out of a market that you can't get a job in anyways and provide you with something to work towards while waiting for jobs to possibly pick up.
If you have the grades most professors will tell you it is a good/great idea to go on and get your Master's degree. Not every field needs you to get a Master's and not every professor truly knows if it is necessary or not to have outside of academia. Ask your adviser/professor if they know someone outside of academia in your field of choice you can contact to ask questions. While doing this you may just create a new bridge to help with employment.
As a recent job searcher, I found that having a Master's helped immensely in just getting my foot in the door for interviews. That being said, without work experience, I don't believe it will help out initially. I worked full-time while going to grad school, so not only did I have 5 years of work experience, but a Master's (which work paid for) to go along with it. My opinion: suck it up and go to school while working. It makes for a tough few years, but the benefits will far out-weight the costs. Just keep in mind, that you may need to switch jobs to take advantage of the extra pay potential from getting the degree.
http://online.wsj.com/article/SB124181970915002009.html
To summarize, it basically takes a decade for a person, who starts his/her career in recession, to catchup with a person who starts his/her job during boom time.
I'm also a computer engineering undergrad getting my degree in less than a month. From what I have heard from professors and professionals in the field is that there are plenty of opportunities to get your masters without paying for it.
Look to work for a company that would be willing to pay for your masters degree. It may take you a year or two longer because you will have to work part-time and school part-time, but you won't have to pay a nickel for it.
One of my professors went so far as to say "If you pay for your masters degree, you're an idiot."
One of my colleagues who works for the military is getting his masters tuition paid for and is going to school full-time and getting paid what he would if he were working full-time (provided he maintain a reasonable GPA). Imagine that, getting paid to go to school.
Once again, find a good employer who will invest in your education for you.
I am very surprised to see all the comments saying how a masters will not earn you more money. But than again they seem to be mentioning CS degrees and IT work. The poster was speaking about a computer engineering degree. I am currently getting a masters and for my degree in electrical computer and systems engineering someone with a masters has a good 20,000 ish higher salary than in individual with only a B.S as published by my schools career development center. Even still the C.S. stats Ive seen indicate that there is still a significant differance in pay between a B.S. and a M.S. On a side note. I may recommend going for a combined PHD/MS program and just stopping when you get your MS. Doing this will potentially get you more funding in forms for a teaching assistant position or grants.
Speaking from experience, having work experience post-undergrad made my graduate work all the more meaningful. I don't necessarily recommend waiting a long time like I did (8 years), but I did get a lot more out of my grad classes having had industry experience.
Professors in the academic bubble recommend that you stay in the academic bubble and continue to help pay their salary? Shocking.
Vote Libertarian
If you have a job lined up GO FOR IT! I know individuals who were turned down for jobs with Masters Degrees who would have recevied and offer without one. This is because the Government pays Master Degree holders more then on holder.
Most in my field get a job with a BA and study nights for their Masters so come pay increase or job change time they have EXPERIENCE and the Sheepskin.. Besides most companies pay for post graduate studies..
In the United States, a masters degree is roughly equivalent to a European bachelor's, because the education system in the US doesn't properly cover basic maths etc. at high school level, you will spend the first 1.5-2 years covering high-school type work.
If you live in Europe, you are probably employable with a bachelor's.
Get a decent job now, have them pay for grad school. Get a raise on their tab. You'll also get an income during the 2 years and plus the degree... if you can handle that.
I have a BS and MS in computer science, and over a decade of experience. This is for me, but it could be different for you:
When I got out of school, the cost of my MS was paid for in less than 6 months by the difference in salary. This was at HP; I would guess that most smaller companies do not differentiate that much based on degree, but it was an influential factor.
Because I stayed at the same school and got my MS straight away, I didn't have to take the GRE. This REALLY influenced my decision.
I would never expect or rely on my MS to help me get a job. In general, experience trumps your degrees. If it does help, great, but if you have an MS and don't pass the interview questions the tech guys throw at you, it's not going to matter.
The exception to the above paragraph is if you wanted to be an instructor at a junior college; in that case you generally need an MS (but requirements vary). You'll never get paid as well as an instructor (and depending on where you are, positions can be scarce), so you should only do it if you love it.
I have no regrets over that "lost" time. I learned a bunch of good stuff, and it was fun--way more fun than being an undergrad. :) I had, after all, the whole rest of my life to work.
I bounced around, out of HP to a dot-com, to a big game studio, to being an independent contractor. One thing's for sure: you never stop learning. I'm familiar with technologies that were unheard of when I was in school. It can take time to keep up with what's going on, but I can't recommend it enough!
/o Tape monkey get up, get coffee, tape monkey go to job... o/
Tape monkey rotate last week's backups, push a button, turn a knob.
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
I got my masters mostly because I didn't want to leave the college social scene without first finding someone who I could marry. Once you leave school, the sort of people you meet in the professional world fall into an assortment of categories, most of which come with an ex-husband, all sorts of baggage, are married to their work, and/or have no interest in actually having a family and settling down. It's better to find a girl who's not so committed to the career that they can't make you a priority.
http://www.beanleafpress.com
I did it when I had the chance, if you're in no rush to start working, have money to pay for it and you know which area of interest you're going to pursue, go ahead and do it. Later in life it'll be harder (but not impossible).
Vi havas e-poston.
I have two masters degrees, one of which is in IT, and I work for the Federal government.
I can't say what the environment is like in other than the Department of Defense or Department of Homeland Security, but when we get surveyed for our job qualifications we are always asked for information on specialized certifications (e.g. Project Management Professional, Contracting Officers Technical Representative, Acquisition Level 1, etc.) than can be earned or awarded through work experience or taking short training courses. No one for the last eight years has asked about advanced education.
My suspicion is that most of the people in civil service who deal with workforce management and job classificaion do not have advanced degrees and do not understand the amount of work and rigor that goes into earning a masters or PhD in relation to targeted training that fills a niche. While a PhD may get you a GS-11, a Bachelor's degree combined with a PMP Level 1 certification can get you in as a GS-13, which is a big pay and status boost.
The opposite is true in acedemia. If you don't have a PhD, don't even both applying for a college teaching job, and in some states one of the requirements to get public school tenure is to have a masters degree plus continuing education credits.
Business doesn't care as long as you can make them more money than they pay you.
Most people seem to hire people who resemble them. So, figure out where you want to work, find out how the people who run the system were trained, and get yourself trained so you look like them.
TLR
A man no more knows his destiny than a tea leaf knows the history of the East India Company
In my years of IT, I have never encountered this "glass ceiling of knowledge" that can only be surpassed by taking a Masters. Books and the Internet are plenty enough to overcome most obstacles.
Why not pursue a M.A. in another field (e.g., business, psychology)? It will broaden your exposure and your experience, potentially making you a more attractive candidate during your job search, and potentially giving you some fall-back career options should you ever find yourself downsized or outsourced.
Beyond that, get your experience. If it's easier to get your graduate degree now, then that's great for you. If not, consider landing that job now (if you can find one) so you can start gathering some real-world experience, and go back for your graduate degree later on (while you are still working). The latter option can be especially attractive if your future employer has a tuition-reimbursement benefit.
I use irony whenever I can, but my shirts are still wrinkled...
There's a big difference between getting your Master's to work in a drone position and getting your Master's and climbing the ladder. If you want to get to a higher-level job, a master's is pretty much the best thing you can do. When you go for that promotion to technical or project manager then it's going to be your degree, knowledge, and experience up against your colleagues'. A Master's degree is a great way to prove that you have a commitment to excellence in your field, but if you aren't going to use it to move around then don't get it.
I would argue that most people who say "waste of time" flat out to a Master's degree are the people that are happy with the low-level, technical positions. There's absolutely nothing wrong with this, but know what YOU want out of your career.
If you are interested in a related field, a masters can be useful. If it's just the same field, probably not.
For example, a masters in Physics or Math on top of the engineering degree would make you stand out. (Or chemistry, or biology, or fine arts...)
If you want to apply your engineering to a field of interest, great. If it's just computer engineering for computer engineering's sake, then gain job experience and get a masters later. (Hopefully at employer's expense.)
Overall, yes, though you might want to consider getting a full-time job first and then get the company to pay for it through their tuition reimbursement program. Some companies will even pay 100% if you maintain a decent GPA. Once you're in the program at work, they're spending money on you and it's effectively free education and guaranteed employment for the duration. Kind of tough to beat that. During that time, you're salary increases might be smaller (added compensation by education), but you're becoming more valuable to them as well as other potential employers.
If you are considering a Masters, then consider one that will round-you out as an overall candidate for employment. Get an MBA or other type of business / management - even IT Management. This will show that not only do you have technical knowledge, but that you understand the requirements of a business. Employers will know that they can present a business problem to you and that you will both understand the business side of it as well as how to execute the technical side.
Hi,
I think a masters always looks good. Period. It shows commitment and discipline in a particular pursuit and shows you do have at least half a brain.
However, real-world experience simply can't be beat.
For example, (ISC)2 will give you one year towards your required five years of experience for their CISSP if you have a masters.
If you're not willing to read most of both sites, I'd say that your answer regarding CS grad school should be "no." Any form of grad school requires an enormous amount of reading, and the amount you should do in preparation ought to in part tell you whether you should go.
"Is a masters in computer engineering better than two years of experience at a company?"
If that two years of experience is actually teaching at a company (like I taught new hires laptop repair,) it might be better than the Master's Degree, as you're already teaching in a mega-million dollar environment and you've been recognized to have the skills to be usable as an internal trainer. Looks great on the resume.
Otherwise, most companies will look for that piece of paper, and then proceed to place you in a section not relevant to your degree. What was the last figure; 70-80% of people with college degrees have a job that isn't related to their degree, or something like that? Get that Master's in Computer Science and you'll get put in Marketing.
At minimum get a Bachelor's Degree and a few certifications that you can keep up to date.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
I see in the comments that Computer Engineering has been categorized as IT, and/or Computer Science. If you got a good Computer Engineering degree then you should have had about half Electrical Engineering, and half Computer Science - which means those people are lumping you into categories when in fact you're asking opinions about life long decisions. Here are a couple of things a masters can do for you:
1. make you more marketable for job positions
2. make you less marketable for job positions because you cost too much (gets even worse with PhDs). this won't happen right away but later on in your career you can end up taking a paycut to move to a better job that you're overqualified for.
3. help you decide upon a specific area of research and development that you'd like to be involved in - i.e. what did you concentrate in while doing the degree
4. railroad you into doing that specific thing for the rest of your life (again reference the PhD comment above)
5. get you contacts!!!! this is important no matter where you go - my wife who's not in engineering uses her contacts all the time
6. prepare you for academia
7. make you disgusted with academia
There's more but I won't continue - there's two sides to every coin. If money is your concern - go to work, you're job might want you to get a masters in something else (like an mba) so why put yourself through that twice. If your concern is happiness and interest in your job then I say take everyone's advice on this forum and then do what you feel is right.
If you ever want to get into teaching at all even retiring into it or something suck it up and go immediatly for your phd. If you are not ever even remotly interested in teaching then get a job for a company willing to pay for your masters, and then do both. you can school part time for a couple of years while working full time and not have to pay for the masters at all. On top of that you will be getting very valuable work exp. also its important that you dont put off starting the masters long, the longer you wait the harder itl be to get.
Since you've chosen Computer Engineering as your feild, you've chosen a lifetime of misery that comes along with it. Getting a Master's degree will only tie you more to your dark cruel fate.
In times of recession, get your masters and learn more about the field. In boom times, get a great job. Trust me, this is the determining factor you need to consider.
Many CS jobs won't tear you open a new horizon of understanding each and every year. During recession your odds of getting a "google" job is very low even if you are outstanding. So you could get your masters and then when the economy turns around, get your great job and have everything.
For me, getting a master's turned out to be a great decision career-wise. But I would say it depends a great deal on the specifics of your situation. Here's mine:
I graduated with a BS in computer engineering from a middle-of-the-road university. I had a decent job offer coming out of college, but not with a company I wanted to work for in the long term. I was accepted to a master's program in computer science at a top tier university, and decided to do that instead. I'm going to graduate with my MS next week.
I believe just being at a better university has opened doors for me. Last summer I was able to score an internship at a company that probably would not have given me a second look if I was an undergrad at my previous school. Now I have an offer to work as a full-time software engineer with another great company.
My pay will be slightly higher than my undergrad friends at this school who are going to that same company, but probably no higher than theirs will be after two years of experience there. If I had spent two years working at the company that gave me an offer after undergrad, would I have been able to get this same job? Maybe, maybe not. I do know that my initial salary with this company will be nearly 50% higher than the other company offered me two years ago.
In your situation, you have to consider what value will be added by going for another degree. What work opportunities are available to you now? What new opportunities will open up as a result of your master's education? How much will a master's degree cost, both in terms of tuition and lost earning potential from being out of the workforce during that time? These are all things you need to consider. There is no easy, cookie-cutter answer.
2 years from now having 0 years real world experience and a masters compared to 2 years experience and a BS sounds like a no brainer.
10 years from now 8 years experience and a masters sounds pretty good compared to 10 years experience and a BS.
Also, let's be clear YOU SHOULD LEARN DIFFERENT THINGS FROM A MASTERS THAN WHAT YOU WOULD LEARN WORKING. The type of job you could apply for would be different.
Let's say the job you are hiring for is that of a technical lead on a distributed computing system. You have 2 candidates. One has 3 years of Java experience. One has a masters and did their thesis on distributed systems. Which candidate would you suspect would provide new high level technical ideas to the project?
Steal my band's record! Seriously,
A masters is almost necessary in any field today. In your "free time," do some open source work & distinguish yourself as a hacker. You spend your two years doing those two things, and you will be able to write your own ticket. In any case, the economy is down; so, just do it -- it's a perfect opportunity, before you're married with kids and working 60 hour weeks...
If you have strong English-speaking skill and decent grades, then you have a good chance to get funded as a teaching or research assistant in grad school. Poke around and talk to professors, dropping your resume and letting them know you in the market for an assistanceship.
If you get funded, you live like a student for two years more and have a master's degree. If you have no funding options other than paying for it yourself, then START WORKING and get your employer to pay for it, but it'll take a bit longer probably 3+ years part time. You'll make much more money in the long term if you work and go part time, then you can get the best of both worlds.
-7th-year grad student in electrical and computer engineering
I have a MS in Computer Science which I got in 2005. I would definitely recommend getting a MS. While you are constantly working, it doesn't look like a big deal to have a MS- but in case you ever go on a break from work a MS will stand by you in good stead. And its always better to have done a MS earlier in life than later. A good MS with diverse courses and an in-depth thesis is definitely worth more than two years in the industry. Having said that- I did my MS after working for three years in the industry after my Bachelors under-graduation in Computer Engineering. And that surely helped me pick the right courses and a thesis topic.
Get your masters degree. Spend your summers working at internships. Most likely you won't even have to pay for graduate school (RA ship or TA ship). This gives you a leg up on the typical graduate w/ a BA because you'll have 2 more summers of internships and a documented ability to learn at a high level. Additionally, it's two more years of college. And being a graduate student in college is very fun.
-Graduating Masters Student in Mechanical Engineering with a job when he graduates
Later on in life you will almost certainly accrue responsibilities that make it harder to go back to school. Two year's experience at a job doesn't mean much-- the time's gonna fly by, so get to it now while it's relatively easy.
You need to go get a few years, specialize or think about specializing then go back and get it. You'll get way more out of it. I went straight from undergrad to grad school because it was paid for and I ended up being over-educated and under-experienced and without really knowing specifically what I wanted to do. I even had applicable work experience while in school and still spent a year looking for a job in '06-'07.
And only if you investigate schools carefully, and talk to lots of different students in the programs you're applying to.
I got stuck in a program I hated. I loved the material, but the people ruined it for me. My performance fell, I lost my fellowship, I spend my life savings working to finish a masters, due to stress a dormant medical problem got out of control and my health fell apart, and now I'm unemployed, broke, sick, uninsured, and I wasn't able to finish my masters yet.
I still love my field of research, and once I've taken care of my looming health and debt problems, I can't wait to get back into a DIFFERENT program. I just regret I nearly lost everything because I didn't do enough due diligence on my PhD programs.
I guess a lot must partly depend on your actual discipline. Here in Australia, my discipline (molecular biology or biotechnology) tends to favour jumping straight from BSc honours to PhD. Nobody is interested in watching you spend that much time ploughing through secondary research; they want you doing proper original research right now.
However, I'm aware that degrees are "rated" differently according to what country you're in: for instance a Scottish Master's degree is rated here (by Govt overseas qualifications assessment bodies) as equivalent to a Bachelor's degree. Recognition of US degrees varies a lot. So I guess the answer to the OP's question depends on whether or not he plans on staying where he is.
Get experience, get a degree part time - you might even get your employer to pay for it. Education is always good. More experience is always good. With This plan you can get both.
A lot of companies will pay the course fees for your masters. Take a class or two each semester/quarter. It takes three years instead of two, but you come out waaay ahead cost wise, get the work experience and the masters. I'm still kicking myself for not doing it my first few years working, when my only real time obligations were video games.
I got a job as a programmer upon graduation, then after settling in, started a masters part-time. I quit the masters for a couple of reasons: I didn't want the time cost, but primarily I quit because I realised that what I thought was important for me to learn to be better at programming was not what the university thought was important for me to learn.
Specifically, I decided that practical skills like test-driven development and solid o-o design etc were more immediately relevant and important, and I got a better learning environment at work.
I have found that if you want to be good at programming, then you need to study constantly regardless. There is a lot to learn, and you should not stop just because you have left uni.
Also, there is a lot to be said for getting some real-world experience to guide your study direction. If you are going to invest in a masters (and it is an investment), then make sure that it will pay a good return. That means be sure you want to follow through with the implied career, and be sure that you are learning stuff that will enhance that career.
So far, not having a masters has not held me back. If one day it does, then I can address that lack then. This is not the impossible thing that people make it out to be. I know several people who have taken this route. It is hard work sure, but at least when you decide to do it you already know it will pay off. And frankly, you should have been studying off your own bat already anyway, at least if you want to be good.
I recently had to make the same decision. I had an offer to do an MS on a very interesting project, but chose to go work instead (I had a competing offer with a good position at a hardware company). The big kicker for me was: How do you do effective research in an industry you've never worked in? The majority of professors I see went BaSC->MS->PhD, and frankly, are horrible. The best professors? They've gone and worked in industry for at least a few years. And their research reflects this, and is usable. It is also worth considering that some companies will pay for you to do your master's part time. Granted, this might be an M.Eng, not an MS, but HR probably won't know the difference. This is the route I'm going. If in a few years I want an MS or MBA, I'll go back to school to get it. I don't see myself in this field in 5 years so it's less of an issue for me.
Baver
If you want a masters, get an MBA instead. Your future and income will benefit 100x more than a Masters in some obscure field doing research that the corporate market can't/won't use for 10 years anyway.
Both school and work are a huge waste of time.
Concentrate on growing your own food, not using fuel to get around and sharing the skills you already have with others.
I'm heavily involved in the FLOSS non-profit world. I have a Master's Degree in Computer Science that has not done all that much for me. I regret getting it.
If you don't plan to teach high school or college, then you would be better served getting a degree in another field. For example, getting an MBA or a law degree might make it possible for you to broaden the range of things you can do. (I'm against getting a law degree, but for other reasons.)
If you want to go into not-for-profit or governmental policy work in computing, getting an MPA (Master's in Public Administration) would be good.
In short, your professors want you to do what they did. Given that B.S. degrees are not as valuable as they once were, it's worthwhile to have some sort of graduate degree, but getting it in another field will expand your horizons and opportunities and also give you more perspective as a computer scientist/engineer.
Do get your master's if you can, I am telling you that as somebody working in the industry. A master's (or a PhD) is a very distinguishing feature, while two years of experience is not. Also, two more years in school can give you (different kind of) insights and deep knowledge which two years of work can't. Having achieved a high level of education before you start a full-time job and getting family will reward you handsomely in long term.
Experience is non-transferable outside your own cloth-covered cubicle. That is, reputation is largely a self-inflicted delusion, because your work experience is so tightly integrated to the company you're working for that only headhunters looking for you already will be impressed — and those guys are middlemen with an even harder sell to make that you could do on your own. Your own jobhunting efforts are hard enough, especially if non-disclosure agreements prevent you from demonstrating your contributions to major projects, but with a Master's you're heavily invested in yourself, when no one else really is. That makes your postgraduate degree a nifty credential that's hard to ignore (not impossible, but hard); and even if you impress no one but your family and yourself, that confidence casts a longer shadow than your student's resume ever will.
``Tension, apprehension & dissension have begun!'' - Duffy Wyg&, in Alfred Bester's _The Demolished Man_
All I will say is this. I didn't go on for my Masters and I've regretted it ever since. IMNSHO It's a lot harder to go back to school after working for a while than it is to just continue on after your Bachelors.
It's especially hard after you get married and have kids. It's not impossible but if you can do it now, I highly recommend that you DO IT!
Get some experience (three to four years) under your belt before you decide to go back to school. Figure out what you want to study. Also look at what you want to accomplish after you complete your degree. You may want to do something a little different than computer engineering.
I would look at other alternatives to an MBA, especially if you find you are very technical. You may find a senior engineer is a better fit for you than a manager. I would also recommend finding a university level program instead of a quick, online program. It will look better to a hiring manager.
I got a BSCS, went out and worked for a few years and saw that all the really good jobs in the company I worked for, and the companies I wanted to work for, were filled with guys with MSCS degrees.
So, I got the MSCS. And, I was able to get the jobs I wanted. Companies will hire a MS for a job that requires a BS. They will also hire an MS with experience for a job the says it requires a Ph.D.
When the world tilted sideways and I couldn't get the kind of jobs I really wanted anymore, the MS let me get jobs teaching in Junior colleges. Not bad. I took an online teaching certificate course and passed the Texas test that qualifies you to teach CS in grades 8-12, so I have that out of the way and that qualifies me as a "Highly Qualified" teacher if I ever get around to working in a high school. But, so far, I have been able to stay ahead of the bills working in junior colleges.
I'm now 56 and looking back, once I made the decision to get a CS degree, the MS was the smartest thing I ever did (except for marrying my wife :-). The only thing that I can think of that would be smarter would be to have gotten a J.D and become a lawyer.
OTOH, I had a boss who nearly cried when I decided to go to college. He kept saying I should study to be a turbine mechanic. Yah, know what? If I had I would have worked fewer hours, in better working conditions, made more money, had more freedom to choose where I wanted to live, and I most likely would be retired with a nice pension by now. And, I would still be able to get jobs as a turbine mechanic. My next door neighbor is my age and is a retired turbine mechanic...
Stonewolf
Not to be pedantic, but I feel like being pedantic!
I think someone else might have mentioned this already:
Facts:
- Tuition always go up.
- You'll earn your least amount of $$$ during the first few years of your career. Think about your hourly wage.
- In 10~15 yrs, when you get to middle or senior management, it may be difficult in managing people with more advanced degrees than you do.
Conclusion:
- Pay the lowest tuition while your hourly wage is still low. You'll lose out a lot more if you delay getting the degree (higher tuition and you will be spending higher waged hours studying).
- Master degree helps you in the long term to rid of any doubt of your ability/credential
Personal note:
As someone who has worked in the industry for almost 20 years around the world, I can tell you a good number of you future bosses/clients will *care* what degree you have and which university you got it from. The extra 2~3 years of junior level work experience in place of a degree will not gain you any favor on your resume.
http://www.ted.com/index.php/talks/ken_robinson_says_schools_kill_creativity.html
Cram as much formal education into the part of life where it is easiest.
You'll have to study all your life. In addition to your day job. So get a head start, get something that looks good on a job application and will pay for itself. Then concentrate on stuff you WANT to learn or NEED to learn for the rest of your life - because a lot of the stuff you are just learning will be utterly meaningless in 20 years time.
So... While work experience might be OK and most things you are going to learn will be obsolete rather quickly, a good choice of topics will allow you to have a better foundation later on.
That means theory and useless-looking stuff. OSI layers instead of HTTP implementation details. Knuth instead of C++ for Dummies. And Knuth is still very much a practical guy. :)
You are unlikely to spend much time on theory after starting to work. So concentrate on it now, while you can.
My advice (having just finished my Masters after working for 3 years after undergrad) is to work for a few years and then go back.
It's a good idea because:
* You get a good idea of what the day to day of being a software developer is like.
* You may get to branch out on the areas you get to work with before you decide which area you want to focus on in your Masters (I got to do databases, networking, and several other topics that weren't covered in depth in school).
* You will become a better coder. There is no replacing sitting down and designing, writing, and debugging code for 40-60 hours a week for 2 or 3 years.
Chance for computer engineer to have a sexual encounter based on location:
porn studio: 18%
university campus: 17%
workplace: 3.3%
If you can get an entry-level position, go to work. A M.Sc. in CS will get you nowhere. The Ph.D. is the next "stepping stone," and that will open up new doors for you. So unless you're wanting to go all the way to a Ph.D., don't bother going back. Academia sucks and is full of all sorts of social cues that are distressing, misleading, petty and small.
Quote:
"median earnings for an
advanced degree were 31 percent
higher than earnings for a bachelors degree" - US Census report
High school or more : $26,894 / yr
Some college or more: $32,874 / yr
Bachelor's or more : $46,805 / yr
Advanced degree : $61,287 / yr
Also, looking at the overall education level of the US:
High school or more : 84%
Some college or more: 54%
Bachelor's or more : 27%
Advanced degree : 10%
So, do you want to be part of the 10% group, or the 27% group?
Reference:
http://www.census.gov/prod/2009pubs/p20-560.pdf
"Educational Attainment in the United States: 2007", pg 10
Yes, I know that this doesn't differentiate between master's and PHD, but I think the point is still valid : advanced degrees earn more.
I received my masters in 1995, and I'm very happy that I did. It gives me an extra certification that I'll have for the rest of my life - it helps provide a differentiator in the marketplace, and at many companies, your education level goes into a formula that determines pay raises and salary caps.
So it doesn't just come into play at the salary cap - it can definitely affect your annual raises.
Is it a magic bullet - no. But it sure doesn't hurt.
I also completely agree that a PhD doesn't make sense if you are primarily interested in maximizing your earnings.
And remember, you will NEVER have an easier time getting a masters than right now.
- you are already in 'academic' mode from your undergrad
- you are used to having no money and living like a student
- you don't have the the larger cost basis of modern life (car, house, kids)
While yes, it is possible to go back to school and get a masters later, it is 100 times harder.
You either need to find an employer that will sponsor you + work double hours (work + school), or you have to self-sponsor.
If you self-sponsor and take a year off work to get your masters, you are losing a year of salary + tuition + books + living expenses = $100k + easy.
That gets _reeeeaaallly_ hard to justify.
Getting work experience will help you realize what is important and why. I'm in the midst of a masters in CS, 5 years out of undergrad. I'm amazed at how clueless most of the other students are. Having the work experience will make the experience of returning to school that much more enriching for you. The best option is to work for a few years, save some money, then go back to school and bang out the masters in a few semesters. My only complaint is that I didn't plan very well and can't just drop my job right now (plus have too miuch responsibility at work). Plan for it and you won't be disappointed.
Maybe it will be useless. Maybe you'll switch careers. Maybe you'd make more money working now than the increased pay later. Heck, in my case, I don't even have a bachelor's in CS and I do pretty well.
On the other hand, after a certain age it gets a lot harder to go back. Your time is suddenly spoken for by family, career, etc. Why take 3-4 years to finish part time at 2012 tuitions when you can knock it out in 1-2 years now?
Does it hurt to hear them lying? Was this the only world you had?
It's not worth getting a Masters in IT unless you are going for executive management. Even then I have yet to see people at that level with that type of degree. Go for your certifications if you are after the money. You will make more with current certifications than a degree!
I notice you say Computer Engineering, not EE or CS. To me, this means you're probably interested in digital design or something similar. If so, definitely get the Master's degree.
I work in a microprocessor design group and we won't even interview someone without a master's degree anymore. 90% of what I learned in school that I apply to my job, I learned in grad school. Grad school teaches exactly what you need to know to do the job in our group, so we don't have to teach you much before you can get started working with us.
So it's not so much that you should do it for money as just the ability to get a job in the field you want. Plus in 1-2 years maybe the job market will be better.
It used to be, perhaps 10 years ago, that developers were hard to come by. Any fool who could write code could get a great development job even if he didn't have a degree. Some folks were being hired without even a HS diploma.
The industry has matured significantly since then.
Right now when I look around at the software architects and principal engineers at various companies in Los Angeles, I see the majority of them have Masters or even Ph.D.s. There are quite a few job opportunities where the job description strongly recommends a masters degree--and in quite a few places where I've done interviews, I've had my boss tell me that person was highly recommended because he had a masters or a Ph.D.
In my opinion, (1) a masters is not worth two years of experience, if you're interested in getting your hands dirty and learning real-world stuff. But (2) a masters will open more doors for you. A Ph.D. will open even more doors.
Used to be the industry was such that simple merit would allow you to work your way up the ladder. Now, you need a degree if you are going to go beyond certain boundaries, regardless of whatever talent and experience you may have.
And my barber said I need a haircut, what were the odds?
What do you mean by "better"? It's better to go for a Master's, and then for a Ph.D. You will learn more and different things, and you will have a great time. This may or may not translate to a better salary later on. But at least for me, a deeper understanding of the subject is very satisfying on its own.
Stephan
This was not the case for me. I got my B.A. in mathematics from a small school and was hired by an aerospace company to operations in an entry-level, but well-paying job. I showed some initiative and moved up the ladder and became a satellite engineer within a few years, and I continue to progress. Most of my colleagues have a Master's in aerospace, but I was able to get there without having an undergraduate in engineering, let alone a Master's (my math degree had a completely theoretical emphasis, even). On top of this I have a better understanding of the business now since I moved up the ranks a little bit over the years.
There are a few engineering classes that I wouldn't mind taking at this point for my own enrichment, but I think a Master's would be overkill for me.
Nowadays, I would never say to someone that a Master's degree is essential to arrive at the job he or she wants. It just takes a bit of hard work and a little luck.
Why back in my day....
Ok, I'll cut the old fogey schtick.
To broadly over-generalize, a Masters in CS will let you skip over the first 2-5 years of your career.
Whether this makes economic sense is going to depend on just how fast you can get that masters, and how much it will cost you.
Beyond about 5 years, work experience becomes far more important than degrees. Which means this is a "do it now or skip it" kind of thing. Going back for a Masters in CS after you've got several years under your belt isn't going to help all that much. (The common exception being getting a Masters in CS when you don't have a BS in CS to aid getting through the HR filter. It helps more than for those with a CS degree, but again not all that much.)
That being said, it's not exactly a wonderful job market out there at the moment. So delaying your entry into the job market until you've got a Masters may be a good idea. This is gonna depend on the job market where you want to live.
My son is graduating next week with a Bachelor's degree in bioengineering. I would have suggested that he go on for a Master's, except that he got a job offer with a prominent company in his field that will contribute substantially to tuition for grad school. At that point, and in these financial conditions, he agreed that he should take the job and pursue the Master's while there.
Personally, I went immediately from undergrad (physics/math) to a master's program (CS/EE) both to dig a little deeper and to optimize my chances at Member of Technical Staff jobs with my then ideal employers, Bell Labs and Hewlett-Packard. Got offers from both!
Live in the Future; It's Just Starting Now!
Too true.
The questions are the same and the answers are just as mechanical. If /. ever put out a FAQ, these types of questions should lead the list.
I have to admit I howl w/laughter at some of the career advice given here. People, if you are not earning over USD120K/annum then you suck and only serve as a bad career example. Yes, only money counts and if you aren't old enough to know better than you should also STFU.
Nothing looks better to your employer than actual work experience. Think about it this way: if you were hiring a programmer, would you rather hire someone with two years experience, or someone with no experience but a master's degree? Someone with a proven track record is a safer bet, and the employers that stay in business usually play it safe.
The Govt will pay, per hour XXX for someone with 10 years experience. If you have an MS, then they consider you to have +2 years XP for pricing purposes.
If it takes you 2 years to get the degree and you earn no extra, then you actually LOSE money by paying for school. That's the Math of it
I have an MS in CS and I can tell you from first hand, for the most part, no one cares at all; particularly contractors.
I hear rumors, and only that, that it matters when you are going for management. The most important thing to consider: Do you want an MS? some MS degrees are seriously the BS classes with a research paper; woot! And, most people cop-out with their MS and take a final test rather than do research.
Bottom line: You won't earn any extra money or prestige. So if you do it, do it only for yourself.
I think I have a good answer for you. I graduated in Computer Science and I've been considering getting my masters for sometime. A lot of my friends started going for their masters while I got a job after interning for a science facility. Immediately I got the standard wage for a computer science bachelor. I made sure that was I was getting paid was competitive and reasonable so that if I were to move on to another company they would offer me something competitive.
My friends worked at the same company as master's students getting paid dump wages. At the same time the company I worked for offered me a 70% pay for any masters classes I wanted to take. I took a course and in the meantime moved to another company that offered me more money the next summer. By the time my friends graduated with their masters companies didn't want them because they had no serious work experience and they all took some seriously bad pay cuts. They also were in more dept because of school.
Your professor is going to tell you to stay in school, because that means he can make more money off of you. In a field like computer engineering (seriously IS majors go back to school and pass calculus so you'll make some money) the demand for you is really high. What causes a lot of confusion with people wanting to get their masters are friends that have other majors that require a masters in order for them to be worth anything and even then they have a hard time getting a job.
The best advice for you is consider getting your masters, but first get a job that you enjoy for the time and pay. (Don't work for bloodsucker companies, there are plenty of chill engineering jobs). Then find out what programs the company offers for people that desire to get their masters . The job I currently work at is better than the last in that if I get an A in a course I get a full reimbursment, B->half, C->25%.
Also ask yourself why you even want to get your masters because you won't be worth more money. If you intend to get your PHD and teach one day then get your masters. I also want to point out that a lot of professors in school are outdated. One of my masters courses we had a masters student teaching because he was the only one in the department who knew python. You make more money in engineering by being on the edge of technology and knowing what's new and catching on. Thanks for listening, I'll keep an eye on this post if there are other questions.
You have to ask yourself why you would consider going for a master's degree.
Faster career advancement? Or different opportunities? A Master's may get you to places that you can't get without it (and a PhD definitely can), but do you want to go to those places? If so, it's a great thing. Research tends heavily towards MSc and PhD types.
If you're planning on being a 'normal' tech geek (developer, sysadmin, web coder, etc. etc.), then the work experience is probably far more valuable. In fact, I think that most computing jobs would be better met by a technologist diploma rather than a computing degree.
"People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
Out of college, I worked 6 years at a small business contractor for the DoD. I still like my job and love the interesting work. A Master's degree will help me win more proposals for my company, and give me more opportunities to do more interesting work as a Principal Investigator. My employer is supportive and is letting me take a leave of absence. So it's a win-win from my perspective.
In this current economy, it's best to stay in school. There are jobs out there, but the competition is tighter. It's the perfect time to buckle down and get that extra education in. Of course you can learn on your own while you have a job. But it's far more convenient to get a TA position and not have to worry about spending hours reading texts and white papers and figuring out things on your own on top of working.
After 2-5 years, the difference an MSE will make vs just a BSE is quite minimal. But that assumes you land your first job. If you have no work experience, an MSE will go a long way towards helping you get that first job. What's far more important is that you start interning now. Part-time work at a company -- if you're in any way competent -- will most likely lead to a job offer before you even graduate. They may even pay for your MSE if you decide to work part-time there.
Of course, the primary concern is your specialty. Picking something you're really good at and understand intuitively where others struggle can be the single-most important thing to standing out and becoming "the guy". It's also the single-most important factor to getting raises early on.
I've you're motivated and have big plans to develope new technologies (basically write your own code or start your own company), no need for a Masters. If you just want to find someone else to work for and work your way-up in their organization, get your Masters.
In good companies the IT people write the requirements and internal company policy grants HR a minor role in the hiring process, they have to adhere to the wishes of the respective department when looking for candidates.
In my anecdotal experience, field expertise triumphed education almost always.
IANAL but write like a drunk one.
Too often, I get the impression from employers that they seem to feel that any kid with a high school diploma and a Microsoft Certification in Office is sufficient enough experience to be a system administrator or software developer. Worse, there is also a lot of pressure that a professional should be paid at the same level as a high school graduate with a Certification in Office.
In one company, the CEO was convinced that his staff could put together a professional web site with an online store for the company using a consumer-level automatic web site generating program. Then he blasted his staff, because the web site didn't work like eBay or the Apple Store.
It gets better!
He was upset that the pictures on the site looked lousy compared to other companies' web sites. That's because he gave a cheap, 2.5MP camera to some engineers and told them to take pictures of the products. Companies like Apple hire photo studios to image their products. Then he really got worked up when deadlines started slipping. That's because he had his engineers and developers working on the web site instead of actually working on finishing product and software development! He started complaining that he was going to let some people go for "incompetence". One of his comments was that he could hire a high school student to do this work. He didn't really get the opportunity to fire anyone, though, because most of the development staff got fed up with him and walked out!
Whew! This water sure is cold!
No offence, but how would you react if somebody told you that your company is losing $10000000 *an hour* because something you are responsible for just broke?
There is no amount of PhDidgery that can teach you to deal with such a situation (unless you are really lucky, but it is rare that PhD and Masters students will be ever faced with such situations).
When people talk about companies prefering experience to academic qualifications this is the kind of things they refer to, not necessarily the technical or cutting edge aspects of any given field.
IANAL but write like a drunk one.
Something that nobody seems to have mentioned is that you get a better perspective of the field once you get work experience.
Once you are an experienced professional then you can judge much better if a Masters will be of any use and which one would be the one to pursue.
IANAL but write like a drunk one.
Suggestions, if you care about the code you will write in your career:
1) Figure out whether you're learning deep CS fundamentals in your undergrad program. A good Masters program will teach you CS fundamentals that make you a better software engineer in a real job. Some undergrad programs don't do that, and knowing the difference should help you decide.
2) Research (really research) the curricula at some graduate programs. They differ. You can probably tell if any of them sound like you'd learn a lot.
3) If you target the Masters degree, GET IT FAST. Make it a goal to finish the degree and start using it. Do as much programming as possible during the degree program, so you're ready to code for real. Use it as a powerup.
I'm a electronics engineering bachelor, and though I consider myself well qualified to the local standards, I haven't been able to find a good job. I am right now considering taking a second degree on computer sciences and go for a master's after that. I'd like to go for a master degree right now but I think that while I may be well for a third world country in South America, I'm not good enough for Developed countries' competition on the same fields.
I got my master's (CS, after a Comp. E. BS) strictly out of economic necessity--it was 2003, and there were no jobs to be had. The length of time it takes to get a master's correlates nicely with the average length of a recession.
Media that can be recorded and distributed can be recorded and distributed.
-kfg
I think it's up to you. If you have some project you'd like to get a chance to work on, want to really dig into something then you should get a masters. I wouldn't do it for purely economic reasons though. I mean, look at these comments, it basically is a wash. Some places limit people without a masters, some won't even higher someone WITH a masters as being too uppity.
get as far from this field of endeavor as possible. No job sucks more, is less rewarding, makes you work harder for your money. Go do something worth doing. Being a fucking drone in cube is the worst hell a person can subject themselves to. The only thing worse is spending 6 years in school for the privilege.
Learn to play an instrument, act, sell sex or drugs. Hell run for office. If the current set of morons can get elected anyone can. Whatever it is it will be better than a job in engineering in this fucked up country!!
IT is not Mechanical Engineering.
Do what you love.
You do want to get your Master's. The real question is when. At one end is the time it may take to get a handle on what you want to do in your career. That usually requires some work experience. At the other end of the timeline is the date you start to work. The longer you are out of school, the harder you'll find it to get an advanced technical degree.
If you are young and don't have a family, I would recommend trying to work and get a master's degree at the same time, especially if you can find a job that will pay you educational benefits. If you study a field you like, it won't be so rough. It's certainly not easy, but you can stretch out a master's degree over 2-3 years. Most semesters I took one class at a time, but occasionally I took two.
In a year, when you graduate, the economy will still be emerging from this recession. The worst will be behind us, but there will still be plenty of time to find a great job. With a Masters Degree, your first job should be much better than the job you would have spent the last two years doing. And those first jobs are bullshit anyway. Phone support, desk side support, crappy web design, jr. developer, etc. With a Masters, the company that hires you will want you doing something useful. Your experience and reponsibility will be greater and advancement up the ranks better. To those telling you to make sure you can use it, I say, pshaw. At the end of the day, 10 years after you graduate, no one will care if you have 10 years experience or 12, but they will ALWAYS care that you have the Masters degree.
The real question is, do you want to make more money, or maybe make yourself more useful? If you want to make more money, GET THE MASTERS NOW. Once you get out in the real world, you will NEVER go back. Some do, but 99% do not. Also, if you will be graduating in a year, we will just be coming out of this recession. Wait one more year, and you will likely see people hiring for real, with signing bonuses and more, especially for people with advanced degrees. You will be in short supply, and in the REAL WORLD(tm) that is always the place to be.
But its your WORK experience that gets you THROUGH that door. I've been in this industry for almost 25 years... no, I'm not that old... I started as a Software Engineer at Intel when I was a Senior in HIGH SCHOOL. I already had almost 4 years of part time experience in Software when I got that job. Did my BSCS-EE get me any jobs? Nope. By the time my fellow high school alums got into the workforce, I was making at least twice what they could get coming out of college. When I've hired (and I was in a hiring role when my compatriots got into the job market) A degree would get you past my HR or Recruiter, but it took experience to get past me.
On the other hand... you SHOULD get a masters... and do it part time while you're working in the industry. But get an MBA. THAT will help your career enormously one day. but it'll be a dozen or so years before that'll pay for itself.
There are a glut of first-degree-only people out there. Your first job at a company may be doing anti-virus work, or other menial "he has no experience, therefore useless" chores. Getting a masters will only put that sort of crap off, but at least you will get better (less crappy) crap work as you start the work world. Over time, your 'top end salary' will also shoot farther than first-degree-only people.
A masters is useful if you want to eventually have a senior role - architect, development manager, CIO etc. Not because it helps much from a technical point of view, but because it helps to separate you from the crowd. But why not work for a year or two to find out whether CS is what you want to do? Then come back to do a masters or if you are that way inclined an MBA. (I am a VP of Product Development who encouraged his son to go into a different field. IT/SW/CS is now a vocation - you do it for the love of the profession - not the easy money it used to be)
Get some experience if you're serious about making a corporate career. That way, you'll know what your strengths and interests are and can focus your masters in those areas. If you have management skills, you can double your degrees with an MBA and a Masters in your area of specialty. If you're never planning on leaving the academic environment, then you'll want the Masters as a step on the path to a Ph.D.
An MBA might qualify you for management in your field, and it also gives you a parachute to use if you either don't like the field or find yourself out of work. Also, there are 17 month MBA programs available. I got mine at Franklin University, Columbus, OH, in 17 months with one evening class per week and a fair amount of homework, mostly essay writing and group projects. I spent at least a few hours one evening a week for homework, sometimes on two evenings. Most group work was done by email. Most of the time I was the editor of the group papers to pull it all together so that it appeared to be written int he same style by the same person (which helps get a better grade than something that is hastily thrown together and doesn't transition well between the contributed parts).
Be aware that with a master's degree of any sort, you should expect to see more group work, something that I didn't care for since the group can pull you down and some might use the group to try to get a free ride with their work. If that latter thing happens, make sure that the instructor knows about it, make up for that person's lack of contribution to the project, and move on. That way the group is less likely to take a hit on the grade, but someone must make up for the slacker.
Also, don't expect a master's degree to make a big entry level salary. But it should get you more respect from interviewers and probably a somewhat higher salary over what you would get without one. If you get an MBA, you can work into your career interviews that you would like to get into management eventually once you have proven yourself to your superiors.
One other thing I would mention if you have any elective credits to earn yet is to look into experiential learning credits. I earned about a year's worth of college credits in my undergrad work that way and it didn't cost me anything but the effort to document my experiential learning. I got into a routine where I could crank out one documentation "booklet" in a day or two and get 3 credit hours for the work, even a course waiver if it was for one of my required subjects. I got out of a lot of schooling by doing that!!!
Donald
I have a BS in math. While working I went nights to get an MBA in Operations Research. Picked up all the business courses that a math undergrad doesn't get. BTW, never did use the Operations Research much. Just knew I could get a lot of computer science and math that I could get good grades in. Check around for CS specialties in the MBA programs.
"There are good ships, and there are wood ships, the ships that sail the sea. But the best ships are friendships, and ma
I was development manager before becoming an independent consultant. For the most part a master's degree meant very, very little in the hiring process. If we were looking for entry level it was a matter of passing a basic technical test and interviewing well. If we were looking for senior it was work-experience centric.
In our limited set of hires that approach was justified. We hired both a masters and a bachelors directly out of college. The bachelor performed better in the interview and went on to perform better in the job.
If you're looking to make more money think MBA, sadly.
Seriously, in today's economy where you have tens of thousands of unemployed job candidates with masters and 3-10 years work experience hunting for jobs and beginning to settle for lower level, lower paid positions just to feed themselves, a masters and a Ph.D. is a very good idea, if for no other reason but to delay your entry into the job market.
Besides, 2 years work experience on a bachelors and 2 years work experience on a high school diploma is the same. This is really your only chance you'll ever have in life to get the masters and it will make a huge difference later on when you want to move up the corporate ladder.
The masters might not help you today, but it will in 10-15 years.
If you have the option to get a masters degree now and you're not jumping at the opportunity, you should just drop out and flip burgers instead.
As I've said it many times, it's been my graduate studies (funded in part by a large local hospital on advanced security topics on distributed systems for medical records) that got me two of my jobs (one in a medical-related start up, and another one in a large multinational bank.)
It was also the fact that had grad studies that I got hired for a job to implement a custom network protocol from scratch (which wasn't really rocket science, but it was my credentials that got me the gig.)
Again and again for the last decade, it's been my grad studies that have helped me 1) get a job, and 2) apply my grad studies to the job at hand.
A masters is what you make it out to be. You are a good or terrible software developer with or without it.
Get a full time job at a university. Plunder the employee benefits. i'm about to start at a very expensive school for 100$ a credit.
Utilizing the synergization of benchmark e-solutions to pre-workaround action items!
Technology changes, and eventually you will enter a branch that demands specialisation. That may serve you well for 15 - 20 years, when you will discover that your obsolete. Technology advanced faster then you could keep up. Get a degree. Get an Masters and even an MBA. Actually, become a doctor-- a job for life. I am around 50, and considered over the hill, and I have a masters in math. Too expensive they say, or too old. Am I bitter. No, because I should have started my own business.
Leslie Satenstein Montreal Quebec Canada
I had more fun in grad school than undergrad. I guess the fact that I had a BS to fall back on. 2 more years to live and have fun. do it.
Pragmatic answer: check the pay scales for MS vs BS. Also amortize the two years lost salary while still in school. Emotional answer: consider the source. Slashdot responses will be evenly split. Those who have Master's will endorse it. Those who stopped at BS will poo poo it. Fatherly Advice: make sure you like school and remember that grad school is a different world. It's more research-oriented than undergrad studies.
If you want to work in a foreign country, find out what the job market there requires. It's much easier to get a CS job in Germany with a masters because they are all about the papers/certificates.
Seriously, a person fresh out of grad school in a subject is much more desireable than someone with a bachelor and proven work experience in the same subject.
Frustrating, but true.
Go for the Masters but be sure to apply for a Graduate Assistant Position with one of the lead professors at your University.
This will sky rocket your career and allow for a mentoring session after your undergraduate degree. Although many are lucky to have this in their work life, very few positions is a mentor guaranteed. Most of the time these Professors are in Education for a reason and have excellent contacts in Industry. With the Economy as it is now, getting a full ride to Graduate School while having a built in Mentor, and doing research in a field you enjoy is a win win. Also look to the advantage to starting right away, some of your course work may be waived and adds to the ROI of time invested now vs later.
This was a no brainer for me in the same position
Richard Bodey
Web Development | Networking | Security | Admin
http://www.wkntech.com/
RickBodey@WKnTech.com
The responses I'm reading rather evenly fall on both sides for the same reasons!
* Get your Masters you will:
* be hired more readily - companies look for people with degrees.
* be paid more when you are hired for a net $ win
* Don't get your Masters, get a job you will:
* be hired more readily - companies assume people with Masters want to be paid more and screen them out.
* make 2 years of income which will more than offset the cost of grad school plus any increase in pay you might get
This isn't terribly surprising - any one person on /. has only worked for or been exposed to the hiring practices of a relatively small number of companies, even if they've been changing jobs for at the average tech rate (?) of 3 years or something.
The conclusion you should draw from this is:
* when you go to work, either way apply to lots of companies! Some might screen you out because you have a Masters or because you don't!
* salary probably has a lot more to do with your negotation skills, location, job market etc.
I have some other things for you to consider, given how open you left the question: "which is better?"
Obviously your professors think you should stay in school. After all - they all did, didn't they? It worked out for them. And they might have some non-obvious stake in you sticking around too.
Well, what do you mean by better? This is a pretty personal decision. Perhaps "make more money (immediately or in total)" isn't your deciding factor.
How much do you like your field? Many responses seemed to assume that you wanted to get a career as a sysadmin/network admin, which wouldn't match your degree (not that it matches any degrees really). Do you want to get a fair bit more depth in a more narrow subject area in your field of study? If you are unsure about your field, you should probably get out and work!
Consider that once you are working full time, it will be a LOT harder to go back to school even part time, even if you work for a company that pays for all of it. This will get even harder if you get married or have kids.
Maybe you are already in a serious relationship or have kids? That should drive you pretty solidly towards "get a job."
How much do you care about -where- you work? Do you want to work for a specific company or range of companies? Maybe do a straw poll of the company or companies you are interested in, and see if THEY prefer an advanced degree. In computer engineering you might want to go work for HP, Intel, AMD or IBM - in which case a PhD might not be out of the question. And you might even get paid accordingly.
How much did you pay for your undergrad? If you got a fancy degree from Caltech or MIT at $50k/yr you are going to have a hard time "upping" that with a Masters. On the other hand if you went to a "low end" school (this is by your field mind you! An affordable state school could have an excellent rep for your field) AND you have excellent grades it might be wise to try for an MIT Masters to top it off.
What is your funding situation? Would you be paying your way (or would someone else pay it for you?) or would you need to be a TA/RA? Obviously if you've got someone lined up to pay it for you that weighs pretty heavily in the "yes do it" side!
Interested in starting your own business? How does the degree factor into that? Timing - would a 2 year delay help or hurt? Funding - would the money you spend on your degree impact your ability to start the business? Or are you one of "those" people who find grad school the perfect environment in which to start a startup?
Some mentioned teaching - but I didn't see much mention of mention teaching college. I'm guessing since you didn't mention it that teaching high school is not under consideration or you'd be looking at the well-covered Education degree. Teaching college doesn't necessarily mean full time. Increasingly colleges are hiring adjunct facult