United States
I help US engineering teams reduce regression bottlenecks, eliminate flaky tests, and build CI signal that release decisions can rely on. All my experience comes from full-time SDET roles at enterprise and product-scale companies — not theory, not side projects.
⏰ EST/PST overlap: 6:30 PM – 11:30 PM IST (8–10 AM ET / 5–7 AM PT) 💰 Pricing in USD
What US teams usually need
Regression drag
This is the #1 problem I've fixed across Oracle, Flipkart, and Enclouden. The fix is not adding more tests — it's restructuring what you have, removing noise, and aligning coverage with release risk.
Flaky CI signal
Flakiness erodes engineering credibility. I've stabilized suites at product scale (Flipkart: 99% stability, 0% leakage) and know exactly which patterns to fix first.
Framework trapped in the past
I've modernized frameworks at Oracle (Java + Rest-assured), Logitech (Cypress + Backstop.js), and Enclouden (Python + pytest from scratch). I don't rewrite for the sake of it — I fix what's costing you time.
Proven outcomes
Oracle (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 enterprise environment at Oracle.
Read the full outcomeFlipkart (Aug 2017–Jul 2020)
Built and scaled UI automation from scratch (Java + Selenium + TestNG), achieved 68% GUI coverage on Self-Serve post-order flows, automated Integration Tests with 99% accuracy. Handled platform-level releases across Ultra platforms (MMT, PhonePe, 2Gud). 2× WOW Award winner.
Read the full outcomeHow I work with US teams
Time zone
My standard day runs 12:30 PM – 9:30 PM IST, which gives me 3–4 hours of real-time overlap with EST teams (6:30–9:30 PM IST / 8–10 AM ET). For PST teams, we use async + daily written updates. I've done this successfully at Oracle and Flipkart with US-based stakeholders.
Communication
I provide a written daily status: what was done, what blocked progress, and what needs a decision. Weekly video syncs for deeper review. No status-meeting bloat.
Payment
Pricing is in USD. 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 US buyers
Framework choice
A decision guide grounded in maintainability, team maturity, and release pressure.
Read the articleROI
Why script counts do not matter and which business metrics actually justify automation spend.
Read the articleHiring guide
A buyer's guide with red flags, green flags, and questions to ask before hiring.
Read the articleMaintenance
Five high-leverage fixes to cut maintenance cost by 30-50% without losing coverage.
Read the articleFAQ for US teams
Yes, with overlap. IST is 9.5 hours ahead of EST. My working day includes 6:30–9:30 PM IST, which is 8–10 AM EST — your morning standup and core collaboration window. For urgent matters, I adjust. At Oracle I regularly aligned with US-based release schedules.
Yes. Oracle (US-headquartered enterprise), Logitech program (US-based client via Tech Mahindra), and Flipkart (worked with US-based platform partners like MMT and PhonePe). I understand US engineering culture, async communication, and release discipline expectations.
Yes. All pricing is in USD. See the pricing page for fixed-price options. I do not charge by the hour — every engagement has a defined scope and outcome.
I sign NDAs. At Oracle and Flipkart I worked under strict confidentiality agreements. Proof pages on this site use outcome-level descriptions, not proprietary details. If you need more references, I can arrange them during qualified discovery.
Freelancers deliver code. I deliver a system: diagnosis, execution, handoff, and a team that can sustain it. Fixed scope, defined outcome, guaranteed timeline. The Stabilization Sprint includes a 50% outcome guarantee.
Next step for US engineering leaders
I'll review your situation and tell you what's slowing your releases — and what to do about it. If we are not a match, I will say so.