- Upload Your CV
- Go to your Inbox & Confirm Your Application
For any enquiries on this job please contact the job poster
$53K - $58K• Company Website https://resin.io
Resin.io provides a software platform that helps developers build, deploy and manage code on connected devices. We brought Docker to embedded GNU/Linux devices in 2013 and have been building our IoT toolkit ever since. We also maintain a variety of successful open source projects including Etcher, Balena, and resinOS, and made contributions to high-exposure projects such as Docker, Electron, and AppImage.
Our technology is open, standards-based, and proven in production across a wide range of scenarios from drones, 3D printers, point-of-sale devices, tidal turbines, skyscrapers and more. Our investors include DFJ, Aspect Ventures, GE, and Ericsson.
Resin is a highly distributed, remote-friendly company with a pretty much flat hierarchy. Our organization is adaptive, getting feedback signals from our users and systems. Right now we organize ourselves by projects, which allow us to build complex features and solve big problems, while staying mutable. As a distributed group, we rely on clear communication and the rule of “assume positive intent” to help us work together across time zones, cultures and first languages. Our base of operations is nominally London, though really we are living all over the world: from Barcelona to Bulgaria, Argentina to Vietnam, and many more.
We maintain a service infrastructure for IoT devices, and this is where we have quite a bit of our engineering talent. You will be actively working on one or more of these core components, fixing bugs, solving complex technical problems, and implementing user-facing features across the resin.io stack. While resin.io focuses on IoT, the majority of our engineers don’t require embedded programming expertise.
People who are successful engineers are well-rounded generalists and great communicators. They are eager to take responsibility for a project, and are able to make good decisions about the project because they have the context of what’s important.
We don’t require engineers to be already familiar with the technologies we use. We are happy to invest in people that showcase a strong understanding of the challenges of building secure distributed systems.
Need to have:
Nice to have:
Make sure to let us know if any of these items apply to you!