QA & Validation Specialist

Data Drone runs partner implementation practices that ship one outcome in 45 days. The Service Now practice takes one revenue- or service-critical workflow and gets it automated and audit-ready in 45 days — typically clearing ~62% of the manual tickets that used to eat the team alive. We are not a license shop. The workflow we ship has to actually work, hold up under real conditions, and survive an audit.

That's where you come in. Verify, never trust.

You validate the workflows the crew builds — functional testing, audit-readiness, and acceptance-criteria sign-off. You are the last clean line before the client owns the automation. You test against the acceptance criteria the Engagement Manager locked, you test the edge cases the build team hoped you'd miss, and you confirm the workflow is audit-ready — logged, governed, traceable. Your sign-off means the outcome is real, not claimed.

You don't take  it works on my instance  for an answer. You verify, never trust. The proof is reproducible — screenshots, test evidence, a sign-off that holds in an audit.

• Open the day on what's ready for validation and what acceptance criteria each piece must meet.
• Test functionally against real scenarios and the locked acceptance criteria — happy path and the edges.
• You hunt the failure the build team didn't think about — bad data, missing permissions, the unhandled error.
• Mid-day you log results clean: what passed, what failed, with reproducible evidence the crew can act on.
• You close the day with validation state current — what's signed off, what's blocked, what's audit-ready and what isn't.

• Validate automated workflows against locked acceptance criteria — functional, edge-case, and end-to-end.
• Confirm audit-readiness: logging, governance, traceability, and controls that survive scrutiny.
• Own acceptance-criteria sign-off — your yes means the outcome is real and reproducible.
• Hunt the edge cases and failure modes the build team hoped you'd miss.
• Log validation results with reproducible evidence so failures are fixed fast and cleanly.
• Hold the line on quality — no sign-off until the workflow actually meets the bar.

• Real depth in QA and validation of software or platform workflows — functional, edge-case, and end-to-end testing.
• Hands-on familiarity with Service Now workflows enough to test them meaningfully (ITSM/ITOM, Flow Designer outputs).
• Proven skill writing and running acceptance-criteria-driven test cases.
• An eye for audit-readiness — logging, traceability, governance, controls.
• Clear, evidence-based reporting; your failure reports are reproducible, not vague.

• Service Now certifications or platform testing experience.
• Direct experience with audit and compliance validation.
• Familiarity with test automation on the platform.

You verify, never trust.  It works on my instance  means nothing to you until you've reproduced it against the criteria. You take quiet satisfaction in finding the break the build team missed — not to score points, but because the client shouldn't find it first. You hold the line on sign-off even when the deadline is breathing down everyone's neck. Your yes is worth something because you never give it cheaply.

• 30 days:
  You can take locked acceptance criteria and build a real validation pass — functional and edge-case — that the crew respects.
• 60 days:
  You're catching the failures before deploy, confirming audit-readiness, and your sign-offs hold. The build team trusts your  no  because it's always reproducible.
• 90 days:
  You're the quality line of the practice — nothing ships without a sign-off that survives an audit, and your validation patterns get reused…