Rabindra Yadav

Rabindra Yadav / Software Development Engineer II

Software, infrastructure,
and everyday work.

I’m a software engineer at AWS in Austin. I work on database networking, with previous experience in Lambda and an interest in tools that make day-to-day engineering a little easier.

Areas I work inDNS & IPv6Fleet reliabilityServerless infrastructureApplied AI

01 / Selected contributions

Selected projects

Some of my work on database and serverless networking, with a little context on each project.

01

IPv6 support for RDS

I worked on networking workflows across 30+ AWS regions, including split-horizon DNS and validation for failover and network conversion.

AWS RDS · Go · Route 53 / 2025–2026

The engineering challenge

The same endpoint needs to resolve correctly inside and outside a VPC, over both IPv4 and IPv6. I built validation across nine critical failover and conversion scenarios to address migration risk before launch. More than 200 enterprises adopted IPv6 in the first 60 days.

Read project context
700K+public databases in the rollout
02

Separating networking from a larger service

I worked on moving Lambda networking logic into a dedicated gRPC microservice, using parallel initialization to reduce cold-boot time.

AWS Lambda · Java · gRPC / 2024

The architectural decision

Networking logic was coupled to a larger service. Extracting it established a dedicated service boundary and allowed initialization to run in parallel. The result was $3M in annual infrastructure savings and cold boots 180 seconds faster.

Read project context
$3Mannual infrastructure savings
03

Making operational knowledge easier to find

I built an AI diagnostic tool that retrieves relevant context from 10,000+ technical documents, helping on-call engineers investigate incidents faster.

Amazon Bedrock · Python · OpenSearch / 2025

Why this approach

Engineers were spending time searching runbooks during incidents. Retrieval over the existing technical corpus puts relevant documentation closer to the question, reducing investigation time by 74%.

Read project context
74%less investigation time
04

Reducing the DNS window during failover

I’m working to shorten DNS propagation after an RDS Multi-AZ failover, so customers can reach the standby database sooner.

AWS RDS · Go · Route 53 / In development

The reliability problem

A standby database can take over before DNS finishes propagating. That gap becomes downtime visible to customers. This work targets the propagation window, with a projected 70% reduction; this is a target, not a measured production result.

Read project context
70%projected reduction in propagation time

02 / Experience

My experience

Full experience & résumé
SDE II · AWS RDS

Platform networking, global IPv6 rollout, DNS reliability, and AI-assisted operations.

SDE I / II · AWS Lambda

Serverless compute networking. Promoted to SDE II in October 2024.

SDE Intern · AWS

Network health insights, automated error detection, and a return offer.

03 / A little context

A little about me

I grew up in Gaighat, Nepal, and came to Texas to study computer science at UT Arlington. Teaching other students was an early lesson in making complicated things understandable.

That instinct carries into my work today. Outside AWS, I explore iOS apps and AI tools — a chance to think about the person using the software as closely as the system running it.

More about my path

Get in touch

If you’d like to chat about my work or a project, feel free to reach out.

Get in touch