New opportunity

AI Quality Engineer

Zyoin Group · Bangalore, India

About this role

Zyoin Group is hiring an on-site AI Quality Engineer in Bangalore for a permanent role with one of its clients. The posting specifies 5–8 years of experience and compensation of ₹20–25 lacs per annum. The role focuses on automation testing and quality evaluation of AI products.

Responsibilities

  • Develop a product testing strategy and perform API and automation testing using frameworks and behavior-driven development, including Python, Behave and Git.
  • Evaluate LLM outputs for accuracy, relevance and contextual appropriateness; report results, communicate findings, establish feedback mechanisms and support continuous validation.
  • Test for bias, safety, non-subjective response handling, fallback behavior, edge cases and harmful prompts. Consider the application of legal frameworks when testing before production.
  • Carry out basic performance testing, including p50 and p95 measures, response-time SLAs and load testing. Support CI/CD integration and ensure data storage, traceability and auditability.

Preferred qualifications

  • Production experience with generative AI or LLM applications; exposure to AI governance, responsible AI or model risk management.
  • Familiarity with AWS, GCP or Azure and cloud-based CI/CD pipelines; collaboration with data scientists and ML engineers; understanding of prompt engineering and prompt versioning.
  • Experience in regulated domains such as fintech, healthcare or enterprise SaaS.

For full details about this role, click “Apply on company site” to view the employer’s original posting.

Skills for this role

AI product testingAutomation testingAPI testingBehavior-driven developmentPythonBehaveGitCI/CDLLM evaluationBias testingSafety testingPerformance testingLoad testingPytestAWSAzureGCPAI governanceResponsible AIModel risk managementPrompt engineeringPrompt versioning

Your skill match

Checking your profile…

YOUR NEXT STEP

Get interview-ready for this role

A focused preparation guide, built around this job’s responsibilities and requirements.

✦ AI-generated guide
Preparation suggestions, not the employer’s actual interview questions. Always check the original posting for current requirements.
01

Understand the role

What matters most

  • Product testing strategy and automation

    The posting calls for AI product testing strategy, API testing, automation frameworks, BDD, Python, Behave and Git. Prepare to explain how you would organize an automated test suite across product behavior and APIs.

  • LLM evaluation and feedback

    The role evaluates outputs for accuracy, relevance and context, then reports findings and supports feedback mechanisms and continuous validation. Prepare to describe evaluation criteria, reporting and how results feed back into testing.

  • Safety and edge-case testing

    The posting names bias, safety, non-subjective response handling, fallback behavior, harmful prompts and edge cases, plus consideration of legal frameworks before production. Prepare examples of test categories and how you would document observed behavior without claiming a particular legal standard applies.

  • Performance, integration and evidence

    The duties include p50 and p95 latency, response-time SLAs, load testing, CI/CD integration, and data storage, traceability and auditability. Prepare to explain what you would measure and what test evidence you would retain.

Likely challenges to think through

  • Making variable outputs testable

    Preparation hypothesis: LLM responses may differ while still being acceptable, making rigid expected-answer checks inadequate. Be ready to discuss criteria for accuracy and relevance, how ambiguous cases are reviewed, and how evaluation remains repeatable.

  • Balancing safety coverage with practical testing

    Preparation hypothesis: harmful prompts, bias and fallback behavior create a broad test space that cannot be exhausted before release. Prepare a risk-based way to select cases, record failures and identify where legal-framework input is needed.

  • Reconciling latency with quality evidence

    Preparation hypothesis: load and response-time targets may compete with thorough validation and traceability. Prepare to distinguish fast CI checks from deeper evaluation and load tests, while preserving results that can be audited.

03

Practice your answers

Technical practice

How would you build a product testing strategy for an AI application?

What to coverThe posting calls for product testing strategy and automation testing of AI products. Suggested preparation: explain how you would identify critical user flows, prioritize risks, and decide what to automate versus evaluate manually.

How would you test an AI product’s API?

What to coverAPI testing is an explicit responsibility. Suggested preparation: cover request and response validation, error handling, repeatable test data, and how you would investigate a failing test.

How would you structure BDD automation using Python, Behave and Git?

What to coverThe posting names BDD, Python, Behave, automation frameworks and Git. Suggested preparation: describe readable scenarios, reusable steps, maintainable test code and version control practices.

How would you evaluate LLM outputs for accuracy, relevance and context?

What to coverThose three qualities are explicitly named in the posting. Suggested preparation: explain how you would define evaluation criteria, assemble representative cases and handle outputs on which reviewers disagree.

How would you report evaluation results and support continuous validation?

What to coverThe role includes evaluation reporting, communication, feedback mechanisms and continuous validation. Suggested preparation: describe how you would make findings actionable, track recurring failures and check whether changes improve results.

How would you test bias, safety and fallback responses?

What to coverThe posting calls for testing bias, safety, non-subjective response handling and fallback behaviour. Suggested preparation: explain how you would select cases, assess responses against defined expectations and record ambiguous outcomes.

How would you probe harmful prompts and other edge cases?

What to coverHandling harmful prompts and edge cases is explicitly listed. Suggested preparation: discuss systematic case selection, safe test execution and how you would distinguish an isolated failure from a broader pattern.

How would you assess response-time performance under load?

What to coverThe posting specifies basic load testing, p50 and p95 measures, and response-time SLAs. Suggested preparation: explain what each percentile reveals, how you would compare results with an SLA and what you would investigate after a regression.

How would you integrate AI quality checks into CI/CD?

What to coverCI/CD integration is a responsibility; cloud-based pipelines are listed as nice to have. Suggested preparation: distinguish fast, repeatable checks from more variable LLM evaluations, and explain how you would make failures useful to developers.

