Quality Lead

Quality Lead

Location: Remote (Time zone UTC+0 - UTC+3)

About Brahma AI

Brahma AI operates at the intersection of enterprise Media Asset Management (MAM) and cutting-edge generative media. We build and scale industry-leading generative AI models, including hyper-realistic digital humans (ATMAN) and multilingual voice synthesis (VAANI), for world-class enterprise clients in entertainment, sports, healthcare, and retail.

Role Overview

We are looking for a Quality Lead to establish and drive the strategic quality framework across Brahma Studio—our high-fidelity digital human creation engine.Reporting directly to the VP of Engineering, your primary objective is to build a modern, high-bar quality culture where quality is embedded into every stage of the engineering lifecycle. You will serve as a strategic coach to Studio developers across testing paradigms, establish system-level reliability standards, turn open-ended or subjective product expectations into objective benchmarks, and design streamlined, asynchronous workflows to partner seamlessly with our shared QA team.

Key Responsibilities

1. Quality Culture & Developer Coaching (40%)

• Testing Architecture & Mentorship: Coach and enable Studio developers on designing comprehensive testing strategies—challenging them to think through integration workflows, system boundaries, and end-to-end failure paths.
• Standards & Accountability: Establish clear quality standards, test coverage expectations, and pre-release accountability across Studio feature streams.
• Shift-Left Integration: Partner with product and engineering leads during early architectural and PRD stages to ensure testability and quality criteria are defined prior to development.

2. Environment Health & Subjective Quality Benchmarks (30%)

• System & Environment Reliability: Define testing strategies and operational health checks to challenge engineering teams on verifying pipeline execution, job execution health, and infrastructure stability across compute environments.
• Subjective to Objective Benchmarking: Create structured frameworks to translate open-ended or subjective requirements—ranging from media output standards to UI responsiveness and executive performance targets—into measurable quality gates.
• Exploratory Testing Frameworks: Design structured exploratory testing practices that empower teams to uncover unhandled edge cases and unexpected system behaviors outside automated suites.

3. Tooling Governance, Process & Shared QA Alignment (30%)

• Quality Systems Governance & Adoption: Define and govern the ecosystem for test management, quality gate tracking, and release health documentation—focusing on driving consistent team adoption, enforcing usage standards, and maintaining accurate documentation rather than managing technical infrastructure.
• Shared QA Integration: Architect clear, asynchronous test-case specifications and handoff protocols to collaborate efficiently with the shared QA team across time zones and organizational boundaries.
• Release Governance & Post-Mortems: Monitor pre-release quality gates, participate in release risk evaluations, and lead root-cause post-mortems to continuously refine engineering practices.

Must Haves

• Quality Leadership & Coaching: Proven track record as a Quality Lead or Quality Architect guiding engineering teams to adopt advanced testing methodologies, embrace end-to-end quality ownership, and challenge developers to uncover hidden system risks.
• Translating Ambiguous Requirements: Exceptional ability to turn subjective or qualitative goals (e.g., performance expectations, UX polish, output fidelity) into clear, repeatable testing standards and acceptance criteria.
• Process & Tooling Ownership: Experience selecting, structuring, and driving team-wide adoption of test management platforms, quality documentation workflows, and gate tracking metrics.
• Cross-Team Collaboration: Demonstrated ability to build efficient, asynchronous workflows that align product development teams with shared QA resources across regions and time zones.

Nice to Have

• System & API Architecture Awareness: Familiarity with web APIs, distributed systems, and backend integration flows—enough to effectively challenge engineers on edge cases, contract boundaries, and silent failures.
• Experience defining quality or performance baselines for complex media pipelines, AI-driven applications, or non-deterministic systems.
• Experience operating in scaling, high-growth engineering organizations undergoing rapid integration.