QA Engineer

Team pumpkin; Maharashtra; Hybrid; INR 900,000 - 1,500,000; Full time

Job summary

Team pumpkin is seeking a QA Engineer to own quality across multiple projects. You will lead QA for concurrent mobile and web projects, setting test strategy and managing time across them.

Emphasizing a test-once-then-automate approach, you will convert manual passes into durable Maestro flows and maintain a regression suite integrated into CI.

Qualifications

• 3+ years in QA or test engineering
• Hands-on with mobile UI automation (Maestro, Appium, Detox)
• Practical use of AI tools in testing and a view on their limits
• Experience with CI/CD and device farms/cloud devices
• Strong exploratory testing instincts and ability to read specs

Responsibilities

• Own quality across multiple projects and define test strategy
• Define done and shippable criteria per project
• Communicate risk to product managers and developers
• Test once and automate the rest with Maestro flows
• Maintain regression suites on Maestro Cloud or device agents

Skills

QA strategy

UI automation

AI testing tools

CI/CD

Device testing

Tools

Maestro

Appium

Detox

Maestro MCP

Job description

We're looking for a QA Engineer who can own quality across several products at once. You'll be the primary QA on multiple projects, working closely with each team's developers and product managers, and you'll keep up by working smarter, not by testing everything twice.

The core idea of this role: test a feature once, deeply and by hand, then hand the retesting to machines. Every manual pass you do should end with a Maestro flow, an AI-driven check, or an automated suite that catches the regression next time so you never have to. Your time goes into understanding products and finding new bugs; the repetitive verification goes to automation.

What you'll do

Own quality across multiple projects

• Lead QA for several concurrent mobile and web projects, setting the test strategy for each and managing your time across them.


• Define what \"done\" and \"shippable\" mean for each project and hold releases to that bar.


• Communicate risk clearly to product managers and developers: what's tested, what isn't, and what could break.

Understand the product before testing it

• Read specs, designs, tickets, and code changes closely. Ask questions until the intended behavior, edge cases, and business rules are clear to you.


• Build a working mental model of each project's users, flows, and failure modes so your tests reflect how the product is actually used, not just what the acceptance criteria say.


• Flag ambiguities, contradictions, and gaps in requirements early, before they become bugs.

Test once, automate the rest

• Perform thorough exploratory and manual testing on new features and changes, once.


• Convert every meaningful manual pass into durable Maestro flows so regressions are caught automatically on subsequent builds.


• Maintain a regression suite that runs on real or virtual devices via Maestro Cloud / device agents, integrated into CI so every build is verified without your involvement.


• Keep automated tests fast, reliable, and low-flake. A test that cries wolf gets deleted or fixed.

Leverage AI and new tooling aggressively

• Use Maestro MCP and AI agents (Claude, Cursor, and similar) to generate, extend, and repair test flows from specs, screenshots, or recorded sessions.


• Use AI to triage failures, draft bug reports, analyze logs, and suggest edge cases you might have missed.


• Continuously evaluate new testing tools and techniques, adopt what saves time, and drop what doesn't.


• Build lightweight scripts and tooling that remove manual steps from your own workflow.

Report and close the loop

• Write bug reports developers can act on immediately: clear reproduction steps, expected vs. actual, logs, screenshots, or recordings.


• Track quality metrics per project (coverage, escape rate, flake rate, cycle time) and use them to improve the process.


• Verify fixes, then add coverage so the same bug can't ship again.

What you bring

Required

• 3+ years in QA or test engineering, including experience owning test strategy for a product or feature area end to end.


• Hands-on experience with a mobile UI automation framework such as Maestro, Appium, or Detox.


• Practical use of AI tools in your daily testing work, and a clear point of view on where they help and where they don't.


• Experience with CI/CD pipelines and running automated tests on device farms or cloud device services.


• Strong exploratory testing instincts: you find the bugs the happy path hides.


• Ability to read a spec, a design, or a diff and reconstruct what the feature is supposed to do, then challenge it.


• Excellent written communication. Your bug reports and test docs are read by people who weren't in the room.


• Comfortable context-switching between projects with different stacks, stakeholders, and release cadences.

Don't have Maestro experience? That's fine. We'll give you time to learn it. What matters more is that you're open to changing how you work: moving from repeated manual retesting to a test-once-then-automate approach, and building AI tools into your daily routine. If you're willing to make that shift, we'll support you through the ramp-up.

Nice to have

• Experience with Maestro MCP or other MCP-based agent tooling for test generation and maintenance.


• API testing experience (Postman, REST clients, contract testing).


• Familiarity with mobile platform specifics (iOS/Android build systems, permissions, deep links, push notifications).


• Experience with performance, accessibility, or security testing basics.