Research Scientist: an academic career launch pad
After a long start to 2020 including the past four very busy weeks, I’m happy to announce that today March 16th 2020 I accepted a position as Research Scientist at the Lieber Institute for Brain Development in Baltimore, MD, USA.
What will I do as a Research Scientist at LIBD?
At LIBD we currently have the following scientific ranks:
- Research Technician
- Research Assistant
- Research Associate
- Staff Scientist I, II and III
- Research Scientist (+ Lead and Senior)
- Investigator (+ Lead and Senior)
Research Scientists carry out research, do so scholarly, are tasked with being creative, are encouraged to seek funding, and can have supervisory and mentor roles.
In my agreement with LIBD, I will remain affiliated with the Data Science Team I led by Andrew E Jaffe while also having the opportunity to interact with and collaborate with fantastic biologists, data scientists, and researchers at LIBD, Johns Hopkins University, and beyond. Furthermore, I will officially help mentor LIBD scientists in data science and R tools. LIBD will support me while I build a small team around my research interests and prepare my first set of grant submissions. There will be a transition period and many things I need to learn: from requesting a budget to writing a job ad, as well as many details about grant requests. But ultimately, LIBD offered me a launch pad for an academic career.
One of my first tasks will be to refine the details of my role. For example, right now on the teaching side of things I’m imagining doing the following:
- Lead a weekly LIBD rstats club meeting where I can go over topics common to several users.
- Hold one-on-one data science guidance sessions, similar to the MPH capstone sessions I did during my teaching assistant years at JHBSPH.
- Occasionally lead internal workshops, which could benefit from workshops I prepare for CDSB and elsewhere.
- Get certified by RStudio and attend more R conferences & workshops.
From the scientific side, I will also learn more about the biological questions my LIBD colleagues are working on. These hypothesis-driven projects will provide me a new set of challenges and I will perform what me and my LCG-UNAM classmates were trained to do: to function as a bridge between multiple fields. I will also keep learning from my JHU colleagues and working with them as I refine my ideas. Currently, this is how I have framed my research interests:
My research aims to better understand the roots and signatures of disease (particularly psychiatric disorders) by zooming in across dimensions of gene activity: from studying gene expression at all feature levels (genes to exons to exon-exon junctions and un-annotated regions of expression), to using different gene expression measurement technologies (bulk RNA-seq, single cell/nuclei RNA-seq to spatial transcriptomics) that provide finer biological resolution and localization of gene expression. I’m interested in both hypothesis-driven projects as well as building general resources such as recount2 that enable us to contextualize our findings across all of the public human gene expression landscape. I use the R programming language for nearly all my work and like to organize my code in R packages that I share mostly through the Bioconductor project.
As for building my team, I know that overall one of the challenges everyone faces is recruiting talent. I’ll give this complicated process a shot by tapping into my network which includes many immigrants. I will also expand my network online and through conferences. Furthermore, I am committed to my outreach projects such as CDSB but will synergize them even more: re-use training materials, potentially recruit team members, and help me expand my network. In the meantime, if you are interested in working with me or my colleagues, please let me know!
The decision I had to make was challenging, but in the end, I decided to stay at LIBD because they offered me a path to become a principal investigator in academia which it’s something I want to explore and see where it leads me. I will also formally be someone’s boss and gain managerial experience, work much closer with biologists in hypothesis-driven projects, and overall gain more experience and skills. My brother’s job tasks changed last week, to which I told him: “welcome to the real world”. Well, I guess that’s how it’ll be for me too.
I want to thank everyone that helped me through this decision-making process, provided me with information, asked me questions, answered questions, expanded my universe, advocated for me, advised me, cheered for me, and supported me. Thank you! I look forward to working with you!
This blog post was made possible thanks to:
- BiocStyle (Oleś, 2023)
- blogdown (Xie, Hill, and Thomas, 2017)
- knitcitations (Boettiger, 2021)
- sessioninfo (Wickham, Chang, Flight, Müller et al., 2021)
 A. Oleś. BiocStyle: Standard styles for vignettes and other Bioconductor documents. R package version 2.28.0. 2023. DOI: 10.18129/B9.bioc.BiocStyle. URL: https://bioconductor.org/packages/BiocStyle.
## ─ Session info ─────────────────────────────────────────────────────────────────────────────────────────────────────── ## setting value ## version R version 4.3.1 (2023-06-16) ## os macOS Ventura 13.4 ## system aarch64, darwin20 ## ui X11 ## language (EN) ## collate en_US.UTF-8 ## ctype en_US.UTF-8 ## tz America/New_York ## date 2023-07-11 ## pandoc 3.1.5 @ /opt/homebrew/bin/ (via rmarkdown) ## ## ─ Packages ─────────────────────────────────────────────────────────────────────────────────────────────────────────── ## package * version date (UTC) lib source ## backports 1.4.1 2021-12-13  CRAN (R 4.3.0) ## bibtex 0.5.1 2023-01-26  CRAN (R 4.3.0) ## BiocManager 1.30.21 2023-06-10  CRAN (R 4.3.0) ## BiocStyle * 2.28.0 2023-04-25  Bioconductor ## blogdown 1.18 2023-06-19  CRAN (R 4.3.0) ## bookdown 0.34 2023-05-09  CRAN (R 4.3.0) ## bslib 0.5.0 2023-06-09  CRAN (R 4.3.0) ## cachem 1.0.8 2023-05-01  CRAN (R 4.3.0) ## cli 3.6.1 2023-03-23  CRAN (R 4.3.0) ## colorout 1.2-2 2023-05-06  Github (jalvesaq/colorout@79931fd) ## digest 0.6.31 2022-12-11  CRAN (R 4.3.0) ## evaluate 0.21 2023-05-05  CRAN (R 4.3.0) ## fastmap 1.1.1 2023-02-24  CRAN (R 4.3.0) ## generics 0.1.3 2022-07-05  CRAN (R 4.3.0) ## glue 1.6.2 2022-02-24  CRAN (R 4.3.0) ## htmltools 0.5.5 2023-03-23  CRAN (R 4.3.0) ## httr 1.4.6 2023-05-08  CRAN (R 4.3.0) ## jquerylib 0.1.4 2021-04-26  CRAN (R 4.3.0) ## jsonlite 1.8.7 2023-06-29  CRAN (R 4.3.0) ## knitcitations * 1.0.12 2021-01-10  CRAN (R 4.3.0) ## knitr 1.43 2023-05-25  CRAN (R 4.3.0) ## lifecycle 1.0.3 2022-10-07  CRAN (R 4.3.0) ## lubridate 1.9.2 2023-02-10  CRAN (R 4.3.0) ## magrittr 2.0.3 2022-03-30  CRAN (R 4.3.0) ## plyr 1.8.8 2022-11-11  CRAN (R 4.3.0) ## R6 2.5.1 2021-08-19  CRAN (R 4.3.0) ## Rcpp 1.0.10 2023-01-22  CRAN (R 4.3.0) ## RefManageR 1.4.0 2022-09-30  CRAN (R 4.3.0) ## rlang 1.1.1 2023-04-28  CRAN (R 4.3.0) ## rmarkdown 2.23 2023-07-01  CRAN (R 4.3.0) ## rstudioapi 0.14 2022-08-22  CRAN (R 4.3.0) ## sass 0.4.6.9000 2023-05-06  Github (rstudio/sass@f248fe5) ## sessioninfo * 1.2.2 2021-12-06  CRAN (R 4.3.0) ## stringi 1.7.12 2023-01-11  CRAN (R 4.3.0) ## stringr 1.5.0 2022-12-02  CRAN (R 4.3.0) ## timechange 0.2.0 2023-01-11  CRAN (R 4.3.0) ## xfun 0.39 2023-04-20  CRAN (R 4.3.0) ## xml2 1.3.4 2023-04-27  CRAN (R 4.3.0) ## yaml 2.3.7 2023-01-23  CRAN (R 4.3.0) ## ##  /Library/Frameworks/R.framework/Versions/4.3-arm64/Resources/library ## ## ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────