Asia-Pacific
I help distributed APAC engineering teams reduce regression bottlenecks, eliminate flaky tests, and build release pipelines they can trust. My experience comes from full-time SDET roles at Oracle, Flipkart, and Logitech — with multi-market delivery that spans the region.
⏰ IST sits centrally in APAC: 1.5–4.5h difference to most APAC markets 💰 USD pricing, fixed scope 🌎 Distributed team ready
Why APAC teams hire me
Distributed team coordination
I provide the centralised QA architecture and coordination that distributed APAC teams need. At Logitech I operated across 6 locales. At Oracle I work with global teams. I bring structure without becoming a bottleneck.
Multi-market delivery complexity
Different languages, regulatory requirements, and user expectations across markets create testing complexity. My Logitech experience managing automation across 6 locales is directly relevant for APAC companies with multi-market products.
Time zone advantage
Unlike US or European consultants who offer limited APAC overlap, IST works naturally with most APAC markets (1.5–4.5h difference). I cover afternoon-to-evening for Sydney, Singapore, Tokyo, and Seoul — the core collaboration window.
Proven outcomes
Logitech program (Mar 2021–Jul 2022)
Core automation team: Selenium BDD, Cypress, Backstop.js visual validation, 22+ Jenkins jobs per week across 6 locales. Multi-market, multi-language delivery — directly relevant for APAC companies shipping across the region.
Read the full outcomeOracle (Jul 2022–Present)
Designed Java + Rest-assured automation frameworks, integrated 200+ API checks into Jenkins CI, mentored SDETs, and improved service reliability across a multi-team global enterprise environment.
Read the full outcomeFlipkart (Aug 2017–Jul 2020)
Built UI automation from scratch (Java + Selenium), achieved 68% GUI coverage on self-serve flows, maintained 99% integration test accuracy. Full CI/CD pipeline with Git PR hooks via Jenkins. 2× WOW Award winner.
Read the full outcomeHow I work with APAC teams
Time zone
IST is 1.5h behind SGT/MYT, 2.5h behind PHT, 3.5h behind JST/KST, 4.5h behind AEST. My working day (12:30–9:30 PM IST) overlaps afternoon-to-evening for every major APAC market. No other global region covers APAC as naturally.
Communication
I provide a written daily status: what was done, what blocked progress, and what needs a decision. Weekly video syncs for deeper review. Tailored to each team's preferred communication rhythm.
Payment
Pricing is in USD with fixed-scope engagements. The Stabilization Sprint carries a 50% outcome guarantee — if your release signal is not measurably better, I refund half the fee. No questions asked.
Reading for APAC buyers
Scaling teams
Strategies for growing automation coverage while keeping maintenance cost under control.
Read the articleRegression
How to shorten feedback loops while protecting release quality and engineering credibility.
Read the articleMeasurement
The five metrics that actually determine whether you should release.
Read the articleFramework
Selenium, Playwright, Cypress, WebdriverIO, or Pytest — how to choose based on your team, not hype.
Read the articleFAQ for APAC teams
IST sits centrally in APAC: 1.5h behind Singapore/Malaysia, 2.5h behind Philippines, 3.5h behind Japan/Korea, 4.5h behind Australia (AEST). I cover afternoon-to-evening for every major APAC market. My working day (12:30–9:30 PM IST) gives strong real-time overlap.
Yes. At Logitech I managed test automation across 6 locales with different languages and regional configurations. At Flipkart I coordinated with multiple platform partners. Multi-market delivery is a core part of my experience.
Yes. I have operated in distributed global teams across Oracle, Flipkart, and Logitech. I adapt communication to each team's culture and time zone while maintaining a single, coherent automation strategy across markets.
I offer the same senior SDET capability as local APAC consultants at more competitive rates, with the added advantage of fixed-scope pricing and a 50% outcome guarantee on the Stabilization Sprint. No hourly billing, no scope creep.
It starts with a release diagnosis (7-10 days): review your test suite, map failure patterns, inspect CI configuration, and identify the 2-3 changes that will move the needle most. You get a prioritised action plan, not a vague assessment.
Next step for APAC engineering leaders
I will review your situation and tell you what is slowing your releases — and what to do about it. If we are not a match, I will say so.