What this subject family covers
Electrical, electronic and computer engineering courses share a core of circuit theory, mathematics, signals and digital logic, but they lean in different directions. Your statement is stronger if it shows you know which direction interests you, even if you are applying to a broad course.
- Electrical and power engineering: generation, transmission and conversion of energy, such as grids, motors, power electronics, renewables integration and electrification of transport.
- Electronic engineering and microelectronics: analogue and digital circuits, semiconductor devices, sensors and the design of chips and boards.
- Computer and embedded systems engineering: the boundary between hardware and software, including processor architecture, microcontrollers, firmware and real-time systems.
- Telecommunications, communication and information engineering: how signals carry information, including modulation, noise, coding, antennas and networks.
- Control, instrumentation and automation engineering: measuring physical quantities and using feedback to make systems behave predictably.
If you are applying to a combined course such as electrical and electronic engineering, you do not need to claim equal enthusiasm for every branch. One genuine interest, explained with some technical understanding, is more convincing than a list of every topic in the course title.
How this differs from neighbouring engineering subjects
Several neighbouring courses overlap, so make sure your evidence points at this one.
- Compared with computer science, computer engineering is concerned with the hardware your code runs on: timing, memory, power use, interfacing with physical devices. A statement that is only about writing apps reads as computer science.
- Compared with robotics and mechatronics, the emphasis here is on the electrical, electronic and signal side rather than mechanisms and whole-robot integration. A robot project is still good evidence if you write about the motor driver, sensor conditioning or control loop rather than the chassis.
- Compared with general engineering, you are expected to show why electrical and electronic problems in particular hold your attention.
- Compared with environmental engineering, an interest in renewable energy belongs here when it concerns conversion, storage, grid stability or power electronics, not mainly environmental impact.
Interests worth writing about
Strong interests are specific enough that you could explain the underlying idea to someone. Some examples of the kind of level that works:
- Why switched-mode power supplies are more efficient than linear regulators, and what that costs in electrical noise.
- How an inverter lets a solar panel or battery feed an AC grid, and why grid frequency has to be held stable.
- Why transistors have kept shrinking and what physical limits now make that harder.
- How a microcontroller reads a sensor through an analogue-to-digital converter, and what sampling rate and resolution mean for accuracy.
- Why Wi-Fi slows down through walls or in crowded areas, linked to frequency, attenuation and interference.
- How a feedback controller keeps a drone level or a thermostat from overshooting.
- How a processor pipeline works and why branch prediction matters.
Pick one or two and say what made them interesting, what you read or built to understand them, and what you still do not understand. Naming a topic without explaining anything about it adds little.
Connecting school subjects to this course
Mathematics and physics are the obvious foundations, but say how they connect rather than simply that you enjoy them.
- Mathematics: complex numbers describe AC circuits; differential equations describe charging capacitors and control systems; trigonometry and series underpin signal analysis. If a topic in your maths course suddenly made sense in a circuit context, that is worth a sentence.
- Physics: electricity, fields, waves and semiconductors map directly onto course content. A required practical on internal resistance or capacitor discharge can be reflected on: what caused your error, how you would measure more accurately.
- Computing: binary, logic gates and assembly-level ideas connect to digital electronics and computer architecture.
- Design and technology or electronics qualifications: a product with circuitry is evidence of building something, but focus on the electronic decisions, such as component choice and testing, not the casing.
- Extended projects: a research project on battery chemistry, smart grids or chip supply is useful if you show technical reasoning, not just a summary of articles.
Accessible preparation if you have no placement
None of these are requirements; they are ways to generate something real to reflect on.
- Small electronics builds: a breadboard circuit, a kit, or a microcontroller board such as an Arduino or Raspberry Pi Pico. The value lies in debugging: what did not work, how you used a multimeter or reasoning to find out why.
- Circuit simulation: free simulators let you test circuits without components. Comparing a simulated result with a hand calculation shows you understand both.
- Programming close to hardware: writing code that reads a sensor, controls an LED with PWM or communicates over I2C or serial is more relevant than general app development.
- Reading: textbooks aimed at hobbyists or first-year students, engineering magazines and manufacturer application notes. Write about an idea you took from them, not the title.
- Online courses and lectures: useful if you mention what you learnt and, ideally, applied.
- Competitions and clubs: robotics, electronics or engineering challenges. Describe your specific electrical or programming contribution.
Using everyday experience honestly
Ordinary experience can support your application if you make a precise connection and do not overstate it.
- Repairing devices: replacing a phone battery or fixing a games controller shows practical care and curiosity about how hardware is put together. It does not show circuit design ability, so pair it with what you understood about the fault.
- Building or upgrading a PC: connects to computer engineering through thinking about power supply ratings, thermal limits or memory bandwidth. Assembling parts alone is closer to consumer knowledge than engineering.
- Retail or warehouse work: seeing barcode scanners, automated tills or conveyor systems fail can prompt real questions about sensors and control. It does not mean you worked on those systems.
- Caring responsibilities: managing medical devices, mobility aids or alarm systems for a relative can raise genuine interest in reliability, battery life or safety in electronics. Keep the focus on the engineering question it raised.
- Gaming or music hobbies: audio equipment links to amplifiers, filtering and digital signal processing; latency in online games links to networks and telecommunications. Interest becomes evidence when you have tried to understand the mechanism.
- Volunteering: helping at a repair café or running school AV or lighting gives hands-on contact with electrical equipment, but safety procedures you followed are not professional qualifications.
- Household observations: smart meters, solar panels, an electric car charger or a heat pump can start a sound line of questioning about power and control if you follow it up.
What useful reflection looks like
Reflection in this subject usually means explaining technical reasoning and what changed in your understanding.
- State the problem in engineering terms: a voltage was lower than expected, a signal was noisy, a motor stalled under load.
- Explain how you investigated it: measurement, calculation, simulation, swapping components, reading a datasheet.
- Say what you found and why it happened, even approximately.
- Note a limitation: what you would test next, or what your current maths and physics cannot yet explain.
For example, writing that a sensor gave erratic readings until you added a capacitor, and that this led you to read about decoupling and noise, says far more than writing that a project taught you resilience.
Pitfalls specific to this subject
- Listing components and languages: a string of board names and programming languages without explaining what you did with them is unconvincing.
- Writing a computer science statement: for computer engineering, keep hardware, interfacing and physical constraints visible.
- Vague enthusiasm for technology: interest in smartphones, AI or electric cars needs to lead to a specific electrical or electronic idea.
- Overstating hobby work: a home project is not professional design, and a short work experience week is not engineering employment. Describe exactly what you did.
- Ignoring mathematics: the subject is heavily mathematical; showing you can see maths at work in circuits or signals is more persuasive than claiming to be practical rather than theoretical.
- Confusing the degree with a job: wanting to be an electrician, IT technician or chip designer is a career aim; the degree is about analysis and design across the field. Show interest in the underlying engineering.
- Unsafe or exaggerated claims: do not present working on mains electricity or high-voltage equipment as a hobby achievement; it may raise concerns about judgement rather than impress.
For postgraduate applicants
Postgraduate statements in areas such as power systems, electrification or advanced electronics need more specificity: name the modules, final-year project, lab techniques, software tools or industry problems that shaped your choice, and explain how the taught course extends that particular foundation. If you are moving between branches, for instance from electronics into power, explain which parts of your existing knowledge transfer and what gaps you expect to fill.
For general advice on planning, structure and editing, read our personal statement writing guide.
Electrical, electronic and computer engineering personal statement examples