Open to remote roles — Lead QE · SDET Lead · Automation Architect

Kratant
Jain

QA Automation Architect Lead QE

I built, and now own, the automation framework, Jenkins orchestration, and device management that run regression for Sony's customer-facing SDK releases — ~300 test libraries, ~250,000 test cases, 50+ engineers.

Bengaluru, India · Open to remote 7+ Years Experience Test Automation · CI/CD · Performance

From scripts to
owning the platform

Technical Specialist at Sony India Software Centre, Bengaluru, with 7+ years across QA automation, CI/CD orchestration, and internal platform engineering.

At Sony I designed and wrote most of the regression platform for the SDK: a pip-installable Python test framework, a 3-tier Jenkins orchestration model, a device management service, and the tooling around them. Regression went from 4–5 days to ~20 hours, and every milestone has shipped on time.

Before that: automation scripts and a client go-live at Cognizant, then test coverage, performance testing, and leading a 4-member QE team for connected-vehicle products at Harman. Next, I want to lead QE or automation architecture for a product team, with AI-assisted automation as the edge.

Kratant Jain
Current Role Technical Specialist · Sony India Software Centre
Focus Areas Test Automation · CI/CD Orchestration · Performance · Release Quality
Industry Background Consumer Electronics · Automotive Telematics · IT Services
Looking For Lead QE / SDET Lead · Automation Architect — remote

What I build
and own

Test Automation Frameworks

Python frameworks shipped as pip packages, Robot Framework, Pytest, and Selenium — designed so other engineers can onboard their own tests without going through my team.

CI/CD Orchestration

Multi-tier Jenkins orchestration, declarative pipelines, conditional stages, and parallel execution slots, with spreadsheet-driven run plans in place of manual pipeline setup.

Device & Lab Management

Reservation APIs, pool-based allocation, and health dashboards for hardware devkits — zero allocation conflicts, and adopted by other teams for their own kits.

Environment Automation

Scripted setup of Windows CI agents — SDK retrieval, integrity checks, registry configuration — taking node setup from ~5 hours to ~30 minutes.

Performance Testing

JMeter load, stress, and endurance testing run from CI, with Grafana and Graylog to trace bottlenecks and set server operating limits.

Release Quality Ownership

Regression planning, go/no-go calls, quality and risk reporting to management, and technical escalation for the whole automation stack.

Developer Tooling

A local CLI that mirrors CI execution so failures reproduce on any machine; health monitoring and run-time analytics that surface problems before a regression starts.

AI-Assisted Automation

Roadmap for LLM-based failure triage (flaky vs. environment vs. real defect), intelligent reruns, onboarding from README analysis, and self-healing pipelines.

0%
Faster regression turnaround
4–5 days → ~20 hours
0%
Less CI node setup time
~5 hours → ~30 minutes
0%
Less devkit setup effort
~4 h, 3 people → ~30 min, 1 person
0%
On-time milestone delivery
One major SDK milestone early
0
Test libraries orchestrated
~250,000 test cases
0+
Engineers on the platform
Library maintainers across regions
0
Libraries self-onboarded
No automation-team bottleneck
0
Devkit allocation conflicts
Down from recurring duplicate IPs

7+ years, from scripts
to platform ownership

Jul 2024 — Present Current

Technical Specialist

Sony India Software Centre · Bengaluru · Consumer Electronics