How would you make pre-production test results traceable and auditable?

What to coverThe posting names data storage, traceability, auditability and consideration of applicable legal frameworks before production. Suggested preparation: explain what test inputs, outputs, versions and decisions you would retain, while noting that legal checks depend on the product and jurisdiction.

Behavioural practice

Tell me about a time you worked with data scientists or ML engineers to resolve a quality issue.

What to coverClose collaboration with those roles is listed as nice to have. Suggested preparation: give a real situation, the actions you took to align on evidence or evaluation criteria, and the result.

Tell me about a time you communicated a difficult test finding.

What to coverReporting and communicating evaluation results are part of the role. Suggested preparation: describe the situation, how you presented the evidence and recommended action, and what happened next.

Tell me about a time you raised a safety or bias concern before release.

What to coverThe posting calls for bias and safety testing before production. Suggested preparation: use a real example to explain the risk you found, how you escalated or investigated it, and the resulting decision without claiming a particular company process.

Tell me about a time feedback changed your testing approach.

What to coverFeedback mechanisms and continuous validation are stated responsibilities. Suggested preparation: describe the original approach, the feedback and action you took, and the measurable or observable result.

Tell me about a time you had to prioritize testing across competing risks.

What to coverThe role calls for a product testing strategy spanning automation, LLM evaluation and performance. Suggested preparation: explain the situation, how you chose what to test first, and the outcome or trade-off you identified.

02

Sharpen your knowledge

Topics to prepare

  • AI product testing strategy

    Draft a one-page strategy for a hypothetical AI product, separating API, automated, LLM-output, safety and performance checks. The posting explicitly asks for product testing strategy and experience testing AI products.

  • LLM evaluation criteria

    Define distinct criteria for accuracy, relevance and contextual appropriateness, then explain how you would judge an ambiguous response. These are the posting’s stated dimensions for LLM evaluation.

  • Bias, safety and fallback behavior

    Create a small test matrix covering biased outputs, harmful prompts, edge cases, non-subjective responses and fallback behavior. These are explicitly named testing concerns.

  • Performance measures

    Explain how p50 and p95 response times differ, and how each could be compared with a response-time SLA under load. The role calls for basic performance and load testing.

  • Pre-production accountability

    Sketch what evidence would need to be stored to trace a test input, output and result, then identify questions to raise about applicable legal frameworks before release. Traceability, auditability and legal-framework application are stated; no particular law is specified.

Skills to revise

  • Automate API checks with Python and Behave

    Write a small BDD scenario for an API response, implement its steps in Python and commit the test with Git. API testing, automation frameworks, BDD, Python, Behave and Git are all listed.

  • Report LLM evaluation findings

    Score a small set of example outputs against accuracy, relevance and context criteria; summarize failures and propose a feedback loop for retesting. The posting calls for evaluation reporting, communication and continuous validation.

  • Run adverse-case tests

    Prepare and execute sample harmful-prompt and edge-case tests, recording whether the output is safe and whether fallback behavior works. This practices the posting’s explicit safety-testing responsibilities.

  • Measure response times under load

    Run a small load test on a test endpoint, calculate p50 and p95 response times, and compare them with a hypothetical SLA. The posting requests load testing and these specific measures; the SLA value would be an exercise assumption.

  • Make automated results traceable

    Outline a CI/CD test run that retains test inputs, outputs, results and the Git revision used, then show how a failed result could be investigated. CI/CD integration, data storage, traceability and auditability are stated responsibilities.

04

Your preparation checklist

  • Prepare an AI-product testing walkthrough

    Outline an anonymized project or illustrative case showing how a testing strategy was designed, what was automated, how findings were communicated, and what changed as a result. The posting emphasizes AI-product testing strategy and evaluation reporting.

  • Draft a product test strategy

    Create a one-page plan covering API coverage, automation boundaries, LLM evaluation, risk-based priorities, and continuous validation. Label assumptions about the client’s product rather than presenting them as facts.

  • Build a small automation example

    Prepare a Python API test with a Behave scenario and a Git repository structure, or a concise design if code cannot be shared. Be ready to explain framework choices and how it would run in CI/CD.

  • Create an LLM evaluation scorecard

    Show sample prompts, criteria for accuracy, relevance and contextual appropriateness, a way to record results, and a feedback path for failures. These are evaluation areas named in the posting.

  • Design a safety and edge-case matrix

    Include bias, harmful prompts, fallback behavior and non-subjective response handling, with expected outcomes and escalation notes. Treat applicable pre-production legal frameworks as a question to clarify, not an assumed requirement.

  • Sketch a performance test report

    Prepare an example showing load levels, response-time SLA checks, and p50 and p95 latency reporting. State how test conditions and results would be recorded.

  • Map CI/CD and audit evidence

    Draw a simple flow from versioned tests and prompts through CI/CD execution to stored results, traceability and audit records. Mark any cloud platform choice as illustrative; the posting lists cloud familiarity as nice to have.

  • Prepare targeted employer questions

    Ask what AI product the client tests, how output quality is judged, which safety and legal frameworks apply, and what evidence must be retained before production.

AI-generated from the job information · Prepared Sep 30, 2026 (UTC)Useful preparation, not a guarantee of eligibility or an offer.

Availability last checked: 4 Nov 2026. Status can change after a check; confirm on the employer’s website. Report an issue · Our checking policy

KEEP EXPLORING

Similar AI jobs

Related skills and specializations in India. Matched to this role, not your profile.

Explore more jobs
Finding similar opportunities…