Ask Slashdot: What's The Best Job For This Recent CS Grad?

One year away from graduating with a CS degree, an anonymous reader wants some insights from the Slashdot community: [My] curriculum is rather broad, ranging from systems programming on a Raspberry Pi to HTML, CSS, JavaScript, C, Java, JPA, Python, Go, Node.js, software design patterns, basic network stuff (mostly Cisco) and various database technologies... I'm working already part-time as a system administrator for two small companies, but don't want to stay there forever because it's basically a dead-end position. Enjoying the job, though... With these skills under my belt, what career path should I pursue?
There's different positions as well as different fields, and the submission explains simply that "I'm looking for satisfying and rewarding work," adding that "pay is not that important." So leave your suggestions in the comments. What's the best job for this recent CS grad?

Comments

Security.

[johnnys]

Security is a growth industry.

Big - Small

[utahjazz]

Start at a big company. A big software company. After a while, start looking to leave there and go to a small company.

Why: If you start at a small company, you will confuse the freedom for chaos. You will not appreciate how easy it is to get things done. If you start at a big company, you will learn some big company processes. A few of them are good, most of them are bad, and you will probably have a very constrained job. Then move to a small company where you can actually do stuff.

A prof once put it this way: Work at a big company to learn stuff, then work at a small company to apply what you've learned.

We don't know either

[heck]

We don't know what you find interesting or challenging. you may not know either until you bounce through some place.

go find a company where you like the people; you've got the skill set that most companies are looking for. And figure out what you like. While happiness does in part come from not having a soul sucking job, having a not sucking job that pays enough to not have worries and be able to do the other things in life is just as important.

Despite what they tell you, a job is still just a means to make money to be able to afford to live. You can be paid to do that which you enjoy (shh, don't tell them) - and it is still a job. And before someone says "but but but" I am not saying take a job that sucks your soul out through your eye balls; I am saying I accept the fact that while I love cooking, and I also recognize that when I am done I have to clean the kitchen and if I don't clean the kitchen I suck as a person who shares that kitchen with others. Cleaning the kitchen is fun (and meaning it) said no one ever. (So as much as I do enjoy my job, it comes with some responsibilities that I have to suck it up, realize this is what I accept money for, and go do them. Much like everything in life. No parent ever said they love emptying the diaper pail either, but the end result has been worth it)

back to the first paragraph - a lot of us have bounced through companies and jobs. Our interests have changed. Our skill sets have changed. The job market has changed. When I started, the Web didn't exist. FORTRAN and C were king. I bounced through CAD/CAM, through two small startups (one still exists, and the other long since swallowed by another startup), to contracting, to a large financial company (where we're playing with Angular and such - you'd be surprised what Fortune 100 companies actually do - but also the job stability is through the roof and I have a kid about to start college, which ties back to I have a job to make the rest of life better)

Now if you'll excuse me, I am going to tie an onion to my belt and go yell at clouds. That last paragraph made me feel very old.