This Is What A GOOD Resume Should Look Like:

Note: This is for a US-focused resume. CVs for India and other countries have different expectations, although many of the points will be the same.

Although the example here is a developer resume, almost all of these points (everything but #9 and #11) apply to other positions as well.

If your resume doesn't look like this, we can help!
One Page Resume: Recruiters do not read your resume; they do a 15 - 30 second "spot check" of your resume. When your resume is too long, it just takes your best stuff - the stuff that would have made the "one page cut" - and dilutes it with more mediocre content. Lengthy resumes do not make you more impressive, and there are many other reasons to keep your resume short too. A good rule of thumb is to keep your resume to one page if you have less than 10 years of experience or at most two pages if you have more than 10 years of experience. And if you think you can't get your resume to just one page, trust me, you can! You just need to think about what is really important for a recruiter to see.
No Objectives: All an objective does is state, in a wordy way, what position you're interested in. The company already knows that because you applied for a particular position. At best, it'll just waste space. At worst, it'll limit you since it'll exclude other positions that might have been interesting to you.
Use a Resume Template with Columns: Unless you're great with design, you probably shouldn't be creating your own resume template. It'll most likely look sloppy. Use a template, and make sure it has multiple columns. Using three columns, for example, will allow you to put the company name, position, and date all on one line. This makes it easier to read and saves space.
Use Tables: If you're using Microsoft Word to create your resume (which you probably should), use Microsoft Word's "tables." Just make sure to hide the borders afterwards.
Short Bullets: Because resume screeners only spend 15 - 30 seconds on your resume, length bullets - anything that feels like a paragraph - just won't get read. Keep your bullets to one to two lines (with one line being better than two).
Accomplishment Oriented: Your bullets should focus on your accomplishments - that is, the impact you had - rather than your responsibilities. What did you build, create, design, optimize, lead, etc?
Quantify: Whenever possible, you should quantify your accomplishments. If you optimized something, by how much? If you won an award, out of how many people?
Resume: The general rule of thumb is to list your GPA if it's at least 3.0 or higher, but there are two important rules to know here: (1) You may choose to list your in-major GPA if it's higher than your overall GPA, but you need to specify that it's your in-major GPA. (2) If your school uses a different scale (such as a 10-point scale), you may want to convert your GPA to a 4.0-scale which will be more widely understood.
Projects: Most candidates should pick their top 3 - 5 projects to list on their resume. These can be academic required project or independent projects. They do not need to be completed or launched either. As long as you've done a "meaty" amount of work on them, that's good enough!
Additional Experience: You can put additional experience, like leadership activities or awards, in a section like this (changing the name of the section depending on what you list). Be careful here to focus on what really matters. If you're applying for a coding role, your role as an eagle scout in high school is probably not very important!
Languages and Technologies: It's a good idea to list your languages and technologies, but remember that anything you list here is "fair game" for the interviewer to test. If you want to list a language but you happen to be a bit rusty in it, consider listing it as something like: "C++ (Proficient), C# (Prior Experience), ..."
What did you NOT include?: Is there anything impressive / interesting that you've done that you left out? About 50% of candidates leave out an important project or other component of their experience because it wasn't finished / "official" / etc. If you've done it, and it's impressive enough to "make the cut" (you shouldn't just list everything you've ever done), then it belongs on your resume!
Download this template: Microsoft Word | LaTeX

If your resume doesn't look like this, we can help!


is a comprehensive book on getting a job at a top tech company, while focuses on dev interviews and does this for PMs.

Learn More


CareerCup's interview videos give you a real-life look at technical interviews. In these unscripted videos, watch how other candidates handle tough questions and how the interviewer thinks about their performance.

Learn More

Resume Review

Most engineers make critical mistakes on their resumes -- we can fix your resume with our custom resume review service. And, we use fellow engineers as our resume reviewers, so you can be sure that we "get" what you're saying.

Learn More

Mock Interviews

Our Mock Interviews will be conducted "in character" just like a real interview, and can focus on whatever topics you want. All our interviewers have worked for Microsoft, Google or Amazon, you know you'll get a true-to-life experience.

Learn More