What I do
I am Moez Zhioua, an automation engineer and full-stack developer based in Tunisia. I design workflows and software that connect business systems, move information reliably, and give operators a clear recovery path when something fails. My current work covers n8n, Python, TypeScript, APIs, operational data, practical AI integrations, and web applications.
I also develop connected business systems through LeanOrchestr. Business Brain work focuses on permission-aware access to company knowledge, source-backed answers, and controlled actions. OutreachGenie is a separate product project focused on structured LinkedIn outreach workflows. Its case study documents the architecture and evidence boundaries. The ChatGPT workflow guide explains how drafting and review fit without handing campaign state to a language model, while the automation consulting page describes the commercial scope.
How work is represented here
This website is a professional portfolio and technical reference. Service pages describe the work I currently offer. Project pages distinguish product screens, implementation decisions, client-approved evidence, and illustrative demo data. Articles are written to help someone reproduce a technical step or make a better system decision. A screenshot is not presented as a production result when it is only a mockup or controlled example.
Some client details cannot be published. When confidentiality limits a page, I describe the architecture, safeguards, and testing approach without inventing a company name, revenue result, or private metric. Readers should use the public profiles and linked source material below to verify credentials that matter to them.
How an engagement works
Start with one real workflow
The first useful conversation is about a specific process, the systems involved, who owns each business rule, and what a safe result looks like. If the work is a fit, I prepare a written scope with assumptions, deliverables, acceptance checks, timing, and price. Production access and paid work do not begin from an introductory call alone.
Build for operation and handoff
The implementation includes failure paths, alerts, validation, and a clear owner for exceptions. Handoff material covers configuration, normal runs, failure recovery, and the agreed acceptance results. Platform subscriptions, new requirements, and vendor changes are kept separate from defects in the agreed scope.
Public verification
These independent profiles and records provide additional context about my work and professional history. They are linked directly so you can check the current source rather than relying on a badge copied into this website.
- Toptal professional profile
- Upwork work history and reviews
- LinkedIn professional profile
- GitHub repositories and public code
- ORCID research identity
The research and publications page collects peer-reviewed work, reproducible technical notes, and the source records used to verify each publication.