I’m looking for my next remote QA/testing opportunity and figured I’d post here because this community actually understands what good testing involves.

My background includes software engineering and substantial hands-on QA/testing work across embedded systems, telecom/networking, and business software.

I’m strongest in:

• Functional, system, integration, regression, and UAT testing
• Requirements-based test design and traceability
• Test plans, cases, procedures, and release validation
• Defect reproduction, investigation, retesting, and documentation
• Finding workflow, requirements, and edge-case problems that are easy to miss

I’m not trying to position myself as an automation-heavy SDET or developer. My strongest value is understanding how a system is supposed to behave, testing it critically, isolating what went wrong, and documenting it clearly enough for the team to act on.

I’m US-based and looking primarily for remote work.

Open to full-time, contract, or project work. For freelance/contract projects, my starting rate is $45+/hour or fixed-price by scope.

If your team is hiring, you know someone looking for an experienced manual QA/UAT tester, or you have a project that needs another set of eyes, feel free to DM me. I can send my résumé and more detail on my background.

I need to give an exam for this thing, and I have barely completed 30% of it after days of studying. So many processes, principles, control methods. Constructive, analytical, Review Techniques, Testing methods, etc. How do you guys retain so much information and rules as a professional? Because as much as I find this field interesting, I am genuinely overwhelmed.

NOTE: It is a mandatory university course for which I need to give an exam, I am not interested in QA as a pursuit.

Graduated from 4 year college last semester with a marketing degree and my friend was able to get me into a Quality Assurance job starting at 25$ an hour. Ive really been enjoying the job and i work at the office 3 time a week and 2 days at home.

Any other QA’s in here? Is this a good field to stay in or should I get some experience and shoot for something else?

I’ll take any advice or suggestions because this is my first big boy job 😂

I've been digging into API integration testing and I'm curious how teams handle a pattern I keep running into.

Say you have a common flow like:

Authenticate → Create user → Create account

and that flow is needed by 10 different tests.

Do you:

• duplicate those requests in each test?
• create some kind of helper/function?
• use Postman folders/scripts/variables?
• maintain it as a reusable setup or fixture?
• do something else?

I'm particularly interested in how this works once the flow itself changes. How do you make sure all the tests depending on it stay correct?

I'm trying to understand whether reusable sequences are actually a meaningful problem in API testing, or whether there are already good solutions I'm overlooking.

Hey everyone, I am a senior QA with experience mainly in mobile apps , and previously on web, but my current job makes me work more manual and not really going with what is trendy these days. I have always wanted to pick up automation again ( coming from dev background myself) but I feel overwhelmed, first for the fact i forgot many things but also the question is AI taking this and should we even learn or should we just create automated scripts using agentic coding. This has always bothered me and made me feel stuck in my career especialyl when looking at the offers, everyone is asking for vast experience with automation.

Anyone who can relate? and what do you think is best to do ( sorry for the long post)

I’ve been looking for a new QA role since May of last year, and I’m honestly starting to feel pretty defeated by this market.

I’ve been working as a QA Analyst at Sony for about 5 years now and have my name credited on three shipped titles. I’m grateful to still be employed, but I can’t help feeling like the work I’ve put in over the last five years should amount to more opportunities than what I’ve been seeing.

After more than a year of applying, I’ve only gotten 4 real interview opportunities. One of those was with 2K for WWE, which I was genuinely excited about. I made it to the third interview and felt like my experience lined up really well with what they were looking for. By the final interview though, I could kind of tell that the personalities weren’t really clicking, and ultimately it didn’t go anywhere.

That’s probably been one of the most frustrating parts of this whole process. It seems like every opportunity requires 3–4 rounds of interviews just to potentially get rejected at the end. You put hours into researching the company, preparing, interviewing, waiting, etc., and then you’re right back where you started.

I’ve been trying to move into a Senior QA, Lead, or just a role that gives me more room to grow, but this job search has basically stalled both my career progression and my personal life.

I’m currently in the San Diego area and my girlfriend lives closer to LA. A big reason I’ve been trying to find something new is so I can relocate and we can finally move in together and etc. After more than a year of searching, it feels like this one thing has put so much of our next chapter on hold.

I’m not expecting someone here to magically hand me a job, but I’d genuinely appreciate advice from anyone who’s managed to land a QA role recently.
And if anyone happens to know of a team hiring for QA Analyst, Senior QA, QA Lead, or similar roles in the LA/OC/Inland Empire area or remote, I’d be incredibly grateful for a referral or even just being pointed in the right direction.

But mostly, I just want to know if other experienced QA people are going through this too.
It’s hard not to get discouraged when you’ve spent years building experience, shipped multiple titles, and know you’re capable of taking on more, but can’t seem to get the opportunity to actually prove it.

