Aikouka
Lifer
- Nov 27, 2001
- 30,383
- 912
- 126
In my software engineering experience, it would probably be easier for you to get a job with a Bachelor's and consider going to school while working for any graduate work. It's also good to note that some companies will pay for it. Companies tend to hire a decent amount of newer workers for the "easier tasks" (not to say they're simple) simply because they don't cost as much money.
Graduate degrees can also cause a problem if your company tries to find other work for you. Usually a doctorate would mean a certain pay grade, and they've got to find room for you in their budget. A coworker told me a story about how their program was performing under-budget (and on-time of course), and they ended up placing this high-level, PhD on the team simply because there were no other spots for him, and they had the budget to support him. The guy supposedly caused more harm than good because he couldn't even code in the language, and usually made mistakes.
I've only got my Bachelor's and have considered getting a Master's, but my thought was... what am I going to get out of it? Is it truly worth working and going to school at the same time? At my previous job, I knew people that did that (the company paid for it), and they literally had very little free time for themselves, and I don't really think I'd want that... especially when I wouldn't get much out of it.
In short, I'd probably just stick with a Bachelor's unless your school has something like a 5-year Master's program (includes Bachelor's obviously).
Graduate degrees can also cause a problem if your company tries to find other work for you. Usually a doctorate would mean a certain pay grade, and they've got to find room for you in their budget. A coworker told me a story about how their program was performing under-budget (and on-time of course), and they ended up placing this high-level, PhD on the team simply because there were no other spots for him, and they had the budget to support him. The guy supposedly caused more harm than good because he couldn't even code in the language, and usually made mistakes.
I've only got my Bachelor's and have considered getting a Master's, but my thought was... what am I going to get out of it? Is it truly worth working and going to school at the same time? At my previous job, I knew people that did that (the company paid for it), and they literally had very little free time for themselves, and I don't really think I'd want that... especially when I wouldn't get much out of it.
In short, I'd probably just stick with a Bachelor's unless your school has something like a 5-year Master's program (includes Bachelor's obviously).