Senior contractor,
Contributing to L4F (A Legacy For Future), a platform helping organizations modernize legacy applications by centralizing visibility into code quality, technical debt, test coverage, and security risks — complemented by AI-powered documentation generation and an integrated AI assistant to accelerate developer workflows.
Contributed to a mobile banking application, delivering new features and improving maintainability within a legacy codebase.
Delivered a web app from scratch for CESI clients to manage occupational health, including appointments, medical forms, documents, and employee tracking.
Shipped self-service tools at Proximus to help enterprise clients manage employee mobile subscriptions, reducing reliance on support teams.
Delivered a shared mobile banking framework after migrating a legacy app, cutting development time and improving maintainability across clients like Rothschild & Nagelmackers.
Delivered a mobile and backend solution to port an existing security software to mobile. The project included store deployment and live presentation during the final defense.
I join product teams as a senior contractor and ship alongside your devs — respecting your standards, your stack, and your rhythm.
Modern Angular with Signals, NgRx, and a component architecture your team can extend without rewriting it six months later.
I help teams migrate off old Angular versions, untangle RxJS, and bring ageing front-ends back to a maintainable state.
Front-end to API to database — I own the whole feature, not just the Angular slice.
Capacitor builds from your existing Angular codebase. One codebase, iOS and Android, without a separate mobile team.
For founders and small teams without an in-house dev — I scope, build, and ship the product with you.
"We were blocked on a migration for two quarters before bringing Nasreddine in. He had the codebase mapped out by day two and the first working version shipped by end of week. I genuinely didn't expect that."
"He's the contractor you don't want to see leave. Even after his feature was done, the team kept going to him for architecture questions — not because they had to, but because they trusted him."
"Sent him a Figma and a rough spec on Monday. By Thursday we were in review. He pushed back on two decisions that would've caused us pain later — both times he was right."