00 / Index

Software engineer
Full-stack, realtime & workflow systems

Morocco
31.7917° N, 7.0926° W

Local --:--:--
Open to work

01Workflow platforms
02Realtime interfaces
03Full-stack product systems

I map the behavior beneath a product - roles, states, APIs and realtime flows - then shape it into interfaces people can trust.

View selected workGitHub ↗Download CV

Abdeljalil Wahib

Scroll — follow the work from workflow to code

Workflow logic
underneath.Product clarity
above it.

01 / Selected work

Where behavior becomes product.

Selected projects where process, data and interaction had to line up before the interface could feel simple.

01PHOVA Workflow PlatformFeatured case study
02HoloboardRealtime collaborative whiteboardLive
03SnapShopE-commerce single-page applicationLive
04MinishellUnix shell implementation
05Interactive Visual WorkSupporting work

01 / 05 — Featured case studyPHOVA Technology / Confidential product

PHOVA Workflow Platform

A business-facing platform for shaping commercial-offer and tender-response work into structured roles, statuses, APIs and persisted state.

Role: Software engineering intern - requirements analysis, frontend, backend and workflow integration
Stack: Next.js · TypeScript · FastAPI · PostgreSQL · SQLAlchemy
At: PHOVA Technology

Fig. 02 — Opportunity lifecycle

One record, five stages, four responsibilities — access and notifications follow the work

01.1 — Context

Commercial opportunities move through sales, sourcing, technical evaluation and leadership review. The product had to reflect the real handoffs behind the work.

01.2 — Problem

Each role needed the right view of the same record, with workflow rules that made responsibilities clear instead of duplicating manual spreadsheets.

01.3 — What I built

01Translated ambiguous operational requirements into role-aware product behavior.
02Built and integrated frontend screens, backend APIs and relational persistence.
03Worked on status-driven handoffs, commercial-offer flows and module integration.

01.4 — System

Next.js and TypeScript on the interface; FastAPI, SQLAlchemy and PostgreSQL beneath it, with workflow state modeled explicitly.

02 / 05 — Realtime collaborative whiteboard

Holoboard

A collaborative canvas product with persistent rooms, drawing tools, live cursors, avatars, undo/redo and synchronized room state.

Role: Full-stack engineer - realtime architecture, canvas behavior and product UI
Stack: Next.js · TypeScript · React Konva · Socket.IO · Node.js
Live: holoboard-navy.vercel.app

Fig. 04 — Event stream

Canvas state, cursors and room events shared between clients over Socket.IO

02.1 — Context

Several users can draw, move, undo and interact in the same workspace, while each browser needs to stay responsive locally.

02.2 — Problem

The interface has to feel immediate, while room state, cursors and drawing operations stay synchronized over the network.

02.3 — What I built

01Realtime Socket.IO events for shared room updates and live cursors.
02Canvas interactions for drawing, selection, undo/redo and persistent whiteboard rooms.
03A distinctive holographic interface built with Next.js, TypeScript and React Konva.

02.4— Liveholoboard-navy.vercel.app

Visit landing page

03 / 05 — E-commerce single-page application

SnapShop

A storefront SPA with product filtering, persisted cart state, authentication-oriented flows and checkout interactions.

Role: Frontend engineer - application state, product flows and responsive UI
Stack: Next.js · React · Redux Toolkit · Sass
Live: snapshop-ajwahib.vercel.app

Fig. 03 — State graph

A shopping session connects products, filters, cart state and checkout intent

03.1 — Context

Product lists, filters, cart state and checkout decisions form a graph of user intent across the shopping session.

03.2 — Problem

The application needs predictable state transitions so filtering, cart updates and checkout actions stay clear across navigation.

03.3 — What I built

01Dynamic product filtering and cart persistence.
02Redux Toolkit state management for product and checkout behavior.
03Responsive UI translated into production-ready frontend components.

03.4 — System

A Next.js frontend with React state boundaries and Redux slices modeling product discovery, cart state and user actions.

03.5— Livesnapshop-ajwahib.vercel.app

Visit landing page

04 / 05 — Unix shell implementation

Minishell

A custom shell implementation that recreates core Bash behavior through parsing, process control, signals, pipes and redirection.

Role: Systems programmer - parser, builtins, process execution and memory discipline
Stack: C · Unix · Signals · Pipes · Parsing

Fig. 01 — Command lifecycle

Input line -> parser -> execution branches, gated by syntax rules and cleanup

04.1 — Context

A shell starts as a line of text and becomes a controlled execution plan across processes, files, pipes and environment state.

04.2 — Problem

Parsing and execution need strict boundaries: syntax rules, expansion, redirection, signal behavior and process lifecycle.

04.3 — What I built

01Command parsing, tokenization, environment expansion and built-in commands.
02Pipes, redirects, heredoc handling and process execution.
03Signal handling and careful memory management in C.

04.4 — System

Low-level Unix programming made visible: every command passes through parsing, validation, execution and cleanup.

05 / 05 — 3D, graphics and UI studies

Interactive Visual Work

A supporting layer of 3D models, graphics projects and frontend challenges that sharpen visual judgment and implementation detail.

