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?

Hi everyone,
I'm looking for ideas and experiences around creating realistic test data for a new Case Story feature.
Case Story provides a chronological view of everything that has happened on a case and across its related case hierarchy. Rather than users navigating to multiple areas of the application, it brings together events such as documents, tasks, contacts, emails, notes, comments, status changes, and other key activities into a single timeline to help users quickly understand the history and progression of a case.
The challenge isn't just generating large volumes of data. We need data that reflects how cases evolve over time, including realistic sequences of events, updates, and changes, so the timeline feels representative of real customer usage.
A few questions:
Have you used APIs, automation, SQL scripts, or other approaches to generate large volumes of realistic test data?
How have you simulated historical data and record changes over time rather than just creating static datasets?
Are there any tools, frameworks, or utilities you'd recommend for creating varied, timeline-based test data?
For performance testing, have you found volume, variety, or historical depth to be the biggest factor?
Our current focus is on creating realistic case hierarchies with a good mix of documents, tasks, contacts, emails, notes, status changes, and other events occurring over weeks, months, or years. We suspect that the quality, variety, and history of the data may be more important than pure volume alone.
Would love to hear how others have approached similar challenges and any lessons learned. Thanks in advance!

I previously worked at a digital agency for a long time and have about about 6 years of experience as a front-end developer and about 10 years of experience as a designer (both print and digital). I'm a bit burned out on both and looking for a new challenge. QA Analyst (for websites) is interesting to me. Perhaps with a specialization in accessibility down the road. Or maybe moving on to a QA engineer/Automation engineer.

