Neuroelectronic Research Engineer

A neuroelectronic research engineer designs, builds and tests the electronics and software that record signals from the nervous system or stimulate it electrically — things like brain-computer interfaces, implanted electrode arrays, nerve stimulators and the amplifiers and recording rigs used in neuroscience labs. The work sits between electronic engineering and biology: you're making hardware that has to pick up very small, very noisy electrical signals from living tissue and do something useful with them. Most of these roles are in university research groups, medical device and neurotechnology companies, or research institutes, usually working alongside neuroscientists, clinicians and software engineers.

Starting salary
£28k–£38k
Live graduate jobs
Search all jobs
Main way in
Direct entry from an electronic engineering, biomedical…
They usually ask for
A numerate degree is effectively compulsory

Approximate graduate salary

Typically around £28,000–38,000 to start, though this varies widely. University research assistant and research engineer posts tend to sit at the lower end and follow published academic pay scales; industry R&D roles and PhD-qualified entrants usually start higher, and London or Cambridge-based medtech employers higher again.

What you'd actually do

  • Designing or modifying circuits — typically low-noise amplifiers, analogue front-ends, filtering and digitisation stages — in schematic capture and PCB layout software such as Altium or KiCad, then sending boards out for fabrication and assembling or reworking them yourself
  • Bench testing with an oscilloscope, signal generator and multimeter: injecting known test signals into a recording channel to check gain, noise floor and crosstalk before anything goes near tissue or a human subject
  • Writing firmware (usually C or C++ on a microcontroller, sometimes VHDL/Verilog on an FPGA) and host-side software in Python or MATLAB to stream, store and visualise many channels of neural data in real time
  • Running or supporting experiments — setting up a recording session with a neuroscientist or clinician, troubleshooting why a channel has gone dead or why mains hum is swamping the signal, and keeping careful records of what was changed between runs
Show 3 more
  • Processing the resulting data: spike sorting, filtering, spectral analysis, artefact rejection, and plotting results so the team can tell whether a hardware change actually improved anything
  • Reading papers and datasheets, and feeding what you find into design choices — electrode materials, encapsulation, stimulation waveform safety limits, wireless power or telemetry options
  • Writing up: internal design reports, test protocols, contributions to papers or grant reports, and — in a medical device company — design history records and risk documentation for regulatory purposes

How graduates get in

  • Direct entry from an electronic engineering, biomedical engineering or physics degree into a research assistant or junior R&D engineer post, often advertised by a university group on a fixed-term grant-funded contract. This is one of the commonest ways in, and these posts are frequently filled by people who did a relevant final-year or MSc project.
  • A funded PhD in neurotechnology, neural engineering, bioelectronics or implantable devices — often through a Centre for Doctoral Training. This is the most common route into roles that genuinely carry 'research' in the title, and many employers in this niche treat a PhD as the normal entry point rather than a bonus.
  • A specialist MSc (neural engineering, biomedical engineering, medical device design, bioelectronics) after a general engineering or physics degree — a standard conversion route for people who want the biology side without having studied it.
  • Graduate schemes at medical device, instrumentation or defence/aerospace companies with a neurotechnology or sensing line of work. These are relatively unusual — most neurotech employers in the UK are small and hire individually rather than running structured schemes.
Show 2 more
  • Internships, summer placements and industrial placement years in a neuroscience or medtech lab. Hands-on experience with electrophysiology rigs or electrode fabrication matters a great deal here and often decides who gets shortlisted.
  • Sideways moves from a related engineering job — hardware design, embedded systems, analogue electronics, signal processing — into a neurotech employer that is willing to teach the biology. More common than people expect, because low-noise analogue and embedded skills are the hard part to hire for.

What employers ask for

  • A numerate degree is effectively compulsory, but the exact subject is flexible: electronic/electrical engineering, biomedical or medical engineering, physics, mechatronics, computer engineering and sometimes neuroscience with a strong quantitative or computational component. Pure biology or psychology degrees rarely lead here without added engineering training.
  • A 2:1 or above is the usual expectation, and a first is common among applicants for PhD-track and research-institute posts. Some smaller companies care far more about what you have actually built than about classification.
  • A PhD or MSc is a genuine requirement for many posts titled 'research engineer' in this field, though not all — some roles are really applied development jobs where a strong bachelor's plus hands-on experience is enough. Read the advert carefully; this varies a lot.
  • Demonstrable hands-on evidence: a project portfolio, PCBs you designed, firmware you wrote, a GitHub repository, a final-year project involving biosignals (EEG, EMG, ECG). This weighs heavily because the field is small and employers want proof you can actually get hardware working.
