header

Typing SVG

LinkedIn GitHub Email Status

$ whoami

name : Ashutosh Parihar
title : Quality Engineering Architect
location : India
philosophy : "Quality is a product feature. I build the infrastructure that ships it."
approach:
 - I work upstream — shaping test strategy at the architecture phase, not after
 - I translate quality risk into business language: velocity, incident cost, release confidence
 - I treat test infrastructure like production code: version-controlled, reviewed, maintained
specialization:
 - End-to-end automation frameworks (Playwright · Cypress · WebdriverIO · Selenium)
 - API & contract-level testing (REST · GraphQL · gRPC · Pact)
 - Performance & load engineering (K6 · JMeter · Grafana · InfluxDB)
 - Web3 & blockchain QA (Smart Contracts · DeFi · NFT · Foundry · Hardhat)
 - CI/CD quality gates & release pipelines (GitHub Actions · GitLab CI · Jenkins)
domains : FinTech · Web3 · Healthcare · SaaS · IoT · eCommerce · Gaming
currently : Building → Web3 QA tooling · Crypto exchange test simulator
open_to : Quality Architecture · Platform Reliability · Engineering Leadership

$ ls -la ./featured-work

order-sentinel qrypto

playwright-hybrid-framework k6-performance-lab

solidity-core-labs cicd-blueprints

$ cat ./architecture-thinking.md

$ quality-risk-radar --interactive

Pick a stack. Get an architecture-level quality risk assessment for flakiness, coverage, contract parity, deploy safety, and more.

Launch

$ cat ./tech-stack.json

── Core Languages ──

JavaScript TypeScript Java Solidity Bash

── Web & Mobile Automation ──

Playwright Cypress WebdriverIO Selenium Appium

── API & Contract Testing ──

Postman Newman Supertest Rest Assured GraphQL gRPC Pact

── Performance Engineering ──

K6 Grafana JMeter InfluxDB

── Web3 & Blockchain ──

Solidity Foundry Hardhat Ethers.js Web3.js

── DevOps & Cloud ──

GitHub Actions Docker Jenkins GitLab CI AWS Azure

$ cat ./what-i-bring.md

/**
 * Beyond the tool list, how I think about quality engineering
 * at the architecture and leadership level.
 */
const qualityArchitect = {
 strategy: {
 "Risk-based planning": "I prioritize test coverage by business risk, not just feature surface",
 "Shift-left integration": "QA joins sprint planning — not sprint review",
 "Definition of Done": "Nothing merges without agreed quality criteria",
 "ROI thinking": "Every automation investment is justified by time-to-detect and cost-of-defect",
 },
 engineering: {
 "Framework design": "Scalable, maintainable, low-flake architectures — not script dumps",
 "Contract testing": "Microservice boundaries validated before integration pain hits",
 "Observability as QA": "Prod metrics and error rates are part of my quality model",
 "Blockchain-native testing": "Smart contract invariants, reentrancy, and edge-case simulation",
 },
 leadership: {
 "Team upskilling": "I've grown 0-to-1 QA teams and leveled up developer testing culture",
 "Cross-functional voice": "I translate quality risk into language PMs, CTOs, and investors understand",
 "Quality advocacy": "I make the business case for testing — not just the technical one",
 },
};

$ ./contribution-matrix --render

Snake animation

$ ping ./connect

LinkedIn GitHub Email

footer