Vizzia
Engineering
SeniorCloud&backendEngineer
Neural analysis suggests this role is
optimal for Senior candidates.
“Senior Cloud & backend Engineer at Vizzia. Skills: Cloud Engineering, Backend Development, AWS Architecture, Infrastructure as Code, IoT Cloud Perimeter Management. Take ownership of the IoT cloud perimeter. Document the stack”
What You'll Achieve.
operating 50% of the perimeter autonomously within three months, 100% within six; Make the cloud foundations resilient enough that scaling the fleet doesn't put pressure on a single person; Move MTTR down quarter after quarter, with the numbers to prove it; ship a measurable improvement on reliability or manual correction
Industry & Context.
Make trade-offs (serverless vs container, RDS vs DynamoDB, push vs pull); handle real production incidents; ship a measurable improvement on reliability or manual correction
Run on-call rotation, Hybrid work, three days a week from our Paris office. Full remote only won't fit how this team operates.
What They're Looking For.
Must Have
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), You've handled real production incidents
Nice to Have
IoT, telecom or distributed systems exposure is a plus, Curiosity about what happens between the cloud and the physical world is
What You'll Do.
Take ownership of the IoT cloud perimeter
Make the cloud foundations resilient
Design and evolve compute
storage and IAM across the DLM perimeter
Bring the full stack under CDK
Make trade-offs (serverless vs container
push vs pull) and explain them
keep runbooks current
Move MTTR down quarter after quarter
Build and maintain backend services in Node. js / TypeScript (Python where it makes sense)
Pair with the Tech Lead and the full-stack IC on infra-aware design from the spec stage
Represent CIOT-DLM in cross-team architectural discussions
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
How You'll Work.
Team & Collaboration
pair with Wilfried (Tech Lead) on architecture; work alongside Timon (PM) on what gets shipped; represent CIOT-DLM in cross-team architectural discussions (Platform, Data Platform, NetSec, AI); Pair with the Tech Lead and the full-stack IC on infra-aware design
Communication Scope
explain them to the team without dogmatism; express your concerns clearly; route it through the right channel
Full Job Description
🎯 CONTEXT 250+ local authorities already rely on Vizzia to keep their streets cleaner and safer. By the end of 2026, that number will be 450. Behind every camera in the field sits a cloud and IoT stack that has to keep up — FleetAPI, device provisioning, OpenVPN multi-shard, the routers that keep our cameras online. Doubling the fleet doesn't mean doubling the manual work behind it. It means rebuilding the foundations so it scales on its own. We're looking for the cloud and backend referent of this squad. You'll pair with Wilfried (Tech Lead) on architecture, work alongside Timon (PM) on what gets shipped, and take full ownership of the cloud foundations - so the next 200 cities we onboard reinforce what we've built, rather than stretch it thin. 🛠️WHAT YOU'LL DO 1. Take ownership of the IoT cloud perimeter - 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
Applying for this Senior Cloud & backend Engineer role?
Most applicants get filtered before a human reads their resume. See if yours makes the cut.
How to Apply on Ashby
- Ashby is a fast modern ATS — most applications take under 3 minutes.
- The resume parser is strong; verify parsed experience dates and job titles.
- Custom screening questions are often scored algorithmically — answer completely.
- Location field affects geo-based screening; use your actual metro area.
ANONYMOUS · UNFILTERED
What do employees actually say about Vizzia?
Real rants from real employees. Read before you apply.