jmbiaudisDevOps engineer

From electrotechnics to DevOps

11 October 2026trajectoryeducation

Content created with the help of AI

People often ask where I come from. Here is the detailed version: step by step, what each period brought — and what it left undone.

2005 — 2009: vocational diploma and baccalaureate in electrotechnics

It all starts at the LEP Martin-Bret, with a BEP then a Bac Pro in Electrotechnics (Energy, Communicating Equipment). Over the same period, my first certifications: Cisco CCNA 1 and 2.

That’s where I learned things that still hold: current, protocols, exact gesture. Concrete systems that either work or don’t, and that don’t tolerate sloppiness. Many people see computing and electrotechnics as separate worlds — in truth, a datacenter is an electrotechnical object before it is a software object.

2009 — 2011: BTS MAI

Higher technician diploma (BTS) in Industrial Mechanics and Automation at the Les Iscles high school. Two years of industrial logic: sensors, programmable controllers, reproducible sequences.

What I take from it today isn’t the technical content — it’s the idea that a sequence you can’t re-run identically isn’t a solution, it’s luck. I now spend that reflex every day at alfa-safety.

2011 — 2015: INGESUP, from BTS to level 1

Change of course: I join INGESUP in Aix-en-Provence to prepare the Expert in Computer Science and Information Systems credential — RNCP Level 1 (Bac+5, master’s equivalent).

The program included three internships, and those are what actually built the profile:

Year 1 (2012) — Technical referent at INGESUP itself

Seven months as a technical referent intern: Active Directory, network printers, FTP file sharing, setup and configuration of Cisco Catalyst 3750G and 2960G switches, and a Windows Server 2008 server.

First exposure to an infrastructure of that size, to a server that isn’t only mine to serve.

Year 2 (2012 — 2013) — Sudériane, Manosque

Eleven months as an intern Systems and Networks Technician. The daily routine: phone support, data recovery (viruses, failing disks), remote and on-site interventions (setup, preventive maintenance, incidents). And the preparation of workstations, servers and network equipment — deploying Symantec antivirus.

That’s the internship where I learned the trade in real contact: people on the phone don’t want to know how the system works, they want it working again. Doing both — understanding and reassuring — is the real job.

Year 3 (2013 — 2014) — Amesys, Aix-en-Provence

Eleven months as an intern Systems and Networks Administrator. Administering Debian workstations and servers, supporting a software development project (network mockups, real-time Linux kernel), maintaining collaborative tooling (wiki, SharePoint, Mantis).

First real contact with Debian — and a taste for system administration that never left.

2015 — 2022: consultancy, seven years looking for the right scope

On graduation, three successive consulting firms. Seven years of technical accumulation — and seven years of watching my scope widen without ever filling up.

AUSY (2015 — 2017) — Toulouse area

Engineer, with two main assignments: systems production engineer near Lille, and technical support near Toulouse. Maintenance and operations: keeping things standing. Dense technical work, but the decisions always happen somewhere else.

ALTEN (2017 — 2020) — Cholet

Studies engineer. The best part of that period: the development of a deployment solution for a systems and network monitoring platform — well before building, I was asked to understand and to compose. The rest took me back to classic tasks: integration, verification, validation and qualification of an evolving information system.

Accenture Technology Solutions (2020 — 2022) — Nantes

Senior studies engineer. Two years of maintenance and operations on evolving information systems — support, incidents, routine requests. Well surrounded, well paid, but the scope still wasn’t there.

That’s exactly the point that explains what comes next: it wasn’t the work I was missing, it was building “things that come from me” — solutions assembled from start to finish, documented as deliverables, that I can watch run.

What this long transition left me

Three things additional years on a classic position wouldn’t have bought:

  1. The real before the abstract: my reflexes come from electricity, what heats up, what resists, what cuts. On an incident, that gives me a reading that cloud abstractions don’t distort.
  2. Reproducibility as a reflex, not a slogan: the BTS MAI planted the seed — a procedure that works once isn’t a procedure. Toolbox at alfa-safety is that reflex, turned into code.
  3. A sense of transition: I know what it’s like to keep systems alive that were never designed to be handed over, and that’s why projects like NetBird speak to me — they’re precisely about moving from a tool one person holds to a tool a team runs.

So the step toward DevOps isn’t a jump. It’s this continuity, equipped today with modern tooling: Ansible, n8n, versioned scripts. The trajectory continues, one level up, toward MLOps.