LinkedIn · Technical notes · Mail
Senior backend engineer with nine years across fintech, trading, payments and enterprise platforms — systems where reliability has to hold under high concurrency, large datasets, asynchronous workflows and real production incidents.
Grounded in Java, Spring Boot and distributed systems, with recent production work in Python, FastAPI and AWS. I care about explicit boundaries, observable behavior, and systems that stay understandable as traffic, data and teams grow.
| Area | Stack |
|---|---|
| Backend | Java · Spring Boot · Python · FastAPI · REST · microservices |
| Architecture | DDD · distributed systems · consistency · failure handling · async workflows |
| Data & search | PostgreSQL · MySQL · Redshift · Elasticsearch · Redis · Kafka · RabbitMQ |
| Cloud & ops | AWS · Docker · Kubernetes · CI/CD · tracing · performance tuning |
| Applied AI | Retrieval · evaluation · permission boundaries · human–agent workflows |
explicit boundary ─▶ encoded rule ─▶ tested failure path ─▶ measured result
- Clarity under pressure — a production system should stay legible when it fails.
- Architecture as code — boundaries belong in types, tests and CI, not only in diagrams.
- Evidence before claims — retrieval and performance changes need reproducible numbers.
- Agent-ready engineering — coding agents inherit the same constraints and feedback as people.
A few public repositories where I test ideas and write down trade-offs. Small, evolving, and honest about it.
- grounded-access — permission-aware retrieval with reproducible evaluation
- domain-driven-kit — Spring Boot DDD patterns and executable architecture rules
Open to backend and platform work where reliability, architecture and practical AI meet.
