Background

An executive’s view with an engineer’s depth.

I’m Charles Granet. I step in when Product & Engineering organizations need to evolve and the CEO needs an outside perspective able to go from the overall system all the way down to the code.

In a few lines

Computer science engineer, twenty years across product, software engineering, quality, management, and transformation.

2004 → todayProduct, engineering, quality, and management
2021 → 2026SVP Technology, Alira Health

My most intensive recent experience is in digital health. At Alira Health, I led Product, Engineering, and QA/RA for a digital therapeutics division, drove post-acquisition integrations, and restructured an engineering organization of about fifty people spread across several countries.

Before that, I worked in semiconductors, telecom, video, and startups. That variety taught me not to look for a universal method: what works depends on the company’s stage, the product, the constraints, and the people.

I still code and experiment. When needed, that lets me check the technical reality for myself.

What these experiences taught me

Diagnosis

Don’t believe the first story

Teams, executives, clients, and systems each tell part of the reality. They have to be checked against one another.

Transformation

Act on the system

A team does not deliver in a vacuum: organization, product, architecture, quality, client, and decisions are linked.

Leadership

Own the trade-offs

Keep or shut down a platform, hire or cut, standardize or leave room for autonomy: transforming means deciding.

Timeline

2004–2008

Arteris · semiconductors

Development of a core EDA tool and experience in Silicon Valley.

2008–2012

BeWAN · LaCie · telecom / hardware

Software SDK for carriers, team management, and technical projects.

2012–2016

Intertrust Technologies · video

Client-facing technical role and launch of VOD platforms.

2016–2018

Outbuster · startup

Co-founder and CTO of a VOD platform built from scratch.

2018–2021

Freelance · outsourced CTO

Company leaders asked me to assess teams, code, or organization before deciding what to do.

2021–2026

Alira Health · SVP Technology

Product, Engineering, and QA/RA; post-acquisition integrations, team transformation, and healthcare platforms.

Since 2026

Dune

Diagnosing and transforming Product & Engineering organizations.

How I work

Listen without believing too quickly. Observe before prescribing.

People have legitimate perceptions, but never the whole truth. I listen to them, look at what is actually happening, then look for the few mechanisms that connect the facts.

I can go from a conversation with a CEO to an architecture review, from a client meeting to a discussion with a developer. That range is only worth something if it leads to a better understanding of the system and to choosing the few changes that matter.

I’m not looking for an off-the-shelf solution. I’m looking for the one that fits the system I find.

First conversation

You don’t need to know exactly what’s wrong.

Tell me what has changed, what worries you, and what you have already tried. Thirty minutes is usually enough to tell whether a diagnostic makes sense.

Talk about your situation