Frontend Engineer

A frontend engineer builds the parts of a website or app that people actually see and click on - the pages, forms, dashboards, buttons and animations - usually working in a browser-based language called JavaScript (or its stricter cousin, TypeScript). They work inside a product or engineering team, turning designs and product requirements into working, tested code that connects to data from backend systems. The job exists almost everywhere: tech companies, banks, retailers, the public sector, agencies building sites for clients, and small startups.

Approximate graduate salary

Typically somewhere around GBP 26,000-40,000 to start, though this varies a great deal. London and well-funded tech companies sit at the higher end and sometimes above it; agencies, charities, public sector roles and jobs outside the big cities often sit at the lower end. Bootcamp and self-taught entrants frequently start lower than graduate-scheme hires and catch up within a few years.

What you'd actually do

Writing and editing code in a frontend framework - React is the most common in the UK market, with Angular and Vue also widely used - to build or change a page, component or feature.
Taking a design file (often from a tool like Figma) and turning it into working, responsive HTML and CSS that behaves correctly on phones, tablets and desktops.
Connecting the interface to data: calling APIs (the endpoints backend systems expose so the frontend can fetch or send data), handling loading states and showing sensible error messages when something fails.
Opening pull requests and reviewing other people's - a pull request is a proposed code change that a teammate reads, comments on and approves before it goes live. Expect to both give and receive a lot of feedback here.
Writing automated tests so a change doesn't silently break something else, and debugging in browser developer tools when a layout breaks or a page is slow.
Attending team ceremonies - a short daily stand-up, sprint planning, and refinement sessions where you estimate how much work a ticket is - plus conversations with designers and product managers about what a feature should actually do.
Fixing bugs reported by users or QA, and occasionally investigating why something is slow, inaccessible to screen-reader users, or rendering badly in one specific browser.

How graduates get in

Graduate software engineering schemes at large employers - banks, insurers, retailers, consultancies, media organisations, government departments. Most of these hire 'software engineers' generally and stream you towards frontend later, rather than advertising frontend-specific graduate roles.
Direct application to a junior or graduate frontend role at a smaller company, scale-up or digital agency. This is very common and often the faster route in, but it is less structured - you may be shipping real code in your first fortnight with no formal training programme.
A placement year or summer internship during a computing degree, converted into a graduate offer. Where an employer runs both, the internship is often the main feeder for graduate places.
A coding bootcamp after a non-computing degree. This is a genuinely well-trodden route into frontend specifically, more so than into most other engineering specialisms, but outcomes vary enormously by bootcamp and by how much you build independently afterwards.
Self-taught entry with a portfolio of real projects - a deployed site, open-source contributions, freelance client work. Possible, and more plausible in frontend than in many areas, but you are competing without the filter of a recognised credential, so the portfolio has to do heavy lifting.
A degree apprenticeship in software engineering is an alternative to the graduate route rather than a route after a degree, but it is worth knowing it exists if you are still choosing.

What employers ask for

A degree is usual but the subject matters less than you might expect. Computer science, software engineering and related subjects are the most common; maths, physics and engineering graduates are routinely hired; and plenty of frontend engineers come from arts, humanities or design backgrounds via bootcamps or self-teaching.
Many large graduate schemes ask for a 2:1, some accept a 2:2, and a lot of smaller employers and agencies do not filter on classification at all - they look at your code. Some still apply UCAS points or A-level filters; this varies a great deal.
Demonstrable code you have written. A GitHub profile, a deployed personal project, a university group project you can talk about in detail. For non-CS graduates this is effectively mandatory rather than a nice-to-have.
Working knowledge of HTML, CSS and JavaScript, plus at least passing familiarity with one framework (most often React) and with Git, the version-control system essentially every team uses.
No licence, chartered status or professional exam is required to practise. Some employers value a Chartered IT Professional (CITP) designation via BCS later in a career, but it is not a gateway and many engineers never pursue it.
Expect a technical assessment somewhere in the process - commonly an online coding test, a take-home task building a small interface, or a live pair-programming exercise. Whiteboard-style algorithm interviews are more typical of large tech firms than of agencies or in-house teams.

