Software Engineer · English / French / Deutsch

I ship the whole system — the feature, the pipeline, and the cloud it runs on.

3+ years shipping production systems: payout, compliance, and secure-document infrastructure on AWS at AEQUIFIN, two systems at Medius — an AI pipeline converting Figma designs into design-system-compliant React at 90–95% fidelity, and a zero-downtime migration of its accounts-payable-automation core off a legacy .NET monolith — and real-time industrial energy monitoring at COFICAB.

3+ yrs
production experience
5
systems shipped across 4 companies
355
controllers migrated, zero downtime
3
working languages
Selected work

Four companies. Five shipped systems.

Written the way I'd explain them to your team: what was broken, what constrained me, what changed.

AEQUIFIN · Legal-tech / Fintech · Oct 2025 – present

Moving real money through a legal marketplace — safely

AWSPaymentsGDPRSecurity
Problem

Litigation funding — investors financing legal claims — traditionally runs on paperwork, phone calls, and trust. AEQUIFIN's marketplace digitizes it, which means the platform must do three hard things at once: move investor money correctly, protect privileged legal documents, and satisfy European compliance law. A bug here isn't a glitch — it's someone's money or someone's case file.

My role

Software engineer on the core platform — building new features end-to-end and maintaining existing infrastructure, from database schema migration to production rollout, on a live bilingual (EN/DE) system.

Constraints

Real balances, privileged case material, GDPR obligations, and zero tolerance for stale or corrupted records.

What I built

Payout infrastructure. Self-service payouts with real-time balance validation — overdrawing is impossible by construction — plus trustee-initiated payouts and a fix for reconciliation bugs that were corrupting transaction records.

A secure document vault. Role-based access to privileged legal documents, with a full request-review-revoke audit trail, encrypted at rest and provisioned as infrastructure-as-code.

GDPR right-to-erasure, end to end. A deletion workflow with admin review, full audit history, and cascading cleanup of orphaned records.

Security & lifecycle. MFA built from the ground up, bilingual lifecycle email automation, and a self-serve landing-page system for marketing.

Outcome

Every feature above shipped to production with its own version-controlled schema migration, on a platform where correctness is the product.

“Correctness isn't a nice-to-have when the records are legal evidence and the balances are real money.”
Medius · AI Engineering · Sept 2024 – Aug 2025

Teaching GPT-4o to speak a 350-component design system

GPT-4oReactTypeScriptFigma API
Problem

Every release, engineers manually translated Figma designs into React code compliant with a 350+ component design system — a full-time tax across dozens of product teams. Every existing tool failed the same way: Figma's own AI scored under 30% accuracy, V0 and Bolt.new have no concept of your design system, and fine-tuned models hallucinated props that don't exist. None of them know what your components are allowed to look like.

My role

Owned implementation end-to-end, pairing with the platform architect in an XP-style setup — they owned architectural calls, I owned the build.

Constraints

Hard correctness requirement — generated code had to use only real components with real props. No budget for a labeled fine-tuning dataset. Output had to be trusted without a human reviewing every generation.

What I built

A seven-stage pipeline: extract Figma node metadata and screenshots → match against a component catalogue built from Storybook docs (id, real JSX snippet, exact props and defaults, screenshot) → generate JSX with GPT-4o constrained to that catalogue → render live behind an error boundary → run a reflexion loop that feeds render errors back to the model for self-correction → expose a chat interface so designers can say "make the button smaller" in plain English → log every generation to structured JSON.

Outcome

90–95% visual fidelity against the original designs, strict adherence to component and prop constraints, and fully automated error recovery on common failure classes — the only approach tested that scored high on automation, component awareness, reusability, accuracy, and design-system support at once.

“The win wasn't a better model — it was building the smallest ground-truth structure the model has to stay inside.”
Medius · Backend / Platform · 1-year engagement

Modernizing a .NET monolith — 355 controllers, zero downtime

C#.NET 6ASP.NET CoreEntity FrameworkAzure
Problem

