Tuesday, 8 September 2015

Return on investment, limited ressources and impossible hedges: the postdoc job search

I submitted my first job application for a faculty position last week. It's the first of around 30 opening I currently have listed. The application package (the American Standard: CV, cover letter, research statement, statement of teaching philosophy), took about a week or two to craft. I looked back over old letters I had written three years ago (for which I had already studied the internet intensely), judged them poor, rewrote them. I solicited, and got very good, feedback from my PI and two other professors in the department who know me. One is an associate professor, mid career, established in his field. The other is a pre-tenure, but very successful, assistant professor. The job itself was a neurophysiology position at a research school with a significant budget. And so all the materials will have to be recrafted for the more teaching focused schools, or the anatomy departments, or the more evolutionary and paleontological positions.
While I am working on these job packets, I am hard at work keeping the analysis and writing momentum we have developed in the group. I submitted my second first author paper from my postdoc for review last week, and next week I will take three days to finally revise and resubmit my third dissertation paper (which has been sitting on my hard drive for a year at this point). We have just finished a run of animal experiments, and there are at least two more first author papers (and several middle authors where I will be called upon for analysis) sketched out that could be ready by january.
My PI came and talked to me a couple of days ago. The R01 I'm on is in its final year, and we have not yet had a renewal. She informed me that my position is funded for certain until January 2017. If she gets refunded, the pressure is off. If not, I think that a few favours can be called in to complete that year, but no guarantees. To all intents and purposes, it is in my best interests to get a job this year, after two years in the postdoc.
Academic job applications are laborious, more so than private sector ones. More information is requested, the process is more drawn out, a greater research investment is expected at every stage of the process. And yet all that work is ancillary. Or, more specifically, it is icing. Grant, publications, research: those are the hard substrate you need for the crafting of the job documents to be even worth the effort. All these things take time, huge amounts of time. As a graduate student, or a postdoc, especially in a one grant lab like mine, time can suddenly become an exceptionally rare commodity. Like at the end of graduate school, I am on a timer if I don't want to face a serious gap in income. I have to maximize the ROI on the time I have. And knowing where to maximize that ROI is... non trivial. Obviously, more papers is better. But at this point, most papers I submit now will not be in press by the time applications close on most of the jobs I have lined up. Is a big list of in reviews worth it? How much is it worth relative to getting half a dozen more jobs applications out? After all, publication from the lab will help my PI's grant efforts, which also are of concern to me at this point.
I was in a similar bind at the end of grad school: I had no publications, my dissertation was unfinished, and I had no job lined up, a year away from cessation of funding and the end of my F1 visa. How to maximise my time? In the end, I wasted a few months on job applications: I got the very firm message that an ABD grad student with no pubs was not a hirable commodity. So I finished the dissertation, and headed back to the UK to live with my mother. I spent a year unemployed, applying for jobs and getting my first two papers out. It was not ideal, and owing to life circumstances not a scenario I can afford to repeat.
Which brings me to my next point in this rambling post. I have to prepare for the eventuality that I won't get a faculty position. With the current data on postdoc placement rates, all graduate students and postdocs need to hedge against not making it in academia. Yet what constitutes a good hedge? From my experience outside academia (which was before the recession), I know that field moves without experience are difficult. Again, you need to invest either capital (ie a nest egg to tide you over, difficult on a postdoc salary) or time to build useful contacts and experience. Time, which as I have mentioned, is a limited commodity when on a fixed term appointment.
I maintain that the challenges faced by people like me are not unique in kind to academia. Fixed term gigs, low starting salaries, competition for permanent positions, the open ended nature of projects that can expand to fill all available time, the constant need to re-invent yourself,  even the need to be highly mobile, can be found in so many other industries where young graduates now end up (law, medicine, consulting, finance, tech, game development). But the degree, and specific combinations of these factors, combined with an idiosyncratic job application process that is mostly useless for getting jobs outside of academia, do present unique challenges that can hamstring young people in academic science trying to keep their lives together. And the combination of lack of capital and lack of time means that efficiently hedging for the high likelihood of having to operate a career move is a unique challenge. On this, young academics are in need of mentoring.

Tuesday, 18 August 2015

Why I read the introduction and discussion of papers

Over the past year, I've heard several times the sentiment that introductions and discussions of papers are not worth the .pdf memory they take up. Most recently, it took the form of the following cartoon passed around twitter.

