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
-
LoopQA Hiring Update: Skill Over Resume, Process in Action
Activity Update: Interviews in process, with 1 candidate in final stage. All applicants receive the same Playwright-based assessment before speaking with engineering leadership. The process is intentionally designed to remove resume bias and evaluate skill directly. If you can do the work, you move forward.
Ryan Anderson described it as evaluating how candidates think and execute against real requirements, not how they compare on paper. A few patterns stood out from the first group:
- 2 open reqs
- 250+ applications in 2 days
- 20 candidates completed the assessment, 12 did not pass
Common reasons for not passing:
- Overly complex or unstructured code (missed opportunity for reusable, modular design)
- Missed or partially followed instructions in the prompt
- Over-reliance on AI without validating outputs
What the team looks for:
- Strong fundamentals
- Clear, structured thinking
- Ability to follow requirements precisely
- Clean, maintainable automation approach
This is what skill-based hiring looks like when it’s actually enforced. Personally, I expect to see more companies follow suit over the next 12 months.

The best candidates consistently show strong fundamentals, clear thinking, and precise execution of requirements.
Ryan Anderson, President & COO, Engineering Leader
-
New QA Automation REQ’s
LoopQA just rolled out a couple of QA Automation Engineering roles in the Charlotte market focused on AI-driven testing initiatives. I spoke with the hiring manager this evening, Ryan Anderson.
What stands out is that this is one of the few companies I’ve seen managed by technical leadership that doesn’t hire off a resume. Their process is centered on a practical technical evaluation, and AI usage is actively encouraged. They don’t care where you’ve been, so much as what you know.
For most other companies, though, the process starts with your application. If your resume looks like the generic bullet points below, you’re likely getting filtered into the “standard pile.” It’s worth revamping your experience to include product and business context where possible.
Generic resume signals:
• Analyzed functional requirements and technical documentation to design test scenarios and acceptance criteria.
• Designed and executed test cases covering positive, negative, and boundary scenarios.
• Tracked defects and managed test cases using Jira and Xray.
• Designed and implemented POM-based automation frameworks using Java, Selenium WebDriver, TestNG, and Maven.
• Developed Playwright-based test modules for stable cross-browser and headless execution.
• Executed SQL queries to validate backend data and ensure synchronization between UI and database layers.
• Automated database validation using JDBC, reducing manual backend testing effort.
• Configured Jenkins pipelines to execute smoke and regression test suites.
• Performed API testing using Postman and automated end-to-end API tests using REST Assured.Knowing Playwright or Cypress isn’t getting people interviews anymore. If you’re struggling to get traction in this market, this is probably the step of the ladder you’re on. Your resume shouldn’t read like a QE course syllabus. It should read like someone who helped build and protect a real product.
-
Fractional Senior QA Engineer (AI / Agentic Systems)
We’re hiring a Senior QA Engineer to pressure-test AI systems that don’t fail in obvious ways. This isn’t traditional QA: it’s about breaking agentic workflows, RAG pipelines, and LLM-powered products in ways automated evals miss: hallucinations, tool misuse, context drift, silent regressions, and weird edge cases only a curious human catches. You’ll own quality for fast-moving AI systems where “it works” isn’t good enough. Fractional/contract to start (10–25 hrs/week), with strong potential to convert. This is a remote role but there are team members located in Charlotte, NC
Full role details here: [Ovi AI]
Founder: Owen Boesveld
Site: Ovidius AI -
CK Layoffs: One QE I’d Hire
After Credit Karma’s recent layoffs, I received over a dozen calls from strong engineers. One just hit the market with phenomenal experience, and I had to spotlight him.
Deepak Vasanati is a Senior QE with a decade of experience in consumer fintech who built an AI-powered Quality Engine used across 10+ engineering teams, led large-scale test modernization efforts, and maintained zero P0 production defects for over a year.
P.S. His resume is one of the best I’ve seen in a long time. Clear, concise, and packed with measurable business impact. Honestly, I was starting to wonder if my resume scanner could even give out an A. Worth studying for how he frames impact.


If you’re building or scaling a quality engineering function and need someone who can architect the underlying systems, he’s worth a conversation.
-
Credit Karma’s QA Bench Is Strong
Phone’s ringing from folks over @ Credit Karma after the Intuit layoffs. Hearing a decent number of senior QA engineers were impacted.
If you’re hiring and looking for strong quality engineering talent, I’d take a look at the CK roster. There are some really sharp people there.
And if you’re local to Charlotte and were affected, DM me. Happy to help however I can.
Reuters article HERE
-
QA Market Watch: Current Signals
I’ve heard great things about The Hartford from my engineering community over the years. I noticed a couple good lookin’ QA gigs open on their site here locally (R2623925-166 && R2624556-166).
I spoke with a few engineers there today who mentioned they’d spot check what’s currently open. From what I gathered, QA seems to be embedded across most development teams.
One person did mention the first role (Senior Staff Engineer) is fairly niche: looking for someone with 10+ years as an application developer alongside deep QA automation experience. Beyond that, broader hiring priorities and business initiatives are still a little unclear to me.
Nice set of openings though and thought it was worth mentioning. If you’re currently interviewing with The Hartford, feel free to DM me: would love to connect and compare notes.
Plan to update if I can get clarity.
Update 5/13: reqs only show open in the system. Reached out to TA’s to check true status.
Update: 6/3- Spoke with a candidate interviewing with the hiring manager tomorrow 6/4. Looks like Michael is one of the internal TA’s over the req. Can’t wait to see how their tech IV process looks like.Suggested IV prep for The Hartford from current engineer:
Strong understanding of modern test automation frameworks, particularly Playwright, with experience supporting both in-sprint and regression automation initiatives. Practical experience leveraging AI-assisted development tools such as GitHub Copilot and MCP-based workflows to accelerate test creation and improve delivery efficiency. Focused on achieving high automation coverage and quality metrics while balancing speed, maintainability, and business objectives. Experienced with defect lifecycle management, test execution tracking, and Agile delivery environments. Familiar with emerging considerations around AI adoption, including governance, tool usage optimization, and cost/token management.Also curious: if you’ve been getting calls from SMBC in the Charlotte engineering market, I’d be happy to compare notes. Trying to get a better read on the overall landscape and what they’re building locally. Hear great things.
*I do not manage this requirement and simply sharing what I see in the market*












