Hovhannes B.

Senior backend engineer, 11+ years in PHP, working mainly on systems where the hard part is not writing the code but deciding how it should work. I am most useful when something is already complex or already hurting — architecture that needs rethinking rather than extending, data models that no longer match what the business actually does, performance that has stopped responding to easy fixes, or a codebase that has to be brought back to a standard while it keeps serving production traffic. I take work from design through to delivery and stay responsible for it afterwards. Most of what I get asked to do is the part nobody else wants to own. SYMFONY — MY MAIN ENVIRONMENT Where I work day to day and where I go deepest: application and service architecture, Doctrine data modelling and migrations, console commands, message-driven and asynchronous processing, profiling and optimisation, and upgrades across major versions. This is what I want most of my work to be. LARAVEL Production Laravel experience, including in regulated and data-sensitive domains. I own applications end to end and move between both ecosystems without friction. SHOPWARE & ECOMMERCE Several years on Shopware 5 and 6 at agency scale — plugin architecture, migrations, marketplace and ERP synchronisation, and the transactional edge cases that only appear in real order flows. I still take this work, selectively. TOOLS PHP · Symfony · Laravel · Doctrine · MySQL · PostgreSQL · ClickHouse · Elasticsearch · Redis · RabbitMQ · Blackfire · Docker · Linux · PHPUnit · Git I can work across the frontend when a project needs it, but the backend is where I add the most value — so that is what I would rather be hired for. Tell me what you are building, or what is breaking, and I will tell you honestly whether I am the right person for it.