Live data from Hacker News

Consider working on genomics

claymcleod.dev

281–290 of 299 posts

Re: Consider working on genomics

#281

Earlier quoted context omitted.

Edico developed FPGA-based processing solution for common bioinformatics processing tasks (e.g. dna/rna mapping, variant calling) and the company was bought by Illumina. The product (Dragen) has been around for a few years and now will be integrated in the new generation of sequencers. Extremely impressive technology and a better fit for the niche compared to GPU-based solutions I have seen. More downstream processin…

I'm more excited about NVIDIA's acquisition of Parabricks and the version 4.0 of the software that makes it free to use, than I am about DRAGEN. At the very least it's good to have some competition in the space, Illumina's stuff is always SO expensive. We'll have to see what hardware will win in the end.

I have tried both and dragen was more polished and also faster (that depends on the GPU for parabricks of course). Also more features and they keep adding them.

Agreed that competition is good to have. There is also Sentieon and similar solutions which run on common hardware but are optimized.

Speaking of costs (both upfront and licensing), dragen imo is not expensive relative to sequencing costs (e.g. sequencers and flowcells). Surely it would be expensive to buy for occasional use.

By making parabricks free to use Nvidia tries to gain a market share I guess. In professional settings you still end up buying support and likely dedicated hardware (which is comparable in pricing). Good fit for the cloud and research environments that already have access to GPUs and/or are decoupled from actual sequencing.

Re: Consider working on genomics

#282

> Often, it's not required to know the domain before you join a group, and they will teach you on the job. I looked. There are zero full-time, remote roles that don't require previous genomics experience at any of the companies listed.

I know there are at least a few, because positions on my team offer remote and don't require and previous genomics experience.

https://talent.stjude.org/careers/jobs?keywords=software%20e... , i.e., taking your search and entering my zip code, sShows only 3 positions in St. Jude, none of which mention the word genomics at all.

Re: Consider working on genomics

#283
I write synthetic biology software for a living and maintain this open source, Go package for engineering DNA that has high test coverage and a nice little dev community around it.

https://github.com/TimothyStiles/poly

A large part of my project's community are devs that want to get into the field but can't tolerate the ridiculously low pay, laughably bad management, disrespect, and what amounts to 40+ years of technical debt that's endemic to biotech software.

I've had companies here in the Bay Area offer me 100K a year with a straight face. I've had companies during interview tell me they're looking for someone to help, "set up GitHub". I've seen job listings for low paid web dev positions require applicants to have PhDs.

The reality is that except for a growing handful of places management straight up won't know the difference between IT and software engineers. It's what I call the naive buyers problem.

The demand for software engineers in biotech is generated by naive buyers that don't know what they need, why they need it, or how to get it.

Benchling and Recursion Pharmaceuticals have reputations in the industry of paying, "standard software salaries". So do the research divisions at places like deepmind/microsoft/google but in my experience there's even new multi-billion dollar institutes where senior management has never even heard the term devops.

Most places advertise for "data scientist", positions or some analog, instead of software engineers. This is mostly because upper management has never met an actual practicing software engineer in a professional setting. Many come from academia where the culture and work requirements heavily disincentivize standard software engineering practices.

It's also not uncommon for a biotech company to either have a very under qualified CTO whose main programming experience is what they learned doing ML research like stuff during their PhD or not even have one at all which has huge downstream consequences.

This week a software engineer trying to make the switch to biotech actually DM'd me to ask why they were seeing a ton of data science / ML job positions but no software engineering / devops positions.

They were worried that these companies were trying to save on costs by forcing their data scientists to create infrastructure but it's actually worse than that. Most of these companies aren't even aware that there's supposed to be infrastructure.

Despite all of this the future is looking better and I'm starting to find new companies and positions that are well... reasonable. I learned about this thread from a friend at a party last night that works at one of these companies. There's a small, strong new wave of companies and developers out there pushing biotech software forward. Hopefully some (including myself) make it big while pushing the idea that better tech equals better biotech.

Re: Consider working on genomics

#284
post #231

Earlier quoted context omitted.

This is a great read. Thanks for the information. What you originally described is basically my dream job: software engineers working alongside scientists and engineers, where the software engineers become domain knowledgeable if not experts in certain areas. I had a job similar to that at a similar places (actually places), but I ended up leaving because I was a one man team and got burnt out. Writing software for s…

A really hard aspect to this is that there's a massive impedance mismatch between the research & production side of things. Working in the research side is pretty straightforward - although software development practices are going to be a lot looser & faster. Working in a production environment is straightforward, it's like any other software job. But - working at the confluence of those two states is incredibly diff…

Fwiw I acknowledged the good people directly from the Cromwell team on a presentation recently due to the incredible support/help somebody & their team provided my team. The WDL/Cromwell community has grown and I've heard people mention it everywhere now (far away from the Broad) and it's in no small part due to that team and its former leadership.

