Storyteller

QA Engineer- AI Native

Rol remoto de QA Engineer con fit claro de ubicación del candidato.

Publicado24 jul 2026

Países elegibles4 países aceptados

Señal de seniorityMiddle, Senior

Modelo de trabajoRemoto

Ubicaciones aceptadas para candidatos

ArgeliaEgiptoTúnezTurquía

Resumen del rol

QA Engineer- AI Native

Requisitos y responsabilidades

Contenido del rol extraído en secciones para revisar más rápido.

About the Role

You’ll use AI coding agents and related tools to explore the SDK codebases, understand behaviour and accelerate quality work.
You’ll care about tests that protect important behaviour and run in real development and release workflows.
You’ll use product, technical, integration and release risk to identify the highest-value quality improvements.

RESPONSIBILITIES

Use AI coding agents and related tools to explore the SDK codebases, understand behaviour and accelerate quality work.
Use product, technical, integration and release risk to identify the highest-value quality improvements.
Design, build and maintain useful unit and component tests for SDK behaviour.
Design, build and maintain integration tests covering SDK interaction with Storyteller services and APIs.
Put automated tests into active CI and release workflows, with failures that are clear and actionable.
Prove that tests detect meaningful breakage rather than merely producing passing output.
Investigate bugs using code, logs, APIs, test results and product behaviour.
Where appropriate, follow a well-understood issue through to a bounded production fix.
Work with builders to improve testability and prevent repeated classes of defects.
Turn repeated investigation or testing work into reusable AI workflows, tools, checks or test assets.
Communicate clearly in Slack and other team systems: state the evidence, impact, current understanding, owner and next action.
Contribute useful AI-assisted engineering practices to the wider SDK team while remaining primarily accountable for quality outcomes.
Contribute to tvOS, Android TV, Fire TV, Web and Roku as the role's scope expands.

RESPONSIBILITIES

Important SDK behaviours have dependable automated protection;
Useful quality improvements land incrementally and are easy for the team to adopt;
SDK-to-platform integration failures are detected early and are easy to diagnose;
Tests run reliably in the workflows the team actually uses;
Test failures give the team enough information to act;
Well-understood defects are followed through to an appropriate fix or clear handover;
Repeated quality problems become better tests, tooling or product changes;
Automation and risk-based exploration provide evidence proportionate to the change;
Your communication makes quality risks and next actions easy to understand;
And the Storyteller team becomes more capable with AI because of practical workflows you have demonstrated through the work.

What we’re looking for

AI-native execution – You use AI to do substantive technical work, not only to write or summarise. You can give an agent useful context, break down an ambiguous problem, inspect its work, redirect it when necessary and keep going when the first approach fails.
Quality and validation judgment – You can decide what is worth testing, recognise superficial tests and demonstrate that an automated test provides real protection. You think about false confidence, false positives, brittle tests, maintainability and failure diagnosis.
Agency and ownership – You can take an ambiguous quality risk, investigate it, gather evidence, choose a sensible next step and move the work towards a useful outcome.
Technical comfort – You are comfortable working with repositories, code, APIs, CI, logs, command-line tools and automated test frameworks. You can understand and challenge AI-generated code well enough to validate and land it safely.
Problem solving and systems thinking – You distinguish symptoms from root causes. When a problem repeats, you look for a reusable test, tool, check or workflow instead of treating every occurrence as a new manual task.
Clear communication – You communicate concisely and directly. You make evidence, impact, uncertainty, ownership and next actions visible without requiring someone else to reconstruct the situation.
Learning velocity – You are curious and can become effective in unfamiliar products, codebases and tools quickly. You change your approach when the evidence shows that it is not working.

What we’re looking for

Experience with mobile applications or SDKs.
Experience with Swift or Kotlin.
Experience with API integration.
Experience with automated testing or test frameworks.

What we’re looking for

You can take an ambiguous quality risk from signal to outcome with limited supervision.
You can frame the problem, direct AI and other tools effectively, and choose a practical testing or investigation approach.
You validate output rigorously, communicate what you found and land useful work.
You improve the system for the next occurrence rather than treating every problem as a one-off.
You are comfortable being accountable for quality outcomes while quality remains a shared responsibility across the team.

It probably isn’t right for you if:

You want AI to produce technical work that you do not need to understand, explain or validate.
You prefer to wait for fully defined instructions rather than investigate ambiguous risks and choose a sensible next step.
You are looking for a separate QA gatekeeping role rather than working directly with builders and product owners throughout the lifecycle.

Roles similares