Financial technology personal statement example

Why do you want to study this course or subject?

The thing that first made me curious about financial technology was how ordinary it has become. At the supermarket where I work on Saturdays, almost nobody hands me notes any more; they tap a phone, or a watch, and the transaction is settled before the receipt prints. I wanted to understand what actually happens in those two seconds, so I started reading about card networks, merchant fees and settlement, and realised that a payment is not one event but a chain of messages between institutions that have to agree on who owes what.

That led me into wider questions. My Economics course covers how banks create credit and how regulators try to keep the system stable, while Computer Science has taught me to think about systems in terms of data, latency and failure. Financial technology sits exactly where those two subjects meet: a lending decision made by a model is both a statistical judgement and a commercial and ethical one. I am interested in how credit scoring works when someone has little formal financial history, and in the argument that alternative data can widen access while also introducing bias that is harder to see than a human underwriter's prejudice.

I want a degree that takes both halves seriously, rather than treating code as a tool bolted onto finance. Studying financial markets, data analysis and the regulatory environment together is what attracts me to this course, and in the longer term I would like to work on payments or risk analytics, where the modelling has a direct effect on whether people can buy a home, run a shop or send money to family abroad.

How have your qualifications and studies helped you to prepare?

I am studying Mathematics, Economics and Computer Science, which between them have given me most of what I need to start this course. In Mathematics I have found statistics the most useful strand: probability distributions, hypothesis testing and correlation are the same ideas I keep meeting when I read about risk models, and working through them formally has stopped me treating a number in an article as self-evident. Pure topics such as sequences and series also turned out to matter more than I expected once I understood that compound interest, annuities and discounting are the same mathematics under different names.

Economics has taught me to write an argument that acknowledges its own weaknesses. A unit on financial markets and the 2008 crisis showed me how incentives inside institutions, not only individual error, can produce systemic problems, and I now read claims about technology making finance safer with that in mind. Computer Science has given me Python, SQL basics, and an understanding of how data is stored and queried, along with a healthy respect for testing.

For my Extended Project Qualification I wrote about the shift away from cash in the UK and what it means for people who rely on it. I used publicly available survey and industry reports, compared arguments about efficiency with arguments about financial inclusion, and had to be careful to distinguish between what the data showed and what commentators inferred from it. Choosing what to leave out was the hardest part, and it improved how I plan longer pieces of writing. Alongside my courses I follow the financial pages and have read Tim Harford's The Undercover Economist, which sharpened how I think about pricing and incentives.

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

My weekend job at a supermarket is where I have learned most about how people actually handle money. I work the till and the customer service desk, which means processing refunds, dealing with declined cards and helping customers who are unsure about the self-service machines. A regular customer who kept her weekly budget in a notebook explained that she preferred cash because she could see what was left, and that has stayed with me: any system I might help design has to work for her too, not only for people comfortable with an app. The job has also taught me to stay calm when a queue builds up and something has gone wrong with the card terminal.

Outside college I built a small budgeting tool in Python. It reads a CSV export of transactions, sorts them into categories using rules I wrote, and produces a monthly summary. Two friends tried it and immediately broke it, because their statements used different date formats and included refunds as negative amounts. Fixing that taught me more about data cleaning than any exercise I have been set, and it made me appreciate why standards for financial data matter so much.

I help run our college coding club, mostly supporting Year 10 and 11 students from a nearby school with beginner Python tasks. Explaining loops and variables to someone who has never programmed forced me to understand them properly myself, and I have become better at asking what a learner is stuck on rather than taking over the keyboard. I also play in a local five-a-side league on Sunday evenings, which is a useful reset after a shift, and I keep the team's fixture and subscription list on a spreadsheet, which the others find funnier than I do.

Between the job, the club and my studies I have had to be organised about time, and I am used to combining independent work with being part of a team. I am looking forward to bringing that to a degree where I can build the technical depth these interests deserve.

This example has 5,267 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.

Review this personal statement

Latest reviews