SOFTWARE DEVELOPMENT ENGINEER IN TEST

I build test systems that make releases faster, more reliable, and easier to trust.

3+ years building and scaling automation across UI, API, database and service-integration layers — with CI/CD, Docker and AWS at the execution layer.

RELEASE PIPELINE● live
  1. REQUIREMENTAcceptance criteria reviewed early01
  2. TEST SCENARIOSCucumber BDD scenarios02
  3. UI / API / DB TESTSSelenium · REST Assured · data checks03
  4. CI / PARALLEL EXECUTIONDocker · GitLab CI · parallel pods04
  5. VALIDATIONAsync events · assertions · triage05
  6. RELEASE CONFIDENCEA failure means something06
IMPACT

Numbers I can defend.

Not vanity metrics. These are outcomes from problems I investigated, systems I changed, and automation I owned.

70% → ~5%

FALSE-FAILURE RATE

7+ HRS → <2 HRS

REGRESSION RUNTIME

0+

REGRESSION SCENARIOS

0

MICROSERVICES OWNED

ENGINEERING CASE STUDY / 01

When a green pipeline stopped meaning anything.

How I helped turn an unreliable regression signal into one engineers could trust.

PROBLEM

Regression was producing more than 70% false failures during release windows.

A large regression suite was being run by multiple squads during a 2–3 day release sign-off window. The result was a huge amount of time spent investigating failures that were not actual product defects.

ROOT CAUSE

Continuous polling became a scalability problem.

Async events were being verified by querying MongoDB. The polling approach was reasonable for an individual test, but under concurrent execution across multiple squads it generated enough query volume to bottleneck the database.

INVESTIGATION

  1. 01Concurrent regression
  2. 02Hundreds of tests querying MongoDB
  3. 03Continuous polling
  4. 04Excessive database query load
  5. 05Database throttling
  6. 06False test failures
  7. 07Long reruns
  8. 08Reduced trust in the pipeline

ENGINEERING CHANGES

01

Interval-based polling

Replaced continuous querying with controlled intervals, cutting query volume without losing async coverage.

Engineering decision I drove

02

Graceful failure behaviour

Made tests degrade predictably under load so a failure pointed at product behaviour, not infrastructure noise.

Engineering decision I drove

03

MongoDB → DocumentDB

Migration for additional headroom under concurrent execution.

Collaborative work with DevOps

FALSE FAILURES

>70% → ~5%

REGRESSION

7+ HOURS → ~2 HOURS

“The goal wasn’t simply to make the pipeline faster. It was to make a failed test mean something again.”

Testing is an engineering problem.

01

TRUST THE SIGNAL

A test suite is only valuable when engineers believe what a failure means.

02

FIX THE SYSTEM, NOT THE PEOPLE

Good quality systems reduce dependence on people simply trying harder.

03

SURFACE QUALITY EARLY

I prefer being involved from requirements and acceptance criteria through dev testing, rather than receiving finished stories and simply writing tests.

ENGINEERING / AUTOMATION SYSTEM

Inside the automation system.

From test definition to pipeline execution, I work across the layers that make automation reliable at scale.

TEST DEFINITIONJava · Cucumber · Maven

Scenarios written as readable behaviour, versioned alongside the code they cover.

AUTOMATIONSelenium · REST Assured · PageFactory

UI and API layers share structure so tests stay maintainable as the product changes.

DATA + VALIDATIONMongoDB · DocumentDB · Java Faker · ObjectMapper · API · UI · Async Events

Generated data and typed deserialization keep parallel runs independent and assertions precise.

EXECUTIONDocker · GitLab CI/CD · Amazon ECR · Parallel Pods · Autoscaling

Containerised runs scale out per feature file so regression finishes inside a release window.

CLOUDAWS · S3 · CloudWatch · Device Farm

Artifacts, logs and device coverage handled by managed infrastructure rather than local machines.

REPORTING + TRIAGESerenity · Failure Capture · Debug / Rerun

Post-run capture makes a failure explainable and reruns targeted instead of wholesale.

Explore the engineering →

Things I’ve actually built.

Still building.

FEATURED EXPERIMENT

naukri-profile-refresh

PlaywrightTypeScriptGitHub Actions

An automation project using Playwright + TypeScript with Page Object Model, session reuse and scheduled GitHub Actions execution.

CURRENTLY EXPLORING

  • Playwright
  • PythonFUNDAMENTALS
  • AI-assisted test authoring
  • API automation
  • Quality engineering

Let’s build better release confidence.

Interested in test automation, quality engineering, or building systems that make releases safer?