The core of Medius ran as a tightly-coupled .NET Framework monolith on an Azure hosting model heading for end-of-life. It had to move to a modern runtime — but it processes live invoices for real companies, so a big-bang rewrite was off the table. The migration had to happen one controller at a time, in production, reversibly.

My role

Built the foundation the migration team ran on: an abstraction layer that switches traffic per-endpoint between the legacy and new runtime with a five-minute production rollback, plus the backward-compatibility and testing groundwork — then batch-migrated controllers against it.

Outcome

A proven, reversible path off the monolith: per-endpoint traffic control, old-vs-new non-regression testing backed by ~4,700 E2E tests, SQL-log diffing to verify data-mutating endpoints, and architecture rules enforced in the build — the stepping stones the rest of the team used to migrate all 355 controllers.

Read →
COFICAB · Industrial IoT · Feb 2023 – Feb 2024

Making a factory's energy bill legible in real time

Node.jsReactWebSocketsIoTML forecasting
Problem

A global cable manufacturer had machines consuming energy around the clock and only end-of-month invoices to explain where the money went. The tools on the market were reactive — they reported consumption after the fact but couldn't predict a spike before it happened, so inefficiencies were discovered instead of prevented.

My role

Built the web application end-to-end: a unified sensor-integration framework with adapters for heterogeneous IoT sensors, real-time ingestion, and the prediction layer on top.

Constraints

Live factory-floor data streaming over WebSockets; power-factor and consumption dashboards that plant operators — not just engineers — could read; a sensor network that had to scale without re-architecting.

What I built

Real-time machine-level monitoring with alarm management and event logging, cost-calculation algorithms turning raw consumption into money, and an ML forecasting model that predicts consumption ahead of time and recommends reduction practices — proactive optimization instead of after-the-fact reporting.

Outcome

Consumption forecasting at 89% accuracy across 245 monitored machines, replacing one monthly invoice with continuous machine-level visibility, and cutting manual reporting effort by 18%.

Talan Innovation Factory · Healthcare AI · Mar – Aug 2024

Detecting cancer without the biopsy

TensorFlowPyTorchComputer VisionAngularJenkins
Problem

Biopsies are invasive, painful, and risky — and they're still the default step in cancer diagnosis. The Sonocure project aimed to use ultrasound waves and biomarkers for early detection and targeted treatment instead.

My role

Built ML models and the pipeline around them — training, integration into the Angular/Node application, and CI with Jenkins.

Constraints

Medical-grade ambition on research-project timelines; models had to adapt ultrasound parameters per patient, not one-size-fits-all.

Outcome

A system that adjusts ultrasound settings for each patient and improves as it learns from new cases — moving diagnosis toward non-invasive by default.

Side projects live on GitHub — including searchcore, a Rust search engine built as a pure I/O-free core crate with CLI, HTTP, and WASM adapters.

→ github.com/tahahamdii

What I work with

Backend & distributed systems
Services that talk to each other without falling over.
Java · Spring Boot · .NET · Node.js · Go · Kafka · RabbitMQ · Redis · PostgreSQL · MongoDB · Elasticsearch
AI/ML engineering
Models that ship, not notebooks that rot.
Python · PyTorch · TensorFlow · LangChain · OpenAI APIs · Vector databases · MLflow · DVC · Hugging Face
Frontend
Interfaces people actually use.
React · Next.js · TypeScript · Angular · Flutter · Tailwind
Infrastructure & delivery
If it isn't deployed, it doesn't exist.
AWS (S3 · CloudFront · Lambda · DynamoDB) · Docker · Kubernetes · Terraform · Jenkins · GitLab CI · Prometheus · Grafana · Azure

Experience

  1. AEQUIFIN Software Engineer · Remote
    Oct 2025 – present
  2. Medius Software Engineer · Hybrid
    Sept 2024 – Aug 2025
  3. Talan Tunisia Software Engineer
    Mar – Aug 2024
  4. COFICAB Software Engineer
    Feb 2023 – Feb 2024
  5. ESPRIT Software Engineering degree · after Classes Préparatoires (IPEIM, 2019–2022)
    2022 – 2025

I write about what I build.