- Reading time: 2 minutes
- Price: Free download
- Published: 17th September 2026
- Word count: 568 words
- File format: Text
Personal statement example
My final-year undergraduate project was a modest one: measuring how well a copper-water heat pipe moved heat from a resistive element to a finned block, and comparing the results with a lumped model I had written badly in MATLAB. The model and the rig disagreed, mostly because I had ignored the contact resistance at the evaporator clamp. Fixing that taught me more about thermal engineering than the marks suggested, and it is the reason I have spent the last seven years in cooling and the reason I now want to work on spacecraft, where radiation is the only way out and the margins are set long before anything is built.
Since graduating I have worked as a commissioning and maintenance engineer for a firm that installs industrial refrigeration systems, mainly for food storage and a few data centres. The work is practical rather than glamorous: pressure testing, fault-finding on control loops, replacing compressors in cold rooms at unhelpful hours. What it has given me is a feel for how systems fail. Failures are almost never the exotic thing in the specification; they are a sensor mounted where nobody thought about airflow, or two contractors each assuming the other had allowed for expansion. I have written handover documents, argued for design changes with installers who had already ordered the pipework, and learned to record what I actually measured rather than what I expected. I understand why space projects put so much weight on interface definition and verification, because I have seen small versions of the same problem in plant rooms.
I have also been deliberate about rebuilding the academic side. Over the past year I have worked through an orbital mechanics textbook in the evenings, deriving the two-body results properly and coding simple propagators in Python; comparing my numbers with published TLE-based positions for the ISS was a useful check on my own errors. I have refreshed linear algebra and differential equations, and taught myself enough NumPy and matplotlib to be useful rather than fluent. Reading Fortescue and Stark's Spacecraft Systems Engineering alongside this has helped me see how thermal, power and structural budgets are traded against each other rather than solved separately, which is the part of the discipline I find most interesting. A lecture I attended at a local university on CubeSat thermal design made the point that a small satellite's thermal problem is largely one of surface finish and orbit geometry, which reframed a lot of what I had assumed from terrestrial work.
Alongside this I help run observing evenings for a community astronomy group, setting up telescopes, explaining what people are looking at and maintaining our ageing equatorial mount. Explaining orbits to a field of cold, sceptical teenagers is good practice for technical communication, and repairing the mount's slipping drive was an enjoyable reminder that backlash is universal.
I want a taught postgraduate course because I need the structured grounding I cannot get from evening reading: attitude dynamics, launch and space environments, and the systems engineering process applied to a real design exercise. In the longer term I would like to work in spacecraft thermal or mechanical design, ideally on small satellite platforms, where the whole vehicle is small enough to understand. I am returning to study later than most, but with a clearer sense of why the engineering discipline matters and a habit of checking my assumptions against measurements.
Why this example works — strengths and ways to improve
This is a strong, coherent conversion-style statement for a taught master's. You link a modest undergraduate thermal project, seven years of refrigeration work and structured self-study into a credible path towards spacecraft thermal design. The voice is honest and specific. The main gaps are limited detail on your degree background and slightly thin reflection on the astronomy paragraph's relevance.
Subject motivation
where radiation is the only way out and the margins are set long before anything is built
Your motivation grows naturally from thermal work rather than generic fascination with space. Naming radiation-only heat rejection and early-fixed margins shows you understand what makes spacecraft thermal design distinct, which makes the move from terrestrial cooling feel reasoned rather than romantic.
Academic preparation
deriving the two-body results properly and coding simple propagators in Python
The self-study is concrete and checked against real data, which is convincing. However, you never name your degree subject or level directly; readers infer engineering from the heat pipe project. Briefly stating your first degree would anchor eligibility and show which foundations you already hold.
Evidence and reflection
I had ignored the contact resistance at the evaporator clamp
Admitting a specific modelling error and what fixing it taught you is genuine reflection, not a skill claim. The TLE comparison repeats this habit of testing assumptions. You could add one sentence on what the corrected model showed, to demonstrate quantitative judgement, not just honesty.
Relevant experience
a sensor mounted where nobody thought about airflow
Ordinary commissioning work becomes excellent evidence because you extract a systems lesson about interfaces and verification, then connect it explicitly to space projects. Handover documents and arguing for design changes show transferable professional maturity suited to a systems engineering course.
Credibility and voice
taught myself enough NumPy and matplotlib to be useful rather than fluent
Calibrated self-assessment like this makes your claims believable, and the dry humour (unhelpful hours, backlash is universal) gives a distinct personal voice without overstatement. Nothing reads as exaggerated authority for someone seven years into industry.
Structure and format
I want a taught postgraduate course because I need the structured grounding
The progression from project to work to study to aims is logical, and the closing explains why taught study rather than research. The astronomy paragraph is pleasant but slightly detached; tying the mount repair or outreach more tightly to your aims would tighten flow.
What you’ve done well
- You use a small, imperfect undergraduate project as a genuine origin story with a specific technical lesson.
- Your industrial failures are translated precisely into the interface and verification concerns central to space systems engineering.
- Self-study is evidenced with named resources and an external check against ISS positions.
How this draft could improve
- State your first degree subject and any relevant modules so readers need not infer your academic baseline.
- Either sharpen the link between the astronomy group and your engineering aims or shorten that paragraph to free space.
- When tailoring to a real programme, connect your stated interests (attitude dynamics, design exercise) to what that course actually offers.