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.

Never Miss a New Post

Get the latest posts and tips delivered straight to your inbox.

I don’t spam! Read my privacy policy for more info.

Leave a Reply

Your email address will not be published. Required fields are marked *