Join Neko Health as a backend engineer and make a difference in the health-tech industry! We're looking for an imaginative and talented individual who is eager to help us develop and operate our secure, world-scale, and performant health data platform.

For regulatory and legal reasons we are only looking for people that live in the EU.

About Neko Health

Neko Health is a Swedish health-tech company co-founded in 2018 by Hjalmar Nilsonne and Daniel Ek. Our vision is to create a healthcare system that can help people stay healthy through preventive measures and early detection. Neko has developed a new medical scanning technology concept to make it possible to do broad and non-invasive health data collection that is both convenient and affordable for the public. This requires completely reimagining the healthcare experience and incorporating the latest advances in sensors and AI. We are a remote first company, but the company is based in Stockholm and has 40 employees across Europe.

About the role

You'll play a crucial role in shaping the future design and implementation of our backend and data model for our scanning technology and be a part of our diverse and distributed engineering team, which includes specialists in hardware, firmware, electrical engineering, algorithms, machine learning, optronics, frontend development, and more. Together, we're working towards our mission of building preventive healthcare.

The engineering team is organized into several smaller projects, each centered around a specific goal or deliverable. Here you will be working with the whole chain, with everything from design to deployment and develop and operate our Data platform, APIs and integration with third-party health data providers, or interaction with our hardware devices. You will also assist the teams with backend infrastructure, design and operations in Azure and debug interactions and assist other teams with our devices (implemented in C++ and Python) and backend services (C# and Python).

Requirements

We think that willingness and ability to learn is more important than a perfect match between your skillset and our technology stack, however, some skillset overlap will speed up the onboarding. Our API:s are written in C# with ASP.NET Core, uses Azure Cosmos DB and Azure Active Directory for authentication so if you have experience with C#, NoSQL database modeling, OAuth2, or Azure it is beneficial. If you have experience of other cloud services that is also meriting.

For us it is also important that you have some experience with developing and operating large scale backend systems, balancing customer demands and long-term engineering goals and have experience of managing always-on infrastructure. It is also important that you have a flexible mindset since you will be working with different projects.

About the Engineering Team

Distributed and Remote First

We are 40 full time engineers at the company, working from Berlin, Chamonix, Hamburg, Lisbon, Marseille, Vilnius, and Stockholm and spanning diverse disciplines such as Hardware Engineering, Firmware Development, Electrical Design, Algorithm Development, Machine Learning Development, Optronics Research, Frontend Development and more.

Our headquarters and our hardware development team are in Stockholm, Sweden.

We are a Remote First company; however, it is of course much easier to work remotely as a software engineer than a hardware or firmware engineer (since they require access to hardware or devices occasionally). Software engineers based in Stockholm work maybe one day a week or one day every two weeks from the office.

We meet a couple of times per year to get to know each other and have fun.

Organization and Way of Working

The engineering team is divided into smaller cross functional project teams that each focus on a specific goal or target, where some groups are long-lived, and some are short-lived, depending on how big the goal or deliverable is. We strive to create groups which are cross-functional and able to complete their goals without dependence on other teams, even though this is of course not always possible.

Groups track goals on a yearly and quarterly basis with goal follow-up across the entire engineering organization on a bi-weekly basis.

Most groups do internal planning on a bi-weekly basis, but in the end it's up to the group to decide how they want to work.

We have, however, mandated that all groups must present their progress or failures or hacks at our bi-weekly engineering demo, a fun meeting/presentation where we talk about everything from short-circuiting power-modules, how hard it is to calibrate cameras or align polygons in space, to neat new command line tools for operations, a new auth mechanism in the backend, a cool new way to visualize health data or a new feature which helps our doctors be more productive.

We have a flexible workplace that focuses on work/life balance, and we strongly believe in our mission but do not think that achieving it requires sacrificing everything else.