Show 2 more
  • Programming in Python and/or MATLAB is near-universal; C or C++ for embedded work is often required. Familiarity with version control is assumed in most places.
  • For some roles, additional clearances or approvals — Home Office personal licence for work with animals, ethics training for human subject work, or occasionally security clearance in defence-adjacent labs. These are normally arranged once you're in post rather than required upfront.

Skills that matter

Low-noise analogue circuit design

Neural signals are measured in microvolts and sit beneath mains interference and movement artefact, so the quality of your front-end amplifier and grounding decides whether the whole system works at all.

Embedded programming and real-time systems

Recording and stimulation hardware runs on microcontrollers or FPGAs where timing precision and limited memory are hard constraints, and closed-loop systems have to respond within milliseconds.

Signal processing

Filtering, spectral analysis, artefact removal and spike detection are how raw voltage traces become something a neuroscientist or clinician can interpret.

Systematic debugging and experimental discipline

When a rig stops working you need to isolate whether the fault is the electrode, the cable, the amplifier, the software or the biology — guessing wastes weeks of scarce experiment time.

Enough biology to talk to neuroscientists

You need to understand electrode–tissue interfaces, charge injection limits and what your collaborators are actually trying to measure, or you will design something technically elegant and scientifically useless.

Clear technical writing and documentation

Designs get handed on between grant cycles, and in medical device work undocumented changes are a regulatory problem, not just an inconvenience.

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

  1. Start as a research assistant, junior R&D engineer or PhD student, working on one subsystem — an amplifier board, a data acquisition pipeline, a stimulator channel — under close supervision.

  2. Move to a full research engineer or senior engineer role owning a whole subsystem or product area, specifying requirements, choosing architectures and supervising students or junior staff. For PhD entrants this often follows a postdoc; for direct entrants it typically takes several years, but timelines vary widely because so much depends on grant funding and company size.

  3. From here the paths fork. In industry: principal engineer, hardware or systems lead, or head of R&D in a small neurotech firm. In academia: postdoc, fellowship, then lectureship — a competitive and uncertain route. In a core facility or institute: technical lead running shared electrophysiology infrastructure.

  4. Common sideways moves include regulatory affairs or quality for medical devices, clinical engineering in the NHS, product management at an instrumentation company, or into adjacent sensing fields such as wearables and biosensors, where the analogue and embedded skills transfer directly.

  5. Some people found or join early-stage neurotech spin-outs, often commercialising work from their own PhD. This is a real and reasonably common route in this field, though obviously higher risk.

What people get wrong

“It's mostly about brains and neuroscience, so you need a biology background.”

The bottleneck skill is almost always electronics and embedded software. Teams are far more likely to be short of someone who can design a clean analogue front-end than someone who understands cortical anatomy — the neuroscience can be picked up on the job, the circuit design largely cannot.

“You'll be working on mind-reading brain-computer interfaces of the kind that appear in the news.”

Much of the UK field is less glamorous and more incremental: nerve stimulators for bladder or pain conditions, EEG and EMG instrumentation, electrode arrays for animal research, and lab recording equipment. Human implant work is a small, heavily regulated slice of it.

“'Research engineer' means you spend your time thinking about ideas and publishing.”

A large share of the week is practical and unglamorous — soldering, debugging earth loops, chasing component lead times, rewriting acquisition software that crashed mid-experiment, and filling in test documentation. The thinking happens around the bench work, not instead of it.

“It's a secure, well-defined career path like accountancy or law.”

The UK neurotech sector is small and concentrated in a handful of university cities and start-ups, and many posts are fixed-term and grant-funded. People often move employer or city to progress, and the transferable escape routes into general electronics or medtech matter a lot.

Where this varies

The job varies enormously depending on where you do it. In a university group you are largely building one-off bespoke rigs for specific experiments, working to grant deadlines on fixed-term contracts, with publication as an output. In a medical device company the same technical skills are wrapped in design controls, risk management and regulatory standards, with far more documentation, slower iteration and a much heavier emphasis on safety and traceability. In a start-up you may do everything from circuit design to firmware to cable-making. Geographically, the work clusters around a small number of research-heavy cities and university spin-out clusters, so relocating is often part of progressing. The title itself is used loosely too — some adverts describe a PhD-level research post, others an applied hardware development job with 'research' in the name.

Search Neuroelectronic Research Engineer jobsFrom employers' own careers sites, updated dailyTailor 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.

See all 13,303 graduate jobs

Neuroelectronic Research Engineer is one corner of the feed. See every live role, read straight from employers' own careers pages, with the ones that fit you ranked first.

See all 13,303