Software engineer · Laravel, full-stack & application security

I build web applications with a focus on reliability, maintainability, and security.

Backend and full-stack engineering across legacy and current Laravel codebases, with a practical approach to security and architecture: software that teams can understand, run and extend.

Discuss a projectHiring or collaborating?Explore selected work ↓

Direct:contact.chebaby@gmail.com

Fig. 1. The part users don’t see is the part that has to work.

How I can help

Five related areas of work. The labels say how established each one is, so you know what to expect.

  1. Backend & Full-Stack Engineering

    Core strength

    Laravel and PHP applications with React interfaces: business logic, integrations, APIs and an architecture the next developer can follow.

  2. Application Modernization

    Core strength

    Improving applications that already exist: refactoring legacy functionality, updating dependencies and frameworks, and making the code easier to maintain.

  3. Application Security

    Focus area

    Security as part of application engineering: access control, input handling, dependency management and hardening, plus review of application-level risks. This is engineering work, not a formal audit or certification.

  4. Deployment & Infrastructure

    Hands-on

    Getting applications into production and keeping them there: server configuration, Docker-based environments, queues, background workers and operational maintenance.

  5. Pragmatic AI Integration

    Exploring

    Assessing where AI genuinely improves a product or workflow, and exploring suitable integrations. It is an area I am actively learning, not a long commercial track record.

Selected work

Five projects. Each one states which part was my own work, and the artwork is illustrative rather than a screenshot.

Illustrative concept artwork for Tradix. Not a screenshot of the application.

Mobile scavenger hunt game / Backend engineering

Tradix

An interactive scavenger hunt game built around real-world exploration. Players take timed hunts, alone or in groups, completing missions based on questions, QR codes or augmented reality, and earn points and rewards. I worked on its backend, admin tools and deployment.

Role Full-stack Engineer — Backend & Deployment

  • Laravel 13
  • React 19
  • Docker Compose
  • Laravel Reverb
  • +5 more

Mobile scavenger hunt game / Backend engineering

Tradix

An interactive scavenger hunt game built around real-world exploration. Players take timed hunts, alone or in groups, completing missions based on questions, QR codes or augmented reality, and earn points and rewards. I worked on its backend, admin tools and deployment.

This describes the Laravel web application in the repository (React, TypeScript and Inertia), not a native mobile app.

Illustrative concept artwork for Tradix. Not a screenshot of the application.

My role

Full-stack engineer on the Tradix Laravel application, focused on backend engineering and on getting the application ready to run in production.

The platform itself handles timed play sessions, group play with leaderboards, a points system and protection against duplicate mission rewards. That design belongs to the codebase as a whole; my own contributions are the ones listed below.

Contribution

  • Production deployment setup: a containerized stack that runs the web application, background jobs, scheduled tasks, real-time messaging and the database as separate services, so each can be managed on its own. This describes the configuration, not how a live deployment performed.
  • Mission-location administration: reworked the admin controls for a mission’s location with coordinate checking, radius presets and clearer errors that keep the admin’s input for correction, backed by frontend tests for edge cases and accessibility.
  • Deployment script: production environment configuration and a script improved for error handling and the order of its commands.
  • Seeding reliability: fixed a seeding failure reported in production by correcting how the admin and user factories generate fake data.

Technologies

  • Laravel 13
  • React 19
  • Docker Compose
  • Laravel Reverb
  • TypeScript
  • Inertia.js
  • Nginx
  • MariaDB
  • Vitest
Discuss similar work
Illustrative concept artwork for Doctori. Not a screenshot of the application.

Healthcare / Practitioner platform

Doctori

A healthcare platform connecting patients with practitioners for discovery, booking and consultations. I implemented its ophthalmology module: specialized clinical records, practitioner-level access control and automated follow-up reminders for ophthalmologists.

Role Full-stack Engineer — Healthcare Domain

  • Laravel 8
  • PHP 7.4 / 8.x
  • Blade
  • JavaScript
  • +4 more

Healthcare / Practitioner platform

Doctori

A healthcare platform connecting patients with practitioners for discovery, booking and consultations. I implemented its ophthalmology module: specialized clinical records, practitioner-level access control and automated follow-up reminders for ophthalmologists.

Doctori handles sensitive healthcare data, so this entry shows no patient information, clinical records or application screenshots, and the artwork is conceptual.

