Some superficial and not-so superficial thoughts: Superficial things (not that big of a deal, but still things I noticed): 1. Post a pdf so we can check wheth

Some superficial and not-so superficial thoughts: Superficial things (not that big of a deal, but still things I noticed): 1. Post a pdf so we can check whether you might have a problem with the format of your resume (because I hope your resume isn't formatted like in the Google doc) 2. Some of those courses you list are ones that nobody is going to care about (Econ, for example) 3. Move your Honors section to the bottom, either before or after Leadership Activities. Your education is most important, followed by experience. You should move Technical Skills above Leadership Activities, and below Projects. This isn't a set-in-stone rule - it's just that in this case, your leadership activities aren't that impressive, so the Technical Skills section is more important. The guidelines is that the most impressive and important things go first. 4. Shorten the summary for your NSF Researcher position. 5 bullets is too much IMO. Also, 99% of people will have no idea what the first two bullets are even talking about - find better ways of phrasing what you are saying. When I read about " the Chung-Ross conjecture on a Clos network by simulating different possibilities of data sizes," my brain just glosses over that. Ignore this advice if you're confident that people at the firm you're applying to will know what you're talking about. 5. You use a lot of vague action words like "Worked on," "Collaborated," and "Participated." Find better ways of saying exactly what you did. 6. There are some minor grammar mistakes you need to fix. 7. Ideally you should have your projects on something like Github, and then have a link to your Github profile at the top of your resume, under your contact info 8. Your resume should be 1 page maximum. (One page, one side). Some not-so-superficial things to consider: 1. Have you thought about getting a personal website? You can put a blog on there (with technical blog posts), and you can put a portfolio there too. The blog posts don't even have to be that impressive - a well-written tutorial of a technology you just learned can get passed around over the Internet. I had an engineer at a really hot startup reach out to me because of my website and blog. I've had engineers at a big tech firm (rhymes with Godzilla) follow me on Twitter because of a blog post I wrote. This can be time consuming, though, so I think it's more important to have projects than it is to have a personal blog (see #2). 2. Also, it's hard for us to suggest things for you to learn because we don't know what you're looking for. When I look at your resume it looks like you have mostly a systems development background; is that what you're looking for? For example, I know I want to work in application development - so I focus mostly on web and mobile (iOS) development. What do you want to focus on?