Own the test automation platform that regression-tests Sony's customer-facing SDK: ~300 test libraries (~250,000 test cases) maintained by 50+ engineers, run across ~8 execution PCs and ~40 devkits. Most of the platform is my own design and code.

  • Built the next-generation test automation framework single-handedly, from scratch, as a pip-installable Python package replacing the legacy framework — auto-generated driver scripts, Jenkins execution pathways, and a result-validation utility that catches silent failures
  • Made library onboarding self-service: engineers follow the integration guidelines and request a slot in the next regression; ~30 libraries added this way by my team and other-region teams
  • Designed a 3-tier Jenkins orchestration model (super orchestrator → per-PC orchestrator → single-library executor) with up to 10 parallel slots per machine; a spreadsheet-driven run plan removed ~2 days of manual prep per cycle
  • Cut regression turnaround from 4–5 days to ~20 hours (~75%)
  • Built a device management service (Flask API + NiceGUI dashboard) to reserve, release, and health-check devkits — zero allocation conflicts, replacing a pool tool that assigned the same IP twice; now used by other teams for their hardware
  • Wrote a Python environment-setup framework for Windows CI agents (SDK source detection, zip integrity checks, registry writes with elevated-permission fallback): ~5 hours → ~30 minutes per node, adopted by other regions
  • Automated devkit setup in Jenkins (system/software updates, network configuration): ~4 hours with 3 people → ~30 minutes with 1 (~87%)
  • Built a local CLI that mirrors the CI executor, so the 50+ library maintainers get matching results and reports and can reproduce CI failures on any machine
  • Added network health monitoring with email alerts before each regression, and an execution analytics pipeline for per-library and end-to-end run times
  • Led 50+ engineers through the SVN-to-Git move with sparse checkout on a 300–400 GB repository; fixed Git LFS 0 KB pointer-file issues
  • Own delivery: ~5 major regression runs per milestone, go/no-go calls, quality and risk reporting to management, technical escalation for the stack — 100% on-time, one major SDK milestone early
  • Drafted the AI roadmap for the platform: LLM-based failure triage, intelligent reruns, automatic library onboarding from README analysis, self-healing pipelines
Python Jenkins Groovy Flask NiceGUI PowerShell Windows CI Git / Git LFS SVN
Apr 2023 — Jul 2024

Senior Test Engineer – Product Development

Harman Connected Services Corporation India Pvt. Ltd. · Automotive Telematics

Connected-vehicle platform: in-vehicle dongles and HUDs send data over MQTT to a microservices backend (Kafka, HiveMQ, WSO2, MongoDB, PostgreSQL) that serves trips, live location, vehicle health, and remote operations to end users.

  • Led a 4-member QE team for global customers — 1 on performance testing, 3 on framework maintenance for different customers; co-located and remote
  • Owned performance testing for the customer delivery team: weekly JMeter load, stress, and endurance tests with realistic telematics traffic to set server operating limits; traced bottlenecks in Grafana and Graylog
  • Built Jenkins pipelines that run performance tests as part of CI
  • Architected a reusable Python + Robot Framework + Selenium framework for web and mobile apps (functional, integration, non-functional)
  • Validated device-to-cloud data flow: MQTT publish/subscribe, payload integrity, reconnect/retry on connectivity drops
  • Directed regression at each product stage and gave release sign-off calls; reviewed team test cases and scripts; built Python/Pandas data tools and trained developers and QA on automation
JMeter Robot Framework Selenium Jenkins MQTT Grafana Graylog Pandas
Apr 2021 — Mar 2023

Product Engineer

Harman Connected Services Corporation India Pvt. Ltd. · Automotive Telematics

  • Gathered business and functional requirements with product and development teams; wrote test plans and detailed test cases
  • Ran functional, integration, end-to-end, regression, and exploratory testing; reviewed scalability, performance, and load balancing of each application
  • JMeter load, stress, and endurance testing; reported bottlenecks to developers with supporting data
  • Maintained the known-issues defect database and drove triage and closure; kept build, quality, and performance records
  • Agile/Scrum releases, code reviews, mentoring juniors, and process changes that shortened engineering cycle time
JMeter Test Planning Defect Governance JIRA TestRail Agile / Scrum
Jul 2019 — Apr 2021

Programmer Analyst

Programmer Analyst · Aug 2020 – Apr 2021  |  Programmer Analyst Trainee · Jul 2019 – Jul 2020

