Recruiting as a Freshman or Sophomore, Part 1: Having a Purpose, Resume Advice, and Resources

20 Dec 2017


Recruiting for internships (and clubs, and research positions, and…) as a freshman or sophomore can be daunting at times, and there are not a lot of resources out there specifically tailored to underclassmen recruiting. Where do you start? How do you apply? How do you maximize your chances of getting responses? How do you “do” a technical interview? This blog post will be the first in a series aimed at freshmen and sophomores that will hopefully answer those questions!

Part 1: Getting Started

I want to be realistic and honest with you, so first let’s get a hard truth out of the way: most companies, unfortunately, are looking for juniors and seniors, because they are hoping that after the internship the junior and senior interns will sign contracts for full-time positions after graduation.

However, please do not be bummed out! It does NOT mean you are not qualified, or that companies don’t want underclassmen! It is still absolutely possible to get an internship as a freshman or sophomore! It might take a bit more hustle and hard work, but it’s entirely possible. In addition, there are a LOT of freshmen-friendly companies out there, and there are even internship programs that specifically choose lowerclassmen! I will get into those programs in more detail in a later blog post.

Also, please keep in mind that across the country, the broad majority of CS students do not look for internships their freshman or sophomore year, so if you recruit as a freshman or sophomore you are already ahead of the curve! You will be much more experienced by the time you are a junior or senior.

Hopefully I wasn’t too much of a downer with those thoughts. If you are still reading, let’s get started!

What is Your Purpose?

Before even starting to recruit, you should have a purpose and a plan. Not only will your recruiting process be clearer as you will have an idea of what you want and what your goals are, you will often get asked by a recruiter or hiring manager, “What are you hoping to get out of this internship?” Having a good answer to that question is important. That being said, before even continuing to read this blog post, you should start thinking about your answers to the following questions:

  1. There are so many valuable, productive things you could be doing next summer–out of all of them, why do you want do an internship?
  2. As I mentioned before, most students don’t start finding internships until their junior year. Why do you want to start so early?
  3. What sorts of CS jobs are you interested in doing? Alternatively, what sorts of CS jobs are you interested in learning more about?
  4. There are CS jobs in every industry–music, finance, healthcare, and beyond. What industry interests you the most? What industry do you want to learn more about?
  5. If you don’t end up finding an internship for next summer, what are your backup plans?

Your Resume

Style Templates and Resources

One thing that every company asks for when considering a job candidate is a resume. Whether you are looking to create an entirely new resume or simply edit an existing one, I highly suggest starting with an online template–creating your own from scratch is pretty tedious. There are many great LaTeX resume templates out there, like these or this. If you don’t know LaTeX, you can also use Word or other text editor (though you will likely need to learn LaTeX eventually for other Berkeley CS classes, so now is as good a time as any to start learning!). Here are some great Word templates.

Once you have your template as a starting place, you can edit it as you see fit.

Categories and Content

Your resume should generally have the following categories:

  1. Name and contact info
  2. Education
  3. Experience
  4. Projects
  5. Skills

At the top, include your name in large font. Next, list your LinkedIn if you have one, your Github if you have one, your school email, and your phone number. Some people include their addresses; I personally don’t include it because I’ve never encountered a need for it. However, some people do include it as it shows to local companies that they don’t need to relocate for work, which may be appealing.

Next, include your college and major. Also include any relevant classes you took, using commonly-understood names. Instead of listing “CS 61A” list it as its full name “Structure and Interpretation of Computer Programs”.

For experience, you can list any extracurricular activities that you have done. Include some details under each activity describing what you did and what it was about. Ideally, you should emphasize achievements that you had during that activity. One small tip someone gave me was to make sure you start all your description sentences with an action verb, as it comes across as more impactful–for example, instead of saying “For the robotics team, I built a pneumatic subsystem” switch it around and say “Built a pneumatic subsystem for the robotics team”. There is also no need to include words like “I”, “me”, etc. because all the experiences listed on your resume are assumed to be yours; if they aren’t yours, then they shouldn’t be on your resume anyways. Prioritize activities you did in college, but if you have extra space feel free to include high school stuff too.

CS employers typically like seeing projects on a resume, because that shows that you know how to code beyond simply learning theory in a classroom. Projects you should list here can include hackathon projects, personal projects, and projects done for a club or outside organization. You can also list substantial projects that you have done in school, like for 61A and 61B. Give a description of the project, mention the tech stack that you used, and if possible include a link to it.

The Skills section should take up the least space on your resume. Its role is to simply provide the reader with a quick snapshot with the programming languages, frameworks, and tools that you are familiar with. Some people like to add extra flair/info to their Skills section, like a note on how well they know each programming language, but I personally prefer to keep this section short and concise: “Here are the skills I know; Here are the frameworks I know.”

More Resources

And don’t just take my advice; there are lots of resources out there that I personally found useful when figuring out what the hell to do with recruitment.