I think if you have the right structure, it is easier to train developers to be bioengineers than bioengineers to be developers! Bioengineering tends to be a more wicked discipline, which seriously affects how one writes their code. Makes it kinda crap. Software devs on the other hand typically aren't as experienced in the other field, and so are coming in blind.

Also, I second what Dig1t said. I would gladly get involved and volunteer my time and skills, just to get my foot in the door. Would contributing to dnadesign be a good place to start?

some sets of problems I have right now (on the hardware / software side):

Hardware: It'd be great to have an open source plate gripper. I wrote a little bit about the general problem of transferring here - https://keonigandall.com/posts/transfer_problem.html . I have a uarm lite6, but wanted to investigate building an arctos robotic arm to move plates between machines. Just need the gripper! This is something I cannot do myself - I have software skills, and can build things with my hands, but have zero skills on designing new hardware.

Software: A lot more here, but depends on interests. I have some general life-improvements I'm looking at doing, but also some wild ideas that need prototyping