DEVOPS ENGINEER / INDIA

I’m Prakhar.
I connect code
to production.

I build Azure delivery workflows, automate verification in YAML, and script repeatable cloud tasks with Bash and PowerShell. My work connects code review, environment setup, and releases across Dev, UAT, and Production.

NOW AT EXL SERVICE Azure DevOps Engineer · Noida, India

04+YEARS IN DEVOPS03×SUPER SQUAD AWARD03DELIVERY ENVIRONMENTS
This portfolio has a delivery workflow of its own
MY CLOUD TOOLKITAZURE / IAC / CI/CD
PIPELINE PLAYGROUNDINTERACTIVE DEMO
  1. 01Commit
  2. 02Validate
  3. 03Package
  4. 04Deploy
Ready when you are.

A local simulation of the delivery process. No infrastructure is deployed.

SCROLL TO EXPLORE
MY DAILY TOOLKIT
A Azure⌘ Azure DevOps◇ Terraform▦ Docker⎈ Kubernetes>_ Linux

01 / DELIVERY & AUTOMATION

The work behind
the release.

The context, my contribution,
and why the engineering mattered.

PROFESSIONAL PROJECT CONTEXTS

BUSINESS VERIFICATION / PROFESSIONAL PROJECT

VeriKYB

My contribution: repository governance & delivery automation

THE CONTEXT

A Know Your Business verification platform with application changes moving through Dev, UAT, and Production.

  • Managed GitHub repositories, branching workflows, branch protection, and pull request validation.
  • Built Azure DevOps pipelines with Git and YAML to automate build validation and release workflows.
  • Supported Azure and Linux delivery workflows with PowerShell, with attention to security and cost optimization.
WHY IT MATTERED

Changes could be checked against a consistent workflow before release, with protected branches and defined environment stages supporting code quality and team collaboration.

  • Azure DevOps
  • GitHub
  • YAML
  • PowerShell

FINANCIAL SERVICES / PROFESSIONAL PROJECT

Financial account opening

My contribution: CI/CD & container-based release operations

THE CONTEXT

A financial account opening application that needed reliable delivery across environments and integration with downstream systems.

  • Designed and maintained Azure DevOps pipelines for builds, testing, and deployments across Dev, UAT, and Production.
  • Managed release automation and deployment troubleshooting using Docker and Kubernetes on Azure AKS.
  • Worked with Terraform as part of the delivery tooling and supported downstream application integration.
WHY IT MATTERED

Defined pipeline stages and infrastructure automation supported repeatable application delivery, while deployment troubleshooting helped the team work through release and integration issues.

  • Docker
  • Kubernetes / AKS
  • Terraform
  • Azure

This portfolio ships the same way.Version controlled. Validated in CI. Deployed with GitHub Actions.

See how it ships

02 / PERSONAL PROJECT · THIS PORTFOLIO

A small website.
A real delivery workflow.

I built this portfolio as a practical DevOps project: version-controlled source, automated checks, a container smoke test, and repeatable publishing. The workflow is in the repository, so the implementation can be inspected.

Inspect the source
THE PROBLEM I WANTED TO SOLVE

Publishing should be a process I can repeat.

A portfolio still needs a dependable path from an edit to a published page. I wanted changes checked before release, a way to test the packaged site, and blog previews that could refresh without rewriting HTML every time.

WHAT I BUILT

A static HTML, CSS, and JavaScript site with a GitHub Actions pipeline. PowerShell handles validation, packaging, and RSS rendering. Bash runs the Docker smoke checks. GitHub Pages hosts the verified artifact.

Azure, Terraform, and AKS are part of my professional toolkit. This particular site is hosted on GitHub Pages.

THE ACTUAL DELIVERY PATHWorkflow YAML ↗
  1. 01
    Change & review

    A pull request runs checks. A push to main follows the deployment path.

  2. 02
    Validate & package

    Check HTML, links, assets, JavaScript syntax, and RSS tests; build an isolated _site artifact.

  3. 03
    Test the container

    Start unprivileged NGINX in Docker, wait for /healthz, and check the homepage and résumé.

  4. 04
    Publish the artifact

    Deploy to GitHub Pages with OIDC after the checks pass.

Content follows the same path. The Wix RSS feed supplies two recent posts; a configured featured article stays pinned. A scheduled run refreshes the published page approximately every six hours.

WHY EACH TOOL IS HERE

Every part has a job.

GitHub Actions
Orchestrates pull request checks, the build, container tests, and deployment. The workflow also supports manual and scheduled refreshes.
PowerShell
Validates the page and assets, packages the static output, safely renders RSS posts, and writes deployment metadata and SHA-256 checksums.
Bash & curl
Run the container smoke test and bounded readiness retries. A started container must respond successfully before the pipeline proceeds.
Docker & NGINX
Provide a reproducible preview and CI test environment, running as a non-root user with a read-only filesystem and dropped capabilities.
GitHub Pages
Serves the verified static files. OIDC handles deployment authentication without a personal access token in the workflow.
REPEATABLE PUBLISHING

A push starts the release.

Once checks pass on main, the workflow publishes the built artifact through GitHub Pages.

CONTENT AUTOMATION

