The European Research Council (ERC) is a EU institution that promotes high quality research in Europe. It funds individual investigators in any field of research – and it does so substantially: With up to 3.5 Million Euros, an ERC grant is Europe's highest research funding for individuals – and a very coveted prize: Only about 12% of proposals get funded, so competition is fierce.
Since I got my grant, other applicants have asked me again and again for hints and samples on how to prepare a proposal. Of course, there is no single recipe for success, but there were a few points which I found useful in preparing my proposal. While specific for ERC proposals (and from a computer scientist perspective), these tips should generalize for several other high-profile funding programs.
- Understand the process. The ERC publishes a Guide for Applicants as well as a Guide for Reviewers. Both should be your bible; at all times, ask yourself how your proposal will stand according to the criteria and the process listed. Find out what your panel is, who the chair will be, and which past members have been on the panel. Your proposal will need to win all of them.
- Start many, many months before the deadline. Unless your story is a winner straight from the inception, you will need lots of time for refining and revising the main idea and the many problems. In my case, I started writing the proposal 18 months before the deadline; although 6 months would have been okay, too, refining for another 12 months helped the proposal a lot.
- Reserve several weeks for writing. You will need lots of time for collecting data, shaping the story, and checking the references. Consider a 2–3 week retreat for the writing alone, plus appropriate time for polishing. Let your friends and family know when you'll be back.
- Get plenty of feedback. Your proposal will first be reviewed from people in your discipline, but not necessarily from people in your speciality. It may also be that your proposal will have to stand against proposals from totally different disciplines. Hence, your story must appeal to readers no matter what discipline and speciality they're from. Discussing your ideas and your proposal with as many people as possible and as diverse as possible will help. In my case, I had the proposal reviewed by 12 internal and 12 external people, and used every possible invited talk to present some sketches of the main ideas. (Such presentations not only help you to make your ideas explicit, but will also lobby for your ideas, and get feedback from the audience.)
- Rely on local expertise. ERC projects are huge, and thus involve substantial budget and resource planning. If your university has support for EU and/or ERC proposals, rely on their expertise. (If you have a colleague who is already funded by the ERC, check with her or him as well, of course!)
- Sell yourself. Your proposal will be assessed on two criteria. 50% is your project, and it will be up to you to come up with a great idea. 50%, however, is your past achievements, and you will have to work hard on these. What you need is irrefutable evidence for impact and excellence. That is, facts on awards, services, papers, talks, students, tools; lasting impact in academia and industry; your quality as networker and advisor; and, last but not least, your ability to shape and create research fields. Play by numbers: acceptance rates, citations, downloads. Check the list of past grantees, their numbers and achievements to get an idea of what you're up against.
- Have unique selling points. "So, you're Brad Pitt? That don't impress me much." When you're surrounded by supermen (and you will be), just being another superman is not enough. So:
- Don't just say: "I am an ACM Fellow". But say: "I am the first ACM Fellow from Spain", or "I am the youngest European ACM Fellow in concolic testing". Replace "European", and "concolic testing" by the most general feature you can find; and replace "ACM Fellow" by your most prestigious designation. (Hint: In my case, 6 out of 7 reviews began with "The applicant is an ACM Fellow", as if this would disperse all doubts on my abilities; so go for such designations as you can.)
- Don't just say: "Best Paper Award". But say: "First Best Paper Award for a Debugging Paper written on a one-legged stool". Exercise: generalize as above.
- Don't just say "700 citations". Also say: "Most cited testing paper since 1999".
- Avoid any claim that cannot be independently verified.
Your Project Plan
- No risk, no fun. The ERC funds high-risk, high-gain projects. This means that there have to be substantial risks of failure (otherwise, others would have done this before). However, your specific research plans should help to mitigate these risks and thus bring the high gains promised. Focus on novelty (why is this new?) and potential impact (why is this needed?). Avoid standard cliches from your discipline ("If only everybody had used this formal method from the start, the Ariane failure could have been prevented..."); come up with fresh, real stories and insights instead.
- Clear title, clear abstract. Think of the reviewer as an old, bored, nasty, uninterested, overloaded, overcommitted, latently aggressive, and totally uninterested ignorant doofus who hasn't gotten laid in a long time. (I'm a frequent reviewer, too, so I know what I speak about.) Even so, he or she should get interested in your proposal after a short glimpse of ten seconds. The message has to be in the title, in the abstract, in the figures, in the diagram, in the examples. (Yes, please have a diagram that conveys the approach! And please have an example, too! All these are weapons in the hands of your champions.) If you fear the message could be too complex, try again. If you think the message sounds too trivial to you, it could start to be understandable for the rest of us. (If, after simplification, your approach no longer sounds as cool as before, don't hide this with words, but go back to the drawing board.)
- Have a clear structure and plan. You're a seasoned researcher, so you know how to organize things, don't you? Now all you need to do is to put this in writing: tasks, dependences, milestones, evaluations, and measurable success criteria. The point of this exercise is not for the ERC to ask you to follow the plan by the letter once the project starts; the point of this exercise is for the reviewers to see that you can organize things.
- Get to the point. The length of an ERC proposals is clearly limited, and that's a good thing. Get to the point quickly. Use a clear language: No buzzwords, no yada yada, no lingo. If your project on "Examining the security interoperability of cloud business process models" cannot be motivated in plain English, don't expect the computer science panel chair to pitch it against "Curing cancer once and for all".
- Polish. Polish. Polish. And polish again. With an ERC grant, you're applying for the highest individual funding one can get in Europe. Do your homework.