I build zero-downtime, distributed, and highly secure infrastructure for enterprise AI and SaaS platforms.
My work sits where product urgency meets operational risk: high-throughput backends, AI/RAG systems, cloud-native platforms, and engineering operating models that can survive real production load.
| Problem area | Outcomes I optimize for |
|---|---|
| High-throughput ingestion | Backpressure, idempotency, replay safety, queue isolation, predictable latency |
| Legacy modernization | Incremental migrations, strangler patterns, API boundaries, zero-downtime rollouts |
| AI system reliability | RAG pipelines, semantic caching, fallback routing, evaluation loops, cost controls |
| Platform engineering | Kubernetes delivery, observability, CI/CD, security posture, incident readiness |
- Fractional CTO for early and growth-stage product teams
- Cloud-Native Systems Architect for distributed backend and platform work
- DevSecOps Engineer for production hardening, delivery automation, and observability
- AI Infrastructure Engineer for RAG, semantic search, model routing, and token-cost optimization
- Production-grade TypeScript/NestJS architectures with strong domain boundaries
- Event-driven systems using PostgreSQL, Redis, BullMQ, Kafka, and NATS-style messaging
- Reliable AI pipelines with vector search, semantic caching, evaluations, and fallback paths
- Infrastructure that makes latency, failure modes, and cost visible before they become incidents
- Architecture decisions documented before abstractions harden
- Tests focused on contracts, failure modes, and business-critical flows
- Observability built around P95/P99 latency, error budgets, queue depth, and saturation
- Security treated as a design constraint: least privilege, secrets hygiene, audit trails
- Delivery process based on small PRs, conventional commits, CI, and production-minded reviews
I am a fit when the work needs more than feature delivery:
- You are shipping an AI or SaaS platform where reliability affects revenue or trust.
- Your system is growing past the point where ad hoc backend decisions still work.
- You need a technical partner who can design, implement, and explain the tradeoffs.
- You want production architecture, not a demo that collapses under real users.
- Website: https://myrix.site
- Calendar: ``
- Email:
msaricicek99@gmail.com - LinkedIn: Linkedin