Real-time betting: Worked on betting systems where correctness, speed, and financial safety mattered more than presentation.
>cat about.md
# A deeper look into who I am
~/about.md
background
I am a staff-level engineer who grew into leadership by taking responsibility for systems that need to work under pressure. At SCAYLE, that means leading checkout while staying close to the backend and platform details that affect reliability.
My strongest work usually starts where product scale meets operational pain: noisy alerts, brittle flows, unclear ownership, or systems that only look fine until traffic arrives. I like tightening those edges until the system is boring in production.
how it started
My interest in engineering started early, when the mobile web still felt experimental. I built WML pages back when phones were only beginning to browse the internet, and I learned by working inside tight technical limits.
Later I built a text-based game in PHP4 with SMS payments. Watching mobile operators take roughly 50% of the revenue was frustrating, but it also made the business side of software very real to me. That project is a big part of why I chose to pursue software engineering professionally.
current focus
Right now my work is centered on checkout reliability, observability, and the operational quality of payment-critical flows. That means staying close to incidents, understanding where the system becomes hard to reason about, and fixing the parts that create avoidable noise for the team.
- Led checkout through Black Friday 2025 peak tenants at roughly 550 orders per minute with zero downtime in the domain I was responsible for.
- Owned the cleanup of noisy monitoring and on-call signal so incidents became easier to trust, triage, and sleep through.
- Promoted into the lead role after pushing design docs, proposals, and reliability improvements that changed how the team operated.
different kinds of systems
A big part of my experience comes from working on systems built for very different purposes. I have not stayed inside one product category, and that range changed how I think about tradeoffs, risk, and what good engineering looks like in different environments.
Warehouse and logistics: Built warehouse workflows and shipping integrations for automotive e-commerce, including DHL, DPD, and UPS.
Startup product work: Helped take Atobi from an early startup product into a more mature engineering setup while the team scaled.
Search-heavy systems: Rebuilt search for anwalt.de with GraphQL, geolocation, aggregations, and range filters for millions of monthly users.
High-load commerce: Now focused on checkout at SCAYLE, where reliability and operational quality matter under heavy traffic and peak events.
what matters to me
Before SCAYLE, I rebuilt search at anwalt.de and later helped modernize platform foundations across engineering. Before that, I led delivery for Atobi at Solutionlab, scaling the team from 3 to 10 while keeping architecture and execution practical.
I care about direct communication, understandable systems, and engineering environments where the next person can reason about what is happening. The goal is not flashy tech. The goal is software that keeps working and a team that can keep moving.
Languages
PHPGoTypeScript
Frameworks
LaravelSymfonyReact
Databases
RedisMySQL
Infrastructure
Road-RunnerFrankenPHPKubernetesDockerAWSDatadogSQSSNSGitLab CIk6
Practices
RESTMicroservicesPHPUnitJestCypressPlaywrightgRPC