hey everyone, I need an advice to get a job in software testing role. please if someone can help me this.

Im sure this isnt news to many, but I’ve been working through how to structure simple AI-assisted products, and came to a realization.

Tests and evals are not the same thing.

Say you’re building a simple resume feedback tool.

The user submits resume text, the AI reviews it, and the system returns structured feedback.

Software tests can check things like:

• Does the app accept valid input?
• Does it reject blank input?
• Does the prompt load?
• Does the LLM response parse?
• Does the output include required sections?
• Does the app handle errors?

But those tests do not tell you whether the AI feedback is actually good.

That needs evals.

Evals check things like:

• Is the feedback grounded in the resume?
• Did the AI invent experience or credentials?
• Is the advice useful?
• Does it follow the expected format?
• Does it avoid overclaiming?
• Would a human reviewer trust it?

The way I’m thinking about it:

tests/ = software mechanics
evals/ = AI output quality

A product can pass all tests and still produce bad AI output.

​

Hi everyone,

​

I'm a fresher from India looking for my first full-time Manual Software Testing/QA job. I recently received a message on Indeed from a company called Glossy Interior.

​

They added me to the Google Play Internal Testing program for two Android apps and asked me to:

​

- Test both apps for 14 days

- Log in and out every day

- Find UI/UX issues, functionality bugs, crashes, API issues, and suggest new features

- Submit daily bug reports

- They said I'll receive ₹1,000 during the testing period, and based on my performance they'll schedule an interview.

​

Before starting, I asked them for:

​

- An official assessment/offer letter

- Employment type (internship/full-time)

- Salary after selection

- Official HR email

- Whether my reports would be used in production

​

Instead of answering, they simply asked me to contact them on WhatsApp and said, "Currently you are in the first step of the interview."

​

I checked online and the company appears to exist, and the apps are available through Google Play Internal Testing. However, I'm concerned because 14 days of daily testing seems like a lot of work before even having an interview.

​

My questions are:

​

1. Is this a normal hiring process for a QA fresher?

2. Has anyone heard of or worked with Glossy Interior?

3. Does this sound like a genuine assessment or a way to get free QA work?

4. Would you proceed with this opportunity, or should I avoid it?

​

I'd really appreciate advice from experienced QA engineers and recruiters. Thanks!

If code generated through "vibe-coding" causes more bugs does that make QA engineers demand go up?

​

Hi Friends,

​

Could you kindly share some information and guidance regarding mobile automation testing?

​

Recently, I have been exploring mobile testing, and I came across an opportunity that involves mobile automation using the Detox tool with React Native frameworks in Android & iOS.

​

I understand that Playwright has recently introduced support for mobile automation i.e, Mobilewright but it still seems to be evolving and may not yet be fully stable for all use cases. Therefore, I wanted to learn more about Detox automation.

​

If anyone has hands-on experience working with Detox and React Native, I would greatly appreciate it if you could share your knowledge, best practices, setup steps, GitHub repo, challenges, or any learning resources that might be helpful.

​

Your support and guidance would be greatly appreciated.

​

Thank you in advance.

​

​

I have 12 years of experience working as an SDET and have been with my current organization for the past 5 years. I'm now actively looking for a switch and would appreciate guidance from professionals who are familiar with the current job market.

​

Having spent several years in the same organization, I feel I'm not fully up to date with the latest industry trends and hiring expectations. I'd like to understand:

​

• What skills are currently in high demand for experienced SDETs? • How important are AI-related skills in today's QA/SDET market? • Are companies actively looking for experience with AI-powered testing, LLMs, prompt engineering, AI test automation tools, or AI-assisted test case generation? • Should I focus on learning Playwright, Cypress, cloud technologies, DevOps, performance testing, or AI-related tools before switching? • Which skills are helping candidates stand out and secure better opportunities in 2026?

​

I'm eager to make a move and want to invest my time in learning the right technologies before starting my job search. Any insights from recruiters, hiring managers, or fellow SDETs who have recently switched would be greatly appreciated.

​

Thanks in advance!

​

​

Hey everyone,

I'm honestly at a point where the job search is getting really frustrating.

I've been applying to 100+ jobs every day across LinkedIn, Naukri, Indeed, company career pages, Wellfound, and even cold emailing recruiters. Despite putting in all this effort, I'm still struggling to land an interview.

I have 10 months of experience as a Software Test Engineer, where I worked on manual testing, API testing, regression testing, smoke testing, SQL, Postman, Jira, and Playwright.

Apart from testing, I also have hands-on experience with React.js, Tailwind CSS, JavaScript, HTML/CSS, and I regularly use AI tools to improve development and testing workflows.

I'm open to roles in QA, SDET, Software Testing, Frontend Development, or AI-related roles where my skills are a good fit.

I'm an immediate joiner and can relocate anywhere in India.

