IC

Iheb Chatti

Full-stack product engineering, scalable APIs, async workflows, and cloud delivery

About

A clear view of my background, approach, and how I build.

Senior full-stack engineer with 4+ years of experience building production APIs, workflow-heavy platforms, user-facing applications, and cloud-ready systems with strong ownership across delivery.

Portrait of Iheb Chatti

Profile

Senior Full-Stack Engineer

Positioning

Full-stack product engineering, scalable APIs, async workflows, and cloud delivery

Availability

Available for remote roles and relocation

Focus

Best aligned with senior full-stack, backend, platform, and product engineering roles where reliability, architecture clarity, frontend execution, and delivery quality matter.

Career progression

A progression toward broader system ownership and stronger architecture responsibility.

2021 - 2022

Cyberme

Backend Engineer

Internal APIs, validation automation, and release-support workflows.

DjangoPythonBrowserStackDeployment tooling
Started building engineering productivity systems and delivery-oriented backend tooling.

2021 - 2025

Lokafy

Full-Stack Engineer

Booking workflows, partner integrations, reusable product components, and cloud delivery participation.

DjangoDRFFlaskReactVueGCP
Expanded from feature delivery into architecture-aware API design, workflow consistency, and scale-focused decisions.

2025 - 2026

Aktisea

Full-Stack Engineer

Workflow orchestration, admin tooling, compliance-heavy backend logic, and mentoring support.

SymfonyPHPTwigAsync processingMonitoring
Moved into stronger backend ownership, operational reliability thinking, and technical leadership signals.

Approach

Engineering philosophy grounded in production responsibility.

I optimize for systems that stay legible under change: explicit workflow rules, safe asynchronous execution, and operational clarity that helps teams ship without accumulating hidden fragility.

Ownership means understanding how backend decisions affect operators, users, and future maintainers.

Reliability comes from clear state transitions, retry-safe workflows, and observability that explains what the system is doing.

Long-term maintainability matters most in workflow-heavy products where complexity grows faster than UI surface area.