Embedded image permalink
Cartoon by Anthony Crocco
But I've had this discussion in person too, with assistant professors in our department. And I just don't get it. To me, a paper without the introduction and the discussion is almost literally nonsensical.
The intro, discussion, and conclusion have value because I don't view them as opinion, but as argument. The introduction should set up WHY the problem is interesting to the field, and why the approach chosen is relevant. This isn't just set up. It tells me a number of useful things: whether the person knows what they are doing with regard to the broader intellectual climate they are working in for one, but also, their thoughts on why the problem is important may not be my own. Their thinking, as detailed in the introduction, may modify, interrogate, change my own. And their thoughts about why the work is worth doing will guide 1) how they did it, and 2) what they intended to get out of it (which is important, because that set up will color how they present BOTH the methods and the results).
What is written in a paper is never just a simple narrative of the work done and the results obtained. That is a stylistic conceit. So knowing the set up is essential for critically assessing the "objective" parts (which are not so objective).
But it is the dismissal of the discussion that makes me saddest. The implication that the discussion can be discarded means that what the authors think of their results is irrelevant. There may be fields (particle physics perhaps) where the results are entirely unambiguous. I have yet to encounter a biological problem in which that is the case. Moreover, the non linear hierarchical interaction of biological systems (from molecules to cells to organs to organisms to behavior to ecology to evolution) mean that from an integrated biology perspective, I want to know about potential implications of the resultsfor connected elements of the biological hierarchy of organization. Again, a well crafted discussion is an argument, and a source of ways forward, not the spewing of opinion.
But perhaps what makes me saddest about the sentiment expressed in that cartoon is the solipsistic vision of science it produces. A focus on methods and results discounts the intellectual work, the scholarship done by your peers. It views others' work solely in light of how it might relate to one's own, and assumes that modes of thought about scientific problems are already so fixed, that nothing new will ever be found under the sun. This is not my experience of science.
In my field (evolutionary biology), one of the most important events that ever occurred was the Modern Synthesis. Over the course of ten to fifteen years, a disparate group of biologists came together to generate the modern understanding of evolution by natural selection, rooted in population genetics. The modern synthesis involved no ground breaking discoveries, and happened before we even properly understood the molecular mechanisms of heredity. The modern synthesis was the result of years of discussion and argument, culminating in, not a series of papers detailing new methods and new techniques, but in a series of books detailing a new way of thinking about biology. Crucially, it involved biologists from other fields understanding each other's work, despite being unfamiliar with each other's methods. If Mayr, Simpson, Dobzhansky, Huxley, and Stebbins had only engaged with their colleagues work through the schema of that cartoon, the modern synthesis would have been impossible.


Wednesday, 5 August 2015

Growth

I am currently writing a manuscript. It's the second first author manuscript to come from my postdoctoral work (a little under two years in), and hopefully it will be sent out for review in the next couple of weeks. Currently, my PI and I are sending it back and forth, querying the writing, clarifying the main points, realising (for me at least) some pretty large gaps in my knowledge of the litterature. But, at no point since I wrote the first draft have either my PI or I thought anything other than "this is a good manuscript, we just need to make it even better".
This is in many ways the paper I came here to write. It's the paper that shows that I understand how to do biological kinematics, that is how to study the movement of biological structures as organisms use them. As I've mentioned elsewhere, my background (which now seems quite far off) is in ecomorphology as applied to the fossil record. I correlated variation in mammalian bone morphology with known variation in broad categorical behavioral and ecological variables. But these broad classifications don't tell you about function, and so about the behavioral phenotype on which selection is acting. So I took this postdoc in part to learn how to ask those questions.
And here I am, writing a paper that does just that, yet also so much more than I had anticipated. The study we did was an experimental manipulation to see how a nerve lesion affected the movement of the tongue and oro-pharynx in our animal model. The work replicates a relatively frequent iatrogenic injury in premature human infants, and so it is clinically relevant. But the direction we have taken with this paper is so much more than that. We're using the changes we observe to make inference about the neurological control of these oro pharyngeal structures. My head has, for the past few weeks, been full of discussion of central pattern generators, afferent and efferent pathways.
With this paper, I feel like I have grown immensely as a scientist. I have become the integrative biologist I've always wanted to be. I'm not doing it in this paper yet, but I feel ready to connect my paleontological work and knowledge of mammalian evolution with my understanding of experimental organismal physiology.
I have an idea of the direction I want to head in as a paleontologist, as a evolutionary biologist, as a mammalian physiologist. And it's so much more than I thought it would be when I started this project hoping to learn about kinematics.
I'm heading out onto the job market this year. And my research statement will be nothing like the one I wrote three years ago when I was finishing my PhD. I think it will be so much more interesting. And I hope others will too.

