Senior Backend Engineer
Core Services
Remote France
French & English
About us
Airnity is a rapidly growing French company in the telecommunications field. We are a mobile operator serving automotive manufacturers and helping them meet the challenge of ultra-connected vehicles.
One of our strengths as a telecom operator is that we heavily use "cloud-native" technologies. This allows us to have an extremely agile approach to our business and position ourselves as a viable alternative to traditional players.
We need help
Our Core Services circle owns the components that sit between our telecom network and everyone who uses it: our OEM partners, our support teams, and our own engineers.
That surface keeps growing and we need a senior pair of hands to build, maintain and operate it with us:
-
The B/OSS API, the one that enable management of subscriptions and SIM cards lifecycle
-
The Datalake API
-
The Provisioning Gateway, transforming high level commands on subscriptions into configuration of the telecom network
-
SMS, OTA updates, local profile orchestration – using local virtual SIM card in country's that required it
Within the circle, you will be involved in defining, developing and operating these components so they stay reliable, observable and easy to build on.
In particular, you will be tasked with working on:
-
Business back-ends — managing users, subscriptions, SIM and subscriber lifecycle
-
Technical back-ends — implementing and operating telecom functions (provisioning, SMS, OTA, local profile orchestration)
-
Interfaces — the unified API gateway and the Datalake interfaces we expose internally and to partners
No prior knowledge of Telecom specifics is required – you will receive training on this during the development process.
Your responsibilities will include:
-
Design and architecture
-
Selection of technologies to implement
-
System development
-
Implementation of continuous integration and deployment
-
Writing automated tests
-
Operating the solutions, including taking part in on-call
-
Documenting what you build, for the people who will use and maintain it
You will also help build our internal tooling and AI platform
Alongside our Tools Engineer, you will contribute to the tooling that makes the rest of the company faster: scripts, automations and integrations across our workflows, and the AI platform we are building to put those capabilities in everyone's hands. Concretely, that means designing and implementing solutions from the needs our workflow owners bring, testing and validating them before release, and maintaining them once they are live.
This is a real part of the job — not a side quest — but Core Services components come first.
Our technology stack
-
GCP
-
Kubernetes
-
PostgreSQL, Kafka
-
Elixir, Python, Javascript, Golang
-
ArgoCD & CrossPlane
-
GitHub
Our environment
As Airnity is organized as a Holacracy, you will have complete freedom to propose the role or roles you wish to take on in order to best benefit the team with your experience. You can also develop new skills by choosing other roles.
Airnity is a full-remote company, allowing you to work from anywhere in France, with the possibility of occasional co-working.
And you?
-
You have solid experience as a Backend Engineer, and you have carried systems in production — not just shipped them.
-
You have previously messed up a production database migration.
-
Deploying multiple times to avoid downtime resonates with you.
-
Seeing the test suite pass gives you a particular satisfaction.
-
AI is already part of how you work — and you review its output the way you would review a colleague's pull request. You reach for it by reflex, you know the tasks where it earns its place and the ones where it wastes your time, and you have never shipped something you could not explain.
-
You are comfortable owning a component end to end, in an organization with no managers telling you what to do next.
-
You speak French and are comfortable with English.
Bonus points
-
You already know Elixir
-
OSS/BSS rings a bell with you
-
You have built internal tooling, or shipped something on top of LLMs, and you know the difference between a demo and a system people rely on