I'm Kiril — a language-agnostic backend developer with 4+ years building high-throughput queues, S2S tracking pipelines, and validation APIs for performance-marketing platforms. The kind of engineering that cuts cost and recovers revenue.
Three backend systems where the outcome showed up on the invoice or the revenue line — not just in the changelog.
Architected a high-throughput SMS messaging queue and a custom Short URL Tracking Service that compresses payloads to fit inside 1–2 SMS segments (the 160-character limit) — directly shrinking per-message billing at scale.
Built a complex server-to-server tracking lifecycle with automated fallback logic: when a partner hits its revenue or CPA cap, traffic is rerouted in real time to alternative destinations instead of being lost.
Engineered a multi-layer subscriber validation API using selective backend verification and smart caching — keeping traffic quality high while paying for the expensive verification checks only when they actually matter.
I'm a language-agnostic backend developer with 4+ years shipping systems that live in production. I care less about which framework is trendy and more about the goal: lower cost, recovered revenue, fewer 3am incidents.
Most of my work sits where engineering meets the business — tracking, messaging, and validation systems for performance-marketing platforms, where a 1% efficiency gain is real money. A background in media buying and sales means I read a brief in terms of outcomes, not tickets.
I work well owning a system end-to-end as a sole developer, or embedded in a team. Either way, you get someone who thinks about the whole product.
Grouped by how often I reach for it — and honest about where I'm still ramping up.
Lessons from building backend systems. First posts shipping soon.
Got a backend that's too slow, too costly, or too fragile — or a system to build from zero? Tell me what you're shipping. I reply within 24 hours.