Microelectronics postgraduate personal statement example

Personal statement example

My interest in microelectronics grew out of a stubborn problem rather than a grand plan. In my third-year laboratory work I built a bridge amplifier for a strain gauge and could not explain why the output drifted over the first few minutes of each run. Tracing it back through offset voltage, thermal gradients across the board and the bias currents of the op-amp I had chosen taught me that the interesting engineering was happening inside a package I had been treating as a symbol. From that point I paid attention to device physics and circuit design as one subject rather than two, and I chose electives in semiconductor devices and digital design accordingly.

My final-year project was a low-power front-end for a piezoelectric vibration sensor, intended to log intermittent events without a mains supply. I designed a discrete charge amplifier with a high-value feedback resistor, characterised its noise and bandwidth on the bench, and used a small FPGA to threshold and timestamp events so the analogue section could stay in a quiescent state most of the time. The result was modest: the prototype ran for about eleven days on four AA cells and captured the test events reliably, though my noise floor was roughly twice what my calculations predicted and I never fully resolved whether the excess came from the resistor or from my grounding arrangement. Writing that honestly in my report was more useful to me than a tidier conclusion would have been, and it is a large part of why I want formal training in analogue integrated design, where those trade-offs are decided in layout and process rather than by which part I can buy.

Since graduating I have worked as a test technician at a company producing industrial control boards. I write and maintain test scripts in Python for our functional test fixtures, and I spend part of each week on returned units. The failure analysis has been an education in itself: latch-up on an input port after field wiring faults, a buck converter that only misbehaved above a certain ambient temperature, and a recurring open circuit that turned out to be a reflow profile issue rather than a design fault. Working with the design engineer on a revised input protection network was my first experience of arguing for a change with measurements rather than intuition, and of accepting that cost and footprint constrained what we could add. I have also learned to write clearly for people who will read my notes months later.

Outside work I repair and modify second-hand synthesisers, mostly analogue ones from the 1980s, and I help run a weekly repair session at a community workshop where people bring in lamps, radios and kettles. Both have made me patient with intermittent faults and comfortable explaining a diagnosis in plain language to someone who does not want a lecture on impedance.

A master's is the step I need because the topics I keep running into at the edge of my knowledge are all inside the chip: MOSFET operating regions and mismatch, noise in CMOS amplifiers, layout parasitics, and the tool flows used to simulate and verify a design before anything is fabricated. I would particularly like to develop the analogue and mixed-signal side, with enough digital and fabrication background to understand what a process can actually deliver. In the longer term I hope to work as an integrated circuit design engineer on sensor interfaces, and my test and repair experience should make me a careful rather than an optimistic designer.