What this programme is about
A Computer Engineering PhD lives close to the boundary between hardware and software, where small design choices can change speed, power use, reliability or security.
Research might involve computer architecture, embedded systems, chip design, IoT, accelerators, networks or hardware security.
Unlike a taught degree, the goal is not to master every subfield. You go deep enough into one problem to produce something the research community did not know before.
Prototypes, simulations and benchmark experiments are common ways to test new ideas.
Careful evaluation is crucial. A faster design is not automatically better if it consumes too much energy, breaks compatibility or weakens security.
Supervisor expertise and access to hardware platforms, fabrication resources or specialised computing tools can strongly shape the project.
Inside the curriculum
Skills you'll build
Where this can take you
What studying this programme is like
Architecture research may explore processors, memory systems, accelerators or parallel computing.
Embedded-systems projects can investigate real-time behaviour, resource constraints and interaction with physical devices.
Hardware-security research looks at vulnerabilities and protections that sit below application software.
Digital-design projects may use programmable logic, hardware description languages or specialised prototypes.
Experimental evaluation often requires reproducible benchmarks and careful comparison with existing systems.
Your dissertation must demonstrate an original technical contribution supported by convincing system evidence.
Is this likely to suit you?
Good fit if you...
- You enjoy hardware-software problems.
- You have strong computer-engineering foundations.
- You like building and evaluating systems.
- You are comfortable with low-level technical detail.
- You want advanced R&D or academic work.
Think twice if you...
- You want to focus only on high-level application development.
- You dislike hardware experimentation.
- You want a broad taught curriculum rather than narrow research.
- You are not prepared for repeated benchmarking and debugging.