ETH Zurich: Motivation letter / statement of purpose

Typically about one page, roughly 400 to 600 words; check the specific program or scholarship instructions

The statement of purpose and motivation letter for ETH master's programs and scholarships

What it’s really asking

ETH wants to know why you, specifically, want this exact program, and whether your academic and technical background has prepared you to succeed in it. This is the one piece of free writing ETH genuinely reads, so it should function like a compact research pitch: your relevant training, what you have built or studied, and the precise direction you want to pursue at ETH.

Why they ask it

ETH bachelor admission is decided by certificates and the entrance exam, so this prompt matters most at the master's and scholarship stage, where readers are professors and program coordinators screening for fit and capability. They are deciding whether you can handle a rigorous, often research-heavy program in their field, and whether your interests align with what the group actually does. A vague or story-driven letter signals poor fit; a specific, evidence-led one signals a candidate they can place.

Three ways in

Lead with the work

Open with the concrete thing you have already done in this field, a project, thesis, or internship, not with how long you have loved the subject.

Name the exact program

Name the precise ETH program and, ideally, a research group or course, then connect it to a problem you actually want to work on.

Show one honest gap

Be candid about one weakness and your plan to close it; technical maturity reads as credibility, not as a confession.

✕ Weak opening

“Ever since I was a child, I have been fascinated by the wonders of science and dreamed of studying at a world-class university.”

✓ Strong opening

“Last year I spent four months turning a noisy 12,000-row sensor dataset into a model that predicted bearing failure three days out, and I want to push that work further in ETH's reliability and risk group.”

✦ Annotated example · MSc Robotics SOP. Written by EssayLens to teach, not a real applicant’s essay. Tap a highlighted line →

During my bachelor's thesis at the Technical University of Munich, I spent four months trying to make a quadruped robot walk across loose gravel. My controller worked flawlessly in simulation and fell over in the first ten seconds outdoors.¹ That gap between simulation and reality became the question that now defines my work, and it is why I am applying to the MSc in Robotics, Systems and Control at ETH Zurich.² I diagnosed the failure as an unmodeled contact dynamics problem: my rigid-body assumption ignored how gravel shifts under load. I rebuilt the contact model using a soft-constraint formulation, retrained the policy with domain randomization across friction coefficients, and cut the outdoor fall rate from 70 percent to 12 percent over three weeks of field tests.³ I am not claiming I solved sim-to-real transfer. The remaining 12 percent failures clustered on slopes my randomization never covered, and I have come to see that as the harder and more interesting half of the problem.⁴ That is precisely the territory the Robotic Systems Lab works in. I have read Hwangbo and Hutter's work on learning agile and dynamic motor skills for legged robots, and the use of privileged learning to bridge perception gaps maps directly onto the slope failures I could not solve alone. I would want to extend that line toward terrain where the ground itself is deformable, building on my contact-model work rather than starting over.⁵ My preparation is uneven, and I would rather be candid about it. My strengths are in control theory and C++ implementation: I scored in the top decile of my nonlinear control course and maintain the ROS2 stack our lab uses. My optimization theory is thinner. I have worked through convex methods but never the nonconvex trajectory optimization that modern whole-body control demands, which is why the Optimization for Engineers and Numerical Optimal Control offerings shaped my decision to apply here specifically.⁶ Beyond coursework, I want the failure-tolerant environment ETH builds around field robotics. The systems I admire were not validated on a clean lab floor; they were dragged through snow, rubble, and forest, and they broke publicly before they worked. I learned more from my robot falling on gravel than from any clean simulation result, and I am looking for two years where that kind of breaking is the method, not an embarrassment.⁷ My longer aim is to work on locomotion for robots deployed in disaster response, where deformable and unpredictable terrain is the norm rather than the exception. ETH is where the controllers I would need are being invented, and where my gravel problem stops being a dead end and becomes a starting point.⁸

1Opens with a concrete, specific failure rather than a sweeping passion statement. ETH rewards evidence over narrative, so a real engineering scene establishes credibility immediately.
2Names the exact program. Connecting a personal research question to a named degree signals deliberate fit rather than a generic application sent to many schools.
3Quantified, mechanism-level detail. Giving the actual method and the before/after numbers demonstrates technical maturity and lets the reader verify the claim instead of trusting an adjective.
4Explicit honesty about limits. Admitting what did not work, and treating the residual failure as the real research frontier, signals the technical humility ETH explicitly values.
5Cites a specific lab and a specific paper, then ties it back to the applicant's own prior work. This proves genuine engagement with the group and shows fit at the level of a concrete research direction, not a name-drop.
6Honest self-assessment that names a real gap and then turns it into a reason for choosing ETH's particular courses. This reframes a weakness as evidence of fit and forward planning.
7Connects personal working style to the program's documented culture of real-world testing. Reinforces fit while keeping the evidence-first, anti-hype tone consistent.
8Closes with a forward-looking goal that loops back to the opening image. The full-circle structure gives the letter coherence while keeping the focus on concrete technical ambition rather than sentiment.

Stuck? Start here

What is the most concrete thing I have built, measured, or proven in this field, and what number describes its result?
Which exact ETH program, course, or research group fits the problem I want to work on, and what about it is specific to ETH?
What is one honest gap in my preparation, and what am I doing right now to close it?

Before you submit

Does roughly 80% of the letter cover academic and technical substance rather than personal narrative?
Have I named a specific ETH program or research group instead of praising ETH in general?
Have I addressed the German-language and international-applicant reality where relevant?

Drafted it? Get an honest, admissions-style read, free.

Score my essay