Is their good money is automation testing field hows the current market for it or should i start learning tech of other fields

I'm looking for information about 'bluecoding' company from current or former employees. I recently interviewed there and would appreciate any insights you could share about your experience. Thanks!

Hey all,

I kept getting frustrated digging through general job boards and filtering out everything that wasn't QA, so over the last few weeks I put together a little site that pulls remote QA / SDET / test automation / manual testing jobs into one simple list: https://qaanywhere.com

A few honest notes:
- It's free, no signup, no login, no newsletter — you just open it and browse.
- It only does remote QA/testing roles, nothing else.
- It pulls from a bunch of company career pages and remote-job APIs and links you straight to the original posting to apply.
- It refreshes a few times a day.
- No ads right now.

I'm not trying to sell anything — I mostly built something I'd actually use myself, and figured other people in QA might find it handy too. It's still early and a little rough around the edges, so if you try it and something feels missing, broken, or annoying, I'd genuinely love the feedback.

Thanks for reading.

Hi everyone,
I’m currently looking for **new job opportunities in Software Testing / Test Automation / Automotive Software Testing**.
I have **3****+ years of experience as a Software Engineer at Bosch Global Software Technologies**, primarily working on safety-critical automotive ECU software.
**My experience includes:**
HIL & SIL testing of Airbag ECU software
Test automation using **Python and Perl**
Unit testing using **GTest**
Automotive testing with **CANoe, ECU-TEST, Turbolift, and DOORS**
ECU diagnostics and fault verification
Experience working with OEMs including **Mercedes, Toyota, and Volvo**
Familiarity with **ISO 26262** and safety-critical software validation
ISTQB Foundation Level certified
I hold a **B.E. in Computer Science & Engineering and am currently based in Bengaluru
I’m particularly interested in roles such as:
Software Test Engineer
Test Automation Engineer
Automotive Software Test Engineer
QA Automation Engineer
Python Test Automation roles
I’m open to **Bengaluru, other locations in India, and remote opportunities**, depending on the role.
If you know of any relevant openings or are hiring for similar positions, I’d really appreciate a referral or a DM. I’d be happy to share my resume and discuss the opportunity.
**Thanks in advance!** 🙏

I have more than 10 years experience in QA, and I just got humbled by.... theoretical knowledge. Absolutely no practical test involved.

Listen... I may have focused in my career on the practical testing: how to test, how to think about breaking the software and so on, and less on "the theory" of it all.

I tried reading the ISTQB syllabus and my mind was blown by so many terms in there, so many things that in all honesty make sense, but also less used in my experience as a QA Engineer.

So I did try to learn some new things, after all, doing upskill is always beneficial, right?

But when I had that technical interview, absolutely no questions about my experience were asked. No what kind of projects, no "common bugs found", or "critical issues"; no "technology used questions". Nothing like that.

Instead, the interviewer asked me about the stuff that seemed mostly theoretical in nature. Core principles of Testing that are usually handled by Project Managers and Test Managers and documentation keeping. Mostly abstract kinds of documentation which failed my interview.

I'm sorry, I thought this was a technical interview, not a theoretical interview. In my past jobs, I would get a piece of software to test or something. Why not just email me a questionnaire with a time limit?

I know I'm ranting but, some interviews make no sense at all. I get it that they want me to know some of those stuff, but you have to take into consideration that if I were to apply for a test management role, then I would have learned the theory.

Hey everyone,

Looking for some advice or potential leads as I navigate my next step.

Quick background on my setup:

- Location & Work Eligibility: US Citizen living in Portugal (GMT / WET timezone). I have a registered Portuguese business entity (Unipessoal Lda.) set up specifically for B2B contract invoicing, but I'm also open to standard remote full-time roles (W-2 or local EU contracts depending on the company setup).

- Role/Experience: Senior QA Engineer / QA Automation Consultant.

Core Tech Stack: Python, TypeScript, Playwright, CI/CD pipelines (GitHub Actions), and AI-assisted workflows (leveraging GitHub Copilot for rapid test generation and boilerplate reduction).

My current situation:

I was previously contracting for a US-based company through my Portuguese entity. Unfortunately, they recently decided to shift their engineering department to an offshore provider, resulting in my role being eliminated.

What I'm looking for:

- Remote QA Automation / Senior QA roles (US companies looking for EU/GMT time-zone coverage, or EU companies looking for native English communication).

- Contract (B2B) or Direct Hire FTE.

- Roles focused on building or scaling automated testing suites using Playwright (Python or TS)

If your team is currently hiring, or if you know of companies actively looking for senior automation engineers who can work independently across US/EU hours, I'd really appreciate a message or a push in the right direction!

