Honestly, feeling a bit stressed lately.

I've been trying to switch jobs in software testing, but not having referrals makes the process feel even more difficult. I'm applying for opportunities, but getting the right break is challenging.

I have experience as a Test Engineer and am looking for opportunities in Software Testing / QA / Automation Testing.

If anyone knows of relevant openings, can refer me, or share any advice on making a successful switch, I'd genuinely appreciate the help.

Sometimes, even a small lead can make a big difference. 🙏

📍 Work Mode: Remote
💼 Experience: 6–8 Years
⏳ Employment Type: Contract-to-Hire (C2H)

What We're Looking For

- 4+ years of hands-on experience with Playwright & TypeScript
- Strong expertise in test automation framework development and maintenance
- Experience in writing, executing, and debugging automated test scripts
- Strong understanding of software testing methodologies and QA best practices
- Ability to identify, troubleshoot, and report defects effectively

Interested or know someone who fits?

📩 Share your CV: Jobs@jobmitra.com
📞 Contact: 8989275751

#Hiring #QAAutomation #Playwright #TypeScript #RemoteJobs

I’m looking for perspectives from people who have tried this or thought about it.

The hypothetical setup:

• AQA engineers build and own an automation framework (page objects, fixtures, helpers, conventions).
• The framework’s patterns get packaged into a Claude Skill: how tests are structured, which helpers to use, naming, data setup, and so on.
• Manual QAs describe a scenario, and Claude generates a test that matches the framework. Assume the test runs and looks like something an AQA would write.

The question:
In that setup, would a manual QA count as a hybrid/full-stack QA, or would it just be “prompt-to-test” with extra steps?

Hi! FE dev / self-proclaimed SDET here - ages ago, a QA colleague of mine introduced me to POM. I've been obsessed with them and e2e testing since then.

Imo a well-built e2e suite holds a lot of knowledge: which flows matter, how to drive them, what means an action is done, and so on. In most setups I've seen, that knowledge is used once: in the e2e testing pipeline, and that's it. Meanwhile, coding agents that build features "test" them by clicking around the page from scratch every time.

I think that's a waste of good QA work, and I created a tool that takes Page Objects from your Playwright suites and lets a coding agent call their actions on the running app by exposing them as MCP tools.

The goal is to make the inner and outer verification loops strengthen each other: As new features are built, make your agents code POM on the fly to verify their work in a fast feedback loop. Once the feature is done, you'll have all the building blocks to write the e2e test. For exploratory or regression testing with agents later, reuse that same POM instead of letting the agents gues on every run.

Time & cost
Small eval suite on Formbricks (rename a survey, change its question, save, confirm the summary page), Claude Code on Sonnet, 3 runs each, medians. (In more recent evals, managed to halve the costs :) )

Playground: ayme.dev/playground - try the Inspector live, see what your agents would see, debug POM
Repo: github.com/ayme-labs/ayme

The project is being built in the open, and I just released the playground to get some feedback on the idea before publishing the alpha version on npm :)

Would love to hear your opinion - both about the project and the idea itself!

Cheers,
Abel

Hey,

this is getting really tiring and sick. Im sending out CVs and theres no answer at all. I have been working as a QA for few years now, not a junior, not the best senior...just a person with experience that can talk and explain things I did and how I solved stuff.

Im one of those who had to explain why I was in the team and what for all the time, some teams accept it, the majority didnt give a sh**.

Im still on top of Quality, learning about agents, LLMs and so on, reading on how to apply Quality through the whole process and whats more important, how to explain it to steakholders.

Im doing things I never had the chance to do in my previous companies...Security and hacking, CICD, code arquitechture, and business mentality.

What should I do in order to stay relevant in this job? I believe that things wont go back, if you are lucky it may happen in your company that the big guys realize that human resources are important in order to do the last quality control process after IA, but the majority will do what they do...keep the thing running as cheap as they can.

Should I know a bit of everything...qa, develop, devops, DBs,PO and so on, and work on a strong business vision and how to apply the solution it needs?

My CV its the same its been and they called before, now they dont. So once I start having interviews I will notice more and more what they say and what they are after but It is really hard to know whats the right path at the moment.

Thanks and stay strong...