This job posting is no longer available
cancer.eliminate() // save lives
"The best minds of my generation are thinking about how to make people click ads … That sucks."
-Jeff Hammerbacher
Cancer sucks. But, code is powerful, developers are brilliant, and people are resilient.
In the high cost world of oncology, trial and error treatment is still the norm despite enormous advances in genomic medicine. Patients are given one-size-fits-all treatments that lead to poor outcomes.
CancerIQ is building intelligent analytical technologies aimed to optimize cancer risk prediction, prevention, and treatment. We do this by providing care providers with workflow tools built upon informed decision engines and data-driven classification models. Our mission strives to engage and educate patients, and guide them through the complex, convoluted, and intimidating journey of cancer prevention.
How do you fit in?
CancerIQ Engineering is looking for curious minds that want to solve problems, write elegant code, and iterate quickly. We are a group of ambitious devs who love all things science, web, and technology.
As a CancerIQ Software Engineer, you will to take part in an agile engineering process. You will architect and implement backend and frontend solutions using Javascript, Ruby, Golang, Rust, Elixir, and other technologies best-suited for the goals of the CancerIQ platform. You'll research, design, and propose architectural initiatives that incorporate domain-driven design into the microservices environment, employing sound data validation, provenance, and communication using technologies such as Kubernetes, GraphQL, and Kafka. You’ll be developing robust, performant services and user-friendly web clients that can enable clinicians to operate efficiently and gain new insights. Through intuitive visuals and interfaces, you will be creating modern and appealing applications across multiple platforms for patients of all types and demographics.
We want you to lead new efforts, promote best practices, and help the rest of the team grow in their engineering abilities through mentorship and teaching. We love pairing and so should you.
What are we looking for?
You should have several years of experience and completed many projects that have enabled you to develop strong opinions on code structure and modularization. With the rapid movement in the web landscape, you shouldn’t be afraid to dive into new technologies and learn from top to bottom. We use a mixture of technologies, and focus on those that help us get jobs done most efficiently. Knowledge of Javascript frameworks such as Angular, React, Backbone, and the like, should be something you can bring. You should have an expert-level understanding of Javascript (e.g. prototype-based inheritance, event delegation, closures, callbacks). You need thorough knowledge of the newer frameworks, and the progression of web technologies such as ES6/7, Typescript, etc.
You should have deep knowledge of the surrounding parts of the stack with the capability of designing RESTful APIs and backend services. As we scale to reach many patients and institutions, you’d make implementation decisions around scalability, performance, and web page optimization techniques. The desire to learn and help others are two core values that drive us as a development team. We believe that if you aren’t passionate about these values, then we’re not your best fit. You should be passionate about always learning and growing, as well as spreading new knowledge to just as passionate team members. As such, you’re a clear communicator and should be able to work with team members effectively.
What are the “Nice To Haves”?
Being able to navigate and contribute to the full stack will ultimately prove to be beneficial to the team. Knowledge of server-side technologies such as Ruby, Python, Java, Go, etc., would be excellent.
We employ a rapid, continuous deployment system, and as developers are responsible for seeing their features through deployment. Knowledge of DevOps and infrastructure tools (GitLab, Docker, Kubernetes, Istio, Kafka) will prove to be beneficial.
Anything Non-technical?
What about perks?