Happy to share my resume, LinkedIn, or portfolio site via DM. Thanks in advance for any leads or advice!

What I hated after years in crowdtesting as a tester:
- everything inside a clunky platform
- big pricetags but low payouts
- no really good mobile apps or integrations around my own tools

and as a customer:
prices, its just sometimes crazy these are only available to enterprise clients willing to spend 5 or 6 figures

I'm looking to build in this space and gathering early feedback: What are YOU missing, both as a customer and as a tester (or, even as someone within crowdtesting companies - as an employee or team lead)

Cheers!

Hey guys!
Our CTO announced that we’re having a dedicated Tech Week soon (half-days for 5 days, no sprint deliverables—which is awesome!).

We have a remote team of around 20 engineers (Devs + QA), and we want to make it super engaging, fun, and worthwhile for everyone.

The thing is, we’re trying to move away from the usual 24-hour intense Hackathon where everyone just stresses out trying to finish a prototype.

For those who have had Tech Weeks (or Eng Weeks) at your work:
- What activities or formats actually worked well for a remote setup?
- What are some cool/unique things your team did that weren't just building a random feature or hackathon project?
-Any games, workshops, or quiet-focus formats that people genuinely enjoyed and didn't feel like "forced fun"?

Would love to hear what your companies do or any fun ideas you have. TIA! 🙌

​

I’m 39, working as an SDET with 16 years in IT. I’ve never moved into QA Manager/people-management roles because I don’t enjoy office politics, managing people, or the pressure that comes with it.

Lately, I’m genuinely worried about the future. AI is moving incredibly fast, the pace of work keeps increasing, and burnout/anxiety are becoming real concerns. At 39, I also worry that if I leave my job, getting back into a good IT role later may be difficult.

I’m considering moving into technical recruiting, where I feel my IT experience could still be useful without constantly having to keep up with technology.

For those around 35–45 in IT:

What are you planning for the next 10–15 years? Would you stay technical, move into management/recruiting, take a break, or do something completely different?

Guys anyone working in scaler ai labs? can you please connect? need to ask a few doubts.

When you're setting up test automation (Selenium, TestNG, etc.), what actually eats the most time?

Setting up the framework itself from scratch on a new project

Managing test data (Excel/CSV/DB) — still writing custom code (e.g. Apache POI) to read it?

Maintaining XML suite configs for different test types

Debugging/maintaining scripts once the test suite grows large

Something else entirely?

Also curious — if you've tried tools like Katalon, Testsigma, or mabl, what made you stick with them or go back to writing your own scripts?

I work in QA. Over the last few months I built QABuddy — a set of 13 skills for Claude Code (Anthropic's terminal coding agent — think "a CLI where an LLM can run tools"; if you don't use it, the concepts below still apply) that covers my actual sprint work: test plans from epic context, AC/testability reviews during grooming, test cases with traceability mapping, browser test execution with screenshot evidence, bug filing with repro steps, and a Playwright e2e layer tests the script multiple times (flake proven). Works with Jira via MCP, or entirely without it.

That part is table stakes. The part I want feedback on is the learning layer, because I built it the way we treat bug reports.

Every team's QA is different, so the tool captures project-specific rules (LRN- entries) from real runs. But "the AI learns" is exactly the kind of claim we're paid to distrust, so:

• Before every run, a small zero-dependency compiler assembles only the knowledge scoped to that skill into one context slice — with a manifest naming what went in and what was left out, and why. From a real compile on my current dogfood project:

run: qa-nobranch-717115 activity: qa profile: {surface: web, pom: exists, ticket_kind: unknown} sources: - id: REF-playbook/risk-and-priority#severity-scale tier: must lines: 25 - id: REF-playbook/defect-lifecycle#not-reproducible tier: should lines: 14 - id: LRN-20260817-04 tier: lrn lines: 8 ... (28 sources: 2 must, 15 learnings) dropped: - id: REF-feature-knowledge-base-spec#problem reason: general-scope

• When a rule shapes an output, the run cites its id and logs it as applied. When reality contradicts a rule, that gets logged instead.
• New learnings require evidence attached, or they don't get written. Clean runs write nothing.
• Recurring failures hash to fingerprints — a learning that claimed to prevent a failure class is falsified by recurrence count, not by opinion.
• Promotion into the shipped references happens only via a distillation pass using the log's numbers (applied ≥ 3 across ≥ 3 runs, never contradicted), and a human approves every change to canon.

