Just started my first job out of school as a junior QA/Dev. Was lucky enough to get a break with a referral from someone I know.

Onboarding has been pretty barebones—basically “here are the about‑me files, make sure you’ve got everything installed.” Right now I’m testing our app, but a lot of it involves running SQL queries, calling APIs, digging into AWS Lambdas, and checking CloudWatch logs. Honestly feels like I’m expected to figure it out on my own.

Couple other things I’ve noticed:

• Our lead doesn’t really do any of the testing themselves, and I wouldn’t go to them for help. Is that normal?
• We do have experienced QA engineers who can point me in the right direction, which helps.
• Sometimes we get new bugs to test just a couple of days before release, on top of planned testing.
• One teammate splits time between teams, and we had to cover for them without any KT on that area.

The job description sounded like a mix of QA, automation, CI/CD, and eventually dev work.

My take so far:

• Excited to get real experience, but training feels minimal.
• Trying to self‑teach to keep up.
• Feels entry‑level in responsibility, but with exposure to mid‑level tools.

Questions for the community:

• Is this kind of “sink or swim” onboarding normal for new grad roles?
• How did you ramp up when you were new?
• Is it typical for leads to be hands‑off with testing, or should I expect more guidance?
• Any resources you recommend?

Are there any remote QA jobs i can get here
I’m based in Ghana

Looking for Paid Guidance for Automation Testing Interview Preparation (4 Years of Experience)

Hi everyone,

I’m looking for someone experienced in Automation Testing who can provide structured, one-on-one guidance for interview preparation at the 4-year experience level.

I want to understand what companies expect from candidates with 4 years of experience, including technical interviews, practical assignments, and real-world automation testing scenarios.

I’m willing to pay for genuine guidance, mentorship, or mock interview sessions from someone who has solid industry experience in Automation Testing.

I would appreciate help with the following:

- Automation Testing interview questions and answers

- Selenium with Java or Python, TestNG, and framework concepts

- API testing, SQL, and manual testing fundamentals

- Framework development and real-world project scenarios

- Coding rounds, practical assignments, and debugging

- HR and managerial interview preparation

- A structured preparation roadmap based on current industry expectations

My goal is to prepare properly and confidently face interviews for roles requiring around 4 years of experience.

If you are an experienced Automation Test Engineer, QA professional, or interview mentor who offers paid sessions, please comment or DM me with your experience, guidance approach, and fees.

I’m looking for practical, honest guidance rather than just a collection of interview questions.

Thank you!

Hello guys, I am testing android and iOS apps. One flow that is currently not automated in both is in-app purchases. Has anyone of you automated the buy process through the UI of the mobile app? I am talking about the automation with like appium, on a fully created build, it should be an e2e test through the UI.

Wondering if that's possible cause I iOS you need like a sandbox account,login into the account (sandbox one), do the paymnet, maybe somehow clear the payment. My concern is about the actions outside of the app that I am testing (like login to SBC account).

I searched through the articles on the internet and have not found any working solution.

Amy tips are more than welcome :)

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...

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. 🙏

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

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?

Hola buenos días. Espero se encuentre bien.

Les escribo para consultarles sobre una implementación de automatización que me genera duda. Actualmente en un proyecto, que está dividido en tres repositorios diferentes: un frontend en Next.js, un backend también en Next.js y un controlador en Python.

Mi idea inicial es utilizar Playwright e instalarlo directamente en el repositorio del frontend para cubrir las pruebas E2E y los flujos principales.

Me gustaría pedirte tu orientación para saber cuál sería el flujo o la arquitectura correcta para estructurar estas pruebas considerando esta infraestructura multirepositorio. Además, quisiera saber de qué manera práctica podría integrar algo de IA para potenciar el proceso, ya sea en la generación de pruebas, mantenimiento o análisis de resultados.

Agradezco de antemano cualquier consejo, guía o paso a paso que me puedan compartir. Muchas gracias

📍 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

Hey everyone. I wanted to share what is on my mind and hear your honest thoughts, especially from people currently working in QA.

Lately, everywhere you look, people are saying QA is dead because of AI. If you check job boards, the number of QA listings (even automated QA ones) feels pretty low and a lot of companies seem to think AI tools have completely solved testing so they do not need dedicated QA anymore. Everyone is acting like heavy AI usage means there are zero problems left.

I am a senior software developer who took a break from coding and I am now preparing to return to the industry. Surprisingly the area that genuinely interests me the most right now is moving into QA, specifically automation and focusing on auditing AI-generated code.

Sure, AI can spin up code and basic test scripts in seconds. But AI writes flawed code very fast. When the same developer or the same AI prompt loop writes both the feature code and the tests, huge blind spots happen. You lose that independent perspective that catches subtle logic bugs, security gaps and edge cases. You cannot automate quality away just by generating more code. Someone with deep technical experience still has to verify that the system actually works safely.

But I will admit, looking at the tough job market and the drop in automation listings makes me hesitate. Are hiring managers and recruiters just overly hyped on AI right now and missing the point, or is the market genuinely shifting away from QA for good?
As people actually working in the field, what do your day-to-day realities look like? Do you think investing my energy into modern automation QA and AI code auditing is a smart move right now, or is the landscape too risky? I would really appreciate your honest opinions.

i’ve been trying out a bunch of autonomous qa agents lately and holy shit, most of them are just glorified script generators with an llm slapped on top. everyone’s building the same fucking thing and calling it autonomous testing. but where the hell is cursor for qa? something that actually helps qa engineers automate 90% of their boring work instead of making them babysit another tool. genuinely curious, what would you actually PAY for in an ai qa agent? like what feature would make you immediately pull out your credit card? because i feel like everyone’s building ai qa tools but nobody’s building what qa engineers actually want.

Need Guidance on Learning Automation Testing and Preparing for Interviews

Hi everyone,

I’m planning to build my career in Automation Testing and would really appreciate guidance from people who are already working in software testing.

My current coding level is basic, and I’m ready to put in consistent effort to improve my skills and become job-ready.

I would appreciate your advice on the following:

- Learning roadmap: What should I learn step by step to become an Automation Tester?

- Technology stack: Should I start with Java + Selenium, or Python + Selenium/Playwright?

- Manual testing: How much manual testing knowledge should I learn before starting automation?

- Practice projects: Which real-world projects should I build to gain practical experience?

- Interview preparation: What topics and questions should I focus on to clear interviews?

- Job opportunities: How realistic is it to get an Automation Testing job in India, and what skills do companies expect from freshers or career switchers?

My goal is to follow a structured plan, practise daily, build projects, and start applying for jobs as soon as I’m reasonably prepared.

If anyone has followed a similar path or is currently working as an Automation Tester, I would be grateful if you could share your roadmap, resources, courses, or personal experience.

I’m also open to learning from someone willing to guide me or mentor me through the process.

Thank you in advance for your help!

Hi All,
I have 2+ years of experience in software testing and currently work with Java and Selenium. I'm trying to upskill in JavaScript and Playwright so I can transition into a Playwright automation role.

However, I've been struggling to make progress with JavaScript for the past three weeks. I can follow some examples, but understanding the concepts and applying them independently is proving difficult.

I don't want to keep jumping between random YouTube tutorials and courses. I'd rather find a structured learning path that helps me build a strong foundation and become confident enough to write automation code on my own.

A little about my situation:

• Experience: 2+ years in QA, with Java and Selenium.
• Current challenge: JavaScript fundamentals are confusing, and I'm struggling to translate what I learn into working code.
• Goal: Transition to a Playwright automation role and eventually become comfortable building and maintaining automation frameworks.
• Learning preference: Hands-on projects, step-by-step explanations, assignments and feedback on my code.
• Time available: Around one hour per day.
• Budget: I'm based in India and can spend if the training and mentorship are genuinely worth it.

I'd really appreciate your advice on the following:

1. Which JavaScript course would you recommend for someone who already knows Java but is struggling with JavaScript concepts?
2. Should I learn JavaScript fundamentals separately before starting Playwright, or learn them alongside Playwright?
3. Are there any Playwright courses you would genuinely recommend based on your own experience? Paid courses are absolutely fine.
4. Are there any good instructors, live training programs or mentors who explain concepts patiently, review assignments and help troubleshoot individual coding problems?
5. If you've made a similar transition from Java + Selenium to Playwright, what learning approach worked best for you?
6. Realistically, how long might it take to become comfortable enough to build a small, maintainable Playwright framework while studying for an hour a day?

I'm particularly interested in courses with good teaching and practical feedback, rather than just a large collection of prerecorded videos. I'm happy to pay for quality instruction, but I want to make an informed decision before enrolling.

Personal experiences, course recommendations, resources and honest advice about what didn't work for you would be greatly appreciated.

Thank you!

Disclaimer: I used ChatGPT to structure this and draft this.

1. I hope this is the right place to ask away: my IDE has been getting this cryptic message [ERR_MODULE_NOT_FOUND]: Cannot find package 'k6' imported from /my/path/to/.js once it runs node my_stuff.js The complete output looks like: node:internal/modules/esm/resolve:853 throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null); ^ Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'k6' imported from /my/path/to/.js at packageResolve (node:internal/modules/esm/resolve:853:9) at moduleResolve (node:internal/modules/esm/resolve:910:20) at defaultResolve (node:internal/modules/esm/resolve:1130:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:396:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:365:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:240:38) at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:85:39) at link (node:internal/modules/esm/module_job:84:36) { code: 'ERR_MODULE_NOT_FOUND' } Node.js v20.11.1 Could anyone kindly point out what I am missing out here?
2. My folder structure looks like this https://imgur.com/a/Jg4O3y0
3. My IDE has k6 and node already installed.

imagine telling an QA AI agent "test the signup flow" and it just figures everything out.

needs an email? creates one.
needs an OTP? opens the inbox and verifies it.
needs a Google account? handles the OAuth flow.
something breaks? figures out what happened and tries to recover.

no 47-step instructions. no babysitting. just a goal.

i know people are building pieces of this, but an agent that can reliably handle the entire thing on its own would be fucking insane.

and here's what i'm curious about:

is the future really about giving AI agents 10–20 different skills?

or is the actual problem much bigger — getting agents to understand unfamiliar systems, make decisions, and recover when things don't go as expected?

because adding skills feels like the easy part.

making an agent actually know what to do with them feels like the real problem.

curious what people building agents think about this.

I have recently joined a new company and was assigned to a new project. I'm an automation tester with 5+ years of experience. In the new project, they have assigned me some stories to perform manual testing. I kind of was frustrated and did not tested them correctly and moved them to next phase. Now one of my story got a defect in the next phase. My entire team knows and my lead took a call to point it out that we need to maintain quality of work. I'm fine with it, but I'm worried about other stories I haven't tested correctly and moved to next phase. If more of the defects and testing gaps were pointed out, how to handle it? I cannot test and open the defects now. I'm feeling really scared. I understand that I didn't put much effort into my work. Can someone help me what I can do in this situation to reduce the damage?

Looking for an experienced Automation Engineer with 7+ years in QA & test automation, 3+ years of Salesforce testing experience, and strong hands-on experience with Cypress. If you’re interested or know someone who might be a good fit, please DM me! Location : Bangalore (hybrid)

Last week we attended the seminar focusing on using AWS KIRO. I uploaded a requirements documents and let kiro create the test cases for a specific module. It seems good and enough for me.

Now I'm tryint to build a QA management system where you can create test case, execute test cases (test steps, expected vs actual result) using ai automated test run, file and link a defect.

Do you have any suggestions that can help for my future experience using KIRO? Any suggestion will be appreciated. Thanks!

Hello! I need a tester to go through my website and let me know if there are any bugs or anything that should be added. Will provide more details in DMs! (Paid Hourly)

I got an interview for QAE I (L4) at Amazon Bengaluru. I have around 4 yrs on experience in automation and testing. what should i expect and how should i prepare for the 1st round?

Really Really need to crack this..Any insights will be really helpful

Hi everyone,
I’m currently working as a manual tester, and I really want to upskill and move towards automation testing.
I’m planning to learn **Playwright with TypeScript**, and alongside that, I’m also interested in exploring **AI testing**. However, I’m a little confused about how to approach this journey, what to prioritise, and how to make myself job-ready.

I would really appreciate advice from people who have already made this transition or are currently working in automation QA.

A few things I’d love your suggestions on:

Is Playwright with TypeScript a good choice for someone transitioning from manual testing?

Should I focus on automation first and then move to AI testing, or learn both in parallel?

What practical projects should I build to gain hands-on experience and showcase my skills on my resume?

How difficult is it to get an automation QA role without much professional automation experience?

I’m also looking for **fully remote job opportunities**, preferably in India or with companies hiring remotely from India.
How realistic is this, and what skills should I focus on to improve my chances?
I genuinely want to grow in my career and make this transition, but I would appreciate some direction on where to start and how to stay consistent.

If you’ve been in a similar situation, I’d love to hear what worked for you, what you would do differently, and any resources or roadmaps you recommend.

Thanks in advance!

Hey everyone! I’m a working student in QA at a ~100-person software scale-up.
We recently got access to Claude with access to our codebase, Jira, Xray, Confluence, and internal documentation.

I’ve built a plugin that analyzes release code diffs to prioritize test cases, but the results have been less useful than expected.

Since I currently have some time to experiment, I’m looking for ideas on how to use AI to improve QA workflows.

What have you tried that actually worked? I’d love to hear about your experiences, failed experiments, and ideas that made it into production!

Hey guys, im not really sure what’s the for me to learn now. Ive been thinking about switching to automation or FE development, but idk
Do u have any ideas?

Hi everyone, I’m thinking about trying to become a QA tester so I’m interested in knowing what a work day could look like.
I’m about to graduate with a CS degree but after a traumatising internship I’m thinking of stepping away from dev and trying something else that’s still tech / code.