Pie tests software the way a real user does — explores the product, catches what breaks, opens the fix. Our promise to customers: signal, not noise. Three real bugs, not three hundred maybes.

Someone has to hold that bar. That's on our Pulse team. The agent runs the tests. You decide what positive looks like.

What you'll do
Set the standard. Define coverage strategy, test design, and triage criteria across our customer portfolio — e-commerce, grocery, wellness, fintech, on web, iOS, and Android.
Keep coverage honest. Audit accounts, find the untested flows, kill the suites where pass rates look healthy but mean nothing.
Teach the agent. Write the playbooks that teach Pie how each product behaves. This skill barely exists yet — you'd be inventing it.
Improve the product. Turn field failure modes into sharp requirements for engineering. Decide when an account has earned more autonomy.
Make the hard calls. Real defect or workplace noise? Worth the customer's attention? You're the escalation point.

Who you are
6+ years in QA,



owning quality strategy — not just execution — for a shipped product
Robust on web and native mobile (iOS and Android, real devices)
You think in risk and coverage, not test counts
Debugging instincts: logs, network calls, clean repros
A record of raising the bar — practices you introduced. We'll ask for specifics.
Scripting (Python, JS, or shell) and sharp writing

Bonus: AI/LLM testing tools, customer-facing QA, Appium/Playwright/XCUITest. Why this role The execution layer is already handled. You spend your time on what genuinely needs a human: coverage strategy, defect judgment, teaching a system how software should behave — across more products in a month than most QA engineers see in years.
If you love maintaining Playwright selectors, this isn't for you. If you think quality is a judgment problem, not a scripting problem — talk to us.

📌 Senior Qa Engineer Bengaluru
🏢 PieLabs
📍 Bengaluru