Hello World! What Every CS Student Should Know About the First Job
Join the DZone community and get the full member experience.Join For Free
anyone involved with hiring entry-level technology professionals (or reads posts on reddit’s cscareerquestions forum) is aware that students are being prepared by schools for how to do work in the industry, but are often ill-prepared on how to find work in the industry. there is a major difference between the two, and many grads are being edged out on jobs by equally or even less-qualified peers who were just a bit more proactive about their career. if you think finding a job is only about internships and gpas, please keep reading.
some students feel that if they aren’t working 10 hours a day building the next twitter from their dorm room, or if they didn’t intern at google or amazon, that they will struggle to find work. this is hardly the case, and i assure you that if you do a few things during your college years (that require a minimal time investment and no money), you will be several steps ahead when it is time to apply for your first job.
everyone knows about finding internships, good grades, and putting together a solid résumé. but there’s more to it than that for today’s grads. here are some things that college freshmen (or even high school students) that intend to pursue a career in technology can do to give themselves a head start on the competition.
i tend to find that college students and even early career candidates often have facebook, google +, and twitter accounts, but no linkedin profile.
but i thought linkedin was a place to signup only when i was about to start looking for a job
? nope. linkedin is your
(forgot my audience) address book of professional contacts, and there are plenty of reasons to start building that database and network even before you are a full professional.
did you intern with a company last summer? connect to your co-workers on linkedin. did you interview for an internship, but didn’t get the job ? connect with your interviewers on linkedin. did some industry professionals come to campus and speak to your class? connect with them on linkedin. did a recent grad or classmate start a business? got a f avorite professor? connect!
beyond just the ability to connect like you do on facebook or google +, linkedin also has thousands of virtual networking groups that include a wide range of specific and general topics. many of these groups are related directly to employment, and most of them are monitored (and sometimes infested ) by recruiters that could be valuable connections to make before graduation.
once your profile is completed with your experience and any relevant technical buzzwords to attract recruiters or hiring professionals, you may expect to receive connection invites and blurbs on job opportunities. having more connections means that you will appear in more searches, but most in the industry still use some discretion in connecting.
i don’t want to overstate the importance of linkedin as i think too much is often made of the site by so-called “social media experts” , and endorsements have become a running joke, but industry pros that you don’t know well are more likely to accept a linkedin connection than a friend request on facebook. graduating college with anywhere from 50 to 500 linkedin connections gives you a place to start your job search that is infinitely more productive that applications to random jobs on monster or craigslist.
i write about github so much that even i’m sick of watching myself write about github (where’s my t-shirt?!). if linkedin is your professional address book, github is a combination of your sketch pad, notebook, and even a
folder (did it again) to file past assignments. there are other code repo sites out there, but github is the leader today.
what’s so great about github? first, by using it you’ll learn how to use the git tool itself and how version control works to some degree, which has value in itself (and another skills entry for your résumé). you can also take advantage of github pages , which gives you free hosting and customizable themes for a web page that you can have up in minutes. more importantly, your github account is perhaps one of the best ways to demonstrate your experience to potential employers.
if you are going to be writing some bits of code for various school projects, even if they are small and generic exercises like fizzbuzz or conway’s game of life, why not retain those as potential work samples at github? as your skills improve, you can go back and refactor and optimize your code so that it is representative of your current ability level.
once you develop some comfort level with your coding skills, you can explore some other public repos and start contributing to open source projects or even start your own. you don’t need to have some substantial github account upon graduation in order to get a job, but there is no reason not to keep your code all in a safe place for others to view down the line. a github account has quickly become a common request from many employers in the industry, so having these samples available can make a significant difference.
stack overflow is a question and answer site used by a large percentage of the programming world to help themselves and others. it has a massive collection of past threads that is like a faq for the tech world, as well as many unique threads that would be considered rarely asked questions. the site’s gamification model allows participants to earn reputation points for highly rated questions and answers, and those points can serve as yet another potential indicator of your knowledge as an entry-level candidate.
can i really get a job based on some arbitrary internet points i earned through asking or answering questions? of course not. but again, it serves as an indicator of your interest in the profession, the time you invest in your craft, and your willingness to both seek and provide answers with others in the industry.
i wouldn’t suggest spending hundreds of hours on the site in order to accrue a massive point total, but checking out the questions being asked and chiming in when appropriate has value. the questions and trends will also give you a finger on the pulse of the industry, and perhaps ideas as to which languages or technologies may be lacking a pulse.
users’ groups and meetups are another way to demonstrate your interest while learning. you attend class because you have to (or are supposed to anyway), but you attend meetups because you want to . i have managed a users’ group for almost 14 years that met on a college campus for several years, and many of the student attendees now have highly successful careers. in addition to the ability to hear informative presentations and group discussions, meetups are perhaps the most useful way for students to meet industry pros that may be incredible resources during your first job search. (if you haven’t figured this out on your own, connect with your fellow meetup members on linkedin.)
if you can’t get to group meetings due to location, there may even be some users’ groups and meetups that happen right on your college campus. none at your school, eh? that’s too bad. if only there were a group on campus… congratulations, you are now the founder (and chapter president, of course) of the springfield university python meetup!
creating a profile in any of these sites takes minutes and has no cost. with linkedin you can start making connections in seconds, and logging in even once a month to accept and send connection requests is pretty standard. using github for your coding assignments or projects will become second nature, and exploring other repos can be done as time permits. stack overflow is something you can visit once a week or as necessary, and over time you will build reputation while learning. a user group or meetup is typically a monthly meeting. all this adds up to just a couple extra hours a month, which is a small investment for the rewards it can provide.
Published at DZone with permission of Dave Fecak, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.