Monday, 27 July 2015

Familiar and Strange

I spent this weekend camping in the mountains of Virginia, near Goshen pass. It had been too long since I'd been in mountains. I saw the Milky Way one night (something which, having grown up in a city with some of the worst light pollution on the planet, still blows my mind). We swam in rivers, and hiked up to overlooks. The scenery was spectacular, and deeply rejuvenating. We stayed in the local recreational area, and camped by a river. The nearest town was twenty minutes drive away. The nearest grocery store nearly an hour. We chopped wood and built fire, bathed in the river (using biodegradable soap). And wherever we looked when in the mountains, we saw only wilderness as far as the eye could see. An endless thick forest rolling out over the valleys and mountains.
The mountains of Virginia


Although I grew up in a big city, I spent most of my holidays around mountains: the Vosges of Alsace, the Pennines of the Lake District, the Jura around Lake Geneva, the Alps of Tessino and Aosta. I've spent countless hours running through steep mountain side meadows, and hiking winding paths to spectacular overlooks, with views stretching out for hundreds of miles.
A few years ago, I was able to take my now husband to the small village in Alsace where I spent part of almost every summer holiday. My great grandmother lived there, and four generations of my mother's family has been there now. The Vosges mountains are old mountains, reaching their maximum height at about 1000m. Yet, because of the Ice Age, the valleys are glacial: flat bottomed and steep sided. This is hiking country, and has been in a semi organised fashion for over a hundred years. And so the paths that run from the village to the mountaintops are well known to me.
I took my husband on a mammoth 9 hour hike along these paths that four generations of my family have walked along. Paths that my aunt and cousins and siblings and mother know well. As we climbed up the steep walls of the valley, we passed from the forests to the high meadows, to this day still used as grazing pasture for the cattle that make the cheese for which the valley is famous. In those pastures, farms provide, as they have done for a century, rustic lunches for the hikers. Because this is France, these rustic lunches are delicious, fresh, and come with wine.  Because this is Alsace, the wine is white, and the lunches are enormous. But they go a long way towards making 9 hour hikes bearable.
When you stand on the top of the Hohneck, the highest point of the hike, you look out over similar geology to what you see in the Appalachians: rolling hills, deep valleys. But the geography is totally different.
The view from the Hohneck
Here the land is patchwork. There are forests yes, but they are cut up by pastures, and the valley floor is cleared of trees, and dotted with villages. And all around the mountainsides, small farms, or old shepard's huts, or the odd old country house, are visible. Even after walking up nearly 500m, the land is still human.
Even in the most remote of Alpine valleys in Switzerland or Austria, one will see these marks of humans on the land. What is more, the landscape of Alsace is in some ways more ancient than that of Virginia: much of the Appalachians was once clear logged for wood and farmland. That is why Appalachian forests do not have millenial oaks like European ones do. But with the westward expansion, men moved on, and the forest grew back. In my overcrowded, ancient continent, people stayed.
The Appalachians, and the Vosges, are both rejuvenating to me. But when I stand on those mountaintops and gaze out at the landscape before me, on is familiar, and one is still a reminder that I am not at home. After seven years, even in those places I like most, I am still a stranger here. And, like all expats, I wonder that if I cease to be a stranger here, then that place where generations of my family have walked will cease to be home.
If I have children, will I show them the path up from their great great grandmother's house, through the valley their grandmother, uncles, aunts, father, and cousins played in, up to the mountaintop that looks over a landscape that their family has lived in for over a century? Or will I show them the endless rolling woods that their father discovered with their other father, that have almost no mark of man on them?

Wednesday, 15 July 2015

An apology, and understanding

