JAN HRABOVSKÝ / SENIOR BACKEND & AI VÝVOJ

Backend built to handle change.AI with a concrete purpose.

I design and build backend systems in PHP, Symfony and Nette. I help modernize legacy applications, develop APIs and integrations, and add AI where it delivers a clear product or operational benefit.

Backend topology connecting API, domain, data, queue, integrations and AI API DOMAIN DATA QUEUE INTEGRATION AI
PHP 8 · Symfony · Nette · Doctrine · SQL · Elasticsearch · Redis · Docker

SITUATIONS / 01

When a new requirement is not just another endpoint.

I usually join when a change cuts across old code, a database, queues, search or several external systems — and still has to ship without a big-bang rewrite.

  1. 01

    The roadmap is slowing down

    The team spends more time working around old code than building what the product actually needs.

  2. 02

    One change affects the whole system

    A feature touches data, integrations, performance and operations, and needs someone to keep the full context together.

  3. 03

    A technical area has no owner

    Tasks move between people, but nobody owns the design decisions and delivery into production.

  4. 04

    AI should be a feature, not a demo

    A real process can be automated, but the solution needs measurable quality, cost control and safe boundaries.

SERVICES / 02

How I can help

I can join an existing team or take ownership of a defined technical area. We start by clarifying the problem, the risks and a sensible scope for change.

01 Backend developmentNew features and long-term backend development

I build production applications in PHP, Symfony, Nette and Doctrine, covering APIs, data models, integrations, performance and reliability.

I choose solutions that fit the problem and that the team can continue to maintain safely.

02 Legacy modernizationMake an older system easier to change

I identify the parts of a system that slow delivery or create the most operational risk, then order the work by actual impact.

I prefer continuous refactoring, testable steps and migrations that keep the product running over a complete rewrite.

03 AI integrationsAI features with a clear operational benefit

I design integrations with language models, internal data, information extraction and automation for specific workflows.

The solution includes limits, logging, cost control and ways to verify output — not just an API connection.

PROJECTS / 03

Experience with complex systems

Client commitments prevent me from publishing names and internal figures. These examples describe the areas for which I held technical responsibility.

01 / PROJECT

E-COMMERCE / LONG-TERM DELIVERY

Complex European e-commerce platform

Long-term backend development of a large e-commerce platform with substantial product data, integrations and business logic.

MY WORK
Backend development, solution design, integrations, refactoring and continuous evolution.
Technology
PHP · Symfony · Doctrine · Elasticsearch · Redis · Docker
CATALOGUEPRICESTOCKSEARCH

02 / PROJECT

SAAS / INTERNAL SYSTEM

SaaS / internal business platform

Backend design and implementation, data flows and integrations with a focus on long-term maintainability and a clear domain model.

MY WORK
Backend architecture, APIs, integrations, implementation.
Technology
PHP · Symfony · SQL · REST API · Docker
DEVICEDOCUMENTINSPECTIONDUE DATE

03 / PROJECT

AI INTEGRATION / E-COMMERCE

An interface between product data and AI tools

Design of machine-readable access to product data and controlled interfaces through which AI tools can work with an e-commerce application.

MY WORK
AI readiness, agent APIs, machine-readable content, architecture.
Areas
AI search · Structured data · APIs · AI agents · MCP
E-SHOPINTERFACEAI AGENTACTION

COLLABORATION / 04

Context first. Code second.

  1. 01

    Understand the problem

    Before proposing a solution, I need to know the objective, constraints and current state of the system. A well-defined problem is often the most valuable first result.

  2. 02

    Work in verifiable steps

    I split changes so they can be deployed, measured and rolled back as we go. This reduces risk and gives the team useful results sooner.

  3. 03

    Design for production

    Performance, logging, failure modes, cost and maintenance are not afterthoughts. They belong in the design alongside implementation.

  4. 04

    Communicate as the work progresses

    I raise risks and unknowns early. I prefer short decisions grounded in the actual code and product over long presentations.

ABOUT / 05

More than 10 years building backend systems.

I am a senior backend engineer from the Czech Republic with a strong background in the PHP ecosystem, particularly Symfony, Nette and Doctrine.

Most of my work has involved long-running production systems where engineering means understanding not only the codebase, but also the domain, integrations and consequences of each change across the product.

In recent years I have also focused on practical use of language models in existing applications, including work with internal data, tools, production reliability and cost control.

I work best in long-term collaborations with product teams and on projects where I can take genuine ownership of a backend or technical area.

TECHNOLOGY / 06

Technical range

Backend

PHP · Python · Symfony · Nette · Doctrine

Data & infrastructure

PostgreSQL · SQL · MongoDB · Elasticsearch · Redis · Docker

Architecture

REST APIs · Integrations · DDD · CQRS · Messaging

AI

OpenAI · LLM integrations · AI agents · Tool calling · AI search readiness

CONTACT / 07

Need to move a backend forward or validate an AI use case?

Send me a few lines about the system, the current problem and the result you need. I will reply with whether and how I can help.