OK brosephs I need your opinions. While I have a tech and software background I never took the career path of a coder so somewhat flying blind here.
I have a brother who is graduating a decent state school with his BS in CS soon, OK GPA but nothing outstanding and he's got 4 years of PT experience working in the lab at the school testing new hardware and software to meet IEEE (I think?) specs.
They've offered him his masters for free if he stays on at the lab.
100% with what wormie said.
It depends on
his interests and the
work he is interested in. I would advise him for INFORM himself well, and make his own choice based on his interests and the work and career he might like.
Step 1: inform himself
- research career paths & his industry & hardware/software companies that might employ him. See what they DO, and might WANT to do in FUTURE (2-8 years).
- postgrad is really about RESEARCH.... so he better like research (that he can then help guide grunts to apply to his design later)
- If he is not already there yet, then do a lot of talking to grad students, professors and others at the lab and his university to get a *feel* for the hands on work, research, code & projects they are doing.TRY to talk to industry contacts if he can
A lot of Comp-Sci is different from some other areas of research this way because if you are so interested and inclined you can
almost just study and go and code in your basement and get very good practical experience. Look at game emulator community for example
Self guided learning experience can be VERY highly valued, MUCH more so than just *grades* from a student factory (undergrad Univ).
Step 2: decision
So after informing himself, talking and investigating projects & the work involved, advise him to make his own decision based on IF:
- he is at all interested in the research or development of something more advanced than just grunt coding and making money.
- he is an independant thinker with some interesting ideas or an deeper interest in some promising, usefull area of study? (***)
AND
- .... he has some idea what knowledge & skills will be desired by certain employers that he might like to work for? Basically, make sure there are employers out there that will apply his research.
I would recommend he NOT do MS if he is just doing it for money/job though. Career interest should be there, ballanced with a decent chance of non entry job after. As long as he is not sitting on his ass in school *just doing bare minimum for grades*, and getting some real work experience (coding or relevant specialization) doing his research he should be in a
better position finding a NON entry level job after graduating IMHO. His professors and colleagues should be the ones to seek most information and guidance from. His goal is to get a feel for the market and opportunities in the industry related to his interests.
I would just invite him share his findings with you and family so you can provide an ear and some feedback and opinion, but I would let him do all legwork and decision making without specific judgments for him.
(***) If he does NOT know what he wants to do, or is unable to find out and cultivate any contacts socially to inform himself well enough for his satisfaction to make a decision..... then he should probably drop the *deal* and go to work. Coders do not have a long shelf life career wise btw...... you are expected to progress or risk get replaced by university grunts (or worse soon).
Suggested reading: for a little perspective from present....and future:
No, tis not doomsday yet but automated learning systems are looming..... and will be highly disruptive to ALL thinking professions in the especially in the IT market. There are a LOT of grund *simpler* entry level coding jobs out there ready to be pruned ......
I also think the risk is greater because if he doesn't do better at his MS, he's going to be competing a lot with higher GPA undergrads with less pay requirements/expectations and will suffer.
So what is your experience for software engineering and/or hardware/embedded devices? I perceive there to be very little practical value from an MS and that it might make his eventual job search harder rather than easier if he's competing with recent BS grads. It would be very different if he were going to a top school (or ivy league) or going for something like CE or EE in postgrad.
Thanks
I would NOT get him worry much about $$, GPA or any such stuff because once you are in (work).... nobody gives a sh*t if you got a A- or A+ as LONG as you can WORK well and THINK well. In general F*ck grades, most best jobs are gotten through contacts anyhow, shoot for that.
Re: very little practical value from an MS
IMO it would be up to
your brother to decide if Masters (or phd) would be a worthwhile specialization towards a particular career path. If he so chooses he might want to obtain self guided learning/research for MORE (specific) experience but ONLY for certain jobs, at certain companies (for him to figure out).
Once you are in the industry and get some software dev & lifecycle experience, it would not be difficult to change tracks into different area. It can often be a great asset (broader vs narrower experience). See
Noodleface
here for example.