Avadhut Pisal
Lead Software Engineer at DataBahn.ai
Pune, Maharashtra, India
Summary
🤩
Rockstar🎓
Top SchoolAvadhut Pisal is a Lead Software Engineer based in Pune with over eight years of experience designing and shipping scalable backend systems and cloud-native tooling. He has progressed through roles at MKCL and LogicMonitor to a leadership position at DataBahn.ai, blending hands-on backend engineering with DevOps and platform reliability. Avadhut is an active open-source contributor to the OpenTelemetry ecosystem, improving Kubernetes operator behavior, adding .NET auto-instrumentation support, and hardening Kafka receivers with better rebalance and offset handling plus unit test coverage. He brings a pragmatic focus on performance, resiliency, and deployment flexibility—evident in contributions like priorityClassName/affinity support and partition metrics—that help observability stacks run smoothly in production. Trained in Information Technology (B.Tech), he pairs strong practical experience with a consistent record of improving developer-facing infrastructure.
8 years of coding experience
6 years of employment as a software developer
Yashwantaro Chavan Insttitute of scienceB.Tech, Information Technology, B.Tech, Information Technology at Dr.Babasaheb Ambedakar Technological university10th, 10th at Shri Shivaji Highschool Karad
Stackoverflow
1reputation
175reached
0answers
2questions
Github Skills (20)
kubernetes10
testing10
kubernetes-operator10
go-testing10
go10
kubernetes-pods10
opentelemetry10
apache-kafka10
dotnet9
cicd9
net9
asp-net9
docker8
automations8
automation8
Programming languages (7)
Github contributions (5)
open-telemetry/opentelemetry-operator
Mar 2022 - Nov 2022
Kubernetes Operator for OpenTelemetry Collector
Role in this project:
Back-end & DevOps Engineer
Back-end & DevOps EngineerContributions:51 reviews, 11 commits, 17 PRs in 8 months
Contributions summary:Avadhut primarily contributed to the OpenTelemetry Operator, focusing on improving functionality and adding features related to Kubernetes and the OpenTelemetry Collector. Their work included refactoring code to improve efficiency, specifically with the implementation of break statements for resource reconciliation. They also added support for .NET auto-instrumentation, involving changes to build processes, testing, and configuration. Furthermore, they contributed to the addition of features like priorityClassName and affinity for the collector, expanding its deployment capabilities.
opentelemetry-collectoroperatorobservabilitykuberneteskubernetes-operator
open-telemetry/opentelemetry-collector-contrib
Jan 2023 - Jan 2023
Contrib repository for the OpenTelemetry Collector
Role in this project:Back-end Developer
Back-end DeveloperContributions:3 reviews, 2 commits, 6 PRs in 16 days
Contributions summary:Avadhut primarily contributed to the `kafkareceiver` component, addressing configuration issues related to Kafka consumer offsets and rebalancing. They implemented fixes for auto-commit configuration and rebalancing handling, improving the receiver's resilience. The user also added comprehensive unit tests for traces, metrics, and logs consumer, demonstrating strong focus on code quality. Furthermore, the user's work included the incorporation of performance metrics for partition start/close operations.
contribopentelemetry-collectortracingtempoobservability
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.