Yes you are right, except for the fact that this probe uses a silicon chip instead of a piezoeletric ceramic transducer, and that's exactly the reason why it costs 2000 dollars.
Butterfly Network | Senior Cloud Engineer | NYC | Full Time, Onsite
We just unveiled our first product[1][2][3] and We are looking to expand our team of engineers. For our cloud team, we are looking for the following skills:
- track record of shipping or maintaining modern cloud systems in production
- python (Flask, Django)
- SQL Databases (Postgres, MySQL)
- javascript (react, webpack, ES6, node, graphql)
- docker, kubernetes
- knowledge of internet protocols, REST, microservices architecture
- Unix
- previous experience with medical imaging technologies and systems (PACS)
You can contact me directly at gtagliabue[at]4catalyzer[dot]com or careers@butterflynetinc.com. For a full list of open positions, visit: https://careers.smartrecruiters.com/4Catalyzer
Engineer at Butterfly Network here, very excited to see interest on HN. As you can imagine, we are hiring, there are a lot of very interesting open opportunities
https://careers.smartrecruiters.com/4Catalyzer
Butterfly Network | Cloud Engineer | NYC, NY | ONSITE
At Butterfly Network we are building a device that will make medical imaging accessible to everyone in the world. It’s a breakthrough that will save millions of lives.
As a full-stack cloud engineer you are expected to take ownership of several aspects of the architecture and to be able to contribute at different levels. Here are some of the technologies being used and skills required to apply (knowledge and experience in all of them is not mandatory)
• 3 or more years of experience developing flexible cloud-based computing environments
• Experience with cloud computing leveraging AWS
• Experience with Docker and Kubernetes
• Comfortable with Linux system administration
• Experience with modern web frontend development (React, css modules, ES2017, Webpack)
• Experience with designing RESTFUL APIs for a microservice architecture
• Experience developing with Python environments
• Experience developing with NodeJS environments
• Experience with Graphql or similar technologies
• Experience with scripting, management, and automation tools for CI and CD
• Experience developing high availability systems and software for fault-intolerant applications such as medicine, scientific computing, aerospace, and finance
• Experience with fast and agile development life cycles
4Catalyzer/Butterfly | Sr Full Stack Engineer | NYC | ONSITE | Full Time
At 4Catalyzer we work with different startups that aim at reshaping the status quo of medicine, especially through devices, deep learning/AI, and cloud based services. it's a very unique and stimulating environment, where people from the most disparate background (ASIC, software engineering, mechanical engineering, chemistry, biology) work together on very ambitious projects and we are looking for extremely talented and motivated people. We got extensive funding and unique opportunities to work across multiple projects and startups and build an interesting and diverse portfolio of stock options.
Here is a short list of technologies we use and some high level skills we are looking for:
docker, kubernetes
python (Flask, Django)
react, webpack, ES6, node, graphql
experience with CI/CD pipelines
REST microservices
track record of shipping modern cloud systems in production
Butterfly Network | New York City or Guilford, CT | Full Stack Engineer
We're a team of world-class scientists and engineers working to build the next generation of low-cost, ultraportable medical imaging devices to really change how medicine works. We need you to help us make the software as awesome as the hardware, and build an integrated system that will bring laboratory-grade medical imaging to everyone.
Email me at gtagliabue at 4catalyzer.com or learn more at: https://www.butterflynetinc.com/#opportunities
Some of the technologies we use: docker, kubernetes, python (Flask), postgres, react, graphql, node, react native.
Butterfly Network | New York City or Guilford, CT | Full Stack Engineer, Mobile Developer (React Native)
We're a team of world-class scientists and engineers working to build the next generation of low-cost, ultraportable medical imaging devices to really change how medicine works. We need you to help us make the software as awesome as the hardware, and build an integrated system that will bring laboratory-grade medical imaging to everyone.
hi @kt9, in the kubernetes dashboard, when adding an existing cluster, under "Select a Provider" there is AWS. that means that it also support ECS? I am not aware of AWS supporting kubernetes directly. I have a k8s cluster running on an aws autoscaling group, but I guess in that case I should just click "Other". What's the AWS option for then?
AWS doesn't support kubernetes natively. We allow you to either launch a new kubernetes cluster on AWS by launching new VMs and installing kubernetes, weave and etcd or we allow you to sync an existing kubernetes cluster running on AWS by providing the k8s master endpoint.
We don't currently support ECS clusters but that is on our roadmap.
just for curiosity, what do you use for creating a k8s cluster on aws? Do you use any of the available open source tools like kube-up, coreOS on aws, kops, etc? And if I decide to stop using distelly and preserve the cluster created, will I be able to do so?
We have our own software to create k8s clusters in AWS using weave for networking. We looked at kube-up etc but our customers wanted functionality that didn't force them to create a brand new VPC created but instead just launch multiple clusters in an existing VPC.
FYI we are going to release our kube laucher as open source in the next few months. If you sign up for our mailing list or email me at rsingh@distelli.com (or follow us on twitter / fb) i'll notify you when thats available if you're interested.
Hi I'm an engineer at Distelli. The "AWS" option is a UI utility. When selecting this option while adding an existing cluster you will be able to easily identify where your cluster is situated by inspecting the Distelli UI under the Clusters tab. This helps users to separate where their clusters are located/hosted visually in the event they are running clusters in multiple clouds (as some of our enterprises customers do).
But that option requests a Key Name. What that key would be? there is no arn identifying a kubernetes cluster on aws. It also requires aws credentials, but if distelli manages the kubernetes cluster, you can't do much with the aws credentials
Only partitioning a new cluster in AWS requires a key name. For adding an existing cluster, we need client certificate and key information. Message us on intercom (the small badge on the bottom of our site) -- We are happy to help.
our strategy is to have two dockerfiles for each repo. The main Dockerfile and a Dockerfile-test, that builds FROM the main one and contains the test dependencies. during CI we first build from the main Dockerfile and then from the second one. since the test one builds from the main one, there is no significant overhead and it's usually a very fast build. we run the tests on the test image and if they pass, we push the main image to the tests. This means that we do not in practice, deploy the same image we test, but it's pretty close to that. It just requires some discipline to make sure that the test one just adds test dependencies and nothing more to be as similar as possible to the main one. We use circle for continuous integration but distelli looks really cool. Something that circle and travis don't give you is a pipeline feature. Having a system that is aware of your cluster technology enables some nice pipelines and better control
Very true. Our builds are very slow, and they could be much faster if docker caching worked properly. Seems like these issues will be solved soon with the next major release of the platform. Let's hope
