// 02 — skills
Six disciplines, one goal: back-end systems that are fast, correct and still easy to change years later.
Symfony and Spring Boot for large, long-lived domain models. Laravel and Node.js when speed of delivery matters most. Go for concurrent, low-latency services such as real-time market data, and Python for scripting and AI glue code.
Software ships in containers: reproducible Docker images, Kubernetes for orchestration and CI/CD pipelines in Jenkins, GitHub Actions or GitLab CI that take code from merge to production. On smaller footprints, Coolify and systemd on well-kept Linux servers do the same job with less ceremony.
Picking the store that fits the access pattern: MySQL and PostgreSQL for transactions, MongoDB for documents, QuestDB for high-volume time series and Elasticsearch for search. Redis and Memcached keep the hot paths fast; NATS and Kafka move events between services.
Designing systems that stay correct when parts of them fail: services that talk through events, APIs with clear contracts, and caching and load balancing planned from day one instead of bolted on later.
Bringing LLMs into real products rather than demos: prompt engineering for GPT and Claude, n8n pipelines that generate, review and deploy content, and self-hosted agents with their own identity, memory and tool configuration.
Leading teams of four to six developers through structured planning, code review and architecture guidance — keeping delivery predictable and making sure knowledge never lives in just one person’s head.
// how it fits together
The same skills, arranged the way a request actually meets them — from the edge down to the platform.
L0 EDGE
Where requests arrive — balanced, cached and served close to the user.
L1 API
Clear, versioned contracts in front of the domain logic.
L2 CORE
The business rules — and, increasingly, the LLMs working beside them.
L3 EVENTS
Events and workflows that let services move independently.
L4 DATA
The right store for every access pattern — and a cache in front of the hot ones.
L5 PLATFORM
Containers, pipelines and servers that make every deploy boring.
// git log --career
Where these skills were earned — commits since 2010, newest first.
Domain Leader / Team Lead, Senior Software Engineer
Architecting back-end platforms and leading the team that builds them — system design, code review and delivery ownership for services that have to run reliably under pressure.
Senior Software Engineer
Senior back-end engineering: building and hardening production services and their integrations.
Senior Software Engineer
Senior back-end engineering across APIs, data models and the day-to-day running of production systems.
Team Lead / Senior Software Engineer
First lead role: running a development team while shipping web platforms and products end to end.
Software Developer
Initial commit. Custom websites and e-commerce builds for clients — the foundation for everything after.
// contact
A new platform, a system that has outgrown its architecture, a team that needs a lead, or an idea that needs an LLM behind it — send a message on LinkedIn and let’s talk it through.