At a Glance
- Tasks: Lead quality initiatives and coach developers in a cutting-edge AI environment.
- Company: Join Brahma AI, a leader in generative media technology.
- Benefits: Remote work, competitive salary, and opportunities for professional growth.
- Other info: Dynamic team culture with a focus on innovation and collaboration.
- Why this job: Shape the future of AI-driven media with your expertise in quality assurance.
- Qualifications: Experience in quality leadership and advanced testing methodologies required.
The predicted salary is between 63000 - 77000 £ per year.
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
- 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.
- 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.
- 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.
About BRAHMA AI
BRAHMA AI is the next generation of enterprise media technology formed through the integration of Prime Focus Technologies and Metaphysic. By combining CLEAR®, CLEAR® AI, ATMAN, and VAANI into one ecosystem, BRAHMA AI enables enterprises to manage, create, and distribute content with intelligence, security, and efficiency. Proven, scalable, and enterprise-tested, BRAHMA AI is helping global organizations accelerate growth, efficiency, and creative impact in the AI-powered era.
Quality Lead employer: BRAHMA
Brahma AI is an exceptional employer that fosters a dynamic and innovative work culture, where employees are empowered to lead and grow within their roles. With a strong focus on cutting-edge technology and collaboration, the company offers ample opportunities for professional development, particularly in the rapidly evolving fields of AI and media technology. Located in a vibrant tech hub, Brahma AI provides a unique environment that encourages creativity and teamwork, making it an ideal place for those seeking meaningful and rewarding employment.
StudySmarter Expert Advice🤫
We think this is how you could land Quality Lead
✨Join Local Tech Meetups
Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at BRAHMA or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!
✨Contribute to Open Source Projects
Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to BRAHMA.
✨Tap into Online Developer Communities
Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like BRAHMA.
✨Explore Job Boards Specifically for Tech Roles
Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like BRAHMA that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!
We think you need these skills to ace Quality Lead
Some tips for your application 🫡
Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.
Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at BRAHMA.
Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at BRAHMA and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!
Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!
How to prepare for a job interview at BRAHMA
✨Brush Up on Your Coding Skills
For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.
✨Know Your Tools and Frameworks
Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If BRAHMA uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.
✨Showcase Your Projects
Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.
✨Prepare for Behavioural Questions
While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.