- Reading time: 2 minutes
- Price: Free download
- Published: 17th September 2026
- Word count: 590 words
- File format: Text
Personal statement example
My interest in cryptography grew out of a number theory module in my second year of a mathematics degree. I had expected modular arithmetic to stay abstract, and was surprised to find that the difficulty of factoring large integers, and the structure of finite fields, underpinned the padlock icon I had been ignoring in my browser for years. I followed the module with algebraic structures and computational algebra, and chose a final-year project on elliptic curves over finite fields, working through the group law, point counting for small curves, and why curve choice matters for the security of key exchange. Writing that dissertation taught me how much care sits behind parameter selection: a curve that looks fine on paper can be weak because of its order or its embedding degree. I would like to study cryptography at master's level because my degree gave me the mathematical grounding but only a partial view of how that mathematics survives contact with real implementations.
Alongside the theory I have tried to build practical understanding. In a third-year group project I implemented textbook RSA and Diffie–Hellman in Python, then wrote a short report on why our implementations should never be used: no padding scheme, naive primality testing, and timing behaviour that leaked information about the exponent. Reading Ferguson, Schneier and Kohno's Cryptography Engineering afterwards clarified how much of the discipline is about protocol design and failure modes rather than inventing new primitives. More recently I have been reading about lattice-based schemes and the post-quantum standardisation process, and I am working slowly through some introductory material on learning with errors. I find the shift in assumptions genuinely interesting, and I want formal teaching in provable security so that I can read the literature properly rather than relying on summaries.
My responsibilities outside study have shaped how I work. I share care for my younger brother, who has autism and needs predictable routines, which means my study time has always been planned rather than spontaneous. I learned to break my dissertation into small weekly targets and to write up as I went, which is the only reason it was finished calmly. I also work Saturdays and holidays on the customer service desk of a garden centre, dealing with returns, delivery problems and occasionally people who are already annoyed before they reach me. It has made me patient and clear when explaining something to someone who has no reason to care about the detail.
That skill has been useful at a community computer club I help run in a local library, where most members are over seventy. I explain password managers, two-factor authentication and why a message claiming to be from a bank rarely is. Teaching there has made me more careful about the difference between cryptography and security in practice: the mathematics can be sound while the person is still tricked into typing their code into a fake page. I expect to keep that perspective if I go on to work in the field.
For the master's itself I hope to strengthen my background in provable security and cryptanalysis, get supervised experience of implementing schemes carefully, and complete a dissertation related to post-quantum key exchange or side-channel resistance. In the longer term I am drawn to applied cryptography work in industry or standards bodies, where mathematics and engineering meet. I am comfortable with proof-based work, willing to put in the slow reading that this subject demands, and keen to be taught by people who know where the current problems lie.
Why this example works — strengths and ways to improve
This is a credible, well-grounded taught master's statement. Your motivation grows naturally from coursework, your project evidence shows real understanding of why implementations fail, and your non-academic experience connects honestly to security practice. The main gaps are some loosely linked paragraphs, a slightly generic close, and limited evidence of programming depth or performance in proof-heavy modules.
Subject motivation
underpinned the padlock icon I had been ignoring in my browser
Your motivation is specific and believable. It comes from discovering that abstract number theory had practical consequences, not from a vague childhood fascination. The final sentence of that paragraph sharpens it well by explaining what a master's adds beyond your degree: how mathematics survives real implementations.
Academic preparation
a final-year project on elliptic curves over finite fields
This is strong preparation evidence. Naming the group law, point counting and embedding degree shows you worked with the material rather than summarising it. Your point that a curve can look fine yet be weak shows judgement. Briefly indicating your proof-based modules would support your later claim of comfort with proofs.
Evidence and reflection
why our implementations should never be used: no padding scheme
Explaining why your own RSA and Diffie–Hellman code was unsafe is excellent reflection. It shows critical awareness of failure modes rather than pride in a working prototype. The learning with errors reading is honestly framed as early-stage, which is appropriate. Saying what specifically interests you in the shift in assumptions would add depth.
Relevant experience
the mathematics can be sound while the person is still tricked
The computer club gives you a genuine insight that separates cryptography from security in practice, and it is well earned. The garden centre and caring paragraphs show reliability and planning. However, their link to cryptography relies on general skill claims like being patient and clear, which carry less weight here.
Credibility and voice
I am working slowly through some introductory material
Your voice is measured and honest, and that modesty increases credibility. You avoid overclaiming expertise in post-quantum work. Occasional generic phrasing, such as being willing to put in slow reading or being keen to be taught by experts, sounds less distinctive than the rest of the statement.
Structure and format
That skill has been useful at a community computer club
The sequence of theory, practice, life experience, outreach and aims is logical. The transition into the computer club is somewhat forced, since the club stands on its own merits. The responsibilities paragraph could be tightened so that more space goes to academic and technical evidence.
What you’ve done well
- Your elliptic curve dissertation is described with precise technical detail that shows genuine understanding of parameter choice and security.
- Critiquing your own textbook RSA implementation shows the engineering mindset applied cryptography requires.
- The library club gives an authentic, well-reflected distinction between sound mathematics and real-world security.
How this draft could improve
- Add concrete evidence of proof-based work or programming depth, such as a specific module, proof technique or tool, to support your readiness for provable security and careful implementation.
- Condense the caring and customer service material into a sentence or two, and let the computer club stand alone without the forced 'that skill' transition.
- Replace the generic closing sentence with a specific question or problem in post-quantum key exchange or side-channel resistance that you want to explore.