Computer engineering personal statement example

Personal statement example

When the power returns after an outage at my aunt's provisions shop, the chest freezer makes a sharp click before the compressor starts. For months I heard that click without thinking about it. Then the freezer failed, and the repairer said the likely cause was repeated restarts on low, unstable voltage. I wanted to know how low and how often, and that question became the most absorbing project I have attempted.

I had a clone microcontroller board that a cousin gave me, and I bought a small voltage sensor module and a cheap memory card adapter from a market stall. Measuring mains voltage directly was not something I was willing to improvise, so I used a sealed plug-in transformer and measured its reduced output, which rises and falls with the supply. I calibrated the readings against a borrowed multimeter at several times of day and wrote a short program that recorded a value every ten seconds, along with the time from a clock module. Over three weeks the logger showed that power was often restored at a noticeably reduced voltage and then dipped again within a minute or two. Those were exactly the conditions under which the freezer was clicking on.

The practical result was modest but real. My aunt now unplugs the freezer during outages and plugs it back in once the supply has been steady for a few minutes, a delay I chose by looking at how long the early fluctuations usually lasted in my data. A more interesting result for me was what the project exposed about my own knowledge. My first readings drifted, and I learnt that the board's reference voltage changed as its own supply varied. Fixing that sent me into reading about analogue-to-digital conversion, sampling and why a reference matters. I also discovered that my memory card corrupted files when power was cut mid-write, so I changed the program to close the file after each batch. These were small fixes, but they taught me that hardware and software problems are rarely separate.

At school, Physics has given me the circuit theory behind what I was doing, and Elective Mathematics has become more meaningful since I started plotting my own data rather than textbook values. I enjoyed working out a moving average by hand before coding it, because I could see why it smoothed the noise and also why it delayed the response. Logic gates in our syllabus felt abstract until I realised the microcontroller was built from enormous numbers of them, and I now want to understand properly how a processor turns instructions into switching.

Outside the project, I spend most Saturdays serving at the shop, which means handling the cash book and stock lists. Neighbours also bring me phone chargers and torches that have stopped working. Often the fault is a broken cable or a dry solder joint, and I have become careful about testing before replacing anything. I play draughts with older men near our junction most evenings; it is a game where planning several moves ahead matters, and losing regularly to people better than me has made me patient.

I want to study computer engineering because I am drawn to the point where physical signals become data and data becomes decisions. I would like to learn digital design, embedded systems and programming rigorously, not through trial and error alone. In the longer term, I am interested in reliable, low-cost monitoring for small businesses that live with unstable power, a problem I have now measured for myself. I bring persistence, honest record-keeping and a habit of checking my assumptions, and I am ready for the mathematics and discipline the course will demand.