The Unreliable Engineer
Amine · The Unreliable Engineer

Clarify the real issue before starting the machine.

For tech teams, senior profiles, independents and decision-makers who need to make a confused situation readable and decidable.

Entry point: 60 minutes to leave with a sharper decision.

I help untangle situations where architecture, observability, AI, content and market perception get mixed too quickly.

Clarify the problem
The Unreliable Engineer presents an editorial point of view
A blurry situation does not need a bigger plan first. It needs to become readable.

We start from reality: context, constraints, tensions, weak signals. Then we separate what needs framing, support, positioning, an opportunity, or a qualified introduction.

  • Symptom What the team keeps repeating without being able to decide.
  • Constraint What makes the topic politically, technically or commercially sensitive.
  • Decision What must become arbitrable before time, budget or a relationship is committed.
  • Output Clarify, frame, support, connect, or stop cleanly.

The work is grounded in real contexts: large accounts, energy, telecom, critical production, operational debt and shared responsibilities.

The expected value is not one more opinion. It is a clearer reading of the problem, its constraints and what it makes possible.

Logo Orange
Orange Telecom / production Production and large-account experience
Logo Odigo
Odigo Operational systems Operational systems and reliability
Logo Enedis
Enedis Energy / large-scale IT Energy, large-scale IT and observability
Observability Signal, alerting, team practices Clarify useful signal before adding dashboards
SRE / DevOps Production, incidents, reliability Read production and reliability constraints
Architecture Internal systems, flows, debt Make technical trade-offs more decidable
Positioning Freelance, content, market perception Clarify the strategic perception of a senior profile

One entry point, four possible paths.

This page does not sell a competing menu of services. It sells one capability: make the topic readable, then choose the right next step.

60-minute clarification

A short session to formulate the problem, constraints, blind spots and the next useful decision.

Framing

Technical framing

A few days to turn a reliability, observability, architecture, debt or AI topic into a usable decision plan.

Ongoing

Senior support

A regular cadence to challenge trade-offs, technical narrative, priorities and weak signals.

Positioning

Positioning and opportunities

Make an offer, story or senior trajectory more readable before opening an opportunity or producing content.

Qualified signal

Qualified introductions

Open a conversation only when context, value and signal are clear enough for both sides.

Not a service menu. Not a magic promise.

Framing protects as much as action does: sometimes the right next step is to launch nothing, or to avoid opening a conversation too early.

  1. Not a 40-page audit The useful deliverable is a clearer decision, not a document that reassures without changing what happens next.
  2. Not a magic AI promise If AI is not the right lever, we say it before building around a buzzword.
  3. Not vague coaching The discussion starts from a real case: constraints, signals, trade-offs, next actions.
  4. Not automatic networking An introduction has value only when the signal is clear for both sides.

We start by naming the topic. Then we choose the format.

Current format: 60 minutes on video, around a real case, to understand better before acting.

  • A technical or strategic problem to make arbitrable
  • An offer or senior trajectory to make more readable
  • An opportunity or introduction to qualify before opening the right conversations