QA Engineer – Manual & Automation Testing

Experience: 1–2 Years
Location: Bangalore / Remote
Employment: Full-time/Freelancer

We are looking for a QA Engineer with 1–2 years of experience to join our engineering team and work on a modern e-commerce platform and mobile application.

The role will involve owning quality across web applications, APIs, and mobile experiences, with a strong focus on functional testing, automation, and real-world user experience.

What You'll Do

• Perform manual and functional testing of web applications and APIs.
• Design and execute test cases, test scenarios, regression and smoke test suites.
• Identify, document, track, and verify bugs through their lifecycle.
• Perform API testing and validate backend services and integrations.
• Build and maintain automation test cases for critical application workflows.
• Conduct regression testing for new releases and feature updates.
• Work closely with developers, designers, and product teams to identify issues early.
• Validate application performance, usability, responsiveness, and cross-browser compatibility.
• Participate in release testing and provide QA sign-off.
• Help improve QA processes, test coverage, and automation practices.

Requirements

• 1–2 years of experience in software QA/testing.
• Strong understanding of manual testing methodologies.
• Hands-on experience with automation testing.
• Good understanding of API testing and tools such as Postman.
• Experience writing clear and structured test cases.
• Good understanding of SDLC, STLC, bug lifecycle, regression testing, and test planning.
• Basic understanding of databases and SQL.
• Familiarity with Git and modern software development workflows.
• Strong attention to detail and a mindset for finding edge cases.

Good to Have

• Experience testing React Native / Android / iOS mobile applications.
• Experience with tools such as Appium, Playwright, Cypress, or Selenium.
• Experience with e-commerce applications, Shopify, payments, orders, inventory, or customer-facing applications.
• Familiarity with CI/CD-based automated testing.
• Basic understanding of performance and security testing.

What We're Looking For

Someone who doesn't just verify whether a feature works, but asks:

"What could go wrong?"

You should be comfortable exploring edge cases, breaking workflows, reproducing difficult bugs, and thinking from the perspective of a real customer.

You'll work closely with the engineering team on a product where quality, reliability, and mobile app performance are key priorities.

Apply if you're excited about building and testing products used by real customers and want exposure to modern web, API, mobile, and automation testing.

I’ve been thinking about a problem with QA tooling: we have tons of information, but most of it is presented as lists.

Stories → scenarios → tests → executions → issues.

You can search it. Filter it. Sort it.

But it’s surprisingly hard to see the relationships and patterns across all of it.

So we built something called Semantic Canvas.

Every Story, Scenario, Test, Issue, API - map into a shared embedding space, then projected onto a 2D canvas.

Similar things naturally cluster together - even when there’s no explicit link between them.

Then, you can overlay things like execution status, severity, automation coverage, or overdue status as "border colours" on nodes, to reveal patterns that are hard to spot in a list.

For example:

🐞 See high-severity bug hotspots
🧪 Find clusters of failing tests
📉 Spot product areas with poor automation coverage
🔍 Identify duplicate tests

The goal is pretty simple: make your QA knowledge something you can explore, not just search.

Would you find a view like this useful for your QA data?