Portrait of Elie Nehme

From technology strategy to execution

Elie
Nehme

Software & Solutions Director Strategy · Transformation · Engineering · Architecture

I turn complex technology challenges into concrete roadmaps, aligning strategy, organisation, engineering and architecture so that the business builds capabilities that last

Today

Director Software & Solutions Department

Sopra Steria

Technology governance for the department: architecture and security decisions, NIS2, DORA and Cyber Resilience Act compliance, the AI-driven transformation of engineering, programme audits and roadmap reviews against value and financial alignment. Before that, from 2020 to 2025, I led transformations for the CIOs of large organisations, from strategy to execution.

5 programmes reviewed a year, 12 architects led across 4 entities, 7 people under direct responsibility

Scope

Four levers, one level of responsibility

  • Technology strategy

    Turning technology into a measurable competitive advantage

  • Engineering organisation

    Structuring teams, responsibilities and practices so they scale

  • Architecture and platforms

    Reducing complexity so the organisation can keep evolving

  • AI-driven transformation

    Making AI deliver real gains in productivity and quality

Where technology becomes an organisation

Four markers, each grounded in a specific engagement or scope

  • +5 to 10% measured productivity gain from engineering practices transformed by AI
  • Up to 5,000 developers within the scope of the transformations led
  • −40% time to market for every new project, Assurance Maladie (CNAM)
  • −53% deployment time across 3 existing environments, CNAV

Engagements

Working where technology, organisation and business priorities have to converge

Around ten organisations supported since 2020, on engagements of six to twenty months, across social protection, the public sector, energy, nuclear and transport. In the field throughout France and abroad, close to the teams and the managers of each site. Selected engagements include

  • Assurance Maladie (CNAM) · CNAV · INSEE

    Strategy and roadmaps

    • Working directly with each organisation’s CIO: analysis of the technology challenges, scenarios and recommendations
    • Three-to-five-year roadmaps, launched and then supported for 15 to 20 months
    • Multi-site organisations, two to seven sites each

    A technology roadmap the organisation can make its own

  • Orano

    Governance and scale

    • Transformation of the Paris software factory and preparation of its scale-up to four other sites: 25 internal and 12 external FTE, a multi-million-euro annual budget
    • Worked primarily with the Chief Digital Officer (CDO), in liaison with the CIO; monthly progress presentation to the executive committee
    • Reorganisation, optimisation, operational and technical steering

    −15% on the software factory budget

  • DGFiP · EDF

    Audit and transformation

    • Dedicated or embedded audits within transformation assignments
    • Diagnosis of large programmes, risk analysis, recommendations
    • Definition of roadmaps and support through the transformation

    An audit that ends in a roadmap, not in a report

Case studies

A few representative transformations, as evidence

  • Top 10 critical projects

    Bringing a 120-application estate back under control

    Context
    Bugs, vulnerabilities, too little automation, complex incident tracking, manual pipelines, tests disabled or barely used
    Intervention

    Diagnosis, improvement plans, transformation roadmap, engineering practices, automation, delivery pipeline, support for the teams

    Result: no critical or high-severity vulnerabilities in under nine months; automated pipelines across all 120 applications

  • A portfolio of 78 applications · Oracle → PostgreSQL

    Moving off Oracle: validate the method, then hand it over to the teams

    Context
    High Oracle licence costs and a poorer fit with cloud and modern architectures
    Intervention

    Built the migration roadmap, then led a first batch of 5 flagship applications through to production to validate the method, the approach and the converter; then handed it over to the teams, with on-site training

    Result: Method and converter validated in production on the 5 pilot applications, zero regressions, automated pipelines tested across 3 separate environments; 85% of the portfolio covered by the converter with no application-specific changes; 12 tech leads trained, now leading the migration of the rest of the portfolio

  • Cloud architecture

    Optimising a cloud platform

    Context
    Cloud architecture without governance, machines managed case by case and oversized, development, test and performance environments kept up 7/7 and never shut down
    Intervention

    Scenario analysis (architecture, consumption, organisation, roadmap), then optimisation of the projects through Blue/Green deployment strategies and a move to Kubernetes

    Result: −30% on about €6.7M of annual spend, close to €2M a year

Influence and adoption

Transforming practices, not only architectures

  • 1,300+ professionals trained and introduced to new practices
  • Topics AI, Craftsmanship, modern architectures, engineering practices, technology transformation
  • Formats courses of one to five days, webinars, awareness sessions, roadmap briefings

Writing

Understand technology transformations. Put them into words. Pass them on

Architecture

Plus le projet grossit, plus l’IA se trompe: le bounded context comme investissement

On a green-field project, generative AI works wonders; as the project grows, its answers lose accuracy. The model has not changed: what has grown is the context it has to hold. Context Budget, the method I have introduced on several projects, splits the code into bounded contexts the AI can hold in full: the split is paid for once, and each request then pays only for its own context.

Read

Security

Corriger ou atténuer: le CRA ne prévoit que deux réponses

Since 11 September 2026, the Cyber Resilience Act (CRA) has required an early warning within 24h for an actively exploited vulnerability in a product, including products already on the market. Meeting that deadline depends on work done well before the incident: in the delivery chain, in the number of versions maintained, and in whether products can be mitigated without a developer.

Read

View all writing

Ideas

Thoughts, notes and perspectives I publish directly here

Explore ideas

Career

  1. Engineering
  2. Architecture
  3. Transformation
  4. Organisation
  5. Governance
  6. Strategy

See the full career Download the resume (PDF)

Let’s talk

Technology strategy, organisational transformation, engineering and architecture: let’s talk about the roadmaps worth building and the transformations that still have to land.

Get in touch