I was an ass on twitter last night. PIs and postdocs were shouting about the overtime threshold change, and I jumped in, riled up and angry and not paying enough attention to what was being said, so sure I was of what I was saying. I apologize.
I was made to realize (by someone with great patience) that much of the PI ambivalence to this announcement boils down to it adding yet another financial burden on labs whose margin of operation is already so thin as to be invisible. And so, once again, all our great science problems come back to the question of funding.
PI are, everywhere, trying to square an impossible circle, that keeps getting more complicated. And as much as we may think we understand, we postdocs are not squaring that circle. That burden is the PIs.
I still think this rule change is a rare victory for American workers' rights, after decades of seeing them eroded. I still think that the segue through the discussion of a postdoc's worth this weekend was unecessary, beside the point, and vicious. I still think that in the aggregate, this reform will be for the best. The key word there is aggregate.
But I am also reminded that any new law put forward without adequate funding may quickly become little more than window dressing. And that when it comes to its impact on workers paid by the public dollar, that may be what this law becomes.
In the immediate term, if the reform goes through as intended, I suspect HR memos will be sent, and PIs will watch their postdocs comings and goings a little closer. Maybe fewer marathon experiments will be scheduled back to back. Maybe fewer hours will be worked. Maybe this will actually be good for the long hours culture in academia (though I hear the overtime exempt PIs laugh darkly at this).
But what this ugky episode reminds us most, is that no matter how you cut, no matter what you reform, there isn't enough money for all the people in science right now. And until that's addressed, all reforms like these will have similar responses I fear.

Wednesday, 8 July 2015

This isn't about you

I've been trying of late not to blog based on twitter interactions so much, because I think I talk enough on twitter that I don't need to repeat myself on here. But the past few days discussion about the overtime directive has me feeling the need to expand on my thoughts slightly.
To recap, the Obama administration is directing the department of labor to raise the threshold for overtime exemption from $23,660 dollars a year to $50,000 dollars a year, on the basis that that threshold no longer reflects the intent of the law as was written.
Justin Kiggins over at the Spectroscope blogged about whether this would apply to postdocs, who are currently paid $42,000 and $56,000 on the NRSA pay scale set by NIH (I believe that the level are slightly less for NSF postdocs, but I have been unable to find clear figures). Thus, postdocs with less than 4 years postdoctoral experience may be concerned by this change (after 4 years NRSA pay scale reaches the new threshold). This was a reasonable point to make. And then all hell broke loose on twitter.
Initially, most postdocs were incredulous that such a thing as "overtime" could even apply to them. Even today, scientists on twitter are arguing that scientists are overtime exempt, pointing to the very directive that is subject to change. Others argued that fellows are already exempt from many of these labor laws. Which is true, but many postdocs are not fellows in a employment sense: if you are paid our of a PI grant such as a R01 and receive a W-2 with witholdings, you are, to all intents and purposes, an employee of the institutions at which you work (this is also why you are illegible for employee benefits, 403bs and such). Most postdocs were convinced that universities and NIH would do everything they could to find ways around this. Which is probably true, that is how labor reform goes. More disturbing to me was how many were convinced that it shouldn't apply to them. Arguments raged that our work could not be quantified (yes it can), that what we did didn't count as work anyway (yes it does), that we didin't fill time cards (indeed, because the current law does not require it). Anything but the status quo seemed unimaginable, and the very idea that may be a limitation of working hours inconceivable.
The response to the possibility that labor laws might apply here
And then the PIs got involved, and it turned into a standard discussion of what postdocs are owed, what they worth, how we are entitled. We were called "giddy", despite having greeted this entire discussion with (in my view) excessive skepticism. We were warned darkly about what this might do to our employment prospects (by the very people who ordinarily would say that lowering the number of postdocs would be a good thing).
And here is where I lost it.
Because this reform is not about postdocs. As Kiggins pointed out, postdocs represent less than 1% of the people who may be affected. This reform is about bar, restaurant and store managers on $24,000 how work 60 hr weeks. This reform is about how nearly 9/10th of US earners are exempted under current legislation (back of an envelope calculations from here). This is about how, as the reaction of US postdoc shows, no one in this country actually believes in labor law anymore. No one believes that they can be protected from overwork, that pay should be proportional to hours worked as well as talent. No one even believes in the benefits their employer gives them. I have yet to meet a single person at my workplace who takes our (generous) 20 day vacation allowance. And trust me, it's not just because they love their work. I've spent enough time with Americans to know how they are socialized to view vacation as a professional liability.
And yes, laws like this have complex and difficult ramifications for small and medium enterprises. If PIs think finding an extra 6 grand for a postdoc will be hard, think of the restaurant manager trying to calculate whether or not to hire a second manager at 24K, pay the existing manager overtime, or bump her salary to the new threshold.
But when we argue about whether we should be exempt, we are not just doing ourselves a disfavour. We're making an argument that will be used by every boss in every sector against people paid far less and with worse career prospects. 
So, PIs, postdocs: this rule is not about you. It is about fair labor compensation for all workers in the US, of which you happen to be a part. A little less onanistic navel gazing would suit you well at this point.
In 2000, France passed a law mandating a 35h working week for all salaried workers, with further limits on annual amounts of overtime worked. It was cumbersome and stupid, difficult to implement and the subject of much ridicule. But I would much rather come from that tradition then one that is so willing to believe its only right is to work more for less. 
(As an aside, the current salary cap is low enough that most lab techs are also overtime exempt. Have you asked your tech how many hours she works lately?)


