Complete responsibility
Architecture, implementation, quality and delivery responsibility are presented together.
Projects
Selected systems with real architecture beneath the surface.
The selected work below is framed as engineering proof: what kind of system was involved, what the product needed, which surfaces were delivered and where the technical responsibility lived.
Bz Info project map
Product engineering Gantt
A project view as delivered systems: need, architecture, technical surfaces, quality and ownership.
Architecture · Surfaces · Proof
Need
Architecture
Backend
Frontend
Mobile
Quality
Delivery
Framed
Delivered
Verified
Active reading
Platform core
Application foundation focused on business rules, APIs, authentication, data and server consistency.
Backend system
Delivered surfaces
Structured APIsDomain servicesPersisted data
Technical ownership
Backend architecture, API contracts, data models and application security.
FramedDeliveredVerified
Platform coreBackend system
Need
Architecture
Backend
Frontend
Mobile
Quality
Delivery
Application foundation focused on business rules, APIs, authentication, data and server consistency.
APIAuthDomainData
Delivered surfaces
Structured APIsDomain servicesPersisted data
Technical ownership
Backend architecture, API contracts, data models and application security.
Public surfaceProduct website
Need
Architecture
Backend
Frontend
Mobile
Quality
Delivery
Public pages designed for understanding, SEO, structured content and clear experience.
UXSEOi18nContent
Delivered surfaces
Public pagesSEOReadable journey
Technical ownership
Interface, content, accessibility, responsive rendering and editorial consistency.
Business backofficeOperations interface
Need
Architecture
Backend
Frontend
Mobile
Quality
Delivery
Internal tools to operate data, control flows and make business operations visible.
BackofficeAuditOps
Delivered surfaces
ManagementAuditBusiness tracking
Technical ownership
Admin models, access security, business actions and operational readability.
Mobile appUser product
Need
Architecture
Backend
Frontend
Mobile
Quality
Delivery
Mobile journeys centered on onboarding, sessions, device context and useful error states.
FlutterAuth UXDevice
Delivered surfaces
OnboardingSession flowMobile UX
Technical ownership
Flutter experience, auth UX, screen states and backend communication.
Realtime flowsEvent system
Need
Architecture
Backend
Frontend
Mobile
Quality
Delivery
Interactions connected to events, notifications, messages or contextual synchronization.
EventsWebSocketQueues
Delivered surfaces
EventsRealtimeNotifications
Technical ownership
Events, WebSocket, queues, integrations and state consistency.
Quality pipelineTechnical proof
Need
Architecture
Backend
Frontend
Mobile
Quality
Delivery
Checks that turn a project into a measurable system instead of a visual showcase.
Testsk6ZAPStryker
Delivered surfaces
CoverageSchemathesisStryker
Technical ownership
Tests, OpenAPI contracts, performance, dynamic security and mutation testing.
Factual scope
Project scope stays factual and avoids invented client metrics.
Multi-surface proof
The work highlights frontend, backend, mobile, infrastructure, documentation and hardening whenever they belong to the system.
Proof graph
Each project is read as a system with surfaces, responsibility and proof.
The matrix avoids presenting projects as screenshots only: it shows which surfaces were actually touched, from interface to backend and quality signals.
Project
Web
API
Admin
Mobile
SMS
Quality
Coverage
Luchtreiniger Pro / Afzuigkapreinigenhoreca.nl
67% mapped
Glimpse
50% mapped
Socializus / P4W
50% mapped
SmsService
83% mapped
French Foreign Legion — IT duties in a confidential environment
17% mapped
Luchtreiniger Pro / Afzuigkapreinigenhoreca.nl
67% mappedWebAPIAdminMobileSMSQuality
Glimpse
50% mappedWebAPIAdminMobileSMSQuality
Socializus / P4W
50% mappedWebAPIAdminMobileSMSQuality
SmsService
83% mappedWebAPIAdminMobileSMSQuality
French Foreign Legion — IT duties in a confidential environment
17% mappedWebAPIAdminMobileSMSQuality
Case 01 - Professional multilingual web platform
Luchtreiniger Pro / Afzuigkapreinigenhoreca.nl
A production-oriented B2B web ecosystem designed to present services, structure demand acquisition, handle leads and deliver an operable platform in Dutch and English.
A complete business-facing platform with acquisition, business logic and operations — not a brochure page.
5
Scope
8
Stack
OK
Signal
Product and technical scope
- NL / EN multilingual public website
- Next.js frontend and SEO-oriented content architecture
- Backend, forms, leads and business workflows
- Back-office, VPS infrastructure and deployment documentation
- Quality baseline, build verification and progressive hardening
Stack and proof signals
Next.jsNestJSTypeScriptMultilingual SEOLead workflowBack-officeVPS / DockerDocumentation
Case 02 - Advanced modular backend and social mobile product architecture
Glimpse
A dense backend and product foundation for a social mobile application, with complex domains, deep quality strategy and strict responsibility boundaries.
Architecture depth, testing pressure, validation rigor and product design shaped for serious production readiness.
5
Scope
10
Stack
OK
Signal
Product and technical scope
- Multi-domain NestJS backend architecture
- Prisma, PostgreSQL, PostGIS and complex business rules
- Auth, chat, notifications, wallet, gamification, billing and referrals
- Full quality chain: k6, Schemathesis, unit, integration, E2E, smoke, ZAP and Stryker
- Testing documentation, global runners and API / test repository separation
Stack and proof signals
NestJSPrismaPostgreSQLPostGISk6SchemathesisJestE2EZAPStryker
Case 03 - Multi-surface product recovery and technical reconstruction
Socializus / P4W
A clarification and reconstruction effort spanning mobile application work, backend design, chat, notifications and maintainability, with one concrete objective: making the system understandable and evolvable for a small team.
A practical recovery mindset for systems that need clarity, lower risk and stronger foundations again.
5
Scope
8
Stack
OK
Signal
Product and technical scope
- React Native application for iOS and Android
- Backend recovery, chat, notifications and product-flow consistency
- Architecture decision between isolated chat microservice and modular NestJS monolith
- Maintainability designed for a small team, handover and future contributors
- Documentation, flow stabilization and progressive hardening
Stack and proof signals
React NativeiOS / AndroidNestJSRealtime chatNotificationsProduct reconstructionDocumentationQuality hardening
Case 04 - Public Android SMS gateway prototype
SmsService
A public Kotlin Android prototype that turns a controlled phone into a local SMS gateway for consent-based transactional messages, with backend integration constraints and explicit security limits.
A small but concrete public repository showing Android, backend integration, local infrastructure thinking and security boundaries.
5
Scope
8
Stack
OK
Signal
Product and technical scope
- Android foreground service running on a controlled phone
- Local HTTP-like endpoint for backend-triggered SMS requests
- Shared-secret validation and French mobile number restriction in the prototype
- GitHub documentation, build instructions and local network usage notes
- Security framing: visible secrets must be rotated and the gateway must stay private
Stack and proof signals
KotlinAndroidSmsManagerLocal gatewayBackend integrationConsent-based SMSGitHub publicSecurity hardening
Case 05 - Technical experience under demanding constraints
French Foreign Legion — IT duties in a confidential environment
An IT experience carried out in an environment where rigor, discretion, reliability and service continuity were part of the expected standard.
A formative experience, presented with restraint, that helps explain my current standards for architecture and reliability.
4
Scope
6
Stack
OK
Signal
Product and technical scope
- IT duties performed within a confidential framework
- Experience with demanding environments and strong operational constraints
- Responsibility, continuity and technical reliability as working habits
- Operational discretion: no sensitive or confidential detail is exposed
Stack and proof signals
ConfidentialityReliabilityRigorTechnical responsibilityContinuityDiscretion
What these projects demonstrate
A portfolio becomes strong when it shows responsibility across the whole system.
Backend architecture, public interfaces, mobile products, admin workflows, infrastructure, documentation, quality and operating constraints are not separate arguments. They are the ingredients of systems that can be understood, delivered, maintained and improved.
360°
System scope
Not only screens
1
Clear ownership
An assumed technical zone
✓
Deliverable proof
Visible and measurable quality
System responsibility map
Each area shows a technical responsibility: need, interface, backend, data, operations and quality.
Responsibility · System · Proof
Bz Info
Responsibility
System proof
System proof
Active responsibility
Backend and API
The backend carries rules, access, validation, API contracts and business consistency.
System core
Associated proof
API contractsBusiness rulesSecurity
Connected surfaces
APIDataQuality
Proof loop
A serious project does not stop at development: it must be understood, structured, verified, hardened and maintainable.
Active step
Separate responsibilities, define contracts and choose a durable structure.
Delivered surface matrix
This matrix connects visible surfaces to less visible responsibilities: business flows, risks, operations and maintenance.
Web
API
Admin
Mobile
Data
Quality
Visibility
Business flow
Ownership
Risk reduction
Maintenance
Project conversation
Have a system that needs to become clearer, stronger or production-ready?
Use the contact page to share a product, platform or recovery context. The form is structured around the same request types supported by the backend.