PERSONAL STATEMENT
EXAMPLES
My statements
Home » Subject areas » Artificial intelligence, data and cybersecurity » Data science and computational analysis » Scientific computing personal statement example

Scientific computing personal statement example

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

Why do you want to study this course or subject?

For several years my job involved recording flow rates, turbidity and dosing levels at a water treatment works, then typing them into a spreadsheet. The spreadsheet could tell us what had happened, but it could not tell us what would happen if we changed a setting, and nobody on shift could answer that either. I started reading about how plant behaviour is modelled and found that the interesting part was not the chemistry I already half knew, but the mathematics of describing a changing system and then getting a computer to solve it approximately, because the exact answer is usually unavailable. That is the work I want to do. Since then I have taught myself enough Python to write a small simulation of a stirred tank with a step change in inlet concentration, solving the governing equation with Euler's method and then with a fourth-order Runge-Kutta routine, and comparing both against the analytical solution. Watching the error shrink as I reduced the step size, and then seeing the runtime grow, made the trade-offs concrete in a way that reading about them had not. I am drawn to scientific computing specifically because it sits between the mathematics and the application. I want to understand why a method converges, how floating-point arithmetic quietly loses precision, and how to choose an approach that is good enough for the question being asked. A degree gives me the linear algebra, analysis and programming depth I cannot reach by myself on a night shift, and I am ready to spend three or four years on it properly rather than continuing to pick things up in fragments.

How have your qualifications and studies helped you to prepare?

I left school with GCSEs including grade B in mathematics and went straight into work, so returning to study meant starting again with the fundamentals. I am currently finishing an Access to Higher Education Diploma in Science at my local college, studying mathematics, physics and chemistry over two evenings a week and one day release. The mathematics units have been the most useful preparation: differentiation and integration, sequences and series, matrices, and an introduction to differential equations. I found sequences and limits unexpectedly satisfying, because they underpin the iterative methods I had been using without really understanding why they settle on an answer. For my physics investigation I modelled projectile motion with air resistance, which cannot be solved neatly by hand, so I wrote a short numerical integration in Python and checked it against the drag-free case as a sanity test. My tutor's main comment was that I should state my assumptions more clearly, which was fair and has changed how I write up work. Alongside the diploma I have worked through much of a university-level introductory text on numerical methods, covering root finding, interpolation and Gaussian elimination, and I have been using an online linear algebra course to get more comfortable with eigenvalues and vector spaces. Studying while working shifts has made me organised out of necessary habit: I plan a week at a time and accept that some evenings are for revision rather than new material.

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

My work at the treatment works gave me habits that transfer well. Readings had to be recorded consistently and honestly, because a figure entered carelessly at three in the morning becomes somebody else's confusing data later. I was often the person who noticed a sensor drifting because the numbers looked wrong before any alarm triggered, and I learned to write handover notes that a colleague could act on without ringing me. I also spent a year helping to move our paper log sheets onto a shared digital form, which mostly meant sitting with operators to find out which fields they actually used. That taught me that a tool nobody understands will simply be worked around. For the past eighteen months I have volunteered at a community centre coding club, helping teenagers and a few adults with beginner Python. Explaining why a loop runs one time too many, or why comparing decimal numbers for exact equality is a bad idea, has forced me to be precise about things I thought I knew. In my own projects I keep a repository of small numerical experiments: a Monte Carlo estimate of an area, a routine that fits a straight line to noisy data by least squares, and a comparison of matrix multiplication written in plain loops against a library version, which was a memorable lesson in why libraries exist. Outside study I play five-a-side and have been learning to repair bicycles, which suits the same instinct for taking something apart to find out how it actually works.

This example has 4,573 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 draft is unusually specific and credible. Your water-works data problem leads naturally into numerical methods, and your Access mathematics, Python projects and teaching all support the motivation. The main problem is length. At 4,573 characters, the three answers exceed UCAS's 4,000 limit, so you need to cut about 600 characters without losing your best evidence.

Subject motivation

it could not tell us what would happen if we changed a setting

This is a genuine origin point. A practical limitation leads to a real question about modelling changing systems. You then name precise interests, such as convergence and floating-point precision, which show you understand what scientific computing is rather than offering a generic passion claim.

Academic preparation

sequences and limits unexpectedly satisfying, because they underpin the iterative methods

You connect named Access units to the methods you have used, which shows understanding rather than a list of topics. The projectile model checked against the drag-free case and the self-study in numerical methods and linear algebra are well judged. Together they show preparation beyond the syllabus that suits your stage.

Evidence and reflection

Watching the error shrink as I reduced the step size, and then seeing the runtime grow

This is real reflection. You describe what you observed and the trade-off it taught you. Your tutor's comment about stating assumptions, and the change it made to how you write up work, adds honest self-correction. Very few sentences rely on unsupported skill claims.

Relevant experience

a tool nobody understands will simply be worked around

You use ordinary work well. Spotting sensor drift, writing usable handover notes and digitising the log sheets each produce a specific lesson. The coding club examples are precise. The closing five-a-side and bicycle line is a weaker, forced link and is the clearest candidate for cutting.

Credibility and voice

I have taught myself enough Python to write a small simulation

Modest phrasing like this keeps your claims believable. You present yourself as a capable self-taught learner, not an expert, and the projects match an Access student's level. The voice is direct and personal throughout. Phrases such as 'habits that transfer well' are the only places where it drifts toward generic wording.

Structure and format

Each answer comfortably exceeds 350 characters and each uses distinct evidence, although Python projects appear in all three. The combined 4,573 characters breaks the 4,000 limit. Trim rather than restructure. Cutting about 600 characters still leaves you above the library's 3,500 minimum.

What you’ve done well

  • Your motivation grows from a concrete workplace question and leads to accurate, specific interests in convergence, error and precision.
  • Your Euler and Runge-Kutta comparison and your drag-model sanity check show you test your methods, not just run code.
  • Your outside experiences each yield a distinct lesson, especially the digitisation project and explaining decimal equality to learners.

How this draft could improve

  • Cut about 600 characters to meet the 4,000 limit. Start with the five-a-side and bicycle sentence, the 'organised out of necessary habit' sentence and some of the stirred-tank detail in answer one.
  • Reduce overlap in the Python evidence. Keep the stirred tank in answer one, the projectile model in answer two, and only one or two repository examples in answer three, with the matrix multiplication one as the strongest.
  • Replace the generic opener 'gave me habits that transfer well' by leading directly with the sensor-drift example, which already makes the point.