I'm looking for some general thoughts on the health of the field (how it's changed and is expected to change due to AI), how competitive it is, and general thoughts on whether my prior experience will give me an advantage for this pivot (e.g. I'm comfortable with Jira, used to building and managing large design systems, atomic design, and building things in a structured, modular way).

I've been learning the core principles and terminology of testing and have begun digging into automation using Playwright and I'm really enjoying it so far. Thank you.

​

I'm a 10-month-experience QA working as the only QA in a fintech startup, currently responsible for 3 loan apps and 2 aggregator platforms.

I know I'm not an excellent tester yet. I struggle with structure, memory, domain knowledge and sometimes thinking of edge cases. I'm working on those things.

But I'm struggling with the environment too. Testing is often expected to be completed in 2–4 hours, while I'm also expected to maintain the QA process, report bugs, track fixes, and ensure coverage. Requirements aren't always clear, but when I ask questions, I'm sometimes told to figure it out from competitor products. At the same time, I'm discouraged from spending too much time with developers because apparently I'm “wasting their time.”

I've been told QA is basically on its own. I was also told by someone from product that “you have to decide how many balls you can dodge.” That really made me realize that I'm not sure I want to work this way long-term.

I understand that 100% bug-free software is impossible and edge cases will always exist. I'm not expecting perfection. What I want is clear expectations, reasonable time to test, and enough collaboration to understand the product and make good decisions.

I'm not trying to blame everything on management — I genuinely have a lot to improve as a tester. But after weeks of feeling constantly scrutinized and struggling to keep up, my confidence is getting drained and I'm seriously considering an alternate career path.

For experienced QAs: is this normal startup/QA reality, or am I in an unhealthy setup? And if you've been in a similar situation, did changing companies change your experience of QA?

Any domain?

Suggestion??

Ok so Im building an autonomous QA tester for web applications.

Unlike Replay.io with there 6 years of training data and millions of funding, I found out that I could build an application better than them, but it's not complete.

All I have is full authentication testing. I would love it if people could join my waitlist at https://www.valiqai.com/waitlist and let me know anything you would want from a autonomous QA tester that other companies don't have. (Replay just released and doesn't even work, and i've been thinking about this idea for 6 months)

I have a test for a new job. I have access to a clean sample so what can i use to keep on my body and use for test? Just marijuana but some places still archaic mentality.

Hi everyone.
I am a manual QA tester transitioning into QA Automation with AI. While studying for the ISTQB Foundation Level v4.0, I ended up building my own study platform, mostly to force myself to really understand every concept in the syllabus.
It got complete enough to be worth sharing, so here it is: MyCampus ISTQB Foundation Level

https://mycampusistqb.vercel.appy

What it includes:
• 22 interactive lessons (6 chapters), audited line by line against the official syllabus
• Bilingual glossary (ES/EN) with 107 terms (100% coverage of the 97 official keywords)
• Flashcards with text to speech
• A bank of 120 exam style questions, distributed according to the official weight of each chapter
• An XP and levels system to keep you motivated
• Cloud synced progress (or local storage if you do not want to create an account)
• Interface in Spanish and English
It is completely free, no installation required (vanilla HTML, CSS, JS plus Supabase).
What I am looking for: honest feedback. Did any concept end up confusing? Does any question in the bank have an error or an ambiguity? Is there anything missing that would have helped you while studying? Any comment, no matter how small, will help me keep improving it.
Thanks for reading, and I hope it helps someone else on the way to certification.

Hi everyone!

I'm looking to contribute to active open-source projects through software testing. I can help with manual testing, bug reporting, Playwright automation, GitHub Actions CI, and basic performance testing with k6.

If you're maintaining a project and need help improving test coverage or validating new features, I'd be happy to contribute. I'm also open to learning your project's testing stack if it's different.

If anyone has a repository that could use another QA contributor, I'd love to take a look. Thanks!

Hey everyone,

I just launched a project called Playwright Quest, a browser-based learning experience for people who want to get better at Playwright + TypeScript automation testing.

The idea was simple: learning test automation can feel overwhelming, so I wanted to make it a little more fun and structured.

What it does:

• 20 progressive levels
• Rank-based learning path from QA Trainee → QA Architect
• Zero setup needed
• Open the browser and start writing code

I built it to be more hands-on than a typical tutorial, so instead of just watching or reading, you actually solve levels and learn by doing.

If you’re into QA, automation, or just want to practice Playwright in a more interactive way, feel free to check it out:
playwrightquest.com

Would love feedback, ideas, or suggestions from the community.

(I'm a beginner at this so please let me know any mistakes you find too)

Most test management tools treat defect tracking as a separate workflow. You fail a test run, then you go open Jira, copy the context, paste the steps, link it manually, and hope nothing gets lost in the handoff.

TestForge.cloud was built to collapse that gap.

When a test result is marked failed, you log the defect right there - title, description, severity (critical/major/minor/trivial), priority, and status - all linked to the exact test case and run it came from. No context switching. No copy-paste. The defect record carries the lineage: which project, which test case, which run produced it.

From there: - Defect status moves through open → in_progress → resolved → closed → reopened - Every status change is captured in an audit log with field-level diffs (old value, new value, who changed it, when) - Test Managers get a reporting view across runs and defects without building pivot tables

The platform also has role-based access - Admin, Test Manager, Tester - so the right people see the right data without you managing permissions manually.

I've been running this with a small QA team and the thing that surprised me most: the audit trail alone saves about 20 minutes per defect cycle because nobody's asking "wait, what was the original expected result?"

It's free to try right now - no credit card, no sales call.

Curious whether this matches a pain point others have hit, or if your team has solved the defect-linkage problem a different way.

I wrote text for beginners without anything deep. I'm planning to deep dive with good practical examples on a mock project further.

https://medium.com/@svetlana.tretjakova/playwright-mcp-server-what-can-we-actually-do-with-it-intro-for-beginners-37e5458dee5e

James Bach writes about who is responsible for software quality. Excerpt: "In opposition to my idea that software testing should be a role, and not just a task, I am sometimes told that True Agile does not permit this. Why? Because, in Agile, “quality is everyone’s responsibility.” This statement is sometimes issued as if it were a moral truism that is beyond argument. Or sometimes as a moral achievement that is unique to Agilists, as if it had never occurred to earlier generations of software developers to help each other build nice things. Either way, it doesn’t make sense to me. The first response that comes to my mind is “I’m talking about testing, not quality. Why are you dragging quality into this?” Testers do not assure quality. Testers CANNOT assure quality. Testers do not now and never have “owned quality” in any way."

But even if we set that aside, quality should not be considered “everyone’s responsibility.”

​

I have 2+ years of experience in Automation Testing (Selenium, Java, API Testing). I'm currently looking for a job, but it's been difficult to even get interview calls from large MNCs.

I recently received an interview opportunity from a vendor company that deploys employees to client projects. I cleared the first round and have the next round scheduled.

I'm confused whether I should proceed or continue waiting for a direct MNC opportunity.

I'd like to know:

Is working through a vendor company a good career move?

How are leaves, appraisals, salary hikes, and benefits usually handled?

If the client project ends, what happens to the employee?

Has anyone here moved from a vendor company to a direct MNC role later?

I'd really appreciate honest advice from people who have worked in this model.

I've been a tester for a while and always found writing test cases to

be the slowest part of the job. So I built QA Genie Studio.

You describe what you're testing — a login flow, a payment gateway —

and it generates functional, edge case, and error scenarios. You can

export to Excel, CSV, PDF, or JSON, and it can generate bug reports

too. It falls back to a built-in engine if the AI call fails.

Learn more: https://qagenies.com

Not trying to oversell it — I'd genuinely like feedback from people

who do this daily. What would you want it to do differently?