PhD in Bioinformatics: Is it Necessary for an Industry Career? Insights from Academia and Industry Professionals

OMGenomics

The Eternal PhD Question [00:00:04]

The podcast opens with hosts Maria and Robert addressing a recurring listener question: "Is getting a PhD necessary for a career in industry, or could I still find opportunities with a Master's and experience?" They bring on Steve Osazuwa, a successful bioinformatics professional without a PhD, to offer a contrasting perspective to their own PhD backgrounds.

Steve Osazuwa's Journey into Bioinformatics [00:01:56]

Steve provides a rundown of his academic and professional background, which led him to his current role as a Director of Engineering in bioinformatics.

• Educational Background [00:02:47]
  • Undergraduate degree from MIT, majoring in Chemistry, with an initial interest in mass spectrometry.
  • Developed an early interest in microbial science and Next-Generation Sequencing (NGS) through a lab opportunity in college, sparking his interest in genomics.
• Career Evolution [00:02:11]
  • Began his career in physics at Agilent Technologies, then transitioned into software, and eventually found his passion in genomics.
  • Worked at various startups, including one where he met Maria, before moving to larger companies and eventually becoming a Director of Bioinformatics Engineering.
• Initial Career Aspirations [00:03:22]
  • As a child, inspired by "Dexter's Lab," he aspired to be a scientist with a secret lab.
  • Applied to MIT for undergraduate chemistry, initially aiming for graduate school.

    

Deciding on Industry vs. Academia [00:05:15]

Steve shares his decision-making process during college regarding pursuing graduate school or entering the industry.

• The PhD Dilemma [00:05:32]
  • Initially considered graduate school for chemistry but realized he lacked a specific research focus.
  • Received advice to only pursue a PhD if there's a clear objective and passion.
• Influence of Peers [00:06:10]
  • A friend who worked in industry before starting their PhD inspired Steve to gain hands-on experience first.
  • Financial considerations were also a factor, as industry roles offered immediate compensation.
• Opportunity Cost of a PhD [00:07:05]
  • PhDs typically take around five years, representing lost earning potential and industry experience.
  • Steve and Maria, having graduated college in the same year, illustrate divergent paths leading to similar job roles later (Maria via PhD, Steve via industry).

The Value (and Perceived Lack) of a PhD in Industry [00:07:50]

Steve discusses instances where not having a PhD had an impact on his career, particularly regarding perception and certain roles.

• Privilege and Perception [00:07:50]
  • Acknowledges the "gold ticket" privilege of graduating from MIT, leading to initial trust in his abilities.
  • Observed colleagues from less highly-ranked schools facing trust issues without a PhD.
• Professional Recognition [00:08:43]
  • Recalls a specific instance at a previous company (DNA Nexus, with Maria) where signing off on scientific documentation for a customer was challenging without a "PhD" title, as customers perceived PhDs as more convincing.
  • Experienced imposter syndrome among PhD-holding colleagues, questioning his belonging.
• Job Role Specialization [00:10:50]
  • Bioinformatician skill sets are often split into three roles:
    • Algorithm Developer: Often requires a PhD due to the need to "learn in the unknown" and navigate complex research challenges.
    • Pipeline Engineer: Focuses on turning scientific outputs into production-ready code, requiring understanding of scientific concepts translated into software.
    • Data Analyst: Works with lab data and assay production; a Master's in data science is often sufficient, but the "navigate and learn in the unknown" skill from a PhD can be valuable.
  • Leadership in Research [00:12:40]
    • Experience and time in the field are more critical than a PhD for setting direction in scientific research groups.
    • Professionals with MD-PhDs are often highly effective leaders because they understand the end-user requirements from practical medical experience.

Host Perspectives on Pursuing a PhD [00:14:40]

Maria and Robert share their personal reasons for pursuing PhDs and how their degrees have impacted their careers.

• Maria's Motivation [00:15:06]
  • With only a biology major and limited computer science/math classes, a PhD provided a pathway to interesting jobs beyond being a lab tech.
  • Highlighted the financial benefit: PhD programs in technical fields are often funded, unlike Master's degrees.
  • Emphasizes the importance of a good advisor over the specific program. Her advisor, Mike Schatz, provided cutting-edge research opportunities.

    

