SR.Let's talk
Available for opportunitiesBengaluru, India

SDET / Quality Engineering

Shashank Rushiya.

Software Development Engineer in Test

SDET with 3 years of experience building Python-based automation frameworks, defining end-to-end test strategy, and improving release confidence across UI, API, integration, and mobile testing.

PythonPlaywrightSeleniumPytestOpenAI APIJenkinsJIRA

01TESTING PHILOSOPHY

Quality is a release decision, not a QA checkbox.

I review requirements and code early enough to catch testability and edge-case gaps before a sprint closes, not after a build breaks in staging.

Automation only earns its place if it covers the critical path across UI, API, and integration layers, and runs fast enough that engineers actually trust the result. I build that layer with Python, Playwright, Selenium, and Pytest, and reach for the OpenAI API where it genuinely reduces manual authoring effort.

The job doesn't end at a green checkmark. I track coverage, cycle time, flaky-test rate, and defect leakage, and treat a rising flake rate as seriously as a failing suite.

02TECH STACK

Tools, organized by the work they support.

A practical stack across test authoring, delivery, and quality operations.

Languages & Data

The daily stack I use to build automation and debug real problems.

  • Python
  • JavaScript / TypeScript
  • SQL
  • PostgreSQL

Automation Stack

Hands-on frameworks and test layers used across product flows.

  • Playwright
  • Selenium
  • Pytest
  • BDD (Cucumber)
  • Page Object Model
  • REST API Automation
  • UI Automation
  • Mobile Testing

QA Practice

How I structure quality work from the start of a sprint to sign-off.

  • End-to-End Testing
  • System Integration Testing
  • Functional Testing
  • Manual Testing
  • Test Planning
  • Test Case Design
  • Defect Triage
  • Root Cause Analysis
  • Release Certification

AI & Delivery Tools

The tooling layer around the framework and the team workflow.

  • OpenAI API
  • AI-Driven Test Generation
  • JIRA
  • TestRail
  • Confluence
  • Postman
  • Git
  • Bitbucket
  • Jenkins
  • Linux

03FRAMEWORKS I'VE BUILT

Two independent automation architectures.

Open folders to trace each framework from specifications through CI. Annotated files reveal a short terminal note about their role.

Selenium + Pytest-BDD

Project tree / select folders to inspect

  • reportsAllure/HTML output (gitignored)
  • requirements.txtPython package dependencies
  • pytest.iniPytest and pytest-bdd configuration

Built to scale

  • Config-driven environments keep URLs, browser choices, viewports, and API behavior outside scenario code.
  • Page objects isolate UI changes so shared browser interactions are maintained at the page layer.
  • Reusable step definitions keep Gherkin scenarios focused on behavior rather than implementation details.
  • Pytest fixtures and pytest-xdist parallelism support repeatable execution as the suite grows.
  • CI is native to the framework from day one, including risk-based prioritization before the main test job.

Playwright + Pytest-BDD

Project tree / select folders to inspect

  • artifactsScreenshots, videos, traces on failure (gitignored)
  • reportsTest report output (gitignored)
  • requirements.txtPython package dependencies
  • pytest.iniPytest and pytest-bdd configuration

Built to scale

  • Config-driven environments keep browser, viewport, UI, and API settings outside test scenarios.
  • Page objects isolate UI changes so shared interactions can be maintained without rewriting feature specifications.
  • Reusable step definitions provide a consistent bridge from Gherkin scenarios to implementation behavior.
  • Pytest fixtures and pytest-xdist parallelism support repeatable execution as coverage expands.
  • CI is part of the framework from day one, with risk-based prioritization before the main pytest job.

03SELECTED WORK

Automation as an operating standard.

01 / Vaaree

Cutting regression time by building a real automation framework.

Problem

Release confidence depended on slow, inconsistent manual regression across UI, API, and integration layers.

Approach

  • Architected Python, Playwright, and Selenium automation frameworks to scale automated coverage and shorten regression cycles.
  • Defined test strategy across UI, API, and system integration layers while reviewing requirements and code for quality risks early in the sprint.
  • Built Test Case Builder, an internal web app using the OpenAI API that turns PRDs into test scenarios directly from a Confluence link or upload.
  • Conducted mobile testing, managed JIRA and TestRail workflows, and integrated automated suites into Jenkins CI/CD pipelines.
  • Mentored a 5-person QA team and aligned engineering, product, and QA around clear release standards.
Test Case Builder

Result

Automation coverage grew from 40% to 75% and regression cycles ran 35% faster, while mentoring a 5-person QA team on the new standard.

02 / Synechron

Stabilizing automation for financial workflows in a 3-month engagement.

Problem

Financial workflow testing needed reliable automated coverage fast, with production failures triaged largely by hand.

Approach

  • In a focused 3-month tenure, built and executed automated suites for web, REST API, and system integration testing using Python, Selenium, BDD, and Pytest.
  • Produced test plans, test conditions, and data sets for critical financial workflows, then drove root cause analysis on production failures.
  • Optimized the framework to reduce flakiness and improve execution speed so the team got reliable feedback quickly within a short engagement.

Result

Delivered a working, lower-flake automation layer for financial workflows within a focused 3-month tenure.

03 / TestYantra Softwares Pvt Ltd

Scaling automated coverage for a distributed loan processing system.

Problem

A distributed loan processing system needed systematic API and data validation to catch reliability issues earlier.

Approach

  • Built a scalable test automation framework for a distributed loan processing system using Python and SQL.
  • Engineered REST API automation and systematic validation to improve service reliability and failure triage.
  • Managed defects and sprint delivery using JIRA, and strengthened CI/CD workflow consistency through Jenkins, Bitbucket, and Confluence.

Result

Cycle time dropped 20%, manual testing effort dropped 30%, and API reliability improved 15%.

04TOOLS I'VE BUILT

Shipped tool / built solo

Test Case Builder

An internal web app built for the QA team that turns PRDs into structured test scenarios using the OpenAI API.

Input
A Confluence document link or an uploaded PRD file.
Output
A set of test scenarios the team can refine and use directly.
OpenAI APIInternal Web App

Manual test-case writing

30–40%

less effort for the QA team

View Vaaree case study

05EXPERIENCE

Work history, on the release line.

Dec 2024 - Present

Software Development Engineer in Test

Vaaree

Bengaluru, India

40% → 75% coverage and 35% faster regression cycles

Oct 2024 - Dec 2024

Associate Engineer - Automation

Synechron

Bengaluru, India

Short 3-month automation stint with meaningful impact on financial workflows

Jul 2023 - Aug 2024

Software Engineer in Test

TestYantra Softwares Pvt Ltd

Bengaluru, India

20% lower cycle time, 30% less manual effort, 15% better API reliability

06MEASURABLE IMPACT

The output is confidence—and evidence.

Metrics from automation, delivery, and team practice across recent roles.

40% → 75%

automation coverage at Vaaree

35%

faster regression cycle time

30%

manual testing reduction

15%

API reliability improvement

25%

better delivery adherence

5

QA engineers mentored

07CONTACT

Open to quality work with real ownership.

Open to SDET, QA Automation, and quality engineering roles that need strong automation ownership and practical release discipline.

Download resume