Senior SDET at Moody's
Financial software · Automation strategy · Release confidence
Leading quality engineering work across enterprise workflows with a focus on maintainable automation, testing strategy, and high-confidence releases.
This is the longer read: how the work evolved, what shaped the approach, and why the quality decisions now lean toward systems, clarity, and practical delivery support.

Profile
The homepage covers the positioning. This page focuses on the arc behind it: the enterprise teams, product environments, and working principles that shaped how I approach quality engineering today.
Today
At Moody's, the work is not only about running checks. It is about building the automation architecture, test strategy, and release signals that help teams understand risk and ship with more confidence.
Scope
The throughline is practical quality engineering: maintainable automation, clearer release evidence, thoughtful validation for AI-backed journeys, and systems that stay useful as products and teams grow.
Background
Years across Salesforce and other enterprise environments shaped how I think now: systems over scripts, evidence over noise, and quality work that improves decision-making instead of just increasing activity.
The strongest proof is not just tenure. It is the combination of enterprise scale, real delivery environments, and visible work that shows how the thinking translates into practice.
Experience
20+ years
Enterprise QA, automation architecture, and quality systems across long-running product programs.
Current role
Moody's Corporation
Senior SDET focused on release confidence, maintainable automation, and execution quality.
Prior platform scale
Salesforce
Worked across UI, API, AI-backed experiences, and high-visibility product launches.
Project proof
Live work
Public demos show practical product thinking across AI-backed and data-heavy workflows.
The approach stays consistent even when the stack, product, or team changes: build maintainable systems, reduce noise, and create quality signals people can actually use.
Systems over scripts
Build automation foundations that stay maintainable as product scope grows and teams change.
Signals over dashboard noise
Turn quality work into clearer release evidence instead of collecting green numbers that hide real risk.
Human judgment stays in the loop
Use AI in the assistant role while deterministic execution and engineering review remain the source of truth.
The shift over time has been from executing checks to shaping quality strategy, automation foundations, and release signals that teams can actually trust.
Financial software · Automation strategy · Release confidence
Leading quality engineering work across enterprise workflows with a focus on maintainable automation, testing strategy, and high-confidence releases.
UI · API · CI/CD · AI-adjacent systems
Worked across automation architecture, regression quality, API testing, release signoff, and product systems that demanded both depth and scale.
Foundations · Enterprise delivery · QE growth
Built the foundation in test planning, automation, release support, and team enablement that still shapes how I approach quality systems today.
The role is rarely just about automation. It is about helping teams understand risk earlier, keeping systems maintainable, and making release decisions with stronger evidence instead of more noise.
01
Automation frameworks that stay maintainable as product scope grows
02
Quality strategy that improves release confidence instead of generating dashboard noise
03
Practical test architecture across UI, API, data, and CI/CD layers
04
Thoughtful validation for AI-backed workflows where deterministic checks are not enough
05
AI-assisted quality workflows that use Claude, Codex, and human review to move faster without losing accuracy or judgment
Showing 2 of 4 recommendations at a time
“Mirtunjay is an exceptional engineer and wonderful team player. He consistently delivers high quality work you can depend on.”
Peter Finley
Lead Software Engineer at Salesforce
Worked on the same team · March 2025
Auto-advancing
The throughline is consistent: clearer signals, maintainable systems, and quality work that helps teams make stronger release decisions.
Designed reusable patterns for UI and API automation, environment handling, execution flow, tagging, reporting, and CI integration so coverage could scale without creating maintenance debt.
Worked across regression strategy, environment readiness, release validation, and quality communication so teams could make better release decisions with less ambiguity.
Contributed to data-ingestion, validation, behavior testing, and end-to-end quality thinking for intelligent product flows where deterministic assertions alone are not enough.
Email works best for role conversations, professional inquiries, and collaboration. LinkedIn and resume are here for quick validation.