{jc}
ES

Josue Correa

Backend Developer Peru

Backend Developer specialized in Laravel, PHP and MySQL. I design APIs and scalable web systems to automate business processes.

Get in touch View projects

Backend flow

200 OK

POST /api/v1/business-process

  1. 01 Validate request
  2. 02 Apply domain rules
  3. 03 Persist data
  4. 04 Return reliable response
Josue Correa, backend developer specialized in Laravel, PHP and MySQL

About

Code that powers real-world processes

Systems Engineer experienced in building financial solutions with Laravel, React and MySQL. I work from business rules toward reliable APIs, permissions and operational workflows, using structures designed to evolve without losing traceability.

  • Separation by domain

    Every business area lives in its own module, behind an explicit public boundary.

  • Access enforced on the server

    Session, per-action permission and branch scope are checked in the backend, never in the interface.

  • Verified changes

    Public routes are covered by tests: an internal migration never breaks an existing API consumer.

What I solve

Operational problems, not just code

When daily work runs on loose files and messages, the problem is not technology: nobody knows which copy of the data is the good one. That is where I come in.

The team moves data between spreadsheets, email and chat
One system where every record is stored with a date and an owner.
Each area works from its own version of the information
A single source of data, with permissions by role and by branch.
Finding out what happened to a payment means asking around
A searchable history of every operation, independent of who was on shift.

Experience

Engineering applied to real financial operations

  1. January 2026 — Present

    Software Developer

    Independent project

    End-to-End Credit Management Platform.

    • Modular architecture across nine domains.
    • Access control by user, role and branch.
    • Phased migration backed by contract tests.

  2. April — December 2025

    Web Developer

    Financial-sector organization

    Financial Disbursement Management System.

    • REST APIs with Laravel and a React frontend.
    • Centralized, traceable operation with no local files.
    • Incident support with the system in production.

Projects

Two financial systems: one in production, one being built

Financial Disbursement Management System

Centralize disbursements, payment validation, installments and financial reporting.

Manual steps in payment validation
−50%
REST endpoints in production
153
Automated test suites
21

Technical evidence

  • 153 REST endpoints behind a JWT session: loans, payments, installments, portfolio, arrears and rescheduling.
  • 21 feature test suites, one per critical controller: authentication, clients, portfolio, arrears, rescheduling and calculator.
  • Manual payment-validation steps cut by 50%, measured against the previous process.
  • Financial reports generated from system records instead of parallel spreadsheets.
View technical detail
Context
A financial operation supported by local files and manual checks, with information scattered across different roles.
Solution
A web system that structures the operational flow, centralizes information and improves payment and disbursement traceability.
Role
Web Developer
Technical decision
Separated the API, business rules, interface and persistence responsibilities to reduce coupling and simplify maintenance.

Production

HTTP / API
Use cases
Disbursements domain
Business rules
Persistence and audit

End-to-End Credit Management Platform

Cover the full credit lifecycle — admissions, evaluations, credits and portfolio tracking — on a modular base that grows in phases.

Modular business domains
9
Of the API verified on every change
100%
Access scopes: user, role and branch
3

Technical evidence

  • 118 public routes frozen in a contract test that pins the method, URI, controller and middleware of each one.
  • Nine domains defined, each an independent module with its own public boundary.
  • Authorization at three levels: JWT session, granular per-action permission and branch scope.
  • Domain layer free of framework dependencies; modules talk only through public Actions and Queries.
View technical detail
Context
Nine business domains with their own rules, evaluation that differs by client type, and access scoped by user, role and branch.
Solution
A modular monolith: each domain is a module with its own public boundary and dependencies running one way; the internal layers land module by module.
Role
Full-stack development
Technical decision
The Domain layer does not depend on the framework, and no module reaches into another module’s tables or internal classes: it only consumes its public Actions and Queries.
Contract test excerpt 
// RouteContractTest.php

['GET', 'api/v1/business-process',
  BusinessProcessController@index,
  ['jwt', 'permission:process.list']],

['PATCH', 'api/v1/business-process/{id}',
  BusinessProcessController@update,
  ['jwt', 'permission:process.edit']],

Each row pins the method, URI, controller and middleware. If a migration changes them, the test fails before the frontend does.

In development

Http · controllers, requests, resources
Application · use cases and transactions
Domain · business rules
Infrastructure · persistence and adapters

Technologies and tools

My development stack

Core stack

  • Laravel
  • PHP
  • MySQL

Frontend

  • React
  • JavaScript
  • Tailwind CSS

Tools

  • Git
  • Docker

Contact

Let’s build a solution ready to grow

Have a project, a proposal or need technical support? Send me a message and we can review how I can help.

Email contacto@josuecorreaq.com — Open LinkedIn linkedin.com/in/josuecorreaqu — Open GitHub github.com/josuecorreaq — Open X x.com/josuecorreaqu — Open