Why Most Graduate Tech CVs Get Rejected Immediately
UK tech hiring managers spend an average of 6–10 seconds reviewing a CV at the initial screening stage. ATS software may never even pass it to a human if the right keywords aren't present. The good news: most rejections are avoidable with the right structure and content.
The Correct Structure for a Graduate Tech CV
Use this order for maximum impact:
- Name and contact details (LinkedIn, GitHub, email)
- Technical skills
- Work experience (including internships, part-time, volunteering)
- Projects
- Education
- Certifications (optional)
Notice that Education comes after Projects and Experience. Your degree is the baseline expectation - your projects and experience are the differentiators.
Section 1: Technical Skills
Lead with a concise, structured skills section. Organise by category:
- Languages: Python, Java, JavaScript/TypeScript, SQL, C++
- Frameworks & Libraries: React, Node.js, Django, Spring Boot, PyTorch
- Tools & Platforms: Git, Docker, Kubernetes, AWS (EC2, S3, Lambda), PostgreSQL
- Concepts: REST APIs, CI/CD, Agile/Scrum, Object-Oriented Design, Machine Learning
Don't include every tool you've ever touched. Focus on what you can speak confidently about in an interview. Listing Kubernetes when you've only run a tutorial is a trap - interviewers will ask about it.
Section 2: Work Experience
For each role (including internships and placements), use this bullet format:
Action verb + What you did + Quantified result
Examples:
- ✓ "Reduced API response time by 40% by implementing Redis caching, improving user retention on the mobile app"
- ✓ "Built an automated test suite covering 85% of the codebase, reducing regression bugs by 60%"
- ✓ "Migrated a legacy Python 2 codebase to Python 3, enabling adoption of modern libraries and cutting maintenance overhead by 30%"
- ✗ "Helped with the backend development of the company's API"
- ✗ "Assisted the team with various tasks"
Section 3: Projects
This is your most powerful section if you lack significant work experience. For each project, include:
- Project name and one-line description
- Tech stack (be specific)
- Your individual contribution (especially for group projects)
- Outcome or scale (users, performance metrics, GitHub stars)
- GitHub or live URL link
Strong project example:
PriceTracker | Python, FastAPI, PostgreSQL, React, Docker | github.com/yourname/pricetracker
Built a full-stack price monitoring tool that tracks 500+ products across UK e-commerce sites. Implemented a background task scheduler using Celery and Redis. Deployed on a VPS with Docker Compose; currently serves 200 monthly active users.
Section 4: Education
Keep this concise:
- Degree, University, Graduation Year, Grade (if 2:1 or above)
- Relevant modules (only if genuinely relevant - e.g., "Algorithms and Data Structures, Machine Learning, Database Systems")
- Dissertation if it's technically impressive
If your grade is below a 2:1, omit it. Employers will ask if they need to know.
Formatting Rules
- Length: One page, maximum two pages if you have a year's placement experience
- Font: Calibri, Arial, or Helvetica at 10–11pt
- Format: Single column PDF (not Word) - ATS handles single columns best
- No photo, no date of birth, no "References available on request"
- UK English throughout - "optimised" not "optimized", "colour" not "color"
Tailoring Your CV for Each Application
The single biggest impact move: tailor your personal statement and skills section for each role. Copy the exact language from the job description. If they want "a Python developer with experience in data pipelines," your CV should use those exact phrases.
GradSignal's job listings include full job descriptions - use them as your keyword checklist when tailoring your CV for each application.