Android Engineer

An Android Engineer builds and maintains the apps that run on Android phones and tablets - things like banking apps, retail apps, streaming services, internal tools for staff, or the software inside connected devices. You write the code that handles what the user sees and taps, connect it to servers and databases over the internet, and keep the app working across a huge range of devices, screen sizes and Android versions. You usually work in a small team alongside designers, product managers, backend engineers and testers, and increasingly alongside an iOS counterpart building the same product for Apple devices.

Approximate graduate salary

Roughly in the region of £28,000-£40,000 to start, but this varies very widely - London and large tech employers sit at or above the top of that range, while smaller agencies and employers outside the major cities often start lower. Mobile specialists tend to see pay rise quickly with a couple of years of commercial experience.

What you'd actually do

Writing and reviewing Kotlin code (the main language for Android development now, though older codebases are often still Java) to add features or fix defects in an existing app.
Wiring the app up to backend services - calling APIs (the interfaces that let an app request data from a server), handling the responses, and dealing gracefully with slow connections, failures and offline use.
Turning designs handed over by a product designer into working screens, then going back and forth over spacing, animation and behaviour that looks fine in a static mockup but awkward on a real device.
Testing: writing automated unit tests, running the app on emulators and physical test devices, and chasing bugs that only appear on one manufacturer's phone or one older Android version.
Reading and commenting on teammates' pull requests (proposed code changes) and responding to comments on your own - a large share of the week is spent reading other people's code, not writing your own.
Attending stand-ups, sprint planning and refinement sessions where upcoming work is sized and discussed, plus occasional release work: preparing a build, checking crash-reporting dashboards after a release goes live, and responding if something breaks in production.
Investigating production issues from analytics and crash logs - working out why a small group of users are seeing a blank screen or a crash you cannot reproduce.

How graduates get in

Graduate software engineering schemes at larger employers - banks, retailers, telecoms, media companies, consultancies and big tech. Note that most of these hire generalist 'software engineer' graduates and then place you on a team; you may be able to express a preference for mobile but it is not always guaranteed. Dedicated 'graduate Android engineer' adverts exist but are less common.
Direct application to a junior Android developer role at a product company, startup or digital agency. This is a very common route and usually depends on you having demonstrable Android work - a published app, a substantial personal project, or a placement - rather than a specific degree.
A placement year or summer internship in a mobile team, converting into a graduate offer. Internships are probably the single strongest route in because they give you commercial Android experience before you graduate.
Degree apprenticeships in software engineering, which some graduates will not be eligible for but which are a genuine alternative to the traditional degree route for school leavers.
Moving sideways after starting as a general software engineer or QA/test engineer - plenty of Android engineers did not start on mobile and picked it up on the job.
Bootcamps and self-taught routes. These do work, particularly for smaller employers and agencies, but you are competing on portfolio alone, so you need apps that are actually finished and ideally published to the Google Play Store.

What employers ask for

A degree in computer science, software engineering or a closely related subject is the most common background, and some graduate schemes filter on it. But a lot of employers genuinely do not mind the subject if you can code - physics, maths, engineering and conversion-course graduates are well represented.
Grade requirements vary a lot. Structured graduate schemes at large employers often ask for a 2:1 and sometimes UCAS points or A-level grades; smaller companies and agencies frequently ask for nothing beyond a portfolio and a technical interview.
Demonstrable Android work matters more than almost anything else on paper. A GitHub repository with a working app, or something published on the Play Store, carries real weight - more than a module grade.
Kotlin is the expected language; Java is useful because many commercial codebases still contain it. Familiarity with Android Studio (the development environment) and Git (version control, the system teams use to manage code changes) is assumed.
Knowledge of modern Android UI approaches - Jetpack Compose is now the standard way to build interfaces, with older XML layouts still widespread in existing apps. Employers do not expect graduates to know everything, but knowing which of these you have used is a standard interview question.
There is no professional qualification or licence for this role. Chartered status through BCS is available to software professionals later in a career but is rarely asked for by mobile employers.

