Job-Intel has helped 100+ job seekers land interviews. The counter stopped. The mission didn’t 💞

I was able to pivot my career and land an AI-driven testing role through this community. Great experience all around.
Ryan Rossbach, Automation Engineer @ LoopQA
Straight From the Source
Real-time Charlotte QA hiring signals from sourcing conversations, recruiter activity and hiring manager feedback.
This page is where I share intel collected so QA professionals can get a clearer read on the market, from automation roles and interview trends to team expectations and the signals that can help candidates position themselves more effectively.
Automation Candidate Confessions Field Notes Job Local Recruitment Contacts LoopQA Market Signal Ovidius AI
-
Most outreach fails before it’s even read
If you’re applying to jobs without also reaching out to recruiters or hiring managers in your space, you’re leaving opportunities on the table. But knowing how and when to engage is what actually matters.
Top: what my LinkedIn inbox looks like
~8–10 messages/day.
Owen (my boss) gets about double.Nothing wrong with the messages.
But when everything sounds the same, it all blends together.Especially when you’re skimming between meetings…
you don’t get much time to “figure out” what someone means.
Bottom: how I try to approach outreach
I don’t always get a response.
Some of it works, some of it doesn’t.But the goal is simple:
if someone reads it once, they should immediately know:- what I’m asking for
- why it matters to them
No decoding required.
Most outreach fails because it optimizes for sounding professional instead of being understood.
Make it easy on the other person to respond.Genuine question:
Do you think “professional language” actually helps outreach…or has it just become noise we’ve all learned to skim past?Sample Messages:

-
Charlotte QA: Market Watch
Remote, Stateside- Senior SDET Gig:
Briefly swapped intros today with Rob Sarro who mentioned he’s hiring for his team at Anaconda. (remote, stateside- backfill). He noted the 5+ years is more of a baseline signal than a hard filter which I love so if you’re strong in the stack, it’s worth a look!
My Review: title says Auto Engineer but it reads as an SDET:
• Writing production code (Python/TypeScript)
• Debugging and fixing FE + BE code
• Building CI/CD pipelines
• Code reviews + design patterns
• Framework ownership
Application Deadline: 05/30/2026; applicants will be reviewed on an ongoing basis until the role is filled *Rob told me his TA team is great, and will actively review all apps*
Salary Listed: $115,500 – $170,000
*I do not manage this requirement and simply sharing what I see in the market* -
QA Market Watch: May 2026
Disclaimer: Please note these are just updates based on my conversations in the market
- Daniel Haynes : Filled a QA engineering role on his team (automation + AI driven). Looks like they have a couple software gigs open and potentially more QA work down the line.
- CPI: Heard CPI filled a QA role: supporting manual Salesforce and integration testing across sales workflows, including quotes, opportunities, and broader business operations such as install and service processes.
- LoopQA: Filled another QA Automation Engineer opening today supporting a large payroll migration initiative
- Interviews/hires @ companies like: Fastbreak, Moodys, Pratt Miller, QTL, Ovidius AI, Vanguard, WF, BoA & LPL Financial
- SystemsOne hired a local manual tester with specific payment experience for a remote gig
-
Ovidius AI
Title: Senior AI Engineer, Agentic Systems
Duration: Fulltime
Location: Fully remote
Release Date: 05/04
Owner: Owen BoesveldWe’re hiring a Senior Engineer to build production AI agents.
This role owns the full stack: Claude Managed Agents, RAG pipelines over proprietary data, and Claude Cowork Skills used by non-technical teams daily. You scope the problem, pick the tools, and ship.
What we need: production Python, hands-on Anthropic API experience (Claude Code, Managed Agents), and working knowledge of RAG systems and Supabase. n8n and MCP experience puts you ahead.
If you need a spec to know what to do next, this is not the role. If you build agents and care about what they actually solve for the business, apply Here
Ovidius AI
P.S- I hear they’ll be hiring for another QA soon. Be sure to follow our linkedin page!
**Disclaimer: I don’t manage this requisition**
Update 5/15: Candidates currently interviewing. QA REQ was just released! -
LinkedIn: The 5-Minute Sweep
How do people search for QA openings on LinkedIn?
One of the first things I do is search by title, testing niche, or specific tools relevant to my field. Then I switch over to recent posts to see what recruiters, hiring managers, and engineers are actively discussing.
In just five minutes, I found several people who have posted and might be worth reaching out to:
Kyley Roberts
Posted: 2 days ago
REQ: ETL (mid level) QAHemank Narula
Posted: 1 week ago
REQs: Automation Engineer/SDET (TD Bank)Manjari Saxena
Posted: 2 days ago
REQ: Salesforce QA Automation Engineer with PlaywrightSreenivas Mohan
Posted: today
REQ: Automation Engineer (Cypress)Avnish Kumar
Posted: 4 weeks ago
REQ: QA focused on AI/Chatbot and Conversational AIShibashish Sam
Posted: today
REQ: Automation QAHarrison Ferone
Posted: Repost
REQ: Automation QABrianna Healing
Posted: today
REQ: Automation Engineer (remote)I did this exercise with an engineering manager last week, and we kicked up several hiring leaders who had posted opportunities or general signals we could leverage that we wouldn’t have found through the job tab. Job searching isn’t just applying to posted jobs but about identifying target companies and intentionally networking with the right people.
It Could Be As Simple As This:

Now who could use a little help with outreach strategy? 🙂
-
How to Vet the ‘Manual + Automation’ QA Gigs
Over the last couple weeks, I’ve had 3 conversations with different candidates applying to “manual + automation” listed QA roles…that are actually much more engineering-heavy than they appear.
How long has this been an issue?
Quick note: if you’re ~75% of a fit, apply. Don’t overthink it.
My opinion: The goal of your resume is simply to get that conversation. If it’s a solid company and you’re reasonably aligned, that first call is always worth it.Once you’re in that conversation, here are a few questions I think might help you actually vet the role:
▶️ If someone spent 70% of their first 90 days on automation backlog and 30% on sprint coverage, would that be the right balance? What does the week-to-week actually look like?
▶️ What does the current automation setup look like: building from scratch, inheriting a framework, or maintaining what’s already there?
▶️ When you say “manual testing when needed,” who decides when it’s needed? The QA engineer, product, or a defined process?If the rep doesn’t know the answers, that’s fine: ask them to go get them. That clarity helps everyone.











