I'm applying for the Senior Backend Engineer role at your team. I've spent 15+ years building backend systems that carry real traffic, and I'm looking for a team where engineering judgement and long-term ownership matter more than velocity for its own sake.

Most of my career has been in high-load products across e-commerce, fintech and nation-scale infrastructure. I've owned backend for products from zero to production, migrated systems under live traffic, and cut inventory synchronisation from 20 minutes to 2 with ClickHouse, batch integrations and incremental parallel processing. I'm at ease when a system's failure modes are the interesting part of the job.

Technically I'm strongest in Ruby and Rails, with PostgreSQL, Kafka, Redis, ClickHouse and Kubernetes as daily tools. I design event-driven services, treat DDD and observability as design constraints, and I've led monolith-to-microservices extractions and built frameworks other teams adopted. I also build LLM-powered features and agentic workflows in my own projects and on my HeavyTech podcast.

What draws me to your team is the shape of the problem: the parts that are genuinely hard, where the domain is unforgiving and backend decisions show up in the product. I want real scale, real constraints, and engineers who care about the details.

I work fully remote and keep European hours. I'd be glad to talk through how I can help your team ship a dependable backend, and I'm happy to answer anything the CV doesn't cover. Thank you for your time and consideration.