Skills that matter

Kotlin and the Android SDK

This is the day job - writing Kotlin against Android's own libraries for screens, navigation, storage and background work.

Debugging on real devices

Android runs on thousands of phone models with different manufacturer tweaks, so a lot of your time goes on bugs that only reproduce on one device, one OS version or one screen size.

Understanding app architecture and state

Mobile apps get killed, rotated, backgrounded and resumed constantly, so you need to think about where data lives and what happens when the system reclaims memory mid-task - this is what separates junior from mid-level work.

Working with APIs and asynchronous code

Almost every screen depends on data fetched over an unreliable mobile network, so handling loading states, retries and errors without freezing the interface is core to the job.

Reading other people's code

You will join an existing codebase, often large and partly legacy, and your first months are mostly about understanding decisions someone else made years ago.

Design sensibility and attention to detail

Users judge mobile apps on small things - a janky animation, a keyboard covering a text field, a button too close to the screen edge - and engineers catch most of these, not designers.

Where it leads

Graduate or junior Android engineer: typically a year or two working on well-defined tickets with close code review, learning the codebase and the team's release process.
Mid-level Android engineer: you own features end to end, make architectural choices within a feature, review others' code and take part in on-call or release duties. Most people reach this within a few years, though it depends entirely on the employer's levelling system.
Senior Android engineer: responsible for technical direction across the app, mentoring, and decisions with long consequences - migrating to a new UI framework, restructuring modules, setting testing standards.
From senior, the path usually forks. One branch is technical - staff or principal engineer, or mobile architect, staying hands-on and influencing across teams. The other is management - engineering manager or team lead, where you stop writing much code and focus on people and delivery.
Sideways moves are common and easy: into cross-platform mobile work (Kotlin Multiplatform, Flutter, React Native), into backend or full-stack engineering, into developer tooling and platform work, into contracting, or into founding/joining a small product company. Timelines vary enormously - a fast-growing startup may promote in half the time a large regulated employer does.

What people get wrong

“It's mainly about making screens look nice - the easy, visual end of software engineering.”

Most of the difficulty is invisible: managing state across an app the operating system can suspend or kill at any moment, handling offline behaviour, memory and battery use, background processing rules that get stricter with each Android version, and keeping a single codebase working across a wildly fragmented device landscape.

“You need a computer science degree.”

Large graduate schemes often ask for one, but a great many working Android engineers came from other degrees, conversion courses or self-teaching. Outside the big structured schemes, a finished app you can demonstrate usually beats a degree subject.

“Cross-platform frameworks have made native Android specialists obsolete.”

Plenty of companies do use cross-platform tools, but native Android skills remain in demand - and cross-platform teams still need people who understand the underlying Android platform to handle permissions, notifications, performance and the bits the framework does not cover.

“You ship whenever you want, like a website.”

App releases go through the Google Play Store and users do not all update at once, so you may be supporting old versions of your app in the wild for a long time. That makes planning, backwards compatibility and feature flags a much bigger part of the job than in web development.

Where this varies

The role differs a lot by employer type. At a product company or scale-up you may be one of only a handful of Android engineers, owning large parts of a single app and talking directly to product and design. At a bank, insurer or other regulated employer there is far more process - security review, accessibility and compliance requirements, longer release cycles, and a larger team where you own a narrow slice. At a digital agency or consultancy you may build several different clients' apps a year, which gives breadth quickly but less depth in any one product. Some roles are 'Android engineer' strictly; others are really 'mobile engineer' and expect you to pick up iOS or a cross-platform framework too. Geographically, the largest concentration of jobs is London, with substantial mobile teams also in Manchester, Edinburgh, Glasgow, Bristol, Leeds, Cambridge and Newcastle; remote and hybrid working is relatively common in this field compared with many graduate roles, though less so than during the peak of fully remote hiring.

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.