Illustrative concept artwork for Doctori. Not a screenshot of the application.

My role

Full-stack engineer on an existing, multi-contributor Laravel platform, contributing to its ongoing development and maintenance. The ophthalmology module is the work I can attribute most directly to myself; I also made a smaller correction to the prescription PDF.

The wider platform lets patients find practitioners and book appointments or remote consultations, and gives practitioners tools for patients, consultations, prescriptions, documents and invoices. The ophthalmology module extends that practitioner application with eye-care records such as vision exams, eye pressure readings and eyeglass or contact-lens prescriptions. It reuses the platform’s existing patients, practitioners and login instead of becoming a separate application.

Contribution

  • Specialized data model: designed how ophthalmology records attach to a consultation and to the platform’s existing patients and practitioners, so nothing in the core system is duplicated.
  • Access control: a patient can be linked to several practitioners, so a patient ID alone must not unlock their eye-care records. Access is limited to ophthalmologists and to the practitioner who owns each record, with tests for both cases. This is application-level access control, not a security audit.
  • Automated follow-ups: a daily scheduled job creates reminders for prescription renewals and annual checkups, and saving a high eye-pressure reading or a cataract or LASIK procedure creates a follow-up reminder. These are workflow reminders, not medical advice.
  • Clinical interface: built the consultation screens, including an interactive eye diagram and a pressure chart, and removed the patient’s age from the prescription PDF.

Technologies

  • Laravel 8
  • PHP 7.4 / 8.x
  • Blade
  • JavaScript
  • MySQL
  • PHPUnit
  • Spatie Media Library
  • Laravel Snappy
Discuss similar work
Illustrative concept artwork for ABRID. Not a screenshot of the application.

Business platform / Backend architecture / Infrastructure

ABRID

A multilingual platform where project holders, partner organizations and administrators manage projects, program participation and submissions. I was the primary developer in its initial phase and set the application’s architecture, later supporting its infrastructure and maintenance.

Role Primary developer, initial phase

  • Laravel 11
  • PHP 8.2+
  • Docker Compose
  • Laravel Horizon
  • +5 more

Business platform / Backend architecture / Infrastructure

ABRID

A multilingual platform where project holders, partner organizations and administrators manage projects, program participation and submissions. I was the primary developer in its initial phase and set the application’s architecture, later supporting its infrastructure and maintenance.

The repository is private and the project is government-funded, so this is a sanitized summary: no source code, screens or internal data are shown, and the artwork is conceptual.

Illustrative concept artwork for ABRID. Not a screenshot of the application.

My role

Primary application developer during the initial phase. I made the initial architecture decisions, deliberately following established Laravel conventions so the application stays easy to understand and easy for newcomers to join, and I later supported the project through infrastructure and maintenance. Another contributor also worked on the application.

The application was built by more than one developer. The highlights below are the parts I can attribute to my own work.

Contribution

  • Program and project matching: a weighted ranking that matches projects to programs using eligibility criteria.
  • Workflow logic: selection of a project holder’s lead active project, workflow middleware, and event-driven notifications with activity recording.
  • Architecture and modelling: set the initial structure and modelled how projects, programs and their support relate, following Laravel conventions, with feature tests for partner authentication.
  • Infrastructure and maintenance: Docker build and Compose changes, container healthcheck corrections, and hands-on server maintenance, application installations and environment configuration. Measured results are not covered here.

Technologies

  • Laravel 11
  • PHP 8.2+
  • Docker Compose
  • Laravel Horizon
  • MySQL
  • Redis
  • Nginx
  • PHP-FPM
  • Pest
Discuss similar work
Illustrative concept artwork for Agadir Medina Showroom. Not a screenshot of the application.

Early-stage Laravel project / Data modelling

Agadir Medina Showroom

An early-stage Laravel project exploring a digital showcase for Agadir’s artisanal products. I set up the application and designed the data model for artisan profiles and localized biographies. The showroom itself is unfinished.

Role Software Engineer — Backend Development

  • PHP
  • Laravel 8
  • MySQL
  • Eloquent ORM
  • +2 more

Early-stage Laravel project / Data modelling

Agadir Medina Showroom

An early-stage Laravel project exploring a digital showcase for Agadir’s artisanal products. I set up the application and designed the data model for artisan profiles and localized biographies. The showroom itself is unfinished.

