David Allampally
DevOps Engineer
15years in tech
10years in DevOps
SeniorDevOps Engineer
6/10CI/CD Pipelines
Overview
Cloud-focused DevOps engineer at a senior level specializing in AWS-native infrastructure and Kubernetes with a strong emphasis on IaC and automated remediation. The strongest proven skill is cloud infrastructure design and automation as shown by Terraform EKS and IAM modules with IRSA, KMS secrets encryption and a linked GitHub Actions pipeline (AegisHeal/terraform/modules/eks/main.tf and Telecom-Microservices-Platform/.github/workflows/ci-backend.yml). There is limited public evidence of remote Terraform state backends, formal infra test suites like terratest, progressive delivery gates or documented canary/blue-green rollout configurations.
Phone
Timeline
Senior AWS DevOps Engineer
·
Senior
Gen Digitals
·
Full-Time
Built and maintained AWS infrastructure using Terraform, including reusable modules for consistent multi-environment provisioning. Managed Amazon EKS clusters and deployed containerized applications using Docker, Helm, and GitOps workflows via ArgoCD. Implemented CI/CD with Jenkins and GitHub Actions, set up ALB ingress, and configured IAM and Secrets Manager for secure access. Monitored production with CloudWatch, Prometheus, and Grafana and supported releases and incident troubleshooting.
Terraform
Amazon EC2
Amazon S3
IAM
Amazon EKS
DNS
Prometheus
Docker
Kubernetes
Helm
ArgoCD
Jenkins
GitHub Actions
Git
SonarQube
Grafana
Bash
Python
AWS DevOps Engineer
·
Middle
Panasonic
·
Full-Time
Provisioned AWS environments using Terraform and managed networking with VPC components, subnets, gateways, and security groups. Administered EC2 behind Application Load Balancers with auto scaling, and handled data services including RDS and EFS. Developed Jenkins-based CI/CD, containerized services with Docker, and deployed to Kubernetes with Helm-style resource management (Deployments, Services, Ingress). Added observability with CloudWatch logs/alarms and audit via CloudTrail, supporting Linux operations and release troubleshooting.
Terraform
Amazon EC2
Amazon S3
IAM
PostgreSQL
Linux
Jenkins
Docker
Kubernetes
Gradle
Nexus Repository
SonarQube
Git
Prometheus
Bash
Rest API
Full Stack Engineer
·
Middle
HCL
·
Full-Time
Developed full-stack web applications with the MERN stack, building React single-page interfaces and secure REST APIs using Node.js and Express. Implemented authentication and role-based access control, optimized MongoDB access patterns, and improved performance through code optimization and lazy loading. Deployed applications on AWS (EC2, S3, IAM, CloudFront, Lambda, API Gateway, RDS) and automated build, test, and release workflows using Jenkins, GitHub Actions, Docker, Kubernetes on EKS, and Terraform. Worked in Agile with Git, code reviews, and sprint planning.
React.js
Redux Toolkit
Redux
React Router
TypeScript
Node JS
Rest API
Jest
Docker
Kubernetes
Amazon EKS
Terraform
Jenkins
GitHub Actions
Git
Amazon EC2
Amazon S3
IAM
AWS Lambda
API Gateway
PostgreSQL
Webpack
Bootstrap
Ant Design
Sass
Jira
Software Engineer
·
Middle
Clorox
·
Full-Time
Built and maintained single-page applications using AngularJS and reusable components, services, and directives. Implemented responsive front-end features with HTML, CSS, and JavaScript and integrated REST APIs between UI and backend systems. Performed unit testing and debugging, working with Agile processes such as code reviews and production deployments. Used Git for collaboration and Jira for project tracking.
JavaScript
Bootstrap
Rest API
Git
Jira
Software Engineer
·
Middle
SAP BI I-Cura
·
Full-Time
Developed and maintained SAP BW objects including information providers and process chains to support reporting workflows. Performed data extraction from SAP source systems and monitored load jobs to ensure successful processing. Provided production support by resolving user issues and coordinating with teams to deliver scheduled reports. Supported ongoing maintenance of data loads and related BW processes.
SAP BW
Technical skills
Languages
5
JavaScript
Node JS
TypeScript
Python
Bash
Node JS
7
Express
Sequelize
Mongoose
Axios
Joi
Helmet
Nodemailer
Python
3
FastAPI
SQLAlchemy
Asyncio
DevOps
22
AWS
Amazon S3
Kubernetes
Git
Rest API
AWS Lambda
Amazon EKS
GitHub Actions
Terraform
Amazon EC2
Docker
Grafana
API Gateway
Prometheus
Jenkins
Linux
ArgoCD
IAM
Helm
Amazon CloudWatch
Nexus Repository
DNS
Frontend
9
Bootstrap
React.js
Sass
Ant Design
React Router
Redux
Redux Toolkit
Webpack
Material UI
Other
26
SAP BW
PostgreSQL
Jest
SonarQube
Gradle
MLFlow
Azure
Docker Compose
MySQL
GitOps
Recharts
DynamoDB
GitHub
Uvicorn
Windows
Apache Tomcat
Bitbucket
Apache HTTP Server
CI/CD
CloudFormation
Nginx
Ubuntu
TCP/IP
Debian
CentOS Stream
VPN
Senior DevOps Engineer
Confidence: High Cloud Architect
Cloud-focused DevOps engineer at a senior level specializing in AWS-native infrastructure and Kubernetes with a strong emphasis on IaC and automated remediation. The strongest proven skill is cloud infrastructure design and automation as shown by Terraform EKS and IAM modules with IRSA, KMS secrets encryption and a linked GitHub Actions pipeline (AegisHeal/terraform/modules/eks/main.tf and Telecom-Microservices-Platform/.github/workflows/ci-backend.yml). There is limited public evidence of remote Terraform state backends, formal infra test suites like terratest, progressive delivery gates or documented canary/blue-green rollout configurations.
CI/CD Pipelines
6/10
Automated build and deploy
CI/CD pipelines show a production-ready GitHub Actions workflow with secret scanning, multi-job orchestration, build cache, Trivy scanning and OIDC-based AWS authentication, but lack evidence of progressive delivery gates or artifact signing.
Evidence
Telecom-Microservices-Platform/telecom-platform/.github/workflows/ci-backend.yml: full CI pipeline with secret-scan, caching (cache-to/type=gha), Trivy scan and push-to-ECR using OIDC role-to-assume
Telecom-Microservices-Platform/telecom-platform/.github/workflows/ci-backend.yml:update-gitops step updates GitOps repository image tags to trigger ArgoCD sync
Infrastructure as Code
6/10
Managing servers with code
Infrastructure as Code uses structured, opinionated Terraform modules with IRSA, KMS encryption, lifecycle ignore_changes and multi-environment roots, showing real design work but missing explicit remote state/backend configuration or terraforming state migration artifacts.
Evidence
AegisHeal/terraform/modules/eks/main.tf: EKS module with IRSA, KMS for secrets encryption, launch template and lifecycle ignore_changes for scaling_config
AegisHeal/terraform/modules/iam/main.tf: IAM module with cross-service policies and IRSA role attachments for anomaly-detector and remediation-engine
Containerization & Orchestration
6/10
Working with containers
Containerization and orchestration include multi-stage Dockerfiles, non-root users, healthchecks and Kubernetes manifests with tuned probes and resource settings, plus EKS module configuration; however there is limited evidence of advanced pod disruption strategies or production PDB/topologySpread policies.
Evidence
Telecom-Microservices-Platform/telecom-platform/docker/backend/Dockerfile: multi-stage build, non-root user, healthcheck and runtime JVM tuning
AegisHeal/k8s/base/grafana.yaml: Deployment with readiness/liveness probes and resource requests/limits for Grafana
AegisHeal/terraform/modules/eks/main.tf: EKS cluster and managed node group with metadata_options (IMDSv2) and autoscaler IRSA role
Observability & Monitoring
6/10
Watching system health
Observability is well represented with Prometheus alerting rules, Grafana dashboards as code and Prometheus-style SLO-like alerts and business metric rules, but there is no clear evidence of alert routing/inhibition config or documented burn-rate alerting policies.
Evidence
AegisHeal/k8s/base/grafana.yaml: Grafana dashboard JSON embedded as ConfigMap with Prometheus queries for latency, MTTD and MTTR
Telecom-Microservices-Platform/telecom-platform/monitoring/alerts/telecom-alerts.yml: Prometheus alert rules covering availability, error rate, latency, Kubernetes and business metrics
Reliability & Incident Response
6/10
Keeping systems up
Reliability and incident response show automated remediation code, a root cause analyzer and runbook artifacts enabling programmatic remediation and runbook-driven operations, but progressive delivery and explicit rollback/gating strategies in production manifests are not present in the scored files.
Evidence
AegisHeal/src/remediation-engine/remediation_handler.py: remediation handlers for auto-scaler, instance restarter, SSM, Kubernetes actions and rollback primitives
AegisHeal/src/remediation-engine/root_cause_analyzer.py: rule-based root cause detection functions and RCA orchestration
AegisHeal/docs/runbook.md: runbook artifact referenced for incident handling
Cloud & Cost Optimization
5/10
Smart use of the cloud
Cloud and cost discipline is evidenced by autoscaler IRSA, EKS scaling_config and CloudFront price class choices, but there is limited proof of spot/eviction strategies, measured rightsizing, or documented cost-savings telemetry and automation.
Evidence
AegisHeal/terraform/modules/eks/main.tf: cluster_autoscaler IRSA, scaling_config and node group lifecycle settings
Telecom-Microservices-Platform/telecom-platform/monitoring/alerts/telecom-alerts.yml: alerts for HPAMaxReplicasReached and Kafka lag which act as signals for scaling and cost decisions
Expertise
CI/CD & Pipeline Automation· Senior
Infrastructure as Code· Senior
Kubernetes Ecosystem· Senior
Observability & Monitoring· Senior
Industries
Telecommunications· Senior
Health Care· Middle
Technologies
Terraform· since 2022
Docker Compose
MLFlow
GitHub Actions· since 2022
Prometheus· since 2023
GitOps
ArgoCD· since 2024
AWS· since 2016
Kubernetes· since 2022
Grafana· since 2024
Amazon EKS· since 2022
AWS Lambda· since 2022
Amazon S3· since 2022
IAM· since 2022
Amazon CloudWatch
DevOps· mentioned only
Recommendations
- Add a remote Terraform state backend with locking and documented state migration steps to support safe multi-environment deployments.
- Implement infrastructure tests and policy checks in CI (terratest, kitchen-terraform, conftest) to catch drift and enforce module contracts.
- Introduce progressive delivery and deploy gates (canary or blue-green) integrated into CI/GitOps with automated rollback criteria.
- Formalize SLOs and alert routing with Alertmanager rules and escalation policies to reduce noise and enable burn-rate alerting.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Backend Developer
Confidence: Medium API Engineer
A backend-focused API engineer at a middle level who builds full-stack microservice demos integrating Node.js services and a Python FastAPI analytics service with a strong front-end integration capability. The strongest proven skill is building conventional CRUD REST services and client integrations, supported by People-Technology-Manager/backend/src/controller/personController.js and its supertest coverage in backend/tests/person.test.js. The work lacks evidence of production-hardened system design such as migration histories, advanced transactional or concurrency controls, and robust resilience patterns like backoff retries or circuit breakers.
API Design
3/10
How well APIs are designed
Basic REST API design with conventional endpoints and error responses is present, but no versioning, idempotency controls, or advanced API contract patterns are visible.
Evidence
People-Technology-Manager/backend/src/controller/personController.js: REST CRUD handlers and consistent JSON error messages
People-Technology-Manager/backend/src/app.js: /api/people route wiring and /api/health endpoint
People-Technology-Manager/frontend/src/services/personApi.js: client-side REST calls to /people endpoints
Data Layer & Database
3/10
Working with databases
Data layer uses parameterized SQL queries and basic integrity/error handling; no migration history or advanced transaction/isolation logic found.
Evidence
People-Technology-Manager/backend/src/controller/personController.js: parameterized MySQL queries (placeholders ?), duplicate-key error handling
People-Technology-Manager/backend/package.json: mysql2 dependency declared indicating MySQL use
Scalability & Performance
2/10
Handling load and speed
Some scalability-oriented dependencies and patterns are declared across services, but there is little concrete operational logic for caching, batching, or measured performance tuning in the code inspected.
Evidence
Eks-microservice-main-cap/task-service/package.json: includes express, pg, sequelize and express-rate-limit (operational dependencies)
Eks-microservice-main-cap/notification-service/package.json: includes redis and express-rate-limit indicating intent for scaling/resilience patterns
System Architecture
3/10
Overall system structure
Clear multi-service layout and separation of concerns is present, but it reads like a demonstrated microservices scaffold rather than a deeply reasoned, contract-driven service architecture with robust inter-service contracts.
Evidence
Project structure under Eks-microservice-main-cap: separate folders for frontend, task-service, notification-service, user-service, analytics-service
Eks-microservice-main-cap/analytics-service/main.py and routers/analytics.py: separate Python analytics service intended to enrich other services
Security & Auth
3/10
Protecting data and access
Security basics are visible (helmet, rate limiting, JWT usage declared) and some input checks exist, but token lifecycle, revocation, SSRF/SQLi hardening and secrets management are not fully evidenced.
Evidence
Eks-microservice-main-cap/user-service/package.json: bcryptjs and jsonwebtoken dependencies declared for auth
Eks-microservice-main-cap/analytics-service/auth.py: JWT-based auth utilities (signature present in file headers)
People-Technology-Manager/backend/src/controller/personController.js: input presence checks and duplicate email handling
Reliability & Observability
3/10
Stability and monitoring
Basic reliability and observability steps are present such as try/catch handling and a small test suite; there is little evidence of advanced resilience patterns like retries with backoff, circuit breakers, or structured distributed tracing configuration in code.
Evidence
People-Technology-Manager/backend/tests/person.test.js: supertest tests validating health and people endpoints
People-Technology-Manager/backend/src/controller/personController.js: try/catch error handling across handlers
Eks-microservice-main-cap/*/package.json files: opentelemetry dependencies declared showing intent for observability
Expertise
Node.js· Middle
Python· Junior
Microservices & API Architecture· Middle
Technologies
Python· since 2024 · Senior
Rest API· since 2016
SQLAlchemy
FastAPI
Joi
Asyncio
Uvicorn
Mongoose
Helmet
Nodemailer
Recommendations
- Develop and own small-to-medium production REST services and APIs (Node.js/Express) that require end-to-end tests, schema migrations, and CI pipelines.
- Implement a Python FastAPI analytics endpoint with clear schema migrations and async DB access patterns to improve the analytics-service maturity.
- Hardening tasks: add DB migration tooling, structured logging with correlation ids, and retry/backoff logic for critical external calls.
- Build feature-focused performance or reliability improvements (e.g. connection pooling tuning, indexed queries, or caching with invalidation) and document before/after measurements.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Frontend Developer
Confidence: Medium UI Engineer
Frontend UI Engineer (Middle) specializing in building component-driven React interfaces using Material UI. The strongest proven skill is crafting interactive dashboards and data visualizations as shown by Analytics.js and Dashboard.js. There is limited public evidence of advanced backend architecture, SSR/edge work, measured performance engineering or thorough accessibility testing.
UI Component Architecture
5/10
How interface parts are built
Clear component-driven UI with reusable pieces and contexts; deliberate composition and small presentational components but no bespoke design system or deep custom hooks with complex lifecycle logic.
Responsive & Cross-browser
4/10
Works on all screens and browsers
Responsive layouts via MUI Grid/Container and CSS-in-JS; responsive gridTemplateColumns in Kanban shows attention to breakpoints but no advanced fluid type, container queries or explicit RTL/i18n support.
Performance Optimization
3/10
Speed of the interface
Some local optimizations and stable patterns (useCallback, refs to limit drag event churn) but no evidence of measured performance work, code-splitting, bundle analysis or virtualization for long lists.
Accessibility & Semantics
2/10
Usable for everyone
Basic semantic components and form labels are present; some dialogs use autoFocus and native form inputs but there is little explicit ARIA, focus-management across views or automated a11y checks in CI.
State Management & Data Flow
4/10
Managing data in the app
Reasonable server-state discipline with a dedicated services/api layer, error handling and fallbacks (analytics fallback to local data) but no request cancellation, explicit optimistic updates with rollback, or state machines for complex flows.
Evidence
davidtejusvi/Eks-microservice-main-cap/frontend/src/components/Analytics.js (fallback to localStats when analytics-service is offline)
davidtejusvi/Eks-microservice-main-cap/frontend/src/components/KanbanBoard.js (handleDrop updates via taskService and reloads tasks)
davidtejusvi/Eks-microservice-main-cap/frontend/src/components/TaskList.js (handleSubmit with create/update and error handling)
UX & Visual Polish
5/10
Look and feel quality
Good UX and visual polish: empty and loading states, snackbars, dialogs, conditional fallbacks and polished MUI styling; lacks measured perceived-performance improvements or undo patterns.
Evidence
davidtejusvi/Eks-microservice-main-cap/frontend/src/components/Dashboard.js (loading, empty states, polished stat cards)
davidtejusvi/Eks-microservice-main-cap/frontend/src/components/TaskList.js (snackbars, dialogs and empty-state CTA)
davidtejusvi/Eks-microservice-main-cap/frontend/src/components/Analytics.js (ServiceBadge and conditional rendering when analytics-service is offline)
Industries
Software· Middle
Technologies
JavaScript· since 2016 · Middle
TypeScript· since 2022 · Middle
Node JS· since 2022 · Middle
Redux· since 2022
Webpack· since 2022
Express
Helm· since 2024
CloudFormation
Debian
Azure
CI/CD
Bootstrap· since 2016
Jenkins· since 2022
Git· since 2016
Docker· since 2022
Ubuntu
Nginx
React.js· since 2022
Sequelize
Axios
Material UI
Ant Design· since 2022
Sass· since 2022
Recharts
Bitbucket
Nexus Repository· since 2023
Amazon EC2· since 2022
CentOS Stream
Redux Toolkit· since 2022
React Router· since 2022
GitHub
API Gateway· since 2022
Linux· since 2023
Windows
TCP/IP
DNS· since 2024
VPN
Apache HTTP Server
Recommendations
- Develop interactive dashboards and analytics frontends that integrate multiple microservices and fallback strategies using React and Recharts.
- Build and maintain component libraries and design-system work with Material UI, improving accessibility and documented component APIs.
- Implement client-side performance and resilience improvements such as request cancellation, optimistic updates with rollback, and code-splitting for large bundles.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Job preferences
- Work permits
- United States
- Employment type
- Full-Time
Open to AI agents: they read this profile and start a dialog through Alion
alion.io/@david-allampally/mcpAlion · People, companies and AI agents in one graphalion.io/@david-allampally