Graduate Software Developer CV: How to Tailor It to Any Job Description (UK)
The graduate software developer job market in the UK is competitive but accessible. Employers hiring junior developers know they are investing in potential — your CV needs to show technical foundations, evidence of real projects, and the growth mindset that will make you worth developing.
What employers look for in a graduate developer CV
Technical foundations:
Core languages, frameworks, and tools that match the stack in the job description. You do not need to know everything — you need the right things for this role.
Evidence of building things:
Projects — university coursework, personal projects, hackathons, open source contributions, GitHub repositories — are the primary differentiator for graduate developers. A candidate with three completed projects on GitHub is more compelling than one with identical grades and no public work.
Problem-solving approach:
The ability to break down a problem, research solutions, and implement cleanly. Evidenced through project complexity and the technical choices you describe.
Collaboration and process awareness:
Git workflow, code review, agile sprints, documentation — all signal readiness for a professional development environment.
Structure for a graduate software developer CV
1. Personal statement
Lead with your stack and your most relevant project or experience:
"Computer Science graduate (University of Manchester, 2:1, 2024) specialising in full-stack web development with a focus on React and Node.js. Built and deployed a full-stack e-commerce platform as my final-year project, including payment integration, user authentication, and a RESTful API. Proficient in Python, JavaScript, SQL, and Git. Seeking a junior developer role where I can contribute to production code from day one while continuing to develop within an engineering team."
2. Technical skills
List by category. Match the job description exactly:
- Languages: Python, JavaScript, TypeScript, Java, C#
- Frameworks: React, Node.js, Express, Django, Spring Boot, .NET
- Databases: PostgreSQL, MySQL, MongoDB, Redis
- Tools: Git, GitHub, Docker, Linux, VS Code, Postman
- Cloud/DevOps: AWS (S3, Lambda, EC2), Azure, CI/CD basics, GitHub Actions
- Testing: Jest, Pytest, JUnit, Cypress
Only list what you can discuss confidently in an interview.
3. Projects
This section is often the most important for a graduate developer. For each project include:
- Name and one-sentence description
- Technologies used
- Your specific contribution (if a group project)
- A quantifiable outcome or interesting technical challenge
E-Commerce Platform | React, Node.js, PostgreSQL, Stripe API
Full-stack web application with product catalogue, user authentication (JWT), basket management, and Stripe payment integration. Deployed on AWS EC2 with a CI/CD pipeline via GitHub Actions. Handles 500 monthly test transactions in demo mode.
[GitHub link]
Real-Time Chat Application | Socket.io, Express, MongoDB
WebSocket-based chat application supporting multiple rooms and persistent message history. Built to explore real-time communication patterns and NoSQL document modelling.
[GitHub link]
4. Education
Degree first, then A-levels. Include:
- Classification (or predicted)
- Relevant modules: Algorithms and Data Structures, Software Engineering, Database Systems, Computer Networks, Machine Learning (if applicable)
- Dissertation title and brief description if technically strong
5. Experience
Include any technical internships, placements, or part-time technical work first. Then non-technical work — evidenced through transferable skills (problem-solving, teamwork, delivery under pressure).
How to tailor to a specific job description
Step 1: Extract every technology named in the JD. Check which ones are in your skills section and project descriptions. Add any you genuinely have but forgot to list.
Step 2: Mirror the JD's language. If they say "RESTful APIs," use that exact phrase. If they say "microservices architecture," reference any exposure you have, even if academic.
Step 3: Reorder your skills section so the technologies most relevant to this role appear first.
Step 4: Select the project to lead with based on which is most technically aligned with the role.
Frequently asked questions
Should I include my GitHub link on my CV?
Yes — always. Ensure your public repositories are tidy: a clear README for each project, recent commit history, and no incomplete or broken codebases that you would not want a hiring manager to open.
What if my degree grade is below a 2:1?
Focus your applications on employers that do not have a firm grade requirement. Lead with your projects and skills rather than your classification. A strong project portfolio often outweighs a 2:2 for technical roles.
How do I compete with candidates who have internship experience?
With strong projects. A candidate with two well-built, deployed projects and an active GitHub profile is often preferred over a candidate with a summer internship and nothing else to show. Build things — publicly, iteratively, and with documentation.