I design and build ASP.NET Core backends: microservices behind an API Gateway, gRPC between them, and the Angular front end that uses them. I lead the team of four building AzertyUI's company platform this way.
Open to freelance projects · answers within the day
Absences, expenses, tickets, contracts and payslips in one place, on .NET (ASP.NET Core) microservices behind an API Gateway, talking over gRPC, with Angular 21 in front. I lead the four engineers building it, plus the company's server monitoring.
team of 4 led · microservices · gRPC · Angular 21
Five warehouse-management modules on tablets mounted on forklifts, integrated with Microsoft Dynamics 365 Business Central over C#/.NET and REST, in an enterprise stack I learned on the job.
5 modules shipped · D365 Business Central
We talk through the product, the users and what is slow or missing today. Thirty minutes is usually enough.
You get a scope in plain words and a first milestone we can both check against, quoted per project or per day.
Reviewable commits on your repository, tests that grow with each feature, and a deployed build you can click at every step.
Whichever the product needs. AzertyUI's platform is split into services because its domains (absences, expenses, documents, tickets) change independently; a smaller product is often better as one service.
Yes. On the AzertyUI platform the front end is Angular 21, built by the same team I lead.
It depends on the scope, so I quote per project or per day once the scope is written down. The first call and the written scope are free.
Nabeul, Tunisia, at UTC+1: a full European working day of overlap, plus the US East Coast morning.
English and French every day (both B2, English certified by TOEIC), and German at B1.