Status: early-stage, work in progress. The checked-in application is unfinished, and this entry links to the public source repository rather than to a live showroom.

Illustrative concept artwork for Agadir Medina Showroom. Not a screenshot of the application.

My role

I set up the initial Laravel application and designed its artisan and localized-biography schema. This is early work from two commits, and there is no functioning public showroom.

The repository describes an online showroom for artisanal products in several languages, but what is checked in is unfinished: the homepage is still Laravel’s default page, with no gallery, product browsing, e-commerce or working language switching.

Contribution

  • Initial application setup: a conventionally structured Laravel project as the base for the showcase.
  • Artisan data model: profiles with shared identity details, such as name, unique email and an active flag, kept apart from language-specific content.
  • Localized biographies: a separate biography per language for each artisan, with the database preventing duplicates and removing translations together with their artisan. The models are basic and no translation retrieval exists yet.

Technologies

  • PHP
  • Laravel 8
  • MySQL
  • Eloquent ORM
  • Blade
  • Laravel Mix
View the source on GitHub (opens in a new tab)Discuss similar work
Illustrative concept artwork for Fundbid. Not a screenshot of the application.

Financial / Real-estate platform

Fundbid

A French-language real-estate financing platform connecting borrowers with lenders. Borrowers submit financing requests for a purchase, construction or loan redemption, and lenders respond with offers. I contributed backend and full-stack features within a multi-developer team.

Role Software Engineer — Backend & Full-Stack

  • PHP
  • Laravel 5.6
  • MySQL
  • Eloquent ORM
  • +3 more

Financial / Real-estate platform

Fundbid

A French-language real-estate financing platform connecting borrowers with lenders. Borrowers submit financing requests for a purchase, construction or loan redemption, and lenders respond with offers. I contributed backend and full-stack features within a multi-developer team.

Fundbid is a multi-developer codebase and a private repository. This entry describes only my own contributions, and no borrower data, documents or application screenshots are shown.

Illustrative concept artwork for Fundbid. Not a screenshot of the application.

My role

Backend and full-stack developer in a multi-contributor Laravel codebase. I did not build or own the whole platform; this describes the specific work I can attribute to myself.

Borrowers and co-borrowers provide financial details and documents, lenders review eligible requests and submit offers, and an accepted application is transferred to an agent. Fundbid supports applications and offers; it is not a bank or a lender. The platform as a whole was built by a team.

Contribution

  • Demand lifecycle automation: a scheduled command that automatically closes financing requests older than a configurable period. Its production schedule is not covered here.
  • City search: replaced loading a full city list into each of the three request forms with search-as-you-type, coordinating the form, a search endpoint and a database index. No benchmark was taken, so there is no speed claim.
  • Transfer document: made the PDF in the accepted-application transfer more accurate and complete, covering borrower and co-borrower details, living arrangements, income and profession information, and financing summary labels and dates.
  • Data consistency: fixed co-borrower reuse so submitted details update the existing record, and prevented duplicate transfer notifications and an offer display bug.

Technologies

  • PHP
  • Laravel 5.6
  • MySQL
  • Eloquent ORM
  • Blade
  • JavaScript
  • Laravel DomPDF
Discuss similar work

How I approach the work

Principles behind the technical decisions I make on any project.

  • Conventions over cleverness

    I follow established framework and industry conventions where they fit, so a new developer can find their way around quickly.

  • Built to be maintained

    Clear structure and naming, with software a team can understand, change and extend after I have moved on.

  • Business logic, modelled properly

    Complex workflows deserve explicit, readable code. I model the real process before reaching for tools.

  • Security from the start

    Access control, input handling and dependencies are design decisions, not a final checklist.

  • Ready for production

    Deployment, queues, workers and maintenance are part of the job, not an afterthought.

  • Pragmatic about technology

    I weigh trade-offs and technical debt before choosing tools, and that includes AI: I will say plainly when a simpler approach is the better one.

Let’s talk about the work.

A few lines is enough to start. Tell me about the project, the role or the idea, and I will reply by email.

Project enquiries

New applications, improvements to existing ones, or a review of application-level security.

Employment & collaboration

Open to engineering roles and to collaborating with teams and other developers.

Prefer email? contact.chebaby@gmail.com

This form does not send anything by itself. It opens your email app with your message filled in, and nothing is delivered until you send it from there.