Recruiters spend an average of six to ten seconds scanning a resume before deciding whether to keep reading. That's not a lot of time. If your resume doesn't communicate value immediately, clearly and concisely, it gets passed over. The good news is that most resumes fail for the same fixable reasons. Here's what you need to know.
The One-Page Rule
For CS students and new graduates, one page is not a suggestion. It's the rule. Unless you have 10+ years of professional experience, a two-page resume signals that you don't know how to prioritize. Recruiters at large tech companies review hundreds of applications per role. A concise, well-curated single page shows you respect their time and can communicate efficiently, which is itself a skill they're hiring for.
If you're struggling to fit everything on one page, that means you're including too much. Cut older or less relevant experiences, reduce bullet points to two or three per role, and tighten your language. Every word should earn its place.
Lead With Action Verbs
Every bullet point on your resume should start with a strong action verb in the past tense. This structure is active, direct, and easy to scan. Compare these two versions:
- Weak: "Was responsible for managing the team's deployment pipeline."
- Strong: "Automated CI/CD pipeline using GitHub Actions, reducing deployment time by 40%."
Strong verbs to use include: Built, Designed, Engineered, Implemented, Optimized, Reduced, Led, Launched, Automated, Refactored, Deployed, Integrated, Analyzed. Weak verbs to avoid: "helped," "worked on," "was responsible for," "assisted with."
Quantify Your Achievements
Numbers make accomplishments concrete. Wherever possible, attach a metric to what you did. You don't need exact figures; reasonable estimates are fine. Ask yourself: How many users? How much faster? How much did costs drop? What was the scale of data involved?
- "Reduced page load time by 35% through image optimization and lazy loading."
- "Built a REST API serving 500+ daily requests with zero downtime over 3 months."
- "Scraped and processed 10,000+ records to build a dataset for ML analysis."
Even on academic or personal projects, you can quantify. Scope, scale, performance improvements, and user counts all count.
Tailor It to Each Job
Sending the same resume to every job is one of the most common mistakes students make. Job descriptions are a roadmap. They tell you exactly what skills and keywords the team values. Mirror that language. If the posting mentions "React" and "REST APIs," make sure those exact terms appear in your resume, not just "frontend development."
This matters because many companies use Applicant Tracking Systems (ATS) that automatically filter resumes before a human sees them. A resume that doesn't contain the right keywords gets rejected before anyone reads a word. Tailoring takes ten minutes per application and dramatically improves your hit rate.
Common Mistakes to Avoid
- Objective statements: Replace them with a short skills summary or just skip the top section entirely. Nobody needs to read "Seeking a challenging position where I can grow."
- Including every class you've taken: List your degree and GPA (if above 3.2). Relevant coursework is optional and should only include upper-level technical courses directly related to the role.
- Generic project descriptions: Don't just list what the project is. Explain the technical decisions you made and what you achieved with it.
- Unreadable formatting: Use a clean, single-column layout with consistent fonts and spacing. Tables, columns, and heavy design elements often break ATS parsers.
- Typos and inconsistencies: One typo can disqualify you at a competitive company. Proofread three times, then have someone else read it too.
Your resume is not a complete record of your life. It's a curated argument that you're the right person for a specific role. Treat it like a product: iterate on it, get feedback, and keep improving it. The version that gets you your first internship will look very different from the one that gets you your first full-time job. That's a good thing.