Last week I began a list of things I learned from my recent experience applying to postdoc positions — here is the second half of the list. As I mentioned in the previous post, keep in mind that the process can vary a lot across disciplines, besides the fact that even in the same field different people can have quite different experiences. So this just represents my own experience in biophysics, but I hope it will be useful to someone else! We will start the second half with what I think is one of the most important points…
- Have alternative plans. I once heard a professor claim that people should only do a postdoc if they are “academia or bust,” and it really irritated me. There is no “or bust” in life — even under the best of circumstances, there is always a chance things won’t work out the way you wanted, and we all must have alternative plans for every aspect of life. Do think carefully and realistically about your career goals and whether a postdoc is a good fit, but even if you decide a postdoc is your first choice right now, it should definitely not be your only choice. (Corollary: doing a postdoc because you don’t know what else to do is usually a bad idea.) So spend some serious time contemplating what your next moves will be if the right postdoc doesn’t work out. Even if you end up doing a postdoc anyway, careful planning now may pay off if you arrive at a similar juncture later. But moreover, knowing that you have other options will make your whole application experience much less stressful. You can rest easy knowing that even in the worst-case scenario for your postdoc search (i.e., no offers), you’ll have other options and life will go on.
- But still be persistent. Don’t give up if your first few applications or inquiries go nowhere (of course, having those back-up plans will help to make this less discouraging, too!). Unfortunately, many applications or inquiries to professors receive no response. If you are just contacting individual professors asking if they even have a position available, I think it’s worth sending a follow-up e-mail after about a week if you don’t hear from them. If you’ve formally applied to a group or fellowship program, you may need to wait a few months to hear back, although I think it’s still worth following up at some point if you haven’t heard a response. If someone really isn’t interested in you or just doesn’t have an opening, you deserve to hear them say so.
- Be prepared for your visit/interview. After applying, you may get invited to visit the group or department. Sometimes you’ll give a formal research seminar to the whole group; other times there is private interview with just faculty. The Graduate School-New Brunswick has held workshops on such interviews in the recent past, and they are worth attending. You also usually have a series of meetings with faculty, current postdocs, and possibly grad students. Besides having ready a good spiel about your research and career goals, do your homework on the people you’ll be meeting. Make sure you know what kind of work they do, and plan some things to discuss with them. Of course you may discuss each other’s research in these meetings, but they are also key opportunities to get inside information on what the group is like and whether you’d be happy working there. Don’t discount the meetings with the postdocs and grad students. Besides the fact they can give more honest feedback on the working conditions, their advisor may ask them later what they thought about you, so try to leave a good impression.
- Negotiate. Once you receive a formal job offer, you should go over the terms of the contract carefully and consider what is negotiable. Salary and the length of the contract are obviously important, but also find out about health insurance, access to funds for travel and equipment, if they will help you with relocation expenses, employee privileges (can you use the campus gym?), and any other benefits. My understanding is that salary is usually not very flexible for postdocs (since salaries are often set by grants from the federal funding agencies), but some of these other things, like relocation expenses, are. Talk to your current advisor or other postdocs to find out what’s typically negotiable in your field. It usually doesn’t hurt to ask if you are reasonable about it.
So that’s it. I hope the above points are useful to others out there, but if you disagree with something or have other points to add, please post a comment!
Having recently gone through the postdoc application process along with some of my peers, I thought it might be useful to summarize some of the things I learned. But first one major caveat: the application process varies considerably across disciplines, even across subfields of the same discipline. Just within physics, the process is fairly different for particle physicists versus condensed matter physicists versus biophysicists. (NB: my area is theoretical and computational biophysics.) Thus the universality of any one person’s experiences may be fairly limited, so please bear that in mind with everything I say! So here goes…
- Start early. In some fields there is a well-defined application season (e.g., starting in the fall and concluding in January) and in others applications are accepted all year, but starting early is important in either case: you want to have the longest possible window to find opportunities. In general, I think you should start looking about one year before you intend to graduate and start the new position — so start looking now if you will graduate in the spring of 2015.
- Cast a wide net. As you make a list of groups, fellowship programs, etc. you’re interested in, be as broad as possible. Ask your advisor, other faculty, current postdocs, and other students for suggestions; there may be lots of interesting opportunities out there that you haven’t heard of. You want to have as many options as possible. For one thing, unlike undergrad or grad school applications, there’s usually little cost in applying to a huge number of these things (no fees and many have identical application requirements). But besides that, many of these opportunities are very competitive and also subject to a good deal of luck. Sometimes your dream group just isn’t hiring the year you’re looking for a job, or you just happen to apply when they are changing directions or when a rising superstar applies as well. So your top few choices may become unavailable for lots of reasons, and you want to be prepared for that.
- Apply for competitive fellowships. Besides postdoc positions in individual research groups, many fields have fellowships for postdocs. Some are federally funded (e.g., NSF or NIH), others are funded by private organizations, and others are specific to an institution. The Graduate School-New Brunswick’s GradFund program has lots of resources on these, so check out their website and appointment offerings. Fellowships tend to be extremely competitive, but you should apply for as many as you can anyway (remember the previous point?). Many require the same materials you’d submit for any other postdoc application, so they require little additional effort. Even if you don’t get a fellowship, applying to them can still have benefits. Writing research proposals is an important skill, and the more practice you get, the better. Maybe you’ll at least interview for one or two, providing another chance to meet people and practice interview skills. Or maybe they’ll get your foot in the door for another opportunity. Something like this actually happened to me: I applied for a fellowship that I ultimately didn’t get, but the process got my foot in the door with the group that sponsored my application and enabled me to receive a separate offer from them.
- Write a research statement, but first figure out how it will be used. Most applications ask for a “research statement” without specifying what this should include or how it will be used. Since this may vary across disciplines and types of postdoc positions, I recommend trying to figure out the conventions for your field so you prepare your statement accordingly. For example, one field I know consists of two subfields, and faculty merely use the research statement to determine which of those subfields you’re in. So in this case the details of the statement don’t matter much and therefore aren’t worth a huge amount of your effort. This was generally my experience as well — I doubt anyone read my statement in much detail beyond skimming the general topics I listed. (Note: this is in contrast to a research proposal for a grant or fellowship, which likely WILL be scrutinized carefully!)
- Have a decent CV and website. Besides your research statement, most applications will require a CV. I won’t cover how to make a CV here, but spend some time making it organized and easy-to-read if you haven’t already. I also recommend setting up at least a basic website if possible. I made a personal website early in grad school, but for the most part it hasn’t served much purpose. So I was a little surprised to realize people were looking at it when I applied for postdoc jobs. I’m sure they didn’t peruse it in detail, but they at least saw my picture and probably glanced at my papers, research interests, and teaching activities. This probably doesn’t make a big difference, but it’s another data point to confirm your legitimacy, especially for a professor drowning in dubious applications. So if you already have a website, make sure it’s up-to-date and be aware of what you put on it; if you don’t have a website, consider setting up a basic one. It doesn’t need to be fancy, just a place to post contact information, your CV, maybe a photograph. If you don’t know HTML, web services like WordPress offer easy-to-use templates, and even simple composers like iWeb or Microsoft Word will get the job done. Get it linked somewhere on your department’s or advisor’s page to make it easier to find.
I hope these thoughts are useful to some of you — next week I will post part II. In the meantime, feel free to share your experiences and ideas in the comments!
Dynamic Ecology is a fantastic blog (written by a small group of contributors) on various topics in academic research and careers, especially in evolution and ecology. They just featured a provocative new post advancing the idea of taking a “graduate student sabbatical” — when a grad student spends a long period of time somewhere outside of his/her home institution — to achieve research goals (e.g., forming a new collaboration, facilitating field work) or to accommodate family needs (e.g., a significant other with a job elsewhere). Usually we only think of sabbaticals for faculty members, but grad students often do similar things all the time, even if we typically don’t call them sabbaticals. It’s a fascinating angle, I recommend checking it out!
Conference experiences have been explored a few times on this blog before, but given the apparent diversity of conference formats across disciplines, I think another perspective might be valuable. The topic is particularly on my mind since I recently attended the American Physical Society (the major professional society for physicists) March Meeting, which took place in Denver this year. March Meeting is by no means the only important conference in the physical sciences, but it is probably the biggest — almost 10,000 people, from undergrads to Nobel Prize winners, attend from all around the world.
I’ve been to March Meeting three times now, plus a few smaller conferences. Now that I’m nearing the end of graduate school, it thus seems like a sensible time to reflect on how to make the most of these trips. Optimizing your conference experience is important, since conferences are usually a substantial investment of your time, energy, and money (maybe your advisor’s money, but still…), and they can be key opportunities to advance your career. So here are some thoughts on the matter I’ve acquired over the past few years:
- Don’t try to attend everything. This was probably my biggest mistake at earlier conferences, and I think it’s a common one to make. It’s so easy to have eyes bigger than your brain when you look at the schedule of talks. I would try to attend everything the first day or two, and then I would inevitably burn out and end up missing or sleepwalking through some more important events later on. Try to prioritize the absolute most important things on the schedule before the trip, and make a reasonable plan of how much you can actually do. Be conservative with your judgment. It’s better to sleep late and attend only a few talks that you really pay attention to, rather than to wake up early and attend everything but be so tired that you don’t learn anything. So how should your prioritize events? Well…..
- Meeting people is the most important thing. Specifically, it is more important than any talk. Talks definitely can be useful — they put your finger on the pulse of cutting-edge research and can expand your breadth in unexpected ways — but there are still alternative ways of learning about research. You can always read someone’s papers if you really want to know about their work. But there is no substitute for interacting with people face-to-face at a conference. This is how you form new collaborations and meet people who may someday offer you a job. So when budgeting your time and energy, opportunities to meet people should always come first. Skip the talks and just go to the reception afterward if you have to. Now that I’ve stressed its importance, how do you actually go about meeting people?
- Be a little shameless. It’s hard to summon the courage to ask questions during a talk or introduce yourself to someone new, especially when they are much more senior and your questions and ideas seem naive. But you have to be a little shameless and do it anyway. The particle physicist Tommaso Dorigo has some nice ideas on his blog about how to come up with questions for these occasions. The point is that even if your questions are a bit vacuous, or your attempt to introduce yourself and shake hands with that famous person feels awkward and forced, the mere process of getting practice doing it will be beneficial. By the time your questions and ideas are more substantial, you’ll already feel quite comfortable speaking up. Despite science’s reputation as being the domain of introverts and nerds, in my experience the scientific community rewards assertive, outgoing social behavior, people who are aggressive about seeking knowledge and maybe even a little self-promoting. Being “that person who keeps asking questions” will make you stand out and gain respect as a passionate seeker of knowledge. I played such a role at a few events in the past (ones with small audiences, which made this a lot easier), and several people even told me afterward that they noticed me because of all my questions. Hopefully I wasn’t too annoying, but at least they noticed me! But besides meeting new people from scratch, a much easier route is to…..
- Use your existing connections to make new ones. It’s always easier to meet people through people you already know. So if you already know one or two people at a conference, spend enough time with them to meet some of the other people they know. Getting to know grad students or postdocs at other institutions is a great strategy: as a grad student yourself, it’s usually not too hard to meet and get quality time with other young people (compared to, say, faculty), and once you get to know each other, they should be more than happy to introduce you to their friends at their own institution or other people they happen to know. And you can do the same for them. Finally, once you’ve met some new people…..
- Follow up with the new people that you meet. This can be tricky, but it’s important if you want those new connections to last. I have been able to invite a few people I met at previous events to give seminars for our group here at Rutgers, which obviously helped a good deal in solidifying those relationships. But that’s not always possible. Sometimes it’s reasonable to send a follow up e-mail to someone you just met. For example, you might talk to someone about a paper they wrote, and after you go home and read it, you could easily send them an e-mail with a generic pleasantry (“It was nice to meet you at that conference…”) followed by a question or two about the paper. There’s no need to be sycophantic, but if you are honestly interested in their work, it shouldn’t be hard to come up with a few genuine questions. A short e-mail exchange like this will go a long way in preventing you both from forgetting each other. In the worst case, try to track down your new contacts at the next conference, even if it’s a year or two in the future. They’ll probably be flattered that you remembered them and reached out. If your memory for names and faces isn’t acute, find other ways of keeping track of the people you meet: for example, you can ask for business cards (not common in science, but apparently common in other disciplines) or keep a list of professional contacts.
I’m sure five years from now my views on conference-going will have evolved even further, but the foregoing points have at least served me well as I finish up my Ph.D. and prepare for the next stage. So I hope someone else will find them useful as well. In any case, I’m sure these issues probably vary widely across disciplines (and even within a discipline, too, depending on the conference), so different perspectives are welcome in the comments!
As Kenneth described in a recent post, the Center for Integrated Proteomics Research and the BioMaPS Institute for Quantitative Biology at Rutgers recently held a two-week “boot camp” program to cover a range of basic topics in molecular biology and biophysics. The program was intended to serve the increasingly diverse community of scientists — with backgrounds ranging from physics and chemistry to computer science and mathematics — working in quantitative biology.
As a physics graduate student who works in the BioMaPS Institute, I was definitely in the target demographic. In my undergraduate days I was mainly interested in particle physics and cosmology, so my coursework focused entirely on physics and mathematics. I haven’t taken a biology or chemistry course since high school. While I’ve certainly picked up a great deal of the necessary biology throughout my graduate research in biophysics, I could still use more breadth.
But I was primarily interested in gaining a very specific kind of breadth from the boot camp. Besides having a background in physics, I am also a theorist by training, and I’d never had any experience doing “wet-lab” biology experiments. (In physics, there is a very clear divide between theorists and experimentalists.) But recently I’ve become interested in gaining some experience with wet-lab biology, both because it’s helpful for collaborating with experimentalists and understanding experimental papers, but also because there is a serious possibility I will pursue a combination of theoretical and experimental work next year as a postdoc. Luckily, the boot camp included a week-long experimental lab for complete beginners like me, so it seemed like the perfect opportunity to try it out.
The best thing about having zero experience with something is that you can learn a whole lot really quickly. So even the most basic, mundane aspects of doing the lab were new and exciting for me, things I had heard about in talks or read in papers but never really understood. So this is how you pipette…and “streak a plate”…and purify proteins…and run a gel…and so on. Here’s some photographic evidence (credit to Gail Ferstandig Arnold):
As someone who has worked only on the other side of research until now, it has been really eye-opening to have concrete experience doing experiments and generating data that previously existed only as abstractions in my theorist’s mind. While I recognize that a week’s worth of exposure isn’t enough for me to jump right into doing all my own experiments as a postdoc — undoubtedly I’ll have to relearn all the stuff from last week again later — getting that first experience definitely gives me confidence for the future.
In a previous post, I described my experience at a workshop (organized by the Rutgers Graduate School-New Brunswick) on communicating science. I described the importance of preparing descriptions of your work for a spectrum of likely audiences – having at least some idea of what aspects of your work to emphasize to different audiences and what language or ideas to use are critical. However, in addition to these more customized versions, having a more generic but highly-polished description of your research that you can recite from memory at any time is probably worth having. This is often known as the “elevator speech,” since it’s supposed to be something simple and short enough that you can say it during the time you’d spend with a stranger in an elevator.
I’ve had a murky version of this for a while, but it was largely a vague set of examples and analogies I liked to use when describing my research to a friend or family member rather than a well-crafted summary. But the workshop motivated me to finally develop a better version, so here is my latest attempt:
Every cell in your body contains thousands of different kinds of molecules, stuffed into a very small space and interacting with each other in complex ways. How does this mess of molecules ultimately do all things that cells do, such as making new cells, extracting energy from food, and transporting nutrients? And how did the precise interactions of all these molecules develop over millions of years of evolution? This knowledge is important both for treating human diseases in which these cellular functions go wrong (e.g., runaway cancer cell growth), as well as engineering microorganisms to perform useful jobs, such as synthesizing biofuels with bacteria or making better beer with yeast. My research uses mathematical models and computational techniques to understand how natural selection changes these molecules and their interactions over time. We want to use this both to understand how organisms naturally evolved in the past and to predict how they might evolve in the future.
For those who don’t know, the Rutgers graduate school (through Project AGER) regularly offers a variety of outstanding workshops on professional development for grad students. I recently attended one on science communication. The workshop was run by Sangya Varma, of the Rutgers Professional Science Master’s Program and an alumna of the Alan Alda Center for Communicating Science at Stony Brook University. (In his post-M*A*S*H career, Alan Alda hosted Scientific American Frontiers on PBS for many years and has been a vocal advocate for popularizing science.) The center at Stony Brook offers multiple courses, a master’s program, and various workshops to train scientists to better communicate their work with different audiences. It’s a fascinating and one-of-a-kind place, and I for one would love to take part in some of their activities.
The two-hour workshops at Rutgers provide a small sample of what the center at Stony Brook offers. After highlighting the basic motivation for scientists to cultivate communication skills and some general principles of how to convey complex ideas in simple ways, we embarked on exercises of “translating” our own research into accessible language. We also chose from a list of specific audiences (e.g., a family member, a group of investors, a newspaper reporter, etc.) and spontaneously tried to present our research to that audience.
This last activity really hit home for me, since a few months ago I participated in an interview with members of my group about our research for The Daily Targum. Neither we nor the reporter had much experience with this, and while the resulting article was a nice plug, I was rather dissatisfied with it. We ended up saying very little in the interview about our specific research activities, instead being sidetracked on general issues about the state of the field. I also realized how terrible the spontaneous things we say aloud look when put into print. I learned that one really has to prepare for these things: you have little control over what the reporter will pick to include in the final article from whatever you said in the interview, so you have to give them a very polished set of statements (pretty much at the level of sound bites, which is what they will end up using) that you won’t regret having in print. Speaking off the cuff makes it too easy to say something careless, incoherent, or just plain silly.
This previous experience and the workshop (plus all those times I felt dissatisfied after trying to explain my work to friends and family) have inspired me to take a more deliberate approach in the future for communicating my science. I’m starting with a list of audiences that I may likely interact with, based on my research and career interests:
- Family members and friends
- Basic life scientists outside of my specific subfield (e.g., molecular biologists)
- Physicists outside of my subfield (e.g., condensed matter physicists)
- Biomedical scientists (e.g., cancer biologists)
- Biotechnology scientists and entrepreneurs
- Science news media (e.g., Scientific American)
- Mainstream news media (e.g., NY Times, Rutgers Today)
- Program officers and review panels at funding agencies (e.g., NIH, NSF, private foundations)
My goal is to prepare short descriptions of my work customized for each of these audiences. Most of us have at least partially done this implicitly — say, by writing applications to different funding sources or concocting one spiel about your work for your parents and another spiel for your grad student friends. But I think a more systematic approach is a good future goal. Even a list of important points or key words to emphasize for each audience is probably helpful; for most of us, we will definitely emphasize slightly different points or use different words for distinct audiences. For me, I would likely emphasize the “coolness” and basic science relevance of my work when speaking to my friends or peers in science (especially from physics), while to an audience of biotech people I would definitely emphasize future potential applications.