Summer Software Engineer

A summer software engineer is a student taking a paid internship in a software development team, usually for roughly 8 to 12 weeks over the summer vacation. You're given a real (if contained) piece of work - a feature, a tool, an improvement to an internal system - and you build it alongside the permanent engineers, using the same code, processes and reviews they do. The work is for the employer's engineering team rather than being a training exercise set aside from the business, and at many companies the internship doubles as an extended interview for a graduate job.

Starting salary: £25k–£45k
Live graduate jobs: 9 open now
Main way in: Formal summer internship schemes, applied for in the autumn or…
They usually ask for: Usually you need to be a current undergraduate or master's…

Approximate graduate salary

Summer software engineering internships in the UK are almost always paid. Pro-rata pay is often roughly equivalent to an annual salary in the region of £25,000–£45,000, so a 10-week placement might pay somewhere in the low-to-mid thousands overall - but this varies enormously. Investment banks, large US-headquartered tech firms and London-based roles sit at the top end and sometimes well above it; start-ups, smaller firms, the public sector and roles outside London sit considerably lower. Some employers add accommodation support or a relocation allowance. Treat all of this as a rough indication only and check each advert.

What you'd actually do

Writing code against a real codebase - usually a well-scoped project agreed in your first week, such as adding a feature, building an internal tool, or improving performance of something that already exists.
Putting your work up for code review (where other engineers read your changes and ask for alterations before they're merged), then responding to their comments - often several rounds for the same piece of work.
Attending the team's stand-up, a short daily meeting where everyone says what they're working on and what's blocking them, plus sprint planning or retrospectives if the team works in two-week cycles.
Spending a surprising amount of time reading existing code and documentation to work out how the system fits together, and asking your mentor or buddy questions when you get stuck.

Show 3 more

Writing automated tests for your code and getting it through the deployment pipeline, so that what you built actually runs somewhere rather than sitting on your laptop.
Doing a presentation or demo near the end - typically showing your project to the team, and sometimes to a wider audience of interns and managers.
Intern-specific extras at larger employers: tech talks, a social programme, a group hackathon or charity project, and a mid-point and end-point review with your manager.

How graduates get in

Formal summer internship schemes, applied for in the autumn or early winter of the academic year before - this is the most common route, and large tech firms, banks and consultancies often fill places on a rolling basis, so applying early genuinely matters.
Progression from a first-year 'insight' or 'spring week' programme, which are shorter introductory placements aimed at first-years; some employers fast-track participants into a summer offer. Common in finance and large tech, rarer elsewhere.
Direct applications to small and mid-sized companies and start-ups, which often don't run a formal scheme and advertise ad hoc on job boards, university careers services or LinkedIn. Deadlines are much later and the process is usually shorter.
University-brokered routes: careers service placement teams, department industrial-placement coordinators, and employer-sponsored projects run through the university. Useful if your course has a placement or year-in-industry structure.

Show 2 more

Hackathons, open-source contributions and university tech societies sometimes lead to informal offers, particularly at start-ups - real but less reliable than applying through the standard channels.
Converting a part-time or freelance development job during term time into summer full-time work with the same employer - unusual, but it happens.

What employers ask for

Usually you need to be a current undergraduate or master's student, typically in your penultimate year, because the point of the scheme for the employer is to make a graduate offer afterwards. Some employers accept first-years or finalists, but many explicitly don't - check each advert.
Computer science is the typical degree, but it's genuinely not required: maths, physics, engineering and other numerate subjects are widely accepted, and some employers take any discipline if you can demonstrate coding ability.
Grade requirements vary a lot. Some large employers still filter on a 2:1 predicted and specific A-level grades; many tech companies ignore grades entirely and assess purely on a coding test.
Practical coding ability in at least one language - commonly Python, Java, JavaScript/TypeScript, C++ or C#. Employers care more that you can write working code and reason about it than which language you learned it in.

Show 2 more

Evidence you've built something: university coursework is acceptable, but personal projects, a GitHub profile, hackathon entries or open-source contributions make a visible difference at the application stage.
Right to work in the UK for the duration - most summer schemes don't sponsor visas for a short placement, though international students already on a UK student visa can usually work full-time during vacation periods. Check your own visa conditions.

Skills that matter

Reading other people's code

You'll join a codebase far larger than anything you've written yourself, and most of your first fortnight is working out how it already behaves before you change anything.

Version control with Git

Branching, resolving merge conflicts and writing a clear pull request are daily mechanics on almost every engineering team, and arriving without them slows you down immediately.

Debugging methodically

Most of the difficulty in a real codebase is finding why something fails, not typing the fix, and employers watch how you narrow a problem down rather than whether you guess right first time.

Asking for help at the right moment

Interns who sit stuck for two days are judged worse than those who ask after an hour, and knowing what you've already tried before asking is the part that earns respect.

Explaining technical decisions in plain terms

You'll justify your approach in code review and present your project at the end, often to people who haven't seen the code.

Scoping and prioritising your own work

A summer project is short and you'll be given more ideas than you can finish, so deciding what to cut and shipping something working beats half-building everything.

Putting these on a CV? We counted which skills 12,914 live graduate adverts ask for, and what to do with the answer — part of our application advice.

Where it leads

Most commonly, a return offer for a graduate software engineer role, made during or shortly after the internship. Conversion rates vary hugely by employer and year - some schemes exist mainly to recruit, others make very few offers.
If you return, you'd start as a graduate or junior software engineer after finishing your degree, usually with a structured onboarding period and a mentor.
From junior, the usual path is to software engineer and then senior engineer. Timeframes vary widely - a few years each is typical but it depends entirely on the employer and your output, and there's no fixed clock.
After senior, paths typically fork: a technical track (staff/principal engineer, architect, specialism in areas like security, data, machine learning or infrastructure) or a management track (team lead, engineering manager).
An internship that doesn't convert is still useful leverage - commercial experience on your CV makes graduate applications elsewhere substantially easier, and plenty of people intern at one company and take a graduate job at another.

What people get wrong

“You'll be given busywork, dummy projects or coffee runs.”

At most employers the opposite problem applies - you're given genuine production work and the risk is being under-supported rather than under-used. Your code often ends up running in the live product.

“You need to be a brilliant programmer to be worth hiring.”

Interns are assessed heavily on how they handle not knowing things: whether they take code review feedback well, communicate blockers, and work with a team. A technically average intern who is easy to work with frequently converts over a technically stronger one who isn't.

“It's only for computer science students.”

Plenty of summer software engineers come from maths, physics, engineering and even non-numerate degrees, having taught themselves to code. What's being tested is demonstrable ability, which is why coding tests and project portfolios matter more than the subject on your transcript.

“Applications open in spring, close to the summer.”

For large employers, applications frequently open the previous autumn and places go as people apply, so by spring the competitive schemes may be full. Smaller companies do recruit later, but if you wait you're choosing from a narrower pool.

Where this varies

The experience differs enormously depending on where you go. Large tech companies and investment banks tend to run highly structured programmes: a dedicated intern cohort, formal mid- and end-point reviews, a mentor and a buddy, a defined project, an organised social programme and a clear conversion decision at the end. Start-ups and smaller firms usually have none of that - you may be the only intern, embedded directly in a small team, with much broader and less predictable work, and whether a job offer follows depends on whether they happen to have budget. Sector matters too: in finance you may spend the summer on internal trading or risk systems with strict controls and limited ability to see your code deployed quickly; in consultancies you might work on a client project or an internal tool; in gaming, scientific or embedded software the toolchain and languages can be quite specific. Geographically, London has by far the most formal schemes and the highest pay, but Manchester, Edinburgh, Bristol, Cambridge, Leeds and Belfast all have meaningful tech employers, and fully remote internships exist but are less common than during the pandemic years.

See all 9 live Summer Software Engineer jobsFrom employers' own careers sites, updated daily Tailor your CV for this roleFree with an account, 3 a month

General guidance about the role across the UK market, not about any specific employer. Entry routes and requirements vary — always check the individual job advert.