Pramod Baddam
Sr Java Developer at Infinite Computer Solutions Inc

FELLOW MEMBER
In the enterprise corridors where telecommunications meets software engineering, Pramod Baddam has built a career around a practical question: how do you turn sprawling, high-stakes infrastructure programs into predictable, secure, and repeatable software execution?
Across more than nine years in software development—progressing from early application programming roles into senior engineering ownership—Baddam’s work has concentrated on the systems that sit behind national-scale connectivity: the planning, orchestration, and data integrity layers that determine how quickly network teams can move from strategy to build-ready plans.
His longest-running and most consequential chapter is tied to Verizon’s network planning ecosystem. Working across multiple engagements supporting Verizon (via Infinite Computer Solutions, System Soft Technologies, and Apex Systems), Baddam contributed to a Network Planning Platform that bridges Radio Access Network and wired-network planning—software intended to reduce manual engineering effort, improve forecast accuracy, and accelerate market-level build decisions. This sits directly in the current reality of U.S. telecom: 5G expansion and densification depend on continuous upgrades, new site builds, and fiber-first transport decisions, often coordinated at scale through small-cell deployments and long-haul fiber initiatives. Industry reporting has described Verizon’s “One Fiber” approach as explicitly tying fiber rollouts to aggressive small-cell deployment strategies to support the economics and performance requirements of next-generation wireless.
Within that context, Baddam’s platform work centers on building enterprise-grade microservices—primarily in Java/Spring Boot—designed for reliability, security, and performance. His responsibilities, as described, include designing and optimizing REST APIs and integration layers; implementing CI/CD automation (Jenkins and GitHub Actions); containerizing services with Docker and deploying them to Kubernetes; and enforcing identity and access controls through OAuth2 and JWT-based authorization. He also describes applying Redis caching and database query optimization to reduce latency and improve resilience, paired with observability practices using Splunk, AWS CloudWatch, and ELK for root-cause analysis and operational readiness.
A distinguishing feature of his Verizon work is the focus on decision automation: the platform incorporates Machine Learning and AI models to generate predictive recommendations for build planning, aimed at supporting high-priority modernization programs and capital allocation. While the specific internal program names are Verizon-specific, the architectural intent is clear—codifying planning logic and using data-driven recommendations to compress cycle times, reduce integrity issues, and scale planning throughput. In his summary metrics, Baddam attributes outcomes such as a major reduction in manual effort, a large increase in planning capacity, and a substantial drop in data integrity defects—positioning the platform as an operational multiplier for engineering teams rather than “just another application.”
Earlier in his career, he built on a financial-services foundation at Bank of America, contributing to enterprise applications that interface with legacy investment and asset-management data—work that typically demands disciplined persistence-layer design, system integration (SOAP/REST), and strict security controls given regulatory and customer-risk considerations. Before that, he contributed to web application development in an earlier role at Indian Hosting, building baseline experience in Java/J2EE systems, services integration, and application-server operations—skills that later matured into modern microservices, cloud deployments, and security-first delivery practices.
Across these roles, the through-line is operational seriousness: systems that must be correct, secure, and explainable—because they support infrastructure planning and financial workflows where errors are expensive, and recovery windows are short.