Omar Chenine
AI engineer and data scientistRemote

I ship AI systems end to end.From messy data to a deployed, evaluated product.

I am a fourth year Data Science Engineering student. I build retrieval systems, ECG analysis tools, tabular models, and the interfaces that make them usable.

RAG evaluation / ECG review flags / tabular ML / data products

Data

MIRACL, Ames, ECG images

Model

Retrieval, trees, signals

Eval

nDCG, RMSE, review flag

Deploy

Next.js, APIs, dashboards

Interface

The part a person actually uses.

Static map3D on demand

6

featured case studies

32

skills with project proof

6

engineering notes

Remote

timezone flexible

Selected work

Retrieval evaluation, ECG review flags, tabular stacking, warehouse to dashboard, agents, and sports prediction. Each case study states the result, the baseline, and what is still missing.

02CVHealthcare

ECG image analysis

An ECG image goes in. A digitized signal, rhythm, axis, PR, QRS, and a review flag come out.

Digitization error
See demo readout
Review flag rate
See demo
Build and evaluationCase study
03Tabular

Ames housing stacked ensemble

Five models, out of fold predictions, and a baseline table that keeps the stack honest.

RMSE, log target
$245,900
Best single model
LightGBM
Build and evaluationCase study

Project universe

A map you can enter, not a loading screen.

The static map is the default and it is fully usable. The 3D scene is an optional view that loads after activation. Reduced motion and low end devices keep the static version.

AI engineering

The decisions behind the models.

Each card names a flow, the decision that shaped it, the tradeoff it cost, and one failure still missing from the record. No architecture diagram without a reason.

RAG

Retrieval is evaluated before the generator is allowed to speak.

  1. Query
  2. Retriever
  3. Top k chunks
  4. Reranker
  5. Cited answer
Decision
Score retrieval first, then add generation. The retriever is the part a reviewer can measure without trusting a model's prose.
Tradeoff
A retrieval only gate slows the build and exposes weak chunks early. That is the point. A fluent answer hides a bad retriever.
nDCG@10Pending

Failure found and fixed

Pending: Add one real retrieval failure and the fix

AI agents

Tool use with typed inputs, explicit failure paths, and a trace a reviewer can read.

  1. Intent
  2. Planner
  3. Tool call
  4. Validation
  5. Response or fallback
Decision
Every tool call returns a typed object and every step is logged. A free form agent loop is harder to evaluate and harder to debug.
Tradeoff
Typed tools and explicit branches take longer to add. They make the failure surface smaller and the transcript readable.
Task successPending

Failure found and fixed

Pending: Add one real tool call failure and the fix

Voice agents

A latency budget by stage, with a fallback for every timeout.

  1. Speech in
  2. Transcript
  3. Model
  4. Tool
  5. Speech out
Decision
Set a per stage latency budget before writing prompts. A voice turn that sounds smart after two seconds still feels broken.
Tradeoff
Short model calls and narrow tools reduce quality on complex requests. The fallback path has to be good enough to carry the turn.
p95 latencyPending

Failure found and fixed

Pending: Add one real latency or turn taking failure and the fix

Computer vision

Image input is treated as a signal problem, not a classification demo.

  1. Image
  2. Clean
  3. Extract trace
  4. Intervals
  5. Review flag
Decision
A low confidence result returns a review flag instead of a confident label. The interface has to make uncertainty actionable.
Tradeoff
The flag reduces automation and adds work for a reviewer. It also prevents the system from pretending a noisy trace is a diagnosis.
Digitization errorPending

Failure found and fixed

Pending: Add one real image or trace failure and the fix

Skills, with proof

Every skill links to a project.

No badge wall. Pick a skill and the projects that use it stay lit. Pick a project and its skills stay lit. The archive is included because proof is proof.

Stack at a glance

Top 12

Programming

4

ML and DS

9

Data and BI

3

Frontend and Web

6

AI systems

6

Security

4
Core: Used in two or more shipped projects in this portfolio.Working: Used in at least one shipped project in this portfolio.

Writing

Notes from the build.

Short posts about the parts that break: leakage, calibration, regions, latency, and evaluation that tells the truth.

About

I care about the last mile.

Fourth year Data Science Engineering student. I build AI systems end to end and focus on evaluation, failure modes, and the last mile.

Education

Data Science Engineering

Abdelhamid Ibn Badis University

Fourth year of five / Remote

I build in Python and TypeScript. I start with a baseline, keep preprocessing inside the fold, and write down what the model cannot do. The interface is part of the system, not a layer added at the end.

Currently building

  • RAG retrieval evaluation

    In progress

    Freezing the eval set and comparing BM25 with the dense retriever.

  • ECG review flag calibration

    In progress

    Turning signal quality into a threshold a reviewer can trust.

  • This portfolio

    Shipped

    Filling missing facts and running the deployed audit.

Contact

If the work looks relevant, send the details.

Open to AI engineering and data science roles, remote. Tell me the problem, the data, and what a good result looks like. I reply with concrete next steps.

Start a conversation

Remote / response within 2 working days