Cognizant Technology Solutions · IT Services

Automation R&D and integrations for an internal process-automation platform, and an L1-support chatbot used in customer deliveries.

  • Took the Wellington client project live, largely single-handedly — delivered the client's key "one-click fix", where users trigger the fix script on the SCCM server directly instead of raising a ticket; earned the PASSION award and customer and delivery-manager appreciation
  • Solved image-based automation on Citrix with Tesseract OCR + OpenCV where UI automation failed; this led to OCR invoice reading for another client, with a proof of concept delivered
  • Built a periodic Python job syncing user details from ServiceNow into the automation platform, replacing manual onboarding
  • Chatbot: NLU intent/entity extraction, Rasa Core for next-action, ServiceNow fallback for untrained questions; Docker deployment of the chatbot and platform images; Python MFA proof of concept for the bot
  • Python and SQL scripts for test execution across operating systems; feasibility checks on client integrations
Python SQL Tesseract OCR OpenCV Rasa / NLU ServiceNow Docker
Jun 2018 — Jul 2018

Intern, Cloud & Cybersecurity

Happiest Minds Technologies

  • Built a Python tool that runs SQL injection and XSS checks against given URLs
  • Automated discovery of machines on a network and their likely vulnerabilities with Nmap + Python
Python Nmap Security Testing

Tools, and where
I've used them

Languages
Python Groovy (Jenkins DSL) PowerShell SQL Bash C
Automation Frameworks
Custom Python frameworks (pip) Robot Framework Pytest Selenium Appium / ADB (exposure)
CI/CD
Jenkins Multi-tier Orchestration Declarative Pipelines Conditional Stages Git Git LFS SVN
Performance
JMeter Load / Stress / Endurance Capacity Limits Bottleneck Analysis
Web & APIs
Flask REST APIs NiceGUI Django (basics)
Data, Messaging & Observability
Kafka HiveMQ / MQTT WSO2 MongoDB PostgreSQL Pandas Grafana Graylog
Infrastructure
Windows CI Agents Windows Registry Docker Ubuntu / Linux VMware AWS (basics)
Image, OCR & Conversational AI
Tesseract OpenCV Image Comparison NLU Rasa
Quality Management
Test Strategy Release Sign-off Defect Governance JIRA TestRail Agile / Scrum
Security
SQLi / XSS Scanning Nmap
Learning Now
LangGraph LangChain CrewAI RAG Chroma Hugging Face n8n MCP LLM APIs

What I'm
looking for next

Remote roles where I own test automation and release quality end to end — and bring AI-assisted automation to it.

Lead QE / SDET Lead

Leading a QE team and owning test strategy, automation, and release sign-off — the work I already do across the regression platform and did with a 4-member team at Harman.

Automation / Technical Architect

Designing frameworks, orchestration, and lab infrastructure that other teams build on, as a titled responsibility rather than a side effect of delivery.

AI-Assisted Automation

LLM-based failure triage, intelligent reruns, and self-healing pipelines on top of a solid automation platform. Currently learning LangGraph, RAG, and MCP to build these.

Platform Engineering

Internal tooling, CI environments, and developer workflows that let engineers across regions run, debug, and ship without environment guesswork.

2015–2019

B.Tech — Computer Science Engineering

Jaypee University of Engineering and Technology, Guna

Cognizant

PASSION Award

Wellington client go-live; customer and delivery-manager appreciation

Certifications
Scrum Master Security White, Yellow & Green Belt Python Programming Essentials Python and Flask Bootcamp Google Digital Unlocked
Training
Jenkins DevOps Master Robot Framework Level 2 Advanced Python LPIC-2 Linux Kernel & System Startup AWS Security Fundamentals CEH v9 CCNA

Open to remote
Lead QE & architect roles

If your team needs someone to own test automation, CI/CD orchestration, and release quality — or to bring AI-assisted triage to an existing platform — I'd like to talk.