I joined an NIH lab in August 2025 after working as a software engineer in e-commerce. I had learned a lot from building software, but I kept thinking about the biological questions I had explored during earlier research experiences in radiation biology and proteomics. I wanted to return to work where understanding a scientific problem was the goal, and I was beginning to see a PhD as the next step.
The question was how to get there. I had a computer science background, industry experience, and some research behind me. I needed a place where I could bring those experiences together and develop further as a scientist.
An NIH postbac position became that bridge. Here is how I found my lab, what I wrote in my first email, and what helped my prospective mentor and me recognize a good fit.
Finding a lab amid uncertain timing
By July 2025, I was connecting with the PI whose lab I would join the following month. It felt late in the process, especially after the uncertainty surrounding the program being put on hold. I was fortunate that the timing worked out, and I would not treat my experience as a schedule for someone else to follow.
There are also two parts to keep track of: the formal application and finding a research group. NIH requires a completed application for acceptance into the postbac program; contacting a principal investigator (PI) does not replace it. Check the current NIH postbac instructions before applying.
How I found NIH research labs to contact
My search started with something familiar: proteomics. I looked for NIH principal investigators working in that area because it connected to my previous research experience. I had also worked well with female mentors, so I included that preference in my search. Those earlier mentoring relationships had shaped what I hoped to find in my next lab.
That search led me to my current PI. Her work on fold-switching proteins caught my attention, particularly the possibility of using computational methods to understand changes in protein structure. It gave me a specific connection to explore: how could my programming and research experience contribute to the questions her lab was asking?
For readers starting their own search, NIH's guide to finding a research group is a useful starting point. Keep a shortlist of labs, a few relevant papers, and a sentence explaining why each group interests you. That sentence becomes much easier to write when you have spent time with the lab's work.
The cold email I sent to an NIH PI
My subject line was “NIH Postbac Inquiry – Interest in Protein Folding and Structural Bioinformatics.”
In the email, I introduced my computer science background and software engineering work, explained my interest in the lab's research, and described relevant experience at NASA and Genentech. Two excerpts capture the research connection and the request:
I came across your lab while exploring NIH Postbac opportunities, and I was intrigued by your research on fold-switching proteins.
I was curious if you were taking any postbac students this year?
I wanted her to understand why I was reaching out, what experience I could bring, and what I was asking. The full screenshots and adaptable templates are in my cold email guide for professors, internships, and mentorship.
She replied in two minutes. I was shocked. We arranged a call for the next business day, and suddenly an email had turned into a real conversation about joining a lab.
That response time was a fortunate part of my experience, not an expectation I would set for other applicants. The useful lesson was having a specific reason to contact her and making the question easy to answer.
What we discussed in the NIH postbac interview
I was upfront about my goals: I wanted to pursue a PhD and build a stronger research record, including publications. I wanted my next role to help me develop the experience to take that step.
My prospective PI had a concrete need of her own. The lab needed someone with stronger software engineering skills to improve its code repositories. That was work I could contribute to with the experience I already had.
We clicked because those needs lined up. I was looking for an opportunity to grow as a researcher, and she was looking for engineering skills that could support the lab's research. My time in software had given me something useful to bring to that conversation.
For anyone making a similar transition, think about both sides of the match before an interview: what you hope to learn and what you can already contribute. Being specific about both gives a prospective mentor more to work with than a general statement of enthusiasm.
How to decide whether a lab is a good fit
The research topic is only part of the decision. You will also spend a great deal of time learning from the people around you, so it helps to understand how the lab works day to day.
My advice is to ask directly about a mentor's approach. Do they prefer to give detailed guidance or let trainees work independently? How often do they meet individually with trainees? How often does the whole lab meet? The answers can help you picture what support and independence would look like in practice.
These are questions I would suggest asking, rather than a transcript of my own interview:
- Who would supervise my day-to-day work?
- What could a first project look like, and what training would be available?
- How often would we meet to discuss progress or problems?
- Could I speak with a current or former trainee about their experience?
- How does the lab support preparation for graduate school or the next career step?
For a view of my work after joining, read a day in my life as a computational biologist at NIH.
What I would do differently
If I were starting again, I would spend more time exploring lab pages and reach out directly to more PIs whose work interested me. I was lucky with the timing of my application and with finding a lab that needed my particular skills. A broader, thoughtful search would have given me more opportunities to find that kind of match.
I would also put more effort into understanding each lab before writing. Reading about its projects helps you explain your interest, but it also helps you decide whether you want to do the work. Both matter.
The most useful connection in my own search was between a question I wanted to study and a skill the lab needed. Once we could see that connection, the conversation about working together became much more concrete.
NIH postbac application questions
Do I need to apply before I can be accepted?
Yes. NIH states that you cannot be accepted without completing the online application. Use its official application guidance for current requirements.
What should I include in an email to a PI?
Introduce your background, explain your interest in a specific part of the lab's research, and ask a clear question about opportunities. My research cold email templates provide a starting structure to customize.
Can a computer science background connect to NIH research?
It did in my case. I brought computer science and software experience alongside previous biological research projects, and my lab had a need for those skills. The fit will depend on the research group and the position, so check the program requirements and consider how your experience connects to the work a lab is doing.