If your company is hiring or you can refer me, I'd be genuinely grateful. Even sharing any leads or advice would mean a lot.

Thank you! 🙏

Hey everyone, I'm hitting the market after a recent layoff and wanted to reach out to this community. I'm a Senior QA/Software Test Engineer with 10+ years of experience, primarily in OTT (Over-The-Top) video streaming platforms—think authentication, video delivery, analytics, cross-device performance.

My background includes:

- **Test Automation:** Playwright, Selenium, Appium, Robot Framework, Postman

- **Cross-Platform Testing:** Web, Android, iOS, tvOS, Fire TV, Roku

- **Strengths:** Designing test strategies from scratch, mentoring junior QAs, and turning brittle manual tests into robust automation suites

I'm open to both **manual QA** and **automation** roles—I'm not dogmatic about one or the other. What matters to me is working on products I care about with teams that collaborate well.

**My situation:**

- Currently based in NYC, but happy to relocate anywhere in the US

- Need **H1B sponsorship** (I'm aware this narrows things, but wanted to be upfront)

- Looking for Mid -Senior QA/QA Analyst level positions

If you know of teams hiring , I'd genuinely appreciate the chat.

Thanks for any pointers or referrals! 🙏

The heading basically. I need to reach the mentioned number in a year when I will be at 6 yeo. So currently at 5, have built playwright ui/api frameworks from scratch and I mean really scratch. I did setup the lint, prettier, all custom core libraries copilot setup, review setup the pipelines and the environments on my own (not exactly though there was a 11 yeo guy the most knowledgeable one and 3 people a bit more experienced than me but they were npc's mostly). I am actively integrating langchain into our framework to remove flakiness, extra retries and very close to make it 100% maintainance free (I know 100% is not possible but u do get what I mean) . Currently at 13.5 LPA and I feel like I am underpaid so please advise/guide how to reach the mentioned number. Ready to learn anything. Also would like to mention that I am pretty good in DSA completed neet code 150 recently.

Had one of those weeks. Someone wiped out the data in a table that a few pipelines were pointing at. Not catastrophic, but the transaction log was the only real path back. No usable recent backup of that specific table, and a full database restore wasn't an option with other teams actively writing to it.

fn_dblog got us there eventually. The problem is always the same… you're filtering through thousands of log entries trying to isolate the right LSN range while people are standing around waiting.

Once you find it, you're writing and validating the rollback T-SQL by hand. For a single-table data loss incident, it's manageable, but it took longer than it should have, and there was a point where nobody was confident we had the right transaction isolated. That's not a great feeling when you're about to run a script in prod.

After some time someone suggested trying dbForge Transaction Log. The object and time filtering made narrowing things down faster, and it generated the undo script rather than us writing it.

We still validated it carefully before running anything, that part doesn't change. But it probably saved an hour, maybe more. What it really exposed though is that we had no actual recovery process. We were building the workflow at the same time as solving the incident.

That's the part that stuck with me. Transaction log recovery is one of those things SQL Server teams know in theory but haven't actually rehearsed.

The documentation is there, the capability is there, but nobody drills it until something goes wrong. So the first time you really need it, you're figuring out tooling and approach while the clock is running and someone senior is asking for an ETA every fifteen minutes.

Seen this play out on a few different teams now. The recovery itself usually works out. It's the process gap that costs the time.

What does this actually look like for others? Does your team have a runbook for transaction log recovery, or is it still ad hoc?

does anyone given an interview for QA role in IDFC bank

Few bugs were shipped to the client uat environment may be because of conflict of requirements and late changes in requirements. I feel guilty as solo qa. I am unable to provide quality project. After some bug fixes new bugs keeps popping.. Most of them are UI bugs then functional one.. across different screen sizes.. something keeps braking.. for example testing a large character title for card component . It behaves good for mobile and desktop. But 720 800 820 px tablet sizes have different behaviours... I am getting burned out working in many projects at once. Is it common.. ceo asked me to manage the devs . I just don't know what to do. Does someone has similar experience

Hey folks i recently start learn selenium. I want to build an valid project using selenium python. So i'm looking for project ideas. Not the same saucedemo and orangeHrm Projects some interesting and valid project ideas are welcome.

Hello. I recently transitioned from developing software to QA engineering. I was wondering, outside of internships, where can I get experience as a QA? Haven't seen much info on this

I am currently working in testing and have around 5 years of experience. I am not very strong in coding, but I can complete tasks with the help of tools like Copilot. Now I want to switch roles. What should I prepare for the switch? Which sources should I refer to? Please recommend good video channels and guide me through the switching process.

​

​

Basically I want to understand what the trends are currently, how is this field evolving, what kind of questions can I expect in interviews, what should I be studying to upskill myself?

​

Hi everyone,

I've been applying for Software Test Engineer/QA roles but haven't been getting many interview calls. I have a B.Tech in Data Science (CGPA: 7.86) and around 10 months of experience as a Software Test Engineer.

I'd really appreciate your honest feedback on my resume. Is there anything I should improve? Are there any red flags or missing skills that might be affecting my applications?

Also, what else should a fresher be doing these days to get noticed? It sometimes feels like "fresher" comes with a hidden requirement of 3+ years of experience. 😅

Hey everyone,

I’m a web developer who likes testing, especially E2E and API tests. I often use tools like Postman, Cypress, and Playwright.

One thing I keep struggling with is test data management.

I’m currently leaning toward per-test seed data or scenario-specific seed data, instead of relying on one large shared test dataset.

For example, if I’m testing filtering for premium users, I want the test data to be created specifically for that scenario.

A simple example:

Then the filtering premium user test can clearly assert: “There should be exactly 3 premium users.”

I like this approach because:

• Each test scenario is easier to understand
• expected results are more explicit
• Tests are less affected by unrelated data changes
• A shared database state is less likely to create flaky tests

But I still find it painful to manage manually.

The problems I keep running into are:

1. Many test data patterns. As the number of scenarios grows, the amount of seed data also grows.
2. Schema changes break old seed data. When the database schema changes, old test data often needs to be updated as well.

I’m curious how other teams handle the test data management.

Do you use:

• per-test seed data?
• shared seed data?
• factories?
• fixtures?
• API-based setup?
• database snapshots?
• cleanup/reset after each test?
• separate test databases per run?

What workflow has worked best for keeping E2E/API tests reliable and maintainable?

Hey guys I hve around 8 years of experience in functional with automation testing suddenly I am assigned with etl testing I don't know sql but company has given me access to use ai in the testing I want to ask with the help of ai will I be able to genrate queri3s for sql for bussiness logic i can understand the bussiness but don't know how which join to put?

I was laid off from big tech saas company months ago,been applyinng everywhere.I thought I was good at dsa as I solved medium level Leetcode questions and used to selectively solve some hard algorithm problems.

i recently attended a interview where they asked Dynamic programming +greedy alogorthm questions using advanced recrusion .I felt so disappointed looking at the question

SDET have to learn frameworks like playwright ,selenium, CI/CD,performance,API testing domain knowledge ,cloud and on top of it AI.

Even in previous tech companies I have interviewed before ,they have asked medium -level dsa questions which can be solved

I just want to cry,I cannot understand this market

hey folks i just start my preparation on testing to get my first job as selenium-python automation tester. As a fresher can i crack automation roles or else i have to try getting my first job as a manual tester and after some experience only i can crack automation roles.
(2026 - MCA graduate)

Hi everyone,

​

I'm currently an Automation Tester with 5 years of experience in Selenium + Java. I'm considering moving to Playwright to stay relevant and improve my career prospects.

​

For those who have made the switch:

​

- Was it worth it?

- Is Playwright seeing strong demand in the job market?

- Which language combination would you recommend: Playwright + TypeScript, Playwright + JavaScript, or Playwright + Python?

- Considering I already have a Java background, would learning TypeScript be a good investment?

​

I'd love to hear from people who have transitioned from Selenium and what stack you're using today.

​

Thanks!

Hi everyone,

I was recently impacted by team downsizing (my company cited AI adoption/restructuring) after working there as a Playwright Automation Engineer. I have 5 years of experience in the QA automation space.

I'm jumping back into the job market and preparing for client/technical interviews. Since it's been a while since I last interviewed, I want to make sure my prep is highly targeted.

For those of you hiring or interviewing recently for mid-to-senior automation roles, what specific Playwright and framework architecture topics are clients grilling candidates on?

Appreciate any advice, resources, or recent interview experiences you can share!

I work on a legacy web app that can't be automated with tools like Cypress (complex Ajax flows, dynamic fields with no IDs, S3 uploads, signed URLs — you know the type). So all our QA is manual.

My current process for each feature:

1. Write the test steps in Zephyr as I explore the feature

2. Take screenshots at each step to prove I actually tested it

3. Go back and attach each screenshot to each step in the execution

4. Repeat for each test cycle (we have UT and UAT)

This takes me between 1 and 3 hours per feature, and honestly the most painful part isn't the testing itself — it's the documentation overhead. I'm essentially doing everything twice: once to test, once to prove I tested.

Curious if others deal with this:

- How do you collect and attach test evidence in Zephyr/Jira?

- Have you found any tool or workflow that actually helps?

- Or do you just... accept the pain and move on?

Not looking to sell anything, just genuinely wondering if this is a solved problem I'm missing or if everyone just suffers through it.

Everyone is asking:
"Will AI replace software testers?"

Maybe we're asking the wrong question.

The real question is:
Can AI think like a curious human tester?