PHP backend
I build application logic, endpoints, validation, and service layers so business rules do not disappear inside controllers. I work with Symfony, Laravel, and plain PHP codebases.
PHP Backend Developer / Backend Software Engineer
PHP Backend Developer - backends, APIs, and integrations for business systems.
I build PHP backends, design REST APIs, and connect applications with external systems. I work with payments, order flows, legacy PHP, and business applications that need to stay maintainable after the first release.
- Availability
- Available for employment and B2B
- Focus
- PHP backend, REST APIs, integrations
- Contact
- kontakt@solidapps.pl
Availability
- employment and B2B are both real options,
- profile: PHP Backend Developer / Backend Software Engineer,
- my strongest fit is PHP backend, APIs, integrations, and business systems.
Common scope
- REST APIs, API integrations, webhooks, and payments,
- order processes, data imports, SQL, and Docker,
- legacy PHP, PHP refactoring, and backend tests.
What I specialize in
PHP backend for applications that support a real business process.
REST APIs and contracts
I design endpoints, response statuses, validation, and documentation so frontend and backend can move without constant clarification.
Integrations and webhooks
I connect applications with external systems while paying attention to webhook signatures, retries, diagnostic logs, and events that arrive twice or late.
Payments and business flows
I am interested in flows where a mistake costs more than a broken form: checkout, order statuses, refunds, imports, and background operations.
Legacy PHP and refactoring
I clean older code in small steps: separate responsibilities, add tests around critical paths, and reduce regression risk before larger changes.
Tests, Docker, documentation
For important flows I leave tests, a simple run guide, and clear technical assumptions. It makes review, onboarding, and returning to the project easier.
Selected projects
Projects described as case studies, not as a repository list.
Each project shows the context, problem, solution, stack, and what had to be watched on the backend side. Some repositories are private until the work is closed. The page shows project scope, technical decisions, and operating scenarios. I treat UI projects as API consumer examples and contract work, not as a shift toward a separate specialization. I can discuss the code during a technical conversation.
22 projects visible
No project matches the selected filters. Change the query or category.
How I work
First the flow, data, and risks. Then the code structure.
I like to start by understanding what should happen in the system and what must not break. That makes tests, documentation, and responsibility boundaries follow the problem instead of a trend.
Principle
I do not complicate architecture without a reason.
-
01
Flow first
I check what data enters the system, which statuses appear along the way, and where a failure would cost the most.
Result: clear first-change scope and risks to watch. -
02
Contracts and boundaries
I define request, response, error statuses, and module responsibilities before a controller starts growing in every direction.
Result: less guessing between frontend and backend. -
03
Small changes and tests
For critical paths I add tests, readable errors, and a simple run scenario. Refactoring happens in steps, not as a rewrite.
Result: working flow and lower regression risk. -
04
Context for the next person
I leave README notes, commands, assumptions, and areas worth watching after release or during further development.
Result: easier review and maintenance.
For important changes I check
- whether the flow has a test or demo scenario,
- whether an error has a predictable status and message,
- whether a webhook, job, or import can be retried safely,
- whether the next person can run the project.
About
Business-system backend without pretending to be an agency.
I am a PHP Backend Developer focused on business systems. My strongest areas are APIs, integrations, payments, refactoring, and organizing existing code.
Approach
clear boundaries, stable flows, less chaos during further development
Closest fit
PHP, Symfony, Laravel, REST APIs, integrations, SQL, Docker
I like
projects where data, statuses, errors, and maintenance matter
I avoid
architecture added only to make a project look more serious
Tech
The stack I most often work with.
PHP and frameworks
PHP, Symfony, Laravel, Composer, PSR, application services, and work with code without a large framework.
Data
MySQL, PostgreSQL, Doctrine, Eloquent, PDO, indexes, CSV/JSON imports, and slow-query analysis.
APIs and integrations
REST API PHP, OpenAPI, webhooks, API integrations, JWT, OAuth 2.0, RBAC, and contract error handling.
Quality
PHPUnit, Pest, PHPStan, Psalm, php-cs-fixer, smoke tests, and tests for critical backend paths.
Environment
Docker, Docker Compose, Nginx, PHP-FPM, GitHub Actions, application logs, and monitoring basics.
Architecture when useful
Modules, queues, outbox, simple ADRs, and decisions described clearly enough to revisit later.
Looking for a PHP Backend Developer?
I am open to an employment role, a B2B contract, or a concrete backend problem. My closest areas are PHP, REST APIs, integrations, payments, legacy, and business systems.