Open to platform & SRE roles

Ilya
Papou

Site Reliability Engineer
/ Platform Architect

I build and operate the production platforms behind business-critical services — where reliability, observability and automation decide whether the business keeps running.

{{ t }}
IP · 2026
SRE · Platform Architect Remote / EU / US · Financial Crime Prevention
{{ s }}
02 — Why I'm a strong match

Requirements, mapped to real production experience.

I'm an SRE / Platform Architect building production platforms where reliability, scalability, observability and automation directly affect business-critical services — across financial services, iGaming, financial crime prevention, aviation and enterprise. My current work supports Anti-Fraud, AML and KYC workloads; I'm extending it into AI infrastructure and AI-assisted operations.

Requirement What I've actually done
{{ row.r }} {{ row.e }}
Current focus
{{ t }}

Comfortable in English-speaking engineering environments — written technical communication, documentation, incident discussions and async collaboration.

Philosophy

Reliable platforms are not created by manual operations. They are built through architecture, automation, observability and continuous engineering improvement.

Key takeaway

SRE / Platform Architect with production experience across Kubernetes, GitOps, observability, Financial Crime platforms and ML infrastructure.

03 — Current work

Reliability layer for real-time anti-fraud platforms.

{{ t }}

Every transaction is evaluated in real time, and every decision has to be available, observable and reliable. My role is to keep the infrastructure behind those systems resilient, scalable and continuously deployable.

Customer Request Real-time Transaction
Financial Crime Prevention Platform
{{ s }}
Platform Reliability Layer — where I contribute
{{ s }}
Cloud Infrastructure
My responsibilities
{{ r.t }}
{{ r.d }}

I also explore AI-assisted operational tooling as an extension of SRE practices — covered in AI Direction.

Key takeaway

I keep business-critical, real-time platforms reliable, observable and continuously deployable.

04 — Platform

How the platform fits together — and how it's built.

I work across the full platform stack: business-critical workloads, Kubernetes-based platform capabilities, infrastructure foundations, production operations, and the AI/MLOps direction I'm extending toward.

The stack — request flow ↓
Cross-cutting {{ c }}
Business Layer
AMLAnti-FraudKYCRisk ScoringDecision Engine
Platform Layer
KubernetesGitOpsVaultObservabilityCI/CD
Infra Layer
Bare MetalCloudNetworkingStorageMulti-Region
Ops Layer
On-callSLI/SLORCAAutomationRunbooks
↑ Production feedback
Extending toward
{{ e }}

A platform is not a list of technologies. It's a coherent stack of layers that must stay reliable as each layer changes underneath it.

The delivery path

Every platform I build follows the same delivery path — the real tools I run daily, from a developer's commit through production and back again as a feedback loop.

Developer Commit
{{ stage.name }}
{{ it }}
Production Feedback Loop
{{ it }}
Feeds back into the next commit — the loop closes and repeats.
{{ c.h }}
{{ c.d }}

A platform is not a one-way pipeline. It's a loop — production signals shape the next commit as much as the commit shapes production.

05 — Experience

Where I've built and operated production platforms.

From telecom security through Kubernetes consulting to leading DevOps functions and owning business-critical SRE platforms — each role compounds into the platform engineering I do today.

{{ job.co }} {{ job.scale }}
{{ job.role }}

{{ job.summary }}

{{ g.h }}
{{ it }}
{{ t }}
06 — Philosophy

The principles behind every platform I build.

{{ p.t }}
{{ p.d }}
Operational excellence

{{ opLead }}

{{ b }}
Architecture judgment
{{ b }}
Platform leadership
{{ b }}
07 — Decisions

Architecture decisions, with the trade-offs made explicit.

Senior platform work is mostly judgment. These are real decisions from production platforms — the problem, the choice, and what it cost.

Problem

{{ adr.problem }}

Decision

{{ adr.decision }}

Why
{{ w }}
Applied as
{{ w }}
Outcome
{{ w }}
Trade-off accepted

{{ adr.tradeoff }}

{{ t }}
Questions I ask before every decision
{{ q.t }}
{{ q.q }}
08 — Evolution

How my platforms — and I — have evolved.

Every migration below replaced something that worked with something that scaled — the pattern behind how I approach platform engineering.

{{ ev.from }} {{ ev.to }}

{{ ev.d }}

09 — AI Direction

Extending SRE practice into AI-assisted operations.

I already run production MLOps infrastructure — GPU Kubernetes, training pipelines, model serving. The next step is applying AI to operations itself: tooling that investigates, explains and acts under human supervision.

{{ a }}
Key takeaway

AI doesn't replace SRE judgment — it extends it. Reliable automation still needs someone who understands what reliable means.

10 — Final thoughts

What I'm looking for.

I'm looking for business-critical platforms where reliability, automation and observability directly affect product outcomes.

Engineering is ultimately about reducing complexity. Every platform I build aims to be:

{{ t }}

Thank you for taking the time to read my profile.