Role: Designer-developer - 3D modeling, graphics programming and interface implementation
Stack: Blender · C · Graphics · HTML · CSS · JavaScript
Status: Supporting work

Fig. 05 — Visual foundation

Visual and graphics practice feeds back into sharper interface craft

05.1 — Inputs

Blender scenes, raycasting graphics work, fractal rendering and pixel-focused frontend implementation exercises.

05.2 — Output

A broader visual and technical foundation that feeds back into product UI, interactive behavior and polish.

02 / Experience

Foundations you can feel in the product.

Production workflow software, realtime products and 1337 systems work all feed the same engineering habit: understand the behavior first.

L.01 — Surface
PHOVA Technology
Software Engineering Intern
Production workflow software
Translated stakeholder workflows into application behavior across frontend screens, backend APIs and persisted data.
Worked where sales, sourcing, technical review and management requirements needed to become concrete product state.
- Workflows
- FastAPI
- PostgreSQL
- Product UX
L.02 — Interactive
Holoboard
Full-stack Engineer
Realtime web product
Built a collaborative whiteboard around synchronized room state, drawing behavior, live cursors and a distinctive visual interface.
- Socket.IO
- Canvas
- React Konva
- Next.js
L.03 — Foundation
1337 Coding School / 42 Network
Project-based systems curriculum
Software engineering
Built foundations through C, C++, Unix systems, algorithms, memory management, networking, graphics programming and technical defenses.
- C
- C++
- Unix
- Algorithms
- Networking

03 / System

Every tool has to explain the work.

Grouped by how I use them: product interfaces, backend state and interactive behavior. Select a technology to trace it back to the work.

01 Product engineering

The product layer - what people touch

02 Backend & systems

The runtime layer - state, data, transport

03 Visual & interaction

Interaction layer - motion, canvas, graphics

Also - Docker · Git · technical writing · peer review

Method

How I turn requirements into software.

i
Read the workflow
Start with roles, handoffs and state before choosing the interface.
ii
Make behavior explicit
Turn ambiguous requirements into clear rules, screens and API paths.
iii
Build the foundation
Model data, permissions and transitions so the product remains maintainable.
iv
Polish the interaction
Use responsive UI, motion and interaction details to make the system feel clear.

Engineering strengths

01Workflow and product thinking
02Full-stack implementation
03Realtime interaction
04Relational data modeling
05Systems-level debugging
06Responsive interface craft

Portrait of Abdeljalil Wahib — Abdeljalil Wahib

04 / About

I look for the hidden logic before I touch the screen.

I came to software through systems - C, Unix, algorithms and networking at 1337 - then kept moving toward interactive products on the web.

Now I work where those meet. Workflow state, APIs, realtime updates and data underneath; clear flows and interfaces on top. I like software that makes a complicated process feel inevitable.

Based in: Morocco
Studying: 42 Network (1337)
Languages: Arabic — Native English — Professional French — Intermediate
Open to: Full-stack, frontend and software engineering roles

05 / ContactAvailable for full-stack, frontend and software engineering opportunities

Bring the workflow.
I'll make it product.

Write to

ajwahib.dev@gmail.com

Code
github.com/Abdeljalil-Wahib ↗
CV
Download CV (PDF) ↓
Based in
Morocco
Local time
--:--:--

I look for the hidden logic before I touch the screen.

I came to software through systems - C, Unix, algorithms and networking at 1337 - then kept moving toward interactive products on the web.

Now I work where those meet. Workflow state, APIs, realtime updates and data underneath; clear flows and interfaces on top. I like software that makes a complicated process feel inevitable.

Based in: Morocco
Studying: 42 Network (1337)
Languages: Arabic — Native English — Professional French — Intermediate
Open to: Full-stack, frontend and software engineering roles

Abdeljalil WahibAbdeljalilWahib

Workflow logicunderneath.Product clarityabove it.↑ Screens · decisions · people↓ Roles · state · APIs · realtime

Where behavior becomes product.

Foundations you can feel in the product.

PHOVA Technology

Holoboard

1337 Coding School / 42 Network

Every tool has to explain the work.

01 Product engineering

02 Backend & systems

03 Visual & interaction

How I turn requirements into software.

I look for the hidden logic before I touch the screen.

Bring the workflow. I'll make it product.

Abdeljalil WahibAbdeljalilWahib

Workflow logicunderneath.Product clarityabove it.↑ Screens · decisions · people↓ Roles · state · APIs · realtime

Where behavior becomes product.

Foundations you can feel in the product.

PHOVA Technology

Holoboard

1337 Coding School / 42 Network

Every tool has to explain the work.

01 Product engineering

02 Backend & systems

03 Visual & interaction

How I turn requirements into software.

I look for the hidden logic before I touch the screen.

Bring the workflow. I'll make it product.

Abdeljalil Wahib

Workflow logic
underneath.Product clarity
above it.

Bring the workflow.
I'll make it product.

Abdeljalil Wahib

Workflow logic
underneath.Product clarity
above it.

Bring the workflow.
I'll make it product.