New posts, less upkeep.

Blog previews refresh at build time, with a fixed featured slot and no bot commits added to the repository.

A CLEAR FAILURE BOUNDARY

A failed check stops the release.

Build, feed, or smoke-test failures prevent the new artifact from being published. The existing live version stays available.

DECISIONS & LESSONS

The details behind the diagram.

Why use Docker when the site runs on GitHub Pages?

Docker packages NGINX and the generated site into a repeatable preview and smoke-test environment. GitHub Pages serves the final static artifact. Keeping those responsibilities clear makes the setup easier to explain and maintain.

What did a failed container check teach me?

A container can start before NGINX is ready to answer requests. A connection-reset failure in the smoke test led to bounded retries against the health endpoint, with timeouts and container logs retained for diagnosis.

How does the blog refresh stay predictable?

The renderer accepts posts only from the blog’s HTTPS domain, escapes feed text, rejects external XML entities, sorts by publication time, and handles dates consistently across PowerShell versions. Saved featured-post details keep the chosen article available when it leaves the RSS window.

03 / EXPERIENCE & CONTRIBUTION

Four years of
connecting the pieces.

Since 2022, I’ve worked across EXL and Infosys on Azure delivery, Linux operations, scripting, and release workflows. The common thread is making repeated engineering work easier to run, review, and troubleshoot.

WHAT I BRING TO A TEAM

Delivery discipline. Pipeline steps and environment workflows that teams can follow.

Practical automation. Scripts for recurring verification, provisioning, and release tasks.

A troubleshooting mindset. Working through pipeline, configuration, and deployment issues with developers and QA.

Better, together.3× Super Squad AwardRecognized for team collaboration
and exceptional project outcomes.
JUL 2026 — PRESENTCURRENT

Azure DevOps Engineer

EXL Service · Noida, India

Working across application delivery and the Azure infrastructure that supports it.

  • Design and maintain Azure DevOps YAML pipelines for builds, testing, and deployments across Dev, UAT, and Production.
  • Manage Azure infrastructure and delivery automation using Terraform, Docker, and Kubernetes on AKS.
  • Use Git, PowerShell, and Bash to support repeatable deployment operations and investigate issues.
  • Keep security, reliability, and delivery efficiency in view when working on environments and releases.

Contribution: Connecting pipeline configuration, infrastructure automation, and deployment troubleshooting within the release process.

AZURE / CI/CD / TERRAFORM / AKS
NOV 2024 — JUL 2026

DevOps Engineer

Infosys · Noida, India

Azure infrastructure automation, release preparation, and collaboration with development and QA.

  • Developed Bash automation scripts to provision Azure resources, including Azure Container Registry and Azure Container Apps.
  • Implemented Git branching and pull request approval workflows to support consistent code review and release readiness.
  • Developed and maintained Azure DevOps pipelines using Git and YAML for Dev, UAT, and Production.
  • Managed release automation, environment configuration, and deployment troubleshooting with development and QA teams.

Impact: Scripted provisioning and approval workflows improved the consistency of code review, release preparation, and deployment readiness.

BASH / ACR / CONTAINER APPS / RELEASES
AUG 2022 — NOV 2024

DevOps Engineer

EXL Services · Noida, India

Building the automation around code verification, application delivery, and Azure/Linux operations.

  • Designed and implemented YAML-based CI pipelines in Azure DevOps for dependency installation, code quality checks, and testing.
  • Validated pipeline execution to confirm that the automated verification steps ran successfully.
  • Automated application builds, testing, and deployment workflows across environments using Git and YAML.
  • Supported Azure cloud infrastructure and Linux servers, using PowerShell and Bash for deployment automation and pipeline troubleshooting.

Impact: Automated verification reduced the need for manual code checks and made the development workflow more consistent.

YAML CI / QUALITY CHECKS / LINUX / SCRIPTING

04 / THE PROFESSIONAL TOOLKIT

The right tools.
A systems mindset.

What I use, and the work each tool supports.
The portfolio’s own stack is explained above.

01

Cloud & infrastructure

Azure environment work, infrastructure as code with Terraform, and Linux operations that support application delivery.

Microsoft AzureTerraformLinux
02

Delivery & collaboration

YAML build and release workflows, repository governance, code verification, and pull request approvals.

Azure DevOpsGitHubGitYAML
03

Containers & orchestration

Container-based delivery and release troubleshooting, with experience across Docker, AKS, ACR, and Container Apps.

DockerKubernetes / AKSAzure Container RegistryAzure Container Apps
04

Scripting & automation

Bash and PowerShell for provisioning, recurring deployment tasks, and investigating release problems.

PowerShellBashRelease automation
MICROSOFT CERTIFIEDAzure FundamentalsOctober 2026
EXLAWS Cloud PractitionerNovember 2026
LOVELY PROFESSIONAL UNIVERSITYB.Tech, Computer Science2018 – 2022

05 / FROM THE BLOG

Beyond the build.
Into the details.

Notes on building software, working with Appian, and the ideas I take away from life outside the terminal.

Visit my blog

HAVE SOMETHING WORTH BUILDING?

Let’s make
the next release.

ENGINEERING NOTES / PROJECT DETAILS