Skills that matter

JavaScript and TypeScript fundamentals

Frameworks change every few years; understanding how the language itself handles asynchronous code, state and types is what lets you pick up the next one quickly.

CSS and responsive layout

A surprising share of real bugs are layout problems, and being the person who can genuinely fix a stubborn alignment or mobile-breakpoint issue makes you immediately useful to a team.

Debugging in browser developer tools

Most of your time on hard problems is spent working out why something behaves differently from what you expected, not typing new code.

Accessibility awareness

UK public sector work has legal accessibility obligations and many private employers audit against WCAG standards, so knowing about semantic HTML, keyboard navigation and screen readers is practical, not theoretical.

Reading and interpreting designs, and pushing back on them

Designers often hand over a layout that hasn't accounted for long text, empty states or error conditions, and it falls to the frontend engineer to spot that and raise it before the build.

Writing clearly in text

Pull request descriptions, code review comments and Slack threads are how most decisions actually get made, especially on remote or hybrid teams.

Where it leads

Graduate or junior frontend engineer: you work on well-defined tickets with close review, and someone more senior checks your work before it ships. On structured graduate schemes this stage is often formally one to two years; elsewhere there is no fixed clock.
Mid-level engineer: you own features end to end, break larger pieces of work into tasks yourself and review juniors' code. Moving here typically takes a couple of years but depends heavily on how much responsibility the team hands out.
Senior engineer: you make design and architecture decisions for a product area, mentor others, and get pulled into conversations about what to build rather than just how. Timelines vary widely - fast-growing companies promote quicker than large, layered organisations.
From senior the path usually forks. The technical branch leads to staff or principal engineer, or to a specialism such as design systems, web performance, or accessibility engineering. The management branch leads to engineering manager and then head of engineering.
Common sideways moves include full-stack engineering (adding backend work), product management, developer relations, contracting on day rates, or founding something. Frontend skills also transfer reasonably well into mobile app development.

What people get wrong

“Frontend is the easier, less technical half of software engineering - the 'making it look nice' bit.”

Modern frontend involves state management, caching, performance budgets, testing strategy and build tooling. Making a complex interface fast and correct across every browser and screen size is a genuinely hard engineering problem, and senior frontend engineers are paid comparably to their backend peers.

“You need to be fluent in React before anyone will interview you.”

Employers hiring graduates usually care more that you understand JavaScript, HTML and CSS properly, because they expect to retrain you on whatever framework they use. Someone who knows only React patterns but can't explain what's happening underneath tends to struggle at interview.

“It's a solitary job where you put headphones on and write code all day.”

You spend a lot of time in conversation with designers, product managers, backend engineers and QA. A good deal of the job is clarifying what a vague requirement actually means before any code gets written.

“AI coding assistants have removed the need for junior frontend engineers.”

Tools that generate code are now part of normal practice, but someone still has to decide what to build, judge whether the generated code is correct and maintainable, and fix it when it isn't. The skill emphasis has shifted towards reviewing and reasoning about code rather than typing it.

Where this varies

The experience differs sharply by employer type. At a digital agency you may work on several client projects a year, with tight deadlines and a lot of variety but less depth. At a product company or scale-up you work on one codebase for a long time and go deep. In a bank, insurer or large retailer there is usually more process, more legacy code, stricter security and change controls, and slower release cycles - but often better structured training. Public sector and government digital work places unusual weight on accessibility and on open, user-centred design standards. Geographically, London has the most roles, but Manchester, Bristol, Edinburgh, Leeds, Cambridge and Belfast all have real tech clusters, and remote or hybrid frontend roles are relatively common compared with many graduate careers. Job titles also blur: 'frontend engineer', 'web developer', 'UI engineer' and 'full-stack engineer' are often used for overlapping work, so read the actual advert rather than the title.

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.