Before I started my postdoc, I thought I knew what to expect-the long hours in the lab, the gradual build of data, the repeated cycle of hypothesizing, failing, and adjusting — a process I had run enough times that it no longer felt like conscious effort. I imagined more autonomy and the quiet confidence that comes from finally being treated as a peer rather than a student in training. A PhD had given me years of hands-on research: designing experiments, troubleshooting failures, slowly learning to read a dataset the way you learn to read people. By the end, the process felt familiar. I watched enough senior researchers at work to form a picture of what the next stage would look like: more of the same, but with greater freedom and sharper questions. I expected to feel, if anything, more capable.
However, the first few months of the postdoc quietly dismantled that picture, and with it, something subtler; the internal sense of competence I had not realized I was leaning on. It was not a dramatic unraveling. There was no single moment of crisis, no obvious failure I could point to. It was more like returning to a room you know well and finding the furniture slightly rearranged, nothing missing, nothing broken, but your instincts no longer quite reliable. The confidence I had carried out of my PhD, which had felt earned and solid, began to feel more like familiarity with a particular set of conditions that no longer existed. The experiments were not so different, but something in the environment had shifted; what that shift entailed was difficult to pinpoint. During a PhD, there are benchmarks, committee meetings, thesis chapters, and a supervisor who monitors my progress. Those structures, which I had sometimes resented, turned out to be the scaffold that held things together. Without this scaffold in place during my postdoc training, I found myself in a more open landscape than I had anticipated. No one told me which experiment to run next. I was expected to manage my time independently. The direction of my research, largely, was mine to drive forward. It was liberating in theory but disorienting in practice.
The Lessons No One Prepares You For
A few months in, I brought a set of results to my PI that I thought were finally starting to hold together. The data pointed in a direction, but the pattern refused to resolve. One replicate would support the conclusion, the next would deviate, and no amount of optimizing the experimental conditions seemed to resolve the gap between them. I repeated the experiment, optimizing conditions, expecting the signal to sharpen. My PI looked at the figures for a moment, then said something I wasn’t prepared for: “Maybe this is the result”. Not a failure. Not an unfinished experiment. Just an answer that looked messier than I wanted it to be. It wasn't the first time I had encountered complicated data, but it was the first time someone had asked me to stop treating the mess as a problem to fix and start treating it as information. That conversation changed my perspective on how I viewed ambiguity in my data. I treated it as a problem to solve rather than using it as a guide for future troubleshooting. Research, my PI told me, does not usually provide clear-cut answers. There is almost always something unresolved, slightly out of reach. What matters is knowing what to do with that.
That shift in perspective changed how I approached troubleshooting from then on. Before, I would work through problems systematically, expecting that enough rigor would eventually produce a clean outcome. Now, I pay close attention to the small things I had previously dismissed: timing, handling, and minor variations between experiments that seemed negligible, but sometimes were not. I started documenting not just what worked and what did not, but patterns, inconsistencies, and hunches I could not yet explain. The work became less like solving a puzzle with a known solution, and more like learning to read a landscape that kept changing.
One of the hardest and unexpected lessons I had to learn was knowing when to stop. Based on instinct, I pursued a particular line of inquiry for several months, but found that the resolution was out of reach. The experiment, for its part, was stubborn. It gave me just enough encouragement to stay interested, but never enough to feel conclusive. Looking back, I think I was chasing the instinct more than I was reading the data. I kept adjusting, retrying, convinced that one more iteration would break the deadlock. I mentioned this casually to a more senior postdoc in the lab (not really asking for advice, just thinking out loud). He listened, then said quietly, “At some point, the experiment reveals what it’s going to tell you”. It was a small comment, but it reoriented something in me. Not every direction is worth continuing indefinitely. Knowing when to step back is a skill that no one “named” for me before. It protects your time and your clarity, even when letting go feels uncomfortable in the moment.
What surprised me most was how much self-imposed pressure I was carrying. I felt this way because there were external timelines and grant milestones that I was trying to meet. Beneath that pressure was a quiet, yet poignant, expectation — that by this stage, I should carry the load confidently and competently. I also felt that confidence and independence should already be ingrained in me from my graduate training. I found myself feeling like a beginner all over again, trying to cope with learning new techniques, unfamiliar literature in a new field, and navigating scientific concepts that wouldn’t click. I felt like this was a sign that appeared to reflect a deficit in my abilities rather than being a normal condition of the work. It took time to understand that moving towards independence does not mean having all the answers. Instead, it means getting better at moving forward without them.
Some of the most useful re-calibrations of my perspective came from conversations with colleagues rather than performing experiments. Examples included a brief exchange at a conference, an offhand remark from a colleague over coffee, or a question raised during a lab meeting that reframed a problem I focused on too closely. Mentorship and scientific exchange shape careers in ways that rarely appear on a CV. I underestimated how much I would learn simply from being around people who were more experienced, by observing how they thought and by listening to what they said.
My communication skills, too, changed in ways that I had not anticipated. I realized that communicating science is not primarily about presenting results clearly. It is also about making sense of them out loud, packaged in an exciting story, even when the work is still in progress. Data rarely speak for themselves. They require interpretation, framing, and an ability to sit with what remains unclear. I had to learn how to articulate both what I found and what I could not yet explain, without losing confidence in either.
What stays with you
The skills that shaped me the most during this postdoc do not appear in methods sections or figure legends. They are not the kind that produce an immediate output you can point to. I became more comfortable making decisions while the story of the research was still evolving, troubleshooting without the expectation of clean answers, and knowing when to hold a line of inquiry and when to release it. Managing expectations, internal ones especially, while staying in motion turned out to be one of the most demanding and least discussed parts of the work. I built these capacities slowly, through experience and through the people around me, often without realizing they were forming at all.
Once you begin to recognize them for what they are, the experience shifts. Progress becomes less about measuring yourself against some internal standard and more about noticing the quieter changes taking place along the way. A postdoc is not only about generating data or publishing work. It is also about learning how to think, adapt, and keep moving when clarity is slow to arrive. These skills do not announce themselves as they form. But they stay with you long after the experiments end.
Vartika Sharma is a postdoctoral researcher at the University of California, Los Angeles (UCLA) studying how intestinal barrier dysfunction, cellular stress, and molecular pathways contribute to brain aging. She is passionate about science communication and sharing the experiences that shape the journey of early-career researchers. Connect with Vartika on LinkedIn.
Image by Arek Socha from Pixabay
