- Reading time: 3 minutes
- Price: Free download
- Published: 17th September 2026
- Word count: 636 words
- File format: Text
Personal statement example
My degree in chemical engineering finished with a design project on a small solvent recovery unit, and the part I remember best was not the column sizing but the HAZOP-style review our group was asked to run on our own flowsheet. We found that the reflux drum vent we had cheerfully drawn would, under a plausible cooling water failure, have discharged something flammable at head height near a walkway. That exercise stayed with me far longer than the calculations, and eight years of shift work have only sharpened my interest in why plant that looks safe on paper behaves differently at three in the morning.
Since graduating I have worked at a water treatment and industrial effluent site, first as a process operator and now as a shift technician. Much of the job is routine: dosing control, sampling, chlorine and ferric deliveries, sorting out blinded screens and tripped pumps. What has shaped my thinking is the gap between written procedure and actual practice. Our confined space entries into balance tanks are properly controlled, but I have seen how easily a gas monitor gets taken on trust, how often a job is scheduled at the least convenient point in a shift, and how small changes to a pipework run quietly accumulate until the drawings no longer match the plant. For the last two years I have coordinated permits to work on my shift, which means challenging colleagues and contractors I know well, and explaining to a fitter who has done a task a hundred times why this occasion needs isolation proving. Those conversations taught me that safety engineering is partly technical and partly about giving people reasons they find credible.
I wanted a better grounding than experience alone, so I completed the NEBOSH General Certificate, largely in my own time. It gave me useful language for risk assessment and legal duties, but it also showed me the limits of what I currently know. I can describe a bow-tie diagram; I cannot yet assign defensible failure rates to a protection layer or work through a LOPA properly. I would like to be able to do quantitative risk assessment, consequence modelling for releases and dispersion, and reliability analysis with some rigour rather than by borrowing other people's numbers. Reading Trevor Kletz on inherently safer design made me look again at our own chemical storage, where the answer to several hazards would have been less stored inventory rather than more interlocks.
To prepare for returning to study I have been working back through thermodynamics and fluid mechanics from my old textbooks, and taking an online course in probability and statistics because my degree statistics were thin and I know reliability work depends on them. I have also been practising in Python, mostly writing small scripts to pull trends from our SCADA exports and look at how often particular alarms recur; it is modest work, but it has made me comfortable handling data rather than intimidated by it.
Outside work I lead a weekly group run at my local club, which involves route checks, keeping an eye on newer runners and deciding when conditions are poor enough to change plans. It is a small responsibility, but it is the same habit of thinking ahead about what could go wrong for people who are relying on you.
I am applying now rather than earlier because I finally have the financial position and the motivation to study properly. In the longer term I want to work as a process safety engineer in the water or chemicals sector, ideally in a role that includes hazard studies and design review. A taught master's, with a project I can ground in real operating conditions, is the most direct way for me to become genuinely useful in that work rather than simply experienced.
Why this example works — strengths and ways to improve
This is a strong, grounded statement for a taught master's in safety engineering. Your motivation grows convincingly from a degree HAZOP and eight years of operational work, and you name precise gaps such as LOPA and failure rates. The main weaknesses are a slightly forced running-club link and a thin account of the intended project's methods.
Subject motivation
why plant that looks safe on paper behaves differently at three in the morning
This line ties your interest to a real tension between design and operation, which is exactly what safety engineering addresses. Because it follows the reflux drum vent example, the motivation feels earned rather than declared, and it carries through to your closing aims.
Academic preparation
I can describe a bow-tie diagram; I cannot yet assign defensible failure rates
You show a chemical engineering degree, NEBOSH and self-study, then honestly map what you lack. This candid gap analysis reads as readiness for advanced study. You could briefly say what the design project taught you technically, beyond the HAZOP, to strengthen the degree evidence.
Evidence and reflection
the answer to several hazards would have been less stored inventory rather than more interlocks
Here you apply Kletz to your own site, which is genuine reflection rather than name-dropping. The confined space and drawing-drift observations work the same way. Each one moves from what you saw to what it means, which is far more persuasive than listing skills.
Relevant experience
explaining to a fitter who has done a task a hundred times why
Coordinating permits to work is directly relevant, and this detail shows the human side of safety credibly. The Python SCADA alarm scripts add useful data evidence. You could say what the alarm analysis actually revealed, because a finding would turn a modest project into stronger proof.
Credibility and voice
it is modest work, but it has made me comfortable handling data
Your tone is measured and plausible for an experienced technician, and you never overclaim authority. Phrases like this build trust. The voice stays personal throughout, though "genuinely useful" and "properly" recur slightly, so watch for small repetitions in the final paragraph.
Structure and format
It is a small responsibility, but it is the same habit
The structure moves logically from origin to work, then to study, preparation and aims. The running-club paragraph is the weakest link: the parallel feels forced and takes space from your project plans. Consider shortening it or cutting it so the ending gains focus.
What you’ve done well
- You give concrete, plant-specific examples, such as the vent at head height, drawings drifting from the plant and gas monitors taken on trust.
- You state your technical gaps (LOPA, failure rates, dispersion modelling) precisely, which justifies the taught master's.
- The career aim of process safety in the water or chemicals sector follows logically from your experience.
How this draft could improve
- Sketch the kind of master's project you might pursue, for example one built on alarm recurrence or inventory reduction, and the methods it would involve.
- Report one result from your SCADA scripts to show analytical outcome, not just activity.
- Trim or cut the running-club paragraph, and tailor the closing to the actual programme you apply to.