01 / Build
Laravel platforms that don't rot.
Backend APIs, queues, Inertia/Vue or Livewire UIs, integrations with SOAP/XML legacy partners and modern GraphQL services. Written to be read again in two years — by someone else.
Available for senior backend & DevOps work
Backend that ships, scales, survives.
Senior backend & DevOps engineer. I build and maintain Laravel + Vue platforms and the AWS infrastructure underneath them — the same code base, year after year. No revolving door. No vibe-coded fragility.
Working daily with
LaravelVue.jsNuxtPHP 8.xInertia.jsAWSCloudflareDigitalOceanVitePostgreSQLRedisOpenSearchAnsibleDockerLivewireNginxHAProxyHorizon
LaravelVue.jsNuxtPHP 8.xInertia.jsAWSCloudflareDigitalOceanVitePostgreSQLRedisOpenSearchAnsibleDockerLivewireNginxHAProxyHorizon
20+
Years building
production systems
production systems
7+
AWS services running
in production today
in production today
24/7
Uptime on systems
I own end-to-end
I own end-to-end
UA · EN
Languages I work in
across distributed teams
across distributed teams
What I do
Three things, done properly.
I'm not a full-team replacement and I'm not a Friday-night code dump. I'm the senior engineer you keep on retainer when the platform needs to stay alive — and keep growing — for years.
02 / Operate
Cloud infrastructure as code, not folklore.
AWS (EC2, Lambda@Edge, CloudFront, OpenSearch, S3, Route 53) and DigitalOcean droplets — provisioned with Ansible, documented, repeatable. Nginx, HAProxy, Let's Encrypt rotation, no 3am surprises.
03 / Modernize
Legacy code, brought back to life.
Framework migrations done sprint by sprint, with feature flags and a shared queue bridge — so the business never pauses while the codebase modernizes underneath it.
About
Senior engineer. Long-term hire.
I've spent the last two decades as the backend engineer who stays — owning the same systems across framework migrations, infrastructure rebuilds, and three generations of integration partners.
My natural habitat is a Laravel monolith with a Horizon queue, a relational database primary with a replica behind it, and an Ansible playbook that brings the whole thing back from scratch if it ever has to. I write code comments in English, ship features on feature flags, and treat infrastructure the same way I treat code: reviewable, reproducible, recoverable.
I'm based in Europe, work across Ukrainian and English, and prefer long engagements where I can own a system properly rather than rotate through them.
AI in the workflow
AI as amplifier — not autopilot.
I use Claude Code, Cursor and similar tools every day. They're force multipliers for the parts of the job that don't need a human — boilerplate, fan-out refactors, exploring an unfamiliar library, rubber-ducking through trade-offs.
But the code I ship still goes through my eyes line by line, and the architecture decisions are still mine to defend. AI accelerates the work; it doesn't replace the engineer who has to keep that code alive in production three years from now.
Claude Code
Cursor
Copilot
Agentic workflows
AI code review
Selected work
Real systems. Real years.
A snapshot of the systems I've owned end-to-end. Specifics under NDA where appropriate — happy to walk through architecture and trade-offs in a call.
Enterprise SaaS backend
Long-running Laravel platform serving multiple enterprise tenants from a single codebase. Horizon queues, primary/replica databases, OpenSearch full-text, Livewire admin. Owned end-to-end across backend, data, and AWS infrastructure.
1 codebase
many tenants · zero forks
Laravel · AWS
Enterprise integration layer
Bidirectional integrations with enterprise partners: WSDL/SOAP, industry-standard XML field extraction, URL-encoded webhook intake, Base64 document handling. Built so partner pipelines run unattended.
2-way bridge
SOAP in · webhooks out
PHP · XML
Legacy framework migration
Active modernization of a long-running legacy codebase to modern Laravel. Shared Redis queue bridge between old and new runtimes, feature-flagged rollout, Horizon as the single execution plane. Zero downtime, sprint by sprint.
0 downtime
incremental, feature-flagged
Horizon · Redis
AWS edge + search stack
CloudFront with Lambda@Edge for staging assets, OpenSearch Service inside VPC with IAM-signed requests from Laravel, S3 cross-account access patterns. All driven from Ansible — reproducible from zero.
IaC first
Ansible · documented · repeatable
AWS · Ansible
Stack
The tools I actually ship with.
Not a list of buzzwords — a list of things I've debugged at 2am and would happily debug again.
Backend
- Laravel (Horizon, Livewire, Sanctum)
- PHP 8.x (traits, enums, DTOs)
- Flux UI · Spatie packages
- Broadcasting · Ably
- RabbitMQ · Redis queues
- Legacy PHP framework maintenance
Frontend
- Vue.js 3 (Composition API)
- Nuxt 3 · SSR
- Inertia.js (Laravel adapter)
- Vite · HMR · bundling
- Tailwind CSS · Flux UI
- SFC components · design tokens
Infrastructure
- AWS · EC2 · Lambda · CloudFront
- S3 · Route 53 · CodeDeploy
- Cloudflare (CDN · DNS · WAF)
- DigitalOcean droplets
- Ansible playbooks
- Nginx · HAProxy
Databases & Search
- PostgreSQL · MySQL · MariaDB
- Schema design · primary/replica
- Redis (queues, cache, memory analysis)
- OpenSearch · Meilisearch
- pdphilip/opensearch-laravel
- SOAP · XML · REST · GraphQL
Workflow
- GitHub Actions · CodeDeploy · OIDC
- Sentry (self-hosted)
- n8n automations
- Shortcut · Slack
- Docker · docker-compose
- Home lab: TrueNAS · Proxmox
Have a backend that needs a senior engineer who stays?
I'm open to long-term engagements — full ownership of a platform, tech-lead seat on an existing team, or selective DevOps & migration consulting. Reach out wherever's easiest.