PERSONAL STATEMENT
EXAMPLES
My statements
Home » Subject areas » Mathematics, statistics and operational research » Operational research and decision science » Operations research and analytics postgraduate personal statement example

Operations research and analytics postgraduate personal statement example

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

Personal statement example

My interest in operations research began with a timetabling problem that had nothing to do with mathematics lectures. I help organise a volunteer football coaching group, and every autumn we struggle to fit twelve coaches, four age groups and two pitches into three evenings a week. For two seasons we did it with a whiteboard and argument. In my second year I wrote out the constraints properly, treated it as an assignment problem and solved it in a spreadsheet solver. The schedule was not perfect, but it was produced in an hour rather than a fortnight, and it made me see that the mathematics I enjoyed most was the kind that had to survive contact with people's preferences.

My degree gave me the foundations for that. I took linear algebra and optimisation, statistical modelling and stochastic processes, and I chose a final-year project on appointment scheduling at a community clinic. Working from anonymised aggregate arrival and consultation data that the practice manager was willing to share, I built an M/G/1-style queueing approximation and then a discrete-event simulation in Python using SimPy. The comparison was the most useful part of the work: the analytical model was tidy but assumed stationary arrivals, while the simulation let me test what happened when late arrivals clustered after school finishing times. I found that grouping longer appointments at the end of a session reduced simulated average waiting time more reliably than simply shortening slot lengths, though the result was sensitive to how often patients did not attend. Writing the discussion taught me to be candid about the limits of a model built on limited data, and I was pleased that my supervisor's main criticism was about presentation rather than method.

Since graduating I have worked three days a week as a scheduling assistant for a bakery that delivers to around forty cafés and shops. My job is mostly practical: confirming orders, adjusting van loads and rerouting when a driver is ill. It has been an education in the difference between an optimal route and an acceptable one. Two of our drivers know their areas well enough to beat the software on timing, and one customer insists on a delivery window that makes the rest of the round awkward. I have started keeping a simple record of late deliveries by day and route, and the pattern that emerged, consistent Friday delays on the longest round, was enough to persuade my manager to split it. I am aware that this is descriptive work rather than analytics, and that is part of why I want to study further: I can see where forecasting and vehicle routing methods would help, but I cannot yet implement them at a standard I would trust for a business decision.

Alongside work I share care of my younger brother, which has made me methodical about planning my time and comfortable with revising plans when they fail. I read around the subject in the gaps, most recently Bertsimas and Tsitsiklis on linear optimisation, which I am working through slowly because the duality chapters repay rereading, and I have been teaching myself Julia for solver work after using mainly Python and R.

From a master's I want rigorous grounding in integer programming and stochastic modelling, more experience with large-scale solvers, and a dissertation with a genuine client problem behind it, ideally in logistics or healthcare capacity. In the longer term I would like to work as an analyst in a team that sits close to operations, where the modelling is judged by whether the schedule holds on a Friday afternoon.

Why this example works — strengths and ways to improve

This is a strong, coherent taught master's statement. Your motivation, degree project and bakery job connect naturally, and you reflect honestly on the limits of your models and skills. The evidence is concrete and modest rather than inflated. The main gaps are brief detail on validation and a care paragraph that leans on generic skill claims.

Subject motivation

treated it as an assignment problem and solved it in a spreadsheet solver

Your origin story works because it shows you formalising a real constraint problem rather than claiming lifelong fascination. Saying the mathematics had to survive contact with people's preferences gives a clear reason for choosing operations research over pure mathematics, and the later paragraphs consistently develop that idea.

Academic preparation

I took linear algebra and optimisation, statistical modelling and stochastic processes

These modules are directly relevant, and the project shows you applied them. You do not mention integer programming, so naming it as a master's goal is honest. Readers may want to know your level of programming beyond SimPy. This is a general example, so check any real programme's requirements yourself.

Evidence and reflection

the analytical model was tidy but assumed stationary arrivals

This is the statement's best reflection. You compare two methods, explain why the assumption mattered, report a finding with its sensitivity to non-attendance and acknowledge limited data. One sentence on how you validated the simulation against the clinic's observed data would make the methodological claim stronger.

Relevant experience

consistent Friday delays on the longest round, was enough to persuade my manager

An ordinary part-time job becomes strong evidence here. You show judgement about optimal versus acceptable routes, take a small analytical initiative and see a real outcome. Calling it descriptive rather than analytics is credible self-assessment, and it motivates further study well.

Credibility and voice

which I am working through slowly because the duality chapters repay rereading

Your voice is measured and believable throughout, and your claims fit a recent graduate. The reading detail sounds genuine. By contrast, saying that caring for your brother made you methodical is a generic skill claim. Either cut it or tie it to something specific.

Structure and format

where the modelling is judged by whether the schedule holds on a Friday afternoon

The structure moves logically from motivation through degree and work to aims. Your ending echoes the bakery detail without forced sentiment. The label 'Personal statement example' and the extra blank lines between paragraphs should be removed. The prose is economical, with little repetition.

What you’ve done well

  • Your degree project explains a concrete methodological trade-off and a qualified finding, not just the tools you used.
  • Your bakery role is used intelligently to show the gap between your current skills and the methods you want to learn.
  • Your future aims are realistic and specific to logistics or healthcare capacity, without overclaiming.

How this draft could improve

  • Add one sentence on how you checked the simulation's outputs against observed clinic data or tested its assumptions.
  • Either develop the caring-responsibility point with a concrete planning example or remove it to keep the focus sharp.
  • When applying to a real programme, tailor your aims to its actual content and prompt, and delete the example heading.