About Bz
Bz is my public identity: a backend-oriented full-stack profile built through a dated progression, demanding environments, structured studies and shipped projects. My work now connects backend architecture, web/mobile interfaces, data, tests, production, SEO and applied AI.
Path
2003 → 2026
Technical studies, demanding environments, network maintenance, web/mobile training, product experience and complete platform delivery.
Level
IS expert
Progression up to IT and information systems expert level, equivalent to a Master 2 level.
Scope
Full product
Backend, web, mobile, admin, data, realtime, AI, tests, production, SEO and observability connected through concrete projects.
Profile
My professional path is not based on a single technology. It combines systems, networking, backend, frontend, mobile, software quality and production delivery. This lets me read a product through its data, business rules, risks and user surfaces.
Early foundations in applied computing and applied sciences, with a systems culture that remains useful for reading modern architectures.
Seven years in a demanding and confidential environment strengthened discipline, reliability, endurance and execution responsibility.
IT maintenance, diagnostics, local networks, routing, Cisco, Fortinet and simple automation in concrete contexts.
WebForce3, Le Wagon, AFPA and AJC Formation structured the progression up to IT and information systems expert level.
Byrsa Tech strengthened practice across mobile apps, backoffices, APIs, dashboards, business platforms and real delivery.
Bz connects backend, frontend, mobile, data, realtime, AI, tests, SEO, documentation and production into maintainable systems.
Professional timeline
The thread is professional: technical foundations, field experience, structured studies, web/mobile development, backend architecture, quality, production and the current Bz ecosystem.
2003–2005
Higher studies in applied computing and applied sciences, with early systems foundations, technical logic and computing reasoning.
2006–2012
Seven years of service in a demanding setting, described with reserve: operational discipline, method, reliability, endurance and responsibility.
2012–2015
System diagnostics, maintenance, local networks, routing, Cisco, Fortinet and concrete understanding of operating environments.
2020–2021
WebForce3 structured professional foundations in web/mobile development, project logic, interfaces and delivery.
2021
Le Wagon strengthened Python, data, data-driven reasoning and the ability to explore technical problems analytically.
2022–2023
AFPA consolidated full-stack development, web/mobile applications, APIs and practices required for usable products.
2022–2025
Product experience across mobile applications, management platforms, backoffices, APIs, dashboards and business solutions with delivery constraints.
2023–2024
AJC Formation completed the progression up to IT and information systems expert level, equivalent to Master 2.
2024–2025
Recovery and structuring of a multi-surface social platform: NestJS backend, chat, notifications, realtime, auth and product consistency.
2025–2026
Complete systems built with NestJS, Next.js, Flutter/React Native, PostgreSQL, OpenAI-compatible, SEO, tests, production and documentation.
Mastery progression
This graph is explanatory and personal. It does not claim to measure a market; it shows where experience has become shippable practice.
Reading: foundations, practice, delivery, production
Internal signal, not a global statistic.
Linux, Windows Server, TCP/IP, routing, scripts and understanding of execution environments.
NestJS, Node.js, Java/Spring Boot, API contracts, Prisma, PostgreSQL, Redis and business logic.
Next.js, React, React Native, Flutter, public interfaces, dashboards, admin surfaces and user flows.
Jest, integration, E2E, Schemathesis, k6, ZAP, Stryker, smoke tests and OpenAPI validation.
VPS deployment, Docker, Caddy, multilingual pages, technical SEO, restrained analytics and hardening.
OpenAI-compatible chatbot, local AI, WebSocket, realtime messages and product integration.
From experience to product
The value is not the anecdote. It is how each stage becomes useful skill for a recruiter, a team or an existing product that needs structure.
Discipline
Delivery method
Move step by step, stay calm and prioritize paths that reduce risk.
Systems and network
Understandable architecture
Think constraints, flows, environments, security and operations from design time.
Studies restarted
Technical foundations
Structure learning through practice, schools, projects and documentation.
Real projects
Product delivery
Connect backend, interfaces, admin, mobile, data and business needs into usable releases.
Tests
Verifiable trust
Tie tests to real risks: contracts, regressions, performance, security and recovery.
Production
Responsibility
Prepare what must hold: deployment, logs, SEO, maintenance, documentation and continuity.
Capability cards
The global skill is not a cold list. It is the ability to make these layers work together in maintainable projects.
NestJS, Node.js, Java/Spring Boot, APIs, business rules, auth, contracts and services.
Next.js, React, multilingual content, SEO, performance and public interfaces.
React Native, Flutter, mobile journeys, notifications and API integration.
PostgreSQL, PostGIS, Prisma, Redis, MongoDB, models and data consistency.
WebSocket, chat, events, presence, notifications and live product flows.
Chatbot, OpenAI-compatible flows, local AI and useful user-journey integration.
Unit, integration, E2E, contracts, performance, security, smoke and mutation testing.
Docker, VPS, Caddy, scripts, logs, hardening and pragmatic operations.
Localized routes, metadata, sitemap, useful content and recruiter readability.
Linux, Windows Server, TCP/IP, environments, diagnosis and automation.
Built reflexes
The point is not a displayed promise. It is a set of working reflexes: understand quickly, structure existing systems, protect critical paths and make the work transferable.
Enter a project quietly, identify the real flows, isolate risk and make the technical state understandable.
Start with data, contracts, business rules, security and critical paths before polishing the interface.
Change context, rebuild the necessary foundations and progress without losing the product thread.
Think about errors, logs, performance, deployment, SEO, monitoring and maintenance before the system is exposed.
Test what truly protects the product: API contracts, validation, critical flows, security and regressions.
Write so the next team can understand, modify, operate and recover the system without starting again.
Explain clearly, ask for the right context and suggest human follow-up when the decision goes beyond code.
Working philosophy
I prefer to move in verifiable layers: API contracts, validation, logs, scripts, tests, documentation, deployment, technical SEO and first-party measurement. A serious product is not only something that works on screen: it must be understandable by the team, observable in production, readable by Google and recoverable without depending on one person.
Clarity before speed: understand the domain, data and risks before stacking screens.
Backend as the product backbone: business rules, contracts, security, transactions and permissions must hold the system.
Tests tied to real risks: validation, API contracts, critical flows, errors, regressions and production limits.
Interfaces as understanding surfaces: they should make the system readable, not hide fragile architecture.
Technical SEO from the start: metadata, sitemap, robots, localized routes, useful content, performance and structured data.
Clean measurement: first-party events, Google Search Console, Analytics, logs and usable signals without turning the site into a tracking machine.
Documentation as transfer tool: scripts, decisions, commands, constraints and procedures must outlive the first developer.
Maintainability as economic advantage: less debt, less dependency, easier recovery and stronger product confidence.
Contact
Freelance mission, recruitment, backend architecture, technical recovery, mobile platform, business backoffice or realtime system: the first step is to clarify the real need.