Backend engineer with 8 years of experience, currently a team leader at a US company where I lead a team of six and own the most business-critical system in our platform.
I build distributed systems in Go — event-driven microservices communicating through Kafka, running on Kubernetes with autoscaling, gRPC between services, and full observability with Prometheus, Grafana and Loki.
My work tends to land where correctness under concurrency matters: exactly-once processing on top of at-least-once transport, atomic session rotation, and payment integrations where a duplicate isn't a bug, it's someone's money. I've integrated WinRed, Revv, Stripe, CommerceGate and Payable, and built a multi-subscription billing system.
I'm looking for a role where Go and distributed systems are the core of the work.
I lead the backend side of a six-person team, and I'm responsible for the platform's most business-critical system.
My work covers the full lifecycle: I lead projects from planning through architecture, implementation and release, rather than picking up specs someone else defined. I make and drive the architecture decisions across the product's modules, review the team's code, and interview candidates for the team.
On the technical side I work across backend services, infrastructure and deployment — building event-driven systems, integrating third-party payment providers, and writing internal tooling in Go for data and infrastructure operations. I also act as the technical point of contact for Product, scoping work, surfacing edge cases and setting priorities.
Designed the architecture for and led a team of 4 developers building a content subscription and live-streaming platform, from design through production over ~12 months — 12+ Laravel microservices in an event-driven architecture (RabbitMQ), deployed on Kubernetes.
Designed and maintained core product microservices, including: authentication (Laravel Sanctum), transactional email (Twilio Sendgrid), real-time broadcasting and chat (Pusher/Laravel Echo), and payment processing (Stripe Cashier).
Improved platform performance through Redis caching, queues, batches, and asynchronous processing.
Assembled the main Makefile containing the Docker setup for every microservice, standardizing deployment across the whole platform.
Led technical interviews and hiring for the backend team; managed sprint planning and task estimation via GitLab; reviewed and corrected pull requests across the team.