A small team.
Real ownership.

Founding Software Engineer / Technical Lead

Own the software architecture and help turn a founder-built prototype into a dependable product.

The starting point

A rapidly built Python codebase, working voice infrastructure, early diabetes-data integrations, a web prototype, tests and deployment infrastructure. Hardware development is underway.

AI-assisted development has been used heavily. You’ll decide what to keep, simplify or rebuild.

What you’ll shape

• Backend architecture, integrations and reliable data handling.
• Voice latency, context, memory and knowledge systems.
• Hardware interaction, privacy and deterministic safety boundaries.
• Testing, deployment and the foundations for scale.

Who we’re looking for

Strong Python and backend engineering, sound architecture judgement and evidence of shipping substantial systems. Experience with voice, AI, health technology or connected hardware is useful.

You should be ready to work directly with Arthur, challenge decisions and take genuine responsibility for the technical direction.

Early Founding Engineers

Already building ambitious things? We’d like to see your work.

This is a pathway to meaningful engineering ownership, whether you’re at university, pursuing postgraduate study or have already graduated. You could work directly on real Nielo systems with the early founding team, with the possibility of growing into a larger role over time.

What stands out

• Strong software engineering ability, demonstrated through working projects.
• Ambitious personal builds, research or startup work that you can explain in depth.
• The ability to learn quickly, make thoughtful decisions and follow through.
• Curiosity about the product and a desire to own meaningful work.

Computer science, engineering and AI/ML are natural fits, but your background and stage of study are not the deciding factors. Show us what you’ve built and how you think.

Start with your work

Send a project, repository, demo or research contribution. Explain what you personally built, the hardest decision you made and the time you could realistically commit.

For both pathways, scope, location, time commitment and any compensation or employment arrangements will be discussed individually. No terms are promised here.