Wednesday, 17 June 2015

The value of capable

Today was a tough day in the lab. Supertech and I are flying solo (PI is away), and we are running two weeks of experiments using a rather expensive, and rather delicate, piece of custom built equipment. The experiments are supposed to be straightforward. As today showed, "supposed" is the operative word here.
It should be noted that supertech and I (well, mostly supertech. I just help) are pretty anal about planning experiments. We put a lot of thought into how the experiments are going to run, and we test as much as we can beforehand. The reason for this is that once experiments start, there is no time to think. Baby animals are screaming to be fed, multiple multi hour surgeries need to be done, and we need to make sure that people don't get irradiated by the high powered fluoroscopes (there are two). The simple act of getting through experiments drains brains and nerves.
But even with the best laid plans, things go wrong. Not everything can be anticipated. Which lead to today, when our expensive piece of machinery (basically, a series of precise electronically controlled pumps) stopped working. With four screaming hungry pigs in the room.
As in turned out, a crucial piece of information had been left out when discussing the design of the system (before I or Supertech joined the lab). Why? Who knows. The same reason that, with hindsight, really obvious things are missed from experimental planning. Essentially, the pumps got fouled up by the radio opaque particulates in the liquid we pump. Two weeks of experiments and four animals were at stake.
Supertech and I then went into super capable mode. We troubleshooted the system every way we knew. I called the manufacturer, and confirmed what the issue was. We found a way to clean the pumps, and then started to work on solving the problem that our fluid had particles that were too large. Within an hour we had three possible solutions. Within two hours we had started to put in place all three. By seven pm this evening, Supertech and her husband had built a high volume filtering system that would remove the large particles from our suspension (we'd already by this point checked that this kept the solution radio opaque). Tomorrow experiments will resume, and we will only be one day behind.
As a lab team, supertech and I are capable. We can deal on the fly with most crises. When something goes wrong, within half an hour we have a plan, within a hour we're putting it in place. We brainstorm, prioritize, call people and get things fixed. She's better than I am, but I pull my weight. I don't think we've lost much more than a week on any experimental schedule, and that was due to unforeseen animal death. We have stayed overnight in the lab to care for sickly animals. We've harassed suppliers to get things overnighted. We've become conversant in technical topics we knew nothing about. We get things done.
For the science, this is great. For the animals, this is essential. But for us... I worry. I worry that capability, the ability to creatively solve problems on the fly, and to put in the effort to do it, doesn't always reap the rewards equivalent to its cost in hours and stress. I don't mean to impugn our PI. She treats us exceptionally well, recognizes our efforts, and has rewarded us with substantial autonomy and authority on the running of the lab. I mean rather, that the labor market since Taylor and Ford has been structured so as not to rely on the capable worker. To a manufacturer, the added value of a capable line worker is marginal compared to a merely adequate one. And in science, techs and postdocs (and graduate students) are somewhat like manufacturing labor. Yes, a good postdoc adds value to the lab, but how much value relative to a merely adequate one?
Many of my smart, capable friends in other jobs hide their capability, revealing it only to those they trust not to exploit it. Capable people need to learn to say no, because they get asked to do more than most, and all of the difficult, non rote tasks. And problem solving is tiring work.
I like being capable. I like not being helpless in the face of problems. But I worry that capability is a liability, because it becomes assumed, and because its value to the beneficiaries is less than its cost to those who do the capable work.