Anirudh Aithal
Principal Software Engineer at Amazon Web Services (AWS)
Seattle, Washington, United States
Summary
🤩
Rockstar🎓
Top SchoolAnirudh Aithal is a Principal Software Engineer based in Seattle with 11 years of experience building cloud-native infrastructure at AWS, specializing in container and virtualization technologies. He has deep hands-on expertise in ECS, containerd, Firecracker microVMs and CNI networking, contributing upstream improvements that enhance cross-platform portability and VM configuration control. At AWS he progressed from SDE roles into principal-level engineering, driving backend and DevOps work that bridges scheduler, runtime and storage concerns. His open-source contributions include adding FirecrackerConfig support to firecracker-containerd and refactoring CNI/plugins for non-Linux platforms, demonstrating a focus on maintainability and platform compatibility. Known for pragmatic design and strong dependency management, he often surfaces behind-the-scenes improvements—like safer argument parsing and build-tagged platform separation—that reduce long-term technical debt. He holds an M.S. in Computer Science from Stony Brook and blends systems-level rigor with production-scale delivery.
11 years of coding experience
6 years of employment as a software developer
BE Computer Science and Engg, BE Computer Science and Engg at B. M. S. College of EngineeringMaster of Science (M.S.) Computer Science, Master of Science (M.S.) Computer Science at Stony Brook University
Github Skills (29)
kubernetes10
firecracker10
container10
docker10
multiplatform10
apidoc10
cross-platform10
dockers10
networking10
containerd10
go10
api10
aws10
virtualization10
kubernetes-pods10
Programming languages (3)
Github contributions (5)
blox/blox
Nov 2016 - Dec 2016
Open source tools for building custom schedulers on Amazon ECS
Role in this project:
Back-end Developer & DevOps Engineer
Back-end Developer & DevOps EngineerContributions:26 commits, 2 PRs, 1 push in 29 days
Contributions summary:Anirudh primarily focused on back-end development, implementing features such as dependency retrieval and artifact generation. They added targets for obtaining dependencies and integrated generated handler client artifacts into the project's source code. Furthermore, the user performed code cleanup by removing hardcoded values, improving error messages and logs. Additionally, the user made changes related to CLI support, including introducing a queue flag and refactoring the main routine.
ecsamazonschedulersawsamazon-ecs
containernetworking/cni
Feb 2017 - Sep 2017
Container Network Interface - networking for Linux containers
Role in this project:Back-end Developer
Back-end DeveloperContributions:7 commits, 6 PRs, 13 comments in 6 months
Contributions summary:Anirudh focused on refactoring and improving the portability of the CNI project by making it compatible with non-Linux platforms. The user refactored code to separate Linux-specific functionalities, like network namespace operations, using build tags and platform-specific implementations. They also updated dependencies, specifically the vishvananda/netlink library, and addressed type safety issues within the project's argument parsing logic. The user's work demonstrates a strong focus on code maintainability and cross-platform compatibility for the CNI project.
containersnetwork-interfacenetworkinglinuxdocker
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.