Khubaib Rahman

I’m a backend engineer who genuinely enjoys building systems that don’t fall apart under pressure.

Outside of work, I enjoy hiking and long walks — anything that clears the head and forces you to think in layers. That same mindset shows up in how I approach backend engineering: I like understanding how things connect beneath the surface, not just making APIs return 200 OK.

Professionally, I work at Jio Platforms as a Backend Engineer, building high-performance microservices and distributed systems using Java, Spring Boot, Kafka, and Go. A lot of my work revolves around reliability, async orchestration, CDC pipelines, and DRaaS-related recovery workflows — systems that must stay consistent and predictable even during failure scenarios.

I’ve built async validation frameworks that improved throughput 12×, reduced sync failures by 60%, and cut real-time propagation delays by 85%. I care deeply about latency, fault tolerance, and clean architecture. I don’t just ship features — I think in terms of system behavior under load, observability, and long-term maintainability.

I enjoy solving hard backend problems: • Scaling services

• Debugging production bottlenecks

• Designing event-driven systems

• Improving data consistency across distributed components

I’m also curious about where backend engineering is heading — especially AI-driven automation layered on top of resilient systems.

If you’re looking for someone who understands performance, distributed systems, and real-world production constraints — not just tutorials — we’ll work well together.