Senior Cloud & backend Engineer

• Get hands-on with FleetAPI, AWS Step Functions provisioning, RMS, and the Retool layer - operating 50% of the perimeter autonomously within three months, 100% within six.
• Document the stack as you go. The goal isn't a wiki - it's that the team's knowledge becomes shared infrastructure, not tribal memory.
• Make the cloud foundations resilient enough that scaling the fleet doesn't put pressure on a single person.

2. Own AWS architecture and infrastructure-as-code

• Design and evolve compute (Lambda, ECS, Batch), networking, storage and IAM across the DLM perimeter.
• Bring the full stack under CDK - no manual AWS console clicks to ship a critical infra change.
• Make trade-offs (serverless vs container, RDS vs DynamoDB, push vs pull) and explain them to the team without dogmatism.

3. Drive observability and reliability

• Instrument logs, metrics, alerting that ops and engineers can act on.
• Run on-call rotation, write post-mortems, keep runbooks current.
• Move MTTR down quarter after quarter, with the numbers to prove it.

4. Ship backend services

• Build and maintain backend services in Node.js / TypeScript (Python where it makes sense), at production grade.
• Pair with the Tech Lead and the full-stack IC on infra-aware design from the spec stage - so trade-offs are made before the code, not discovered at review.

5. Become the cloud referent across teams

• Within 12 months, represent CIOT-DLM in cross-team architectural discussions (Platform, Data Platform, NetSec, AI).
• Take ownership of one major vertical at six months - provisioning, fleet drift detection, or RMS - and ship a measurable improvement on reliability or manual correction.

Do you have experience in Wiki systems?, * 4-7 years of experience in cloud engineering, DevOps or SRE - at least three of them on AWS in production, on systems that real users depended on.

• You've built APIs and shipped backend services in Node.js / TypeScript (or Python). "I don't really do APIs" is a non-starter for this role.
• You've handled real production incidents - and when you talk about them, you're specific: timeline, decisions, what you'd do differently.
• IoT, telecom or distributed systems exposure is a plus, not a requirement. Curiosity about what happens between the cloud and the physical world is.
• You can operate within a scope set by a Tech Lead and a PM. When you disagree, you know how to express your concerns clearly, route it through the right channel, and move on if your solution isn't the one adopted collectively.
• Hybrid work, three days a week from our Paris office. Full remote only won't fit how this team operates., Contrat cadre and RTT (between 8 and 12 days per year depending on public holidays)

A Mac or PC depending on your preferences

At Vizzia, we care about ownership, ground-truth thinking, and getting things shipped. We're looking for someone who finds the right interface between a cloud stack and a real-world fleet.