I'm a software engineer applying to master's programmes in environmental policy and AI for sustainability. On paper, that looks like a swerve. In reality it's a straight line, but only if I explain it properly.
If you're switching fields, the risk isn't the switch. It's an application that sounds like you're lost rather than moving toward something.
The bridge
Every convincing career change has a bridge: a point where your old field and your new one already overlapped in your actual experience.
For me, bridges include:
- Vayu, an air quality sensor project where engineering produced data meant for public decisions (write-up).
- EUDR compliance work at Dimitra, where software implements environmental regulation (EUDR for engineers).
Find yours. It might be a project, a volunteer role, a client, a thesis, or a problem you kept running into at work.
The structure
- Start in the new field. Open with the problem you want to work on, not with your old job.
- Bring in the old field as evidence. "I've spent X years doing Y, which taught me Z, which matters for this problem because…"
- Show the bridge. One or two concrete experiences where the fields met.
- Name the gap honestly. What you don't know yet.
- Show the programme fills that gap. Specific modules and methods.
- End in the new field. Your future role.
Translate your skills, don't list them
Don't write "I have strong programming skills." Write what those skills let you do in the new field:
| Old-field skill | Translated for the new field |
|---|---|
| Building data pipelines | Turning messy environmental data into evidence policymakers can use |
| Shipping products to users | Designing tools people actually adopt, not just pilot |
| Working with regulations in code | Understanding where policy meets implementation |
Address the obvious question
Reviewers will wonder: why not just keep doing the old job? Answer it in one or two sentences, focused on what you're moving toward.
Weak: "I'm tired of corporate work." Strong: "Building compliance software showed me that the hardest problems were upstream, in how the rules were designed, and I want to work there."
Things that help
- A bridging course or certificate, even a short online one, shows initiative.
- Reading the field. Referencing a specific paper, report, or policy debate shows you've done your homework.
- A referee who can speak to the bridge, e.g. a manager who saw you work on the environmental side of a project.
Things that hurt
- Apologising for your background. It's an asset, so frame it as one.
- Abandoning your old field entirely. Your differentiation is the combination.
- Vague passion. "I've always cared about the environment" is not evidence.