(Boston, MA | Onsite Available, Remote Friendly | Full Time)
My super early-stage startup is seeking engineers to come help teach us science-y folks how to build and ship real applications. We're specifically in dire need of a lead front-end person, but have other roles to fill as well!
Despite its significant potential for improving patient outcomes, brain monitoring is still not easily accessible or interpretable in clinical settings. We're going to fix that, and we'd like you to help.
We're a stealth-mode startup founded by numerical programmers, neuroscientists, and practicing neurologists who are committed to translating our best-of-breed clinical research from the lab into the ICU and ED. We're well-funded, well-connected, and own a well-labeled set of brain data amassed over the past decade at some of the most prestigious medical institutions in the world. This dataset is, as far as we know, the largest of its kind in existence. We intend to put it to good use.
Our team is composed of open-source enthusiasts, former audio/DSP engineers, programming language nerds, and generally easy-going, fun-loving, dedicated folks.
- You know that product development goes off the rails without rapid, early feedback from real users.
- You believe that honesty and frequent, open communication are more signficant contributors to software development than technical wizardy.
- You believe that "looks great" does not necessarily equal "feels great", and that the latter is higher priority (but your favorite applications accomplish both!).
- You want to build tools that help people help others in critical environments.
- You feel that diversity is an integral part of strong engineering culture. Differing viewpoints are borne from differing backgrounds, and lack of diversity contributes to stagnation.
- You're annoyed that modern websites ship megabytes of unnecessary dependencies to user's browsers. You're painfully aware of the difference between "DRY" as an important guiding principle of software development, and "DRY" as a cargo-cult mentality used to justify lazy over-coupling of code.
- You simultaneously hate and love Javascript, and are excited about various LLVM-based languages' recent progress targeting WebAssembly.
- You nerd out about content-specific adaptive streaming and compression techniques.
- You think Observable notebooks are really cool.
- You have a battle-tested workflow for debugging performance issues and deciding which layer of the stack merits optimization.
- From a front-end perspective, you recognize the tension in the development feedback loop between client-side software and a back-end service ecosystem, and derive immense satisfaction from improving development processes to relieve those tensions.
- You're intimately familiar with the lifecycle of software components - from experiment, to prototype, to an incremental release schedule.
- You sigh at bullet-pointed job descriptions that try to prescribe visceral emotional reactions to technical opinions.
Outside of the browser (and perhaps soon within it [1]), our data science team makes heavy use of the Julia language. Our nascent tooling for serving data to the browser is written in Julia as well. We're still experimenting with various parts of our tech stack, however - come help us make the right decisions!
Contact jarrett@beacon.bio if interested.
P.S. We're also hiring for Lead Android and Lead DevOps roles!
[1] https://www.zdnet.com/article/mozilla-is-funding-a-way-to-support-julia-in-firefox/