Available for opportunities

Aakash K S
Implementation Engineer

I take software from working code to running systems — configuring, integrating, and deploying BSS applications for telecom clients, on Kubernetes and beyond.

View Projects → Get in Touch
1.5+Years experience
2Telecom BSS deployments
3+Clients served
99%Uptime achieved
About

Building things that actually work

I'm an Implementation Engineer specializing in configuring, testing, and deploying microservice-based BSS (Business Support Systems) applications for telecom clients. I handle everything from E2E test scenarios to production go-lives, on Kubernetes clusters with ArgoCD and Jenkins pipelines. Alongside client work, I'm building DevOps fundamentals from the ground up — one deployment failure at a time.

What I work with

Skills & Tools

Infrastructure

Cloud & DevOps

AWS · Azure · Docker · Kubernetes · CI/CD · Terraform

Delivery

CI/CD Pipelines

Jenkins · ArgoCD · GitLab CI · GitHub Actions

Integration

APIs & Middleware

REST APIs · Webhooks · MuleSoft · Zapier · Postman · GraphQL

Scripting

Automation

Python · Bash · Shell scripting · PowerShell · SQL · YAML · JSON

Platforms

Enterprise Software

Jira · GitLab · GitHub

Monitoring

Observability

ELK · Grafana · Prometheus

Web & DB

Deployment Stack

NGINX · Let's Encrypt/Certbot · MongoDB · PostgreSQL · MySQL

BSS Domain

Telecom Systems

UPC (Usage & Policy Control) · Online Charging System (OCS)

Collaboration

Cross-functional

Stakeholder Management · Technical Documentation · Training · SLAs

Where I've worked

Experience

Implementation Engineer

6D Technologies
  • Cellcard (BSS) — UPC Application: Owned configuration and implementation of the UPC microservice; ran UI and E2E testing, and deployments to a Kubernetes cluster via ArgoCD and Jenkins pipelines. Application built in Java.
  • Vodafone French Polynesia (BSS) — OCS & UPC: Worked across Online Charging System and UPC applications; designed and executed test scenarios for both, deployed on Java VMs, and used shell scripting to automate recurring release tasks across countless release cycles.
  • Go-live & Post-launch: Supported go-live delivery, production monitoring, and Change Request (CR) implementation for both projects.
  • Reduced average implementation time by 30% through process automation.
JavaKubernetesArgoCDJenkinsShell ScriptingE2E Testing

Quality Analyst

Warship Overseeing Team, Kochi
  • Maintained accurate inspection reports, logs, and documentation for regulatory and senior authority review.
InspectionDocumentationQA Testing
Things I've built

Projects

01 / BSS

Cellcard — UPC Application

Configured and implemented the UPC microservice for a telecom BSS platform. Ran UI and end-to-end testing, then deployed to a Kubernetes cluster using ArgoCD-driven GitOps and Jenkins pipelines.

JavaKubernetesArgoCDJenkins
02 / BSS

Vodafone French Polynesia — OCS & UPC

Built and executed test scenarios across Online Charging System and UPC applications deployed on Java VMs. Automated repetitive release validation with shell scripts across a high volume of production releases.

JavaOCSShell ScriptingRelease Testing
03 / Ops

Go-Live & CR Delivery

Supported go-live cutovers, production monitoring, and Change Request implementation for both the Cellcard and Vodafone BSS projects — closing the loop between deployment and live operations.

MonitoringChange ManagementSLAs
04 / Lab

Portfolio — NGINX + HTTPS on EC2

Self-hosted this site on AWS EC2 with NGINX; diagnosed a mobile-only connection failure to a missing TLS config and fixed it with a Let's Encrypt certificate via Certbot.

AWS EC2NGINXCertbot
Learning in public

DevOps Learning Log

Learning DevOps from the basics — one real deployment, one real bug, one real lesson at a time. Cross-posted from LinkedIn.

NGINX + HTTPS on AWS EC2 +

Hosted my portfolio on AWS EC2 behind NGINX. DNS and NGINX looked correct — curl -I returned 200 OK — but Chrome on Android returned ERR_CONNECTION_REFUSED while it worked fine on laptop.

  • Root cause: missing HTTPS configuration.
  • Generated a certificate with certbot (Let's Encrypt).
  • Configured NGINX to listen on port 443 in nginx.conf.
Lesson: deployment includes TLS, networking, and browser behavior — not just the app running.
.NET + MongoDB +

Built and deployed a .NET application backed by MongoDB. The app failed at startup because appsettings.json held an incorrect MongoDB connection string.

  • Fixed the connection string in configuration.
  • Verified CRUD operations end to end after the fix.
Lesson: deployment depends on application configuration as much as code.
Python + PostgreSQL +

Built a Python application on PostgreSQL — first real pass at virtual environments, dependency management, and DB setup for deployment.

  • Database connection failed due to an incorrect DATABASE_URL.
  • Corrected the env variable and re-verified connectivity.
Lesson: environment configuration is as important as application logic.
Java + MySQL banking app +

Built a Java banking application, packaged with Maven via mvn clean package, connected to MySQL, and deployed on Linux.

  • Most debugging time went into configuration, not Java code.
  • A clean build didn't mean a working deployment.
Lesson: a successful build does not guarantee a successful deployment.
Say hello

Let's work together

Open to new opportunities, collaborations, and interesting conversations about implementation engineering and DevOps.

✉ Email ☎ +91 79022 92113 ⌥ GitHub ↗ LinkedIn