
Tech & Field Versatility
Eleven competencies inherited from the pre-web track (BEP audiovisual to BTS IT). System administration, network design, asset management, support, electrotechnics, schematic reading, and specialized sales. Atypical field-to-CTO journey.
Each segment is a period (journey or achievement) where the competency was applied. The colour and size of the end dot reflect the level reached during that period.
My definition
Tech and field versatility is, in my profile, an 11-competency foundation inherited from the pre-web track: BEP Audiovisual Installer (1998), BAC Pro Maintenance Audiovisuelle, Electrotechnique et Mécanique (2003), MC Multimedia Sales Specialist (2007), BTS Computer Science (2009). System administration, network design, IT asset management, user support, electrotechnics, schematic reading, intervention planning, specialised sales. From cable to cloud. that is what keeps the CTO role from cutting itself off from the field.
I activate it on 3 modes depending on the engagement. Hands-on hardware/network: on demand on customer infrastructure, Docker + Tailscale + Synology homelab to keep the hardware reflex sharp. Customer-facing advisory: continuous, direct transposition of the advisory sales patterns (diagnostic → installation → follow-up) onto the digital product posture. Bridge between ops and engineering: frequent, especially on the 5+ years of self-administered OVH dedicated servers at European Sourcing (Vagrant + Chef + 25 cookbooks). The hands-on fades with disuse but the mental model stays.
In 2026, the operations layer is making a comeback driven by NIS2, DORA, and data sovereignty: certain workloads can no longer leave the corporate network, and 40% of enterprises are projected to have adopted hybrid edge-cloud strategies by 2026. IBM maps the topic in Helping enterprises across regulated industries leverage hybrid cloud and AI. For a scale-up CTO touching regulated sectors (health, critical finance, institutional real estate), the ability to read a network diagram, debug DNS, and operate a hybrid cloud + on-prem infrastructure becomes an explicit differentiator against pure SaaS profiles.
My evidence
Anecdote 1 : Self-administering OVH dedicated servers on European Sourcing
On the European Sourcing extranet between 2010 and 2016, the infrastructure ran on self-administered OVH dedicated Proxmox VE servers - no managed cloud layer, no Kubernetes, no externalised ops vendor. Every B2B catalogue served in 7 languages, every traffic peak, every version upgrade rested on my ability to read the cable, the network, and the OS. For an SMB like Medialeads, externalising ops would have cost more than running it in-house - but the hands-on had to be solid.
I industrialised the environment end-to-end: provisioning with Vagrant + Chef and more than 25 custom cookbooks (Apache, MySQL, Memcache, RabbitMQ, monitoring), Apache hardening (TLS, security headers, disabled modules), DNS BIND management, Postfix SMTP configuration, cross-instance MySQL master-slave backups, and system monitoring with mail alerts. On the application infra side, I daily operated the dedicated sql1, sql2 and web servers, handled catalogue traffic spikes, and orchestrated the automated imports from the 26+ supplier connectors.
Stable infrastructure for more than 5 years without any major incident, cost of an externalised ops contract avoided (net gain for Medialeads), and the know-how built up made it possible to absorb without friction the gradual SVN to Git migration in January 2016 and the gradual Symfony 2/3 rewrite.
That polyvalence on tech and field remains my identity baseline. 20 years after my first Celiane servers (Linux/Debian, Apache, BIND, Postfix), I can still read a network diagram, open a server terminal, debug a DNS issue - and that differentiates me today against the majority of SaaS CTOs who lost that reading. It is exactly what makes me relevant for a scale-up role in regulated industries (NIS2, hybrid cloud + on-prem).
Anecdote 2 : Translating field customer advisory into B2B product posture
Before the web, I spent years in field customer advisory roles: MC Multimedia Sales Specialist (2007), BAC Pro Maintenance Audiovisuel, Electrotechnique et Mécanique (2003), BEP Installer Counsellor for Home Equipment (1998). The deliverable was not a Git commit but a customer leaving satisfied with their kit installed at home. When I landed on the European Sourcing extranet facing demanding B2B buyers (agencies, European distributors), I understood the diagnostic-advisory-installation patterns applied identically.
I applied the advisory sales patterns to the digital product posture: systematic user interviews before each major evolution (what the buyer is looking for, in what context, under what constraint), paper prototypes validated by buyers before code, structured restitution of technical trade-offs in business language (a promotional-products buyer should not have to understand TF-IDF). On sensitive evolutions (search, pricing, markings), I even reproduced the diagnostic-installation-follow-up sales pattern: identify a need, propose an adapted solution, accompany the adoption.
Extranet adopted by B2B buyers with minimal training, low rejection rate on shipped evolutions, and the trust built up made it possible across 6 years to hold the Software Engineer then Senior Software Engineer role as a true business interlocutor - not a simple executor.
The field empathy forged at 16 in retail stays embedded in my CTO posture today: a technical decision must remain legible business-side without loss of fidelity, and the best way to verify it is to go to the end user. That is exactly what makes me effective in CTO advisory at ACCENSEO on field-heavy industries (food trucks, viticulture, automotive, hospitality) where the digital product is just one tool in a very physical value chain.
My self-critique
Level Confirmed. Less a technical domain than a practice identity inherited from my pre-web journey. audiovisual installer, multimedia sales advisor, fleet management and user support. 11 skills covering system administration, network design, fleet management, user support, electrical engineering, schematic reading, intervention organisation, specialised sales. The hands-on fades with disuse but the mental model stays - self-administered OVH dedicated servers for 5+ years, field customer advisory transposed to B2B extranet stewardship.
Identity narrative and operational empathy: it is what prevents the CTO role from cutting itself off from the field and makes tech decisions legible ops-side, support-side, and end-customer-side. For a scale-up CTO role in an industry touching hardware, edge, or regulated sectors (NIS2, on-prem), it is also a differentiator - few SaaS CTOs have kept a reading of cabling, datacentre, and user fleet.
First significant use: Junior Software Engineer · PHP Joomla Webmaster Developer. Progression up to CTO · Founder · technical director, now at 4/5 (Advanced). The continuity of these contexts signals a robust acquisition, battle-tested by repetition and diversity.
My two field gestures
Visit a datacenter or an ops team at least once a year and run an active homelab, even minimal. To others: *do not despise the physical infra layer*. especially in the regulated industries of 2026 where NIS2 brings ops back to the foreground. An hour spent understanding the cable saves a day of network debugging later.
My evolution in this skill
Tech and field versatility is an identity foundation rather than an intensive development axis. In the 24-month plan, it enables a CTO scale-up positioning in regulated or hybrid sectors (health, real estate, industrial) where the cloud / on-prem / edge separation matters. Without it, the profile is reduced to pure SaaS and loses access to industries that stay on tier-1 hybrid.
Maintaining the level is enough; the goal is observable and operational: diagnose a network incident on an SMB fleet in less than 60 minutes, and lead a hybrid cloud + on-prem ops team without depending on an external consultant.
Occasional homelab maintenance (Docker + Tailscale + Synology), occasional participation in ACCENSEO hardware interventions. Master in Software Engineering active, regularly reactivating the network / system layer.
No formal short-term training planned. Possible CKAD or networking certification (CCNA associate level) cohort in 2027 if the target role tilts toward a hybrid regulated industry.
Occasional reading of networking blogs (Cisco Press, Tailscale, Cloudflare 1.1.1.1). Annual visit of a datacenter or an ops team. Homelab kept current with the latest Docker / Traefik / Authentik versions as a reflex-maintenance exercise.