PERSONAL STATEMENT
EXAMPLES
My statements
Home » Subject areas » Civil, electrical and systems engineering » Systems engineering, robotics and mechatronics » Mechatronics personal statement example

Mechatronics personal statement example

PSE example
  • Reading time: 4 minutes
  • Price: Free download
  • Published: 17th September 2026
  • Word count: 917 words
  • File format: Text

Why do you want to study this course or subject?

The machine that made me want to study mechatronics was a broken automatic cat feeder someone left outside our flats. Taking it apart, I found a small motor, a plastic gear train, a microcontroller board and a cheap timer, and none of it was as clever as the box had suggested. Getting it running again meant understanding all of those parts together, not just one: the gears slipped because the motor had no feedback, so it could not tell whether the hopper had actually turned. That idea, that a mechanism is only as good as the information it receives about itself, is what draws me to this subject rather than to mechanical or electronic engineering alone. I like problems that sit in the gaps between disciplines. In Physics I enjoy the sections on circuits and motion most, but what I find genuinely satisfying is when a control idea explains something physical, such as why a system that corrects itself too aggressively ends up oscillating. Reading around the subject, I have been working through introductory material on feedback and sensors, and I was struck by how much engineering effort goes into measurement rather than actuation: a robot arm is easy to move and difficult to move accurately. I want a degree that treats mechanical design, electronics, sensing and programming as one problem, because the interesting failures usually happen where those parts meet. Longer term I would like to work on production or handling machinery, where reliability matters more than novelty, and I am aware that means learning to design for maintenance, tolerance and cost as much as for performance.

How have your qualifications and studies helped you to prepare?

My A levels in Maths, Physics and Design Technology have given me a useful spread of skills for this course. Maths is where I have worked hardest; mechanics and differentiation initially felt separate from each other until I started using rates of change to describe motion in my own projects, and I now find I understand new topics faster when I can picture something moving. I chose Further Maths modules where my timetable allowed, and I have taught myself the basics of matrix operations because they appear constantly in robotics material. In Physics, practical work has been the most valuable part: calibrating a light-dependent resistor for one experiment taught me that sensors rarely behave linearly and that a characteristic curve is something you measure rather than assume. Design Technology has been the closest thing to mechatronics in my timetable. For my coursework I designed a height-adjustable reading stand for someone with limited grip strength, and after interviewing my intended user I replaced my original ratchet mechanism with a geared handle because the forces involved were too high. I made technical drawings, iterated three cardboard and MDF prototypes, and learned to document decisions honestly, including the ones that did not work. Alongside lessons I completed an online introduction to programming in Python and use it for small scripts that log sensor readings from a microcontroller. I have also become more organised as a student, keeping a project notebook after losing an afternoon repeating measurements I had failed to write down.

What else have you done to prepare outside of education, and why are these experiences useful?

Through my college's careers coordinator I spent three supervised days shadowing the maintenance team at a packaging machinery company nearby. I was there as an observer, wearing borrowed safety boots and staying behind the marked lines, but I was allowed to help with simple tasks such as fetching parts, holding a torch and recording readings while a technician diagnosed a labelling head that was misplacing labels at high speed. The cause turned out to be a worn sensor bracket rather than the control software everyone had suspected, which taught me more about fault-finding than any diagram has. I also watched an engineer step through a PLC program on a laptop and saw how much of industrial control is careful sequencing and interlocks so that a machine cannot injure anyone or damage itself. At college I am one of four members of the robotics club, where we built a line-following buggy for a regional competition. My job was the sensor array: I soldered the reflectance sensors, mounted them on an adjustable bracket so we could change the ride height, and wrote the code that averaged their readings. Our first version steered erratically over shiny tape joins, so we added a simple threshold check and slowed the buggy on tight corners. We finished mid-table, and the write-up I produced afterwards is the piece of work I am proudest of. Outside college I work Saturdays and Sundays at a garden centre, mostly on tills and restocking, which has made me quicker at dealing with people who are frustrated and better at judging how long a job will really take. I am also the person friends and neighbours bring broken things to, so I have replaced laptop fans, resoldered headphone jacks and rebuilt a cordless drill battery pack, learning along the way to check datasheets before assuming two components are interchangeable. I read engineering teardowns and watch machine-shop videos for enjoyment, and I am looking forward to having proper workshop and laboratory access rather than a toolbox on the kitchen table.

This example has 5,201 characters across the three answers. Use it for ideas and structure. Your own UCAS answers must fit within 4,000 characters in total, including spaces.

Why this example works — strengths and ways to improve

This is a specific, technically literate statement with genuine reflection, especially on feedback, sensing and fault-finding. Each answer meets the minimum, but the combined 5,201 characters exceed the 4,000 limit by about 1,200, so substantial cutting is essential. Prioritise the cat feeder, LDR calibration, reading stand, shadowing and sensor array; trim generic skills, hobbies and repeated sensor themes.

Subject motivation

a mechanism is only as good as the information it receives about itself

You turn a cheap, ordinary object into a real insight about feedback, then use it to explain why you want mechatronics rather than mechanical or electronic engineering alone. This is convincing motivation. The career sentence on maintenance, tolerance and cost is thoughtful but could be shortened.

Academic preparation

a characteristic curve is something you measure rather than assume

Your LDR calibration shows a real lesson from practical Physics, and the reading-stand coursework shows design iteration driven by user forces. The opening line about a useful spread of skills is generic, and the Further Maths phrasing is vague. Name what you actually studied or cut it.

Evidence and reflection

a worn sensor bracket rather than the control software everyone had suspected

This is strong because you report what happened and what it taught you about diagnosis. Similar reflection appears in the buggy's threshold fix. The garden centre and project notebook points, however, rely more on generic skill claims than subject insight, so they are the weakest candidates to keep.

Relevant experience

My job was the sensor array: I soldered the reflectance sensors

You define your own role precisely within a team, which is more credible than claiming you led the team. Shadowing, the robotics club and the repairs all fit the subject well. Sensors recur across all three answers, so check that each example adds something new rather than repeating the same lesson.

Credibility and voice

I was there as an observer, wearing borrowed safety boots

You present your role in industry modestly and plausibly. Fetching parts and recording readings suits your stage, and that honesty strengthens your voice. Results such as finishing mid-table are stated plainly. The tone throughout is personal and unforced. Keep this restraint as you edit.

Structure and format

Longer term I would like to work on production or handling machinery

Each answer stays on its own question and clears 350 characters. The total, though, is roughly 1,200 over the 4,000 limit. Answer three is the longest, so the casual reading, garden centre and repair lists are the clearest cuts. Trimming should also keep you comfortably above the library's 3,500 minimum.

What you’ve done well

  • The cat feeder opening leads to a genuine conceptual point about feedback rather than a generic passion claim.
  • Your Design Technology coursework shows iteration driven by user needs and measured forces.
  • Your claims about industry and teamwork are modest and fit your stage.

How this draft could improve

  • Cut about 1,200 characters, starting with the garden centre, the repair list, the casual reading sentence and the project notebook anecdote.
  • Replace generic openers such as 'a useful spread of skills' with your concrete examples, or delete them.
  • Reduce repeated sensor and feedback lessons so that each answer contributes distinct evidence.