My undergraduate project, Vayu, an IoT and remote-sensing air quality system, won a national award and represented the country at APICTA. Years later it still comes up in conversations, and it's central to my climate-focused master's applications.
Most people don't get that kind of mileage from student work, because they present it as homework. Here's how to present it as work.
1. Move it out of "Education"
Give it a Projects section. If it's more relevant than your jobs to the role or programme, put it above experience.
2. Describe it like a job
Weak:
Final year project: Air quality monitoring system using IoT.
Strong:
Vayu: IoT and remote-sensing air quality network (team of N, lead developer). Built low-cost PM2.5 sensor stations and a public dashboard combining ground and satellite data. National undergraduate award; represented [country] at APICTA.
3. Quantify honestly
Number of sensors, deployment duration, users, data points, accuracy improvements. Only real numbers. Small, real numbers beat inflated ones.
4. Name the recognition precisely
Award name, year, level (national or international). If you represented your country, say so. It signals the project held up against strong competition.
5. Turn it into a case study
A resume line gets attention. A case study keeps it: Lessons From Vayu does that job for me. Use the case study template.
6. Connect it to what's next
The project is more powerful when it explains your direction:
- For jobs: the skills it proves (IoT, data pipelines, dashboards)
- For master's applications: the question it raised that you now want to study (SOP structure)
- For career changes: the bridge between fields (career change SOP)
7. Use it in interviews
Prepare a two-minute version: problem, your role, hardest technical decision, outcome, lesson. It works for "tell me about a project you're proud of" and for behavioural questions.