{"id":30437,"date":"2026-11-20T12:00:32","date_gmt":"2026-11-20T11:00:32","guid":{"rendered":"https:\/\/voelkerrechtsblog.org\/de\/?p=30437"},"modified":"2026-11-20T10:02:00","modified_gmt":"2026-11-20T09:02:00","slug":"how-to-interview-your-way-to-an-erc-project","status":"publish","type":"post","link":"https:\/\/voelkerrechtsblog.org\/de\/how-to-interview-your-way-to-an-erc-project\/","title":{"rendered":"How to Interview Your Way to an ERC Project"},"content":{"rendered":"<p>In <a href=\"https:\/\/voelkerrechtsblog.org\/de\/how-to-think-your-way-to-an-erc-project\/\">my last blog<\/a> for V\u00f6lkerrechtsblog, I wrote about how to think your way to an ERC project \u2014 how to find an idea, make it fundable, and write it for the panel that will read it. This blog picks up where that one ended. If you are reading it, there is a good chance you have just received the email: your proposal has passed step one, and you are invited to interview. Congratulations. Take a day to enjoy it. Then start preparing.<\/p>\n<p>The interview is a strange moment. Months of work are compressed into a short conversation with a group of people you have probably never met, most of whom are not experts in your field. For many applicants, it is the first time they have had to defend a project out loud in front of economists, political scientists, historians and philosophers. It can feel arbitrary. But having been through the ERC interview twice \u2014 for <a href=\"https:\/\/www.humanrightsnudge.com\/projects\/human-rights-nudge\"><em>Human Rights Nudge<\/em><\/a> and for <a href=\"https:\/\/www.humanrightsnudge.com\/projects\/break-the-bias\"><em>Break the Bias<\/em><\/a> \u2014 and having sat on review panels myself, there are a few things you can do to maximise your chances of success:<\/p>\n<p><strong>1. Prepare, Prepare, Prepare<\/strong><\/p>\n<p>You will typically have around two months between the invitation and the interview. Use them. Block out your calendar, say no to what can wait, and make the interview your main focus. In my experience, those two months are where most of the work on an ERC application actually happens. It may feel excessive to prepare for so long for a twenty-one-minute conversation. It is not: in those few minutes, five years of funding are decided.<\/p>\n<p>In those two months you should find out everything that is wrong with your proposal \u2014 and then build, through practice, the confidence to defend it anyway. Importantly, you are there to <em>defend<\/em> the proposal, not to change it. Rereading it months later, you will see flaws: a concept you would now explain differently, a question you would phrase more sharply, perhaps even an error that slipped through. Resist the temptation to present a new version. The panel evaluated the text in front of them (Parts B1 and B2), and the reviewers commented on that text. Remember what the proposal is: the dream \u2014 the most perfect way the project could go, not a promise of results. In reality, the project will go in many directions and you will adapt. But in the interview, you defend the dream.<\/p>\n<p>Think about how you can embed your project in wider scholarship and disciplinary debates, not just international law but also international relations, political science, etc. Catch up on what has been published since. Then reread the whole proposal as if you were a hostile reviewer. What would I ask about this? Where is it vague? Where did I promise something I am not sure I can deliver? Where did I make a choice \u2014 a case selection, a sample, a time frame \u2014 without explaining why? Then speak to everyone you know \u2013 anyone who works on a similar question, adopts the same methodology, or can give you an idea of what the risks could be.<\/p>\n<p>Write those questions down. I usually end up with fifty or sixty, grouped by theme: the idea, the state of the art, methodology, feasibility, the team, the budget, ethics, and me as principal investigator. For each, I initially write two or three paragraphs, then distill these into sentences. You will not read these out, but writing them forces you to concisely decide what you actually think.<\/p>\n<p>Prepare for the questions you fear. Everyone has one: the gap in your publication record, the weakest work package, the method you have never used yourself.<\/p>\n<p>Finally, the practical side: Know your numbers \u2014 how many cases, interviews, postdocs and for how long, what the money is for. Know what happens in month 18. If the interview is online, test your camera, your light and your connection, and have a backup. Nothing derails a calm answer like a frozen screen.<\/p>\n<p><strong>2. What to Wear (and What to Bring)<\/strong><\/p>\n<p>This sounds trivial. It is not. Think about the panel\u2019s day: they interview candidate after candidate, and discuss them all at the end. By the afternoon, faces and projects blur. So wear something distinguishable \u2014 a colour, a jacket, a scarf. You want the panel to say \u201cthe one in the red jacket, with the project on access to courts\u201d and everyone will know exactly who they mean. It should still be professional, and comfortable enough that you never think about it once you sit down. Online, this matters even more: you are one small square on a screen among many.<\/p>\n<p>The same logic applies to what you bring. In principle, slides are no longer allowed, so consider an object that explains your project. I used a Lego set (<a href=\"https:\/\/www.humanrightsnudge.com\/projects\/break-the-bias\">see video<\/a>) to show how the different parts of my project fit together and build on each other. It sounds playful, and it is. But a physical model of your work packages is something a non-specialist panel understands instantly \u2014 and remembers. Keep it simple, practise with it, and make sure it serves the explanation rather than distracting from it.<\/p>\n<p><strong>3. Do Mocks the Right Way: Know Who Sits on Your Panel<\/strong><\/p>\n<p>Most universities now offer mock interviews, and you should do at least three. But a mock is only as useful if it is realistic. The most common mistake is to run it with colleagues from your own field. They know your literature, share your assumptions, and ask the questions an expert would ask. That is not your panel.<\/p>\n<p>The list of panel members from previous calls is public, and a large part of each panel (about a third) stays the same as two years ago (so for 2027 call the panel would be partly the same as in <a href=\"https:\/\/erc.europa.eu\/system\/files\/2025-09\/ERC-2025-StG-panel-members.pdf\">2025<\/a>). Look it up \u2014 and build your mock accordingly. If you are applying in law and social sciences, your panel will be made up mostly of political scientists, sociologists and economists, with perhaps one or two lawyers. Find a social scientist to question your sample. Find someone from a completely different discipline to ask why any of what you are doing matters. Find someone senior who has sat on an ERC panel, or any large grant panel, to chair.<\/p>\n<p>Beyond mocks, talk to people. Tell colleagues you have been invited and ask for help. You should, however, not contact people who sat on the panel two years ago as you may be approaching your own evaluators. Instead, seek out colleagues in your area and people who have been through an ERC interview before. People are, on the whole, very happy to help.<\/p>\n<p>Then make the mocks hard. Ask your mock panel not to be kind. A friendly mock gives you false confidence; a tough one shows you the gaps. Record it and watch it back (painful, but extremely useful). Do the last one under real conditions \u2014 same time limits, same format, with people you do not know well. By the day of the real interview, nothing about the situation should be new.<\/p>\n<p><strong>4. Respect Your Reviewers and Your Rapporteur<\/strong><\/p>\n<p>In my last blog, I explained that external peer reviewers read your proposal on its own and that their feedback shapes the questions you face at the interview. By the moment of the interview, your proposal has been read very closely: external reviewers have written reports, and the panel members assigned to it \u2014 one of whom acts as rapporteur, presenting your project to the rest of the panel \u2014 have studied both. You will not see those reports before the interview. But many of the questions will come straight out of them.<\/p>\n<p>The rapporteur is not your opponent. In fact, if you have reached interview, someone on that panel thinks your project may well be worth funding \u2014 and in the discussion after you leave, they will need arguments to make that case. Your job is to give them those arguments. Clear, confident, specific answers are ammunition for your champion.<\/p>\n<p>So respect the critique, even when you think it is wrong. Do not say \u201cthe reviewer misunderstood\u201d. Do not imply the question is na\u00efve. A reviewer who misread something has shown you where your proposal was unclear. Acknowledge it, explain, and move on: \u201cThat is an important question, and I should have been clearer. What I mean is\u2026\u201d. Defensiveness is the fastest way to lose a panel\u2019s sympathy.<\/p>\n<p><strong>5. Respect the Question<\/strong><\/p>\n<p>This sounds obvious: Answer the question you were asked \u2014 not the one you prepared for, and not the one you wish they had asked.<\/p>\n<p>Under pressure, we all reach for the rehearsed answer. A panel member asks about your case selection, you hear \u201cmethodology\u201d, and off you go into your well-practised paragraph on mixed methods. This reads as evasion. Even more, it wastes time you do not have.<\/p>\n<p>Listen to the whole question. Take a second before you answer \u2014 silence feels much longer to you than it does to them. If you do not understand, ask for clarification; that is not weakness, it is respect. And if the question is about a weakness, answer it directly before adding context. \u201cYes, that is a risk\u201d is a perfectly good first sentence. Panels trust candidates who can say it.<\/p>\n<p><strong>6. The Pitch: Three Minutes, No PowerPoint \u2014 Answer the Why<\/strong><\/p>\n<p>The interview opens with your pitch: three minutes, no slides. I was able to say 604 words in that time \u2014 not enough to summarise\u00a0my proposal, but rather give them a reminder of what the project was about.<\/p>\n<p>In my last blog, I said every proposal must answer one central question: why this project, why now, and why you? The pitch is that question\u00a0\u2014 and above all, <em>w<\/em><em>hy<\/em> does this project need doing? What will remain unknown if it is not funded? Most of the panel are not lawyers, let alone international lawyers. They need to understand within thirty seconds why someone outside our field should care. For <em>Break the Bias<\/em>, the why was simple: international human rights courts are meant to be open to everyone, but they may in practice be available only to people with money, from the Global North, with good lawyers. If that is true, the system is failing exactly the people it was built for.<\/p>\n<p>I find the following\u00a0structure useful: the problem (why it matters), the gap (why we cannot answer it now), the project (how you will answer it, with one sentence on the method), and you (why you are the person to do it). Do not list work packages. Leave the panel with one sentence they can repeat to each other once you have left.<\/p>\n<p>Write the pitch out in full, then learn it well enough that you no longer need the text \u2014 but not so well that it sounds recited. Time it, again and again. Running over is worse than finishing early: you will be cut off, and that sends a poor signal at the start of the interview.<\/p>\n<p><strong>7. Q&amp;A: The Funnel<\/strong><\/p>\n<p>The rest of the interview is questions.\u00a0This is usually where the decision is made. The whole interview lasts twenty-one minutes. In that time you can answer around eleven questions in one to two minutes each.<\/p>\n<p>When I am preparing, I think of my answers as a funnel. Start wide and short: a direct answer, in one sentence. Then narrow: the principle behind it. Then narrow again: the concrete detail from the proposal \u2014 the work package, dataset, case, month. Then stop.<\/p>\n<p>Why a funnel? Because your panel is mixed. The non-specialist gets what they need from the first sentence; the specialist from the last. And it lets you control the depth: if the panel wants more, they will ask.<\/p>\n<p>A good Q&amp;A is a conversation. The more questions the panel gets through, the more chances you have to show what you know \u2014 and the more material your rapporteur has to work with once you have left the room.<\/p>\n<p><strong>My final point<\/strong><\/p>\n<p>However well you prepare, some of this is out of your hands. Good projects are sometimes not funded, and plenty of ERC grantees did not succeed on their first attempt. If that happens, read the panel\u2019s comments carefully: they are some of the most detailed feedback you will ever get on your project, and the starting point for your next application.<\/p>\n<p>None of the preparation is wasted. Writing grants is not\u00a0a waste of time. The research you do stays with you. If the ERC does not fund it, another funder may, and the next version will be stronger.<\/p>\n<p>So walk into the interview believing that you belong there \u2014 because you do. Of all the proposals the panel read, they want to hear more about yours. You <em>can<\/em> defend your dream. You <em>can<\/em> answer their questions. And you <em>can<\/em> show them, in twenty-one short minutes, why your project needs doing. Good luck!<\/p>\n<p><em>Author\u2019s note: This blog is based on my own experience of applying for and interviewing for ERC grants, on the feedback I have received from panels and colleagues, and on talks I have given on this topic. <\/em><em>I have used Claude to structure my many<\/em><em> handwritten<\/em><em> notes from these <\/em><em>occasions<\/em><em>. This was <\/em><em>a valuable<\/em><em> experience <\/em><em>\u2013 especially <\/em><em>in learning what Claude cannot do!<\/em><\/p>\n<p><em>Note by the Editorial Team: This contribution is published under \u201c<a href=\"https:\/\/voelkerrechtsblog.org\/services\/resources\/\"><strong>V\u00f6lkerrechtsblog Resources<\/strong><\/a>\u201c, which serves as a repository for materials relating to international legal scholarship, thought, and practice. You are warmly invited to contribute. \u00a0<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>In my last blog for V\u00f6lkerrechtsblog, I wrote about how to think your way to an ERC project \u2014 how to find an idea, make it fundable, and write it for the panel that will read it. This blog picks up where that one ended. If you are reading it, there is a good chance [&hellip;]<\/p>\n","protected":false},"author":39,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[6639],"tags":[8070,7468],"article-categories":[8069],"authors":[6812],"doi":[],"class_list":["post-30437","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-funding-applications","tag-legal-academia","article-categories-resources","authors-veronika-fikfak"],"acf":{"subline":""},"meta_box":{"doi":""},"_links":{"self":[{"href":"https:\/\/voelkerrechtsblog.org\/de\/wp-json\/wp\/v2\/posts\/30437","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/voelkerrechtsblog.org\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/voelkerrechtsblog.org\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/voelkerrechtsblog.org\/de\/wp-json\/wp\/v2\/users\/39"}],"replies":[{"embeddable":true,"href":"https:\/\/voelkerrechtsblog.org\/de\/wp-json\/wp\/v2\/comments?post=30437"}],"version-history":[{"count":3,"href":"https:\/\/voelkerrechtsblog.org\/de\/wp-json\/wp\/v2\/posts\/30437\/revisions"}],"predecessor-version":[{"id":30445,"href":"https:\/\/voelkerrechtsblog.org\/de\/wp-json\/wp\/v2\/posts\/30437\/revisions\/30445"}],"wp:attachment":[{"href":"https:\/\/voelkerrechtsblog.org\/de\/wp-json\/wp\/v2\/media?parent=30437"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/voelkerrechtsblog.org\/de\/wp-json\/wp\/v2\/categories?post=30437"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/voelkerrechtsblog.org\/de\/wp-json\/wp\/v2\/tags?post=30437"},{"taxonomy":"article-categories","embeddable":true,"href":"https:\/\/voelkerrechtsblog.org\/de\/wp-json\/wp\/v2\/article-categories?post=30437"},{"taxonomy":"authors","embeddable":true,"href":"https:\/\/voelkerrechtsblog.org\/de\/wp-json\/wp\/v2\/authors?post=30437"},{"taxonomy":"doi","embeddable":true,"href":"https:\/\/voelkerrechtsblog.org\/de\/wp-json\/wp\/v2\/doi?post=30437"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}