Aman Kumar Sahu

I build large scale distributed systems. I design fault tolerant backend architectures. I specialize in reliability, performance, and correctness. I solve systems problems others avoid. My engineering approach is simple. Reduce failure. Improve throughput. Remove bottlenecks. Strengthen guarantees. At Microsoft I built core Azure DNS systems . I managed fleets of 2,000 bare-metal servers. I automated lifecycle operations end to end. I engineered resilient health systems for DNS. I cut mitigation time by seventy percent. I validated billions of DNS queries. I reduced billing disputes at cloud scale. I built API driven automation across clouds. I strengthened backend services with deep observability. I designed integration suites for reliability. I ensured flawless rollouts across global clusters. I delivered systems that stayed predictable under stress. At Uber I moved deeper into critical path systems. I built high availability routing in Go . I enforced strict RBAC boundaries for VIP workflows. I achieved 99.99 percent routing reliability. I eliminated unauthorized access attempts entirely. I built validators that prevented misroutes. I reduced incorrect transfers by eighty five percent. I cut unattended tickets by ninety percent. I saved millions in operational cost impact. I handled high pressure on-call rotations. I managed Kafka failures. I mitigated KCP issues. I handled latency spikes with rapid triage. I kept uptime above 99.9 percent. I work across distributed systems technologies daily. Go. C#. Python. Java. Apache Kafka. Apache Flink. Flink jobs. Dual write patterns. Event driven designs. Cadence Cron. Chronos timers. Async orchestration. Concurrency control. Idempotent workflows. High throughput pipelines. I design systems for scale. For durability. For observability. For clean failure handling. If your team builds mission critical systems. If y