Fundamentally, as someone who went to a Public State University, I feel your pain. Let me take a look (based on my experiences of reviewing resumes)...
Analysis of your "about me" section:
Your CV is "meh". Only interesting thing is the grad school class. Your GPA isn't listed.
Resume:
If I ask you in-depth, hard questions about any language or tech on your resume, I expect an answer. If you can't give me a deep answer, I will give you negative points in my mind. You listed those techs, so you better have something to show.
WRT Technologies. I am a bit idiosyncratic: I want to know your preferred OS and whether you can handle source control. Everything else is noise. You have too much noise.
Your internship this summer details don't tell me why you're awesome. It's too generic.
Your S12 research is ambiguous. what did you find? I don't know what you can do for me.
I don't really care about your in-progress work unless you have a github. You should highlight your leadership experience in tutoring. You should highlight your Honors courses.
In summary, you are an above-average candidate compared to most CS resumes I've seen. Probably in the 80th percentile of the last batch of resumes I looked through. However, you are not a must-hire in my opinion.
---
In order to get to "must hire" state in my mind, you need something like the following:
* Mastery of written communication.
* Explanation of what you have done at each position, why you uniquely made it happen, and what you can do for me and my team.
* Public code repo with a long history and a decent amount of loc in it. You've developed at least a small system (1-10KLoC) and maintained it for years. You support users of it.
* You have studied a "far out" technology - one that may never be written on the job. The more depth is shown here, the more commitment to your craft is demonstrated. At a minimum, this would be, for instance, learning Perl 6 or Haskell. At the higher end, it might be something like writing a working simulator of the CM-2.
* You have extensive internships at well-known companies. While this is limited by location and funds somewhat, it demonstrates that you can play ball with the big boys.
---
Understand that you can better your marketing quickly - set up a github and upload a project, wipe out the placeholder links, rewrite your resume to better express your capabilities. But then the slog starts. You need to commit to building your craft, constantly, in a visibly demonstrable way. Some of that might be expressed via open source, or it might be expressed by a portfolio of shipped software. That's up to you. And, further - express yourself in a more careful fashion. No one wants to take the risk of hiring someone who complains life is unfair.
While I am not a hiring manager, I do assist with technical hiring. I am always happy to look at your resume (or anybody else's) and provide feedback and critique. My contact email is in my HN profile.
The flaw in your thinking here is that there's some sort of "standard" template for a resume that will highlight your excellence. A resume is a sales letter designed to show how awesome you are. Include anything and everything that makes you look good.
As an example, with the research paper, highlight why it was impactful. Saying the paper was published in one of the most prestigious journals in its field is vastly more effective than telling us what your paper was about.
Your work experience tells me what you did, but it doesn't tell me why you're awesome. As an example-my resume highlights the fact that I saved my employer millions of dollars. It only glosses over how.
So write your resume in a way that would make someone say "this guy is awesome", rather than trying to write your resume in a way that describes your life.
No idea what a "official" CV is like. I know I like to see a GPA listed for a college student.
> How can I make those more specific? In my eyes they seemed like pretty specific details to me.
What, precisely, made your internship valuable? Why should I read it as anything more than "wrote some code in C#"?
> I don't know how to compress a research paper into a two sentence resume description. Even the abstract is longer than that by an order of magnitude.
Yup. Rewrite, rewrite, rewrite. More exactly: What did you do in this project? What results did you produce? Did a paper come from it?
> People care about either of those??
I do. Others might not. Tutoring & leadership indicates soft skills, which are, hmm, about 50% of my job... at least. Honors indicates drive & capability beyond the usual "Got Degree, Where's A Job" attitude of the average college student.
Interviewing, IMO, is idiosyncratic. Different people look for different things.
Analysis of your "about me" section:
Your CV is "meh". Only interesting thing is the grad school class. Your GPA isn't listed.
Resume: If I ask you in-depth, hard questions about any language or tech on your resume, I expect an answer. If you can't give me a deep answer, I will give you negative points in my mind. You listed those techs, so you better have something to show.
WRT Technologies. I am a bit idiosyncratic: I want to know your preferred OS and whether you can handle source control. Everything else is noise. You have too much noise.
Your internship this summer details don't tell me why you're awesome. It's too generic.
Your S12 research is ambiguous. what did you find? I don't know what you can do for me.
I don't really care about your in-progress work unless you have a github. You should highlight your leadership experience in tutoring. You should highlight your Honors courses.
In summary, you are an above-average candidate compared to most CS resumes I've seen. Probably in the 80th percentile of the last batch of resumes I looked through. However, you are not a must-hire in my opinion.
---
In order to get to "must hire" state in my mind, you need something like the following:
* Mastery of written communication.
* Explanation of what you have done at each position, why you uniquely made it happen, and what you can do for me and my team.
* Public code repo with a long history and a decent amount of loc in it. You've developed at least a small system (1-10KLoC) and maintained it for years. You support users of it.
* You have studied a "far out" technology - one that may never be written on the job. The more depth is shown here, the more commitment to your craft is demonstrated. At a minimum, this would be, for instance, learning Perl 6 or Haskell. At the higher end, it might be something like writing a working simulator of the CM-2.
* You have extensive internships at well-known companies. While this is limited by location and funds somewhat, it demonstrates that you can play ball with the big boys.
---
Understand that you can better your marketing quickly - set up a github and upload a project, wipe out the placeholder links, rewrite your resume to better express your capabilities. But then the slog starts. You need to commit to building your craft, constantly, in a visibly demonstrable way. Some of that might be expressed via open source, or it might be expressed by a portfolio of shipped software. That's up to you. And, further - express yourself in a more careful fashion. No one wants to take the risk of hiring someone who complains life is unfair.
While I am not a hiring manager, I do assist with technical hiring. I am always happy to look at your resume (or anybody else's) and provide feedback and critique. My contact email is in my HN profile.
Best wishes for your future.