Quickeee logo

QA Engineer

Quickeee
7 hours ago
Full-time
On-site
Mumbai, Maharashtra, India ·
Automation Tester, SDET

About the job

QA Engineer — Quickeee Pvt Ltd

Who we’re looking for

Someone who genuinely cares about creating a seamless experience for users — a person who takes ownership when challenges arise and is driven to find effective solutions. You don’t need to have all the answers from day one, but you should have the curiosity, determination, and problem-solving mindset to learn, explore, and figure things out.

What you’ll own

User Journey Testing –

· Walk through the app end-to-end like a real user and flag every gap, broken flow, or confusing moment.

· Map out critical user journeys and make sure they work across devices, screen sizes, and edge cases.

· Catch UX inconsistencies that devs and PMs are too close to the product to see

API Testing -

· Test REST/GraphQL APIs for correctness, error handling, response structure, and edge inputs.

· Validate auth flows, rate limits, timeouts, and failure states — not just happy paths.

· Write and maintain API test suites (Postman, REST Assured, or similar).

· Catch regressions before they hit prod

General QA -

· Write clear, reproducible bug reports — no ambiguity about what broke and how.

· Build and maintain test cases and regression checklists.

· Work closely with the dev team to understand what changed and what’s at risk.

What we’d love to see

· 1–3 years in QA or testing (or exceptional self-taught work to show for it).

· Hands-on API testing experience — you know what a 401 vs 403 means and why it matters.

· Curiosity about how apps work under the hood.

· A sharp eye for user experience gaps, not just technical bugs.

· Comfort with tools like Postman, Jira, Chrome DevTools

Bonus points

• Experience with test automation (Playwright, Cypress, Selenium)

• Basic understanding of SQL or databases

• Startup or fast-paced environment experience

What we care about more than credentials

• You learn fast and aren’t afraid to ask questions

• You’re thorough but don’t slow the team down

• You communicate clearly — bugs, risks, blockers

• You actually care about the user experience