Re: Consider working on genomics

#285

Earlier quoted context omitted.

Since my post was upvoted a tad... I'll give more feedback about the Broad. When I joined, it was running really like an academic center. Like literally in my lab, if I wanted to go into the lab and pipet and do library prep, the wet lab scientist would teach me and vice versa. It was lit. a place where anybody could pivot their career to anything. We worked on NIAID/NIH grants and went to conferences even as SWE's a…

Current DSPer since 2017 and broadly agree with OP.

Yea I liked almost everybody in DSP.

I disagree strongly however with the management's tech approach, the Broad cannot compete with the other companies in the Boston area in terms of comp. What worked in the past is smart people came to the Broad for the fun, autonomy and intellectual challenge over pay.

If you reduce people to just worker-bee's finishing CRUD tickets on an Agile board - you'll get efficiency for the 1st 2 years but you'll lose so much institutional/domain knowledge and collaboration; the PMs will get promoted in 1 year while projects on a 5 year timeframe get uber-delayed; the smart people will get bored and leave and even the good efficient engineers in the system will also leave for the better well paid tech jobs that Broad cannot compete with. I've seen it in every company who has run this playbook.

Re: Consider working on genomics

#286

Earlier quoted context omitted.

Since my post was upvoted a tad... I'll give more feedback about the Broad. When I joined, it was running really like an academic center. Like literally in my lab, if I wanted to go into the lab and pipet and do library prep, the wet lab scientist would teach me and vice versa. It was lit. a place where anybody could pivot their career to anything. We worked on NIAID/NIH grants and went to conferences even as SWE's a…

> respect of a lab assistant – unless you have a PhD and a postdoc. This applies to even those with those with Biology backgrounds, as an undergrad that entered the Industry after an expensive and precarious 5 years of University and exiting during the aftermath of the financial crisis with tons of debt I knew I was never going to enjoy or like my time there within the first months. I had aspirations to be CLS (you n…

Yea if there's a unsolicited take-away from me... don't ever become a lifer or think a company/field will never change. Nobody, even if it's GOOG circa 2010's, IBM circa 1970's, MSFT 1990's ever offer good combination of intellectual and comp forever. Only you and maybe your mother care about your well-being... I don't feel sad anymore about the good jobs/research opp. is now gone. I realize I was lucky and I aim to always to try adapt to get into those environments and accepting things are always changing.

Re: Consider working on genomics

#287

"From my experience, what works incredibly well is a partnership between biologists and software engineers: the biologists first come up with the first concept of the tool, which is purely focused on ensuring good results. After this first iteration is completed, engineers then come in and rewrite the tool using modern engineering practices with things like speed and reliability in mind." Like others have pointed out…

Janitors maintain, not create or optimize. It's literally an engineer's job to plan and realize a concept.

Re: Consider working on genomics

#288

I will add Mammoth Biosciences to the list. We are looking for Software Engineers, Data Engineers, Data Scientists and more. https://mammoth.bio/careers/

Had a glance at the team page on the Mammoth website, curious to learn more about how the various roles fit together. Mind sharing a way to get in touch?

Re: Consider working on genomics

#289

I'm a software engineer who works on genomics. I see a lot of negativity in this thread, which mirrors my experience: in most places, you'll be paid like a researcher with the respect of a lab assistant – unless you have a PhD and a postdoc. That said, it's possible find work that's respected and pays well. Most of that kind of work is happening in the context of startups or freelancing. My favorite example of this i…

Genomics today is the internet of the early 90s or programming of the late 70s. There is going to be an enormous boom in genomics-derived technologies in the coming decade which has been driven by the exponential decay in data generation costs. You're absolutely right that places with a "startup" mentality are where to be right now.

On that note :) I'm starting a forward-looking research lab at UofT to advance massive-scale (think petabytes) genetic analyses and am looking to find the right few individuals who have a similar vision. It's difficult to find passionate engineers with a solid CS and HPC background who are willing to meet halfway and work _together_ with biologists in getting the analysis right. Robert does this _very_ well, and that's why we recently co-wrote a landmark Nature paper: https://www.nature.com/articles/s41586-021-04332-2.

Job post: https://jobrxiv.org/job/university-of-toronto-27778-full-sta...

Re: Consider working on genomics

#290

Is there any open source projects on genomics that I can start looking into as a hobby rather than jumping right into a full time position in this field?

Serratus (https://github.com/ababaian/serratus) is an OSS bioinformatics project created by a passionate group of volunteers. Short story is we're re-analyzing all of the world's DNA/RNA sequencing data to find new viruses that other people have missed. It works surprisingly well, but there's a ton left to do.
Post reply on HN