• Robert's Motivation [00:17:11]
  • Studied Computer Engineering in undergrad and was drawn to bioinformatics through lab work.
  • Chose a PhD due to a fascination with the biology of genomes, even though he had other industry options.
  • His PhD provided a rare combination of software background and bioinformatics domain knowledge, enabling him to translate technical concepts and flag existing bioinformatics tools.
  • Provides an example of how his domain knowledge prevented a costly mistake where an engineer tried to store the human genome in a relational database not suited for large genetic data.

    

Lessons from Industry Experience for a PhD [00:35:14]

Steve reflects on how his industry experience has shaped his understanding of what he would pursue in a PhD if he were to go back now.

• Gaining Field Perspective [00:36:14]
  • His first job (Mass Spec at Agilent) initially didn't provide the broad perspective he sought, but exposure to genomics through an acquisition and conversations with scientists helped him pivot.
  • Attending conferences and interacting with professionals expanded his understanding of the field.
• Targeted PhD Interest [00:37:20]
  • Now, he knows he'd pursue a PhD in epigenetics, specifically focusing on techniques like ChIP-seq, and would approach specific professors he's learned about.
  • Believes his industry experience and professional network would make it easier to gain acceptance into a desired lab.

Career Growth and Academia-Industry Friction [00:39:06]

Steve discusses his career progression post-DNA Nexus and the common friction points between PhDs and pure software engineers in industry.

• Post-DNA Nexus Progression [00:39:09]
  • Moved to Vitae (where he worked with Robert) to gain more lab and scientific interaction, experiencing a full bioinformatics ecosystem.
  • Highlights a mistake made in RNA-seq analysis (choosing a random normalization technique) as an example of knowledge gaps that a PhD might address.
  • Recognized his strength in turning ideas into production-ready software, a skill often lacking in PhDs.
  • Currently serves as a Director of Bioinformatics Engineering at Keras Life Science, a leadership role focusing on project outlining and strategic direction.
• The Academia-Industry Divide [00:42:11]
  • Observes friction between PhDs (often focused on algorithm development and scientific results, even with "hacky" code) and pure industry software engineers (focused on polished, maintainable, production-ready code).
  • PhDs, accustomed to defending their research in academia ("thesis defense"), can be defensive about their work when given feedback in industry.
  • Industry newcomers (PhDs) often lack experience with collaborative coding practices (e.g., Git, code reviews) and communicating progress frequently.
  • Scientists often use "hacky" code in research because the goal is to test an idea quickly, not to build a maintainable product from the start, leading to issues when transitioning to production.

    

• Bridging the Gap [00:44:58]
  • Emphasizes the importance of "grace and acknowledgment" of each other's expertise and challenges.
  • For academics, learning to respect industry timelines and communicate issues promptly is crucial.
  • For industry, providing frameworks for scientists to prototype and demonstrating the value of maintainable code can ease the transition.
  • Setting clear expectations, like differentiating between a "prototype" and "production code," is vital.

Final Reflections on the PhD Question [00:51:28]

The hosts and Steve conclude the discussion by re-evaluating the necessity and value of a PhD.

• Is a PhD Pointless? [00:54:52]
  • Robert asserts his PhD was not pointless, providing him with critical genomics domain knowledge and the confidence to solve complex problems even when facing uncertainty ("staring into the abyss").
  • Steve acknowledges this "staring into the abyss" problem-solving ability as a key skill he hopes to gain.
• Personal Fulfillment vs. Career Advancement [00:55:40]
  • Steve considers pursuing a PhD for "personal fulfillment" and to "check a box" in his life, seeing it as a way to gain fundamental life skills, even if it might not significantly advance his career at this stage due to opportunity costs.
  • Acknowledges a "masochistic" element to undertaking a PhD, especially after industry experience.
• PhD for Specific Roles [00:57:06]
  • While Heads of Research often have PhDs, senior leadership roles (e.g., CEOs) are increasingly held by individuals with Masters or MBAs, highlighting different skill sets (research vs. product/business development).
  • A CEO with a scientific background can provide "street cred" when leading a science-focused company.
• The Essence of a PhD [00:57:41]
  • A PhD is fundamentally about advancing a field through research, which differs from general learning.
  • The process teaches how to navigate the unknown and push boundaries.
  • Leadership, whether in academia or industry, benefits from curiosity and a willingness to question one's own assumptions rather than making assertions to sound smart.
• Final Answer: A Hybrid Approach [01:02:12]
  • Steve leans towards "yes" for getting a PhD but strongly recommends a "hybrid approach": work in industry first to gain focus and a better understanding of personal and professional goals, then return to school with a more focused objective.