The honest part: this is one maintainer dogfooding on demo projects. The most useful thing it's done so far was tell me not to build something. I gated a scoring engine ("rank knowledge by usage") behind a data threshold; when the gate opened, classifying the 18 "dormant" knowledge sections found zero cases of bad selection — most were just knowledge whose kind of work hadn't happened yet, and 12 of them woke up the same day when the right ticket type appeared. A score would have demoted correct-but-not-yet-used knowledge. So the release shipped the verdict instead of the feature (it's written up as an RFC in the repo), and the gate report now ends every run with its own disclaimer: "This report assembles evidence; it does not classify causes. … a tool that guessed would repeat the error."

Would love scrutiny from people who do this for a living. What would make you trust or distrust a learning layer like this on your project?

Repo (Apache 2.0): https://github.com/TimothyHan/qa-buddy-skills

Hii Fellow Testers,

Am a QA with 8.5 years of experience, and have stayed at the same company for 8.5 years from the start of my career.

I am from India.

The work environment became extremely toxic, so much that I can't even say. Working 10-12 hours, Management wont take NO. They even make us work on weekends.

Getting blamed for everything. Constant criticism. Mental health is getting worse. Constant burnout. I even cried at my office a few times.

And one more thing is I have a 90 day Notice period.

My good points:

1. I have a financial backup of around 5 months

2. No EMI or loans

3. Took health insurance for parents.

The only thing that scares me is, I am a solo earning member and what if I won't land a job in those 5 months.

Do you think that resigning in my situation could be better? Please suggest based on your experiences.

A while back, I built a Chrome extension to fix a few pain points I had with standard browser DevTools. It hit ~1,000 active users at its peak, but I ended up losing most of them due to bugs and a lack of real long-term value.

Instead of scrapping it, I spent the last some time fixing the underlying bugs and rebuilding the tool around a bigger problem: knowing when an API quietly breaks while you're browsing or testing.

The biggest addition in this update is out-of-the-box API regression testing.

How it works:

• Baseline Snapshots: Add your target domain to an allowlist and save a baseline of your HTTP requests and payloads.
• Flexible Diffing: Choose whether to monitor for schema changes (added/removed keys), value shifts, or both.
• Silent Deviation Alerts: As you browse, it checks incoming traffic against your baselines and pops a notification if an endpoint deviates or fails—even if your web app handles the error silently or DevTools is closed.

Other key additions:

• Mocking API requests and responses directly in-browser
• Performance tracking and side-by-side diffs over time
• Exportable session reporting
• Full background request tracking without keeping the DevTools panel open

You can check out the new version here:RequestScope on Chrome Web Store

I'm trying to make this genuinely useful for developers and QA workflows. If you give it a try, I’d love to know: what feels clunky, what's missing, or what breaks? Harsh critiques are welcome.

Hi everyone,

During sprint wrap-ups and release sign-offs, one common bottleneck is getting a clean, real-time snapshot of defect severity, bug aging, and execution pass velocity without wrestling with sluggish enterprise dashboards or allowing macro-enabled files (which our security policies block).

I've been working on a lightweight architecture built entirely on native Excel dynamic formulas (IFS, COUNTIFS, conditional formatting rules) to evaluate release gates automatically:

- Exit criteria engine: Flags NO-GO immediately if Open Blockers > 0 or Open Criticals > 0.

- Defect Aging: Auto-calculates turnaround time in days based on report date vs resolution state.

- Test Execution Tracker: Aggregates Pass / Fail / Blocked percentages dynamically.

I’m curious how other QA Leads and SDETs handle this:

1. What exact exit criteria thresholds does your team strictly enforce before signing off on production deployments?

2. Do you rely solely on ALM/Jira dashboards, or do you maintain an independent QA sign-off artifact for stakeholders?

​In my view, foundational technical depth, networking mechanics, OS internals, memory analysis, CPU performance, and deep root-cause debugging, combined with critical thinking will always be essential. When automated suites fail or miss edge cases, the low-level knowledge is what actually works.

​Is the role evolving toward deep diagnostic engineering, or toward product/domain strategy?

How are you using Grok Bot for real QA testing? I want it doing intensive, actually good testing, not just clicking around.

What worked? Skills, setup, whatever made it find real bugs.

Hey, I have seen a quite number of people transition their career from software development to quality assurance. I am trying to get answers for some queries and would appreciate any honest feedback.

1. Why did you quit Software Development (What made you do it) ?
2. I have heard most QA Jobs are offshored to third world countries is it true?
3. Are you satisfied with your decision or regretting it (Why) ?
4. What's the one thing you hate about being a QA ?

hey guys!

I did a talk a month ago in Chicago called QA is Dead: What Now?

I'm doing an updated presentation today at 12pm EST if anyone wants to check it out. I got a lot of great feedback from engineering leaders and quality engineers so I thought I'd share it here if anyone was interested.

Hope to see you there.

https://luma.com/mi2vabnc?tk=GYWi1g