NITHISH RAJDEVOPS / CLOUD ENGINEERING
ENGINEERING PORTFOLIO

Engineer boldly.
Operate reliably.

I'm Nithish Raj — a DevOps engineer working across cloud infrastructure, delivery automation and operational visibility. I like systems that are understandable, repeatable and ready to recover.

Explore the work View resume
FOCUSDevOps · AWS · CI/CD
SYSTEMS ONLINE
Futuristic arc reactor with a bright blue energy core, metallic graphite and gold rings, and restrained red accents
delivery.flowREFERENCE MODEL
commit›build›verify›deploy
Observability includedTRACE / 0x01
NR • INFRASTRUCTURE / DELIVERY / RELIABILITY
SCROLL TO EXPLORE01 — 09 / PROJECT INDEX
THE THROUGH-LINE

Less hand-off friction.
More dependable delivery.

01
Automate the path

Make build and release steps repeatable.

02
See the system

Use signals and alerts to understand health.

03
Plan for failure

Validate changes and keep recovery in view.

PROFESSIONAL EXPERIENCE

Experience in practice.

Professional roles across DevOps operations, cloud infrastructure, application delivery, and monitoring. Responsibilities are described without unverified performance metrics.

MAR 2024 — PRESENT

Senior Software Engineer — DevOps

Kasplo · Full-time

DEVOPS / CLOUD
  • Contribute to DevOps and infrastructure work across AWS and Linux environments, supporting application delivery and day-to-day operations.
  • Work with CI/CD and containerized delivery workflows using Jenkins, Docker, and Kubernetes/EKS, including deployment validation and rollback practices where applicable.
  • Work with AWS infrastructure and services such as EC2, VPC, IAM, ECR/EKS, load balancing, S3, RDS, and CloudWatch as relevant to the environment.
  • Support observability and operational automation with monitoring tools, logs, Bash/Python scripting, and messaging/email infrastructure components where applicable.
AWSLinuxJenkinsDockerKubernetesTerraformObservability
JAN 2020 — MAR 2024

DevOps Engineer

Itrust Soft Solutions

DEVOPS / OPERATIONS
  • Worked with Linux and Windows environments, supporting application runtimes and monitoring/log analysis using tools such as Splunk and AppDynamics.
  • Supported application delivery workflows involving Jenkins, Maven, Git, and application servers including Tomcat, JBoss, and WebSphere.
  • Used SonarQube for code-quality checks and worked with Docker and Kubernetes as part of container-related workflows.
  • Contributed to infrastructure automation using Terraform and Ansible, including AWS resources such as EC2, load balancing, and S3.
LinuxSplunkJenkinsMavenTerraformAnsibleAWS
SELECTED ENGINEERING WORK

Projects with a purpose.

A practical portfolio of delivery workflows, cloud designs, observability and messaging patterns. Each repository describes what is implemented and what is a reference design.

01 / 09Local-first lab
Delivery systems

Production DevOps Platform

A repeatable path from source to container to cluster, with monitoring built into the workflow rather than added as an afterthought.

JenkinsDockerKubernetesPrometheusGrafana
PUBLIC REPOSITORYView repository
02 / 09Reference architecture
Cloud architecture

AWS DevOps Platform

Application tests, Docker packaging and a Jenkins pipeline paired with Terraform patterns for an AWS EKS delivery path.

TestsJenkinsECREKSALB
PUBLIC REPOSITORYView repository
03 / 09Architecture reference
Messaging platform

SMTP Email Infrastructure

An email-ingress design exploring load-balanced SMTP entry, Kafka-based processing and GreenArrow integration points.

SMTPNLBKafkaGreenArrow
PUBLIC REPOSITORYView repository
04 / 09Hands-on lab
Distributed systems

Kafka Distributed Processing

Go-based producer and consumer workflows that make topics, partitions, consumer groups and processing behaviour easier to explore.

GoTopicsPartitionsConsumer groups
PUBLIC REPOSITORYView repository
05 / 09Local lab + manifests
Signals & response

Production Observability

A monitoring foundation for collecting metrics, exploring service health, building dashboards and routing actionable alerts.

ExportersPrometheusGrafanaAlertmanager
PUBLIC REPOSITORYView repository
06 / 09Local lab
Release safety

Blue-Green Deployment

A blue/green release pattern using Nginx routing, validation checkpoints and a clear path to switch traffic back when needed.

BlueValidateSwitchGreen / rollback
PUBLIC REPOSITORYView repository
07 / 09Reference architecture
Resilience engineering

AWS High Availability & DR

A resilience design covering multi-AZ placement, load balancing, scaling, managed databases, backups and recovery planning.

Multi-AZALBASGRDSRecovery
PUBLIC REPOSITORYView repository
08 / 09Pipeline lab
Secure delivery

DevSecOps CI/CD Platform

Security checks integrated with delivery: tests, secret detection, dependency review, container scanning and deployment validation.

TestsGitleaksDependenciesTrivyDeploy
PUBLIC REPOSITORYView repository
09 / 09Reference architecture
FinOps thinking

AWS Cost & Migration

A decision-focused approach to cost analysis, container image optimization, infrastructure trade-offs and cloud migration planning.

ReviewOptimizeCompareMigrate
PUBLIC REPOSITORYView repository
i

Scope matters. Some projects are local labs and some document reference architectures. AWS architecture diagrams are not presented as live deployments unless a repository explicitly confirms that status.

TOOLS ARE THE MEANS

Core capabilities.

A balanced toolkit across infrastructure, delivery, runtime, observability and secure operations.

ENGINEERING MINDSET

Make the system
easier to operate.

Automation is useful when the workflow is repeatable, the system is observable, and recovery is considered before it is needed.

01

Cloud & infrastructure

AWSEC2VPCIAMS3RDSECR / EKSLoad balancingTerraform
02

Delivery & runtime

JenkinsGitDockerKubernetesAnsibleBashPython
03

Observability & security

PrometheusGrafanaAlertmanagerSplunkGitleaksTrivy
04

Systems & messaging

LinuxKafkaSMTPDNSTCP/IPHTTP / TLS
HOW I THINK ABOUT DELIVERY

Reliable by design.

Good infrastructure is not only provisioned. It is testable, understandable, observable and recoverable.

01 / DESIGN

Make the path clear

Map dependencies, access boundaries and deployment steps before automating them.

02 / AUTOMATE

Repeat the process

Express build, infrastructure and release workflows as reviewable code.

03 / OBSERVE

Keep feedback visible

Use metrics, logs, checks and actionable alerts to understand service behaviour.

04 / RECOVER

Expect change

Validate releases, plan rollback paths and make operational trade-offs explicit.

OPEN CHANNEL

Let's build
something dependable.

Interested in DevOps, cloud infrastructure, CI/CD, platform engineering or observability? Let's connect.

Connect on LinkedIn Explore GitHub
QUICK LINKSResume PDF ↗GitHub repositories ↗LinkedIn profile ↗
Built with care. Documented with intent.