Blog home »
Applying for NSF CAREER
May 13, 2026
I applied for NSF CAREER in Summer 2024 and I worked with an incredible group of junior faculty from BU Computer Science (Nathan Klein, Sabrina Neuman, Vasia Kalavri, plus a few faculty who eventually decided not to apply that year, including Andrea Lincoln who, with Sabrina Neuman, helped with the infrastructure of the working group). It was my second attempt, as I applied the previous year. All four of us who applied from the working group were successful that year, and I don't think it was independent, so I thought I'd share the information, advice, and working group structure we had.
At a high level, the NSF CAREER Award is a five-year grant that funds one PhD student for five years, funds the PI with one month of summer salary for five years, and is highly prestigious (e.g., meaningful toward tenure cases). Pre-tenure faculty get three attempts to apply, and panels take this into consideration, giving higher weight toward repeat applicants. The application requires a 15-page 5-year research proposal with three thrusts, a 1-page summary of that proposal, a data management plan, references, and supplementary documents: a budget, a budget justification, a mentorship plan, a letter of support from the PI's chair, a biosketch, current and pending support information, a statement of work, synergistic activities, a statement on available facilities to the PI, and (optionally) suggested reviewers.
My understanding is that Sabrina started reaching out to the other CS faculty around May 9 and they had their initial meeting on May 14. I joined a broader department-organized meeting on May 28 where some recent winners and senior faculty shared their advice, and then linked up with the working group from there.
Rough Timeline
- May 14: Working group first meeting
- May 28: First department-related meeting
- May 30: Working group: exchange, read, give feedback on 1st thrust + Project Summary draft
- June 6: Working group: exchange, read, give feedback on 2nd thrust
- June 13: Working group: exchange, read, give feedback on Broader Impacts
- June 20: Working group: exchange, read, give feedback on Education Plan & My Expertise to Carry Out Plan
- June 27: Working group: exchange, read, give feedback on Related Works/Background & Evaluation
- July 4: Working group: exchange, read, give feedback on Intro + Project Summary
- July 10: Sent draft to mentors
- July 15: Mentors give feedback to applicants
- July 15: Budget due internally
- July 22: University internal deadline
- July 24: External NSF deadline
General Advice
These were my notes on the advice that the recent CAREER winners and senior faculty gave at our departmental meeting, and much of it stems from Adam Smith, who regularly ushers junior faculty through this application process at BU:- For your topic, think about what you want to be known for when you're going up for tenure.
- Read examples of recently funded proposals—ask for the reviews along with the proposal. (However, be mindful that if the proposal was very recent, people might be weird about sharing because it's still their ongoing research agenda.)
- Show your proposal to people who can comment on the substance AND have more of an arm's length view (e.g., don't know the jargon, etc.).
- Start early. Get an outline together ASAP.
- Think through at different scales: your next paper, longer term goals, then things get a little more nebulous. Show you know how to get started, plus really ambitious more speculative stuff.
- Think big. Nothing written in the proposal is binding. This is a 5 year proposal (really like a 10 year program) that is the subfield that you're going to build that isn't there yet. It should have the conceptual punch and cohesiveness of a job talk.
- Discuss specific conjectures and research questions. Really crisp clean questions go a long way. If you can connect the proposal to work you've done (especially really recent work), it helps it be more credible and less speculative.
- Remember that energy invested in it is generally well-spent. These problems will keep you going for >5 years.
- If you're trying to interpret feedback from a previous year's submission, the panel review is more important than individual reviews, as it represents what the reviewers agreed upon and used to make their final decision.
- Email the program manager NOW/ASAP (May) with your one-pager to double-check fit.
- You should be describing work that can be done by 1 PhD student, as this is what the proposal will fund. But really, some of these thrusts will be expanded into new proposals.
- Your motivation section should be like a job talk, <1 page.
- Don't use cute names in your proposal. Use descriptive, clear names.
- You may want to include an overview figure.
- Successful proposals are very well structured. One suggestion was to align sections with new pages to show how much effort/structure you put into this. Details follow below under strategies.
- Get your budget done sooner rather than later.
- You can get supporting letters from educational partners.
A Few Strategies I Used
The best strategy was by far having the workshop group, forcing me to complete components at certain times and giving me non-expert feedback. It's really helpful to get early feedback that you're simply not describing things hyped up and groundbreaking enough, and similarly, to give feedback and remind yourself how the panel will see it, because the panel is just you in a few years.For the budget (and most supporting documents), I just got copies from recent successful applicants. The most useful examples were people in my subfield (like algorithmic game theory, which you can find from the award search and just email them), or people in my field (who submitted to AF) at my university. Your university grants admin may also be able to connect you with these people.
I kept a "sanity check" document with the NSF review criteria handy at all times to keep me on track as to how it would be reviewed and to make sure I was addressing these things.
Sign-posting: One comment I got from my first submission was that the reviewers weren't confident that I had an approach for each component of my proposal. In my second submission, I sign-posted "Approach Summary" at the end of every section to make it crystal clear what my approach was, instead of burying it in the rest of the section. I also sign-posted research questions, and other concepts that I repeated throughout.
Planning Lengths for Each Section: I followed Renato Mancuso's advice above (he received CAREER two years earlier) and planned the following space for each section to try to make it as clearly structured as possible.
- Overview: 1.67 pages
- Intellectual Merit: 2/3 page
- Broader Impacts: 2/3 page
- Background: 2 pages
- Thrust 1: 2 pages
- Thrust 2: 3 pages
- Thrust 3: 2 pages
- Educational Plan: 2.5 pages
- Validation, Timeline, Prior NSF Support: 1/2 page (Note that as a theorist, the first two categories make less sense for me, hence less space dedicated to this.)
Given the current climate, I would check in with your program manager or look for recent updates about the CAREER program and changes—e.g., changes in recent years to the educational plan and broader impacts that must be directed at all Americans.
Good luck, and enjoy brainstorming good research!


