Bangalore

2-5+ years

Full-time

Technical Solutions Engineer

TestZeus helps teams adopt AI agent-driven testing to validate real user workflows reliably in production-like environments. Customers typically define intent-based scenarios (often BDD/Gherkin), and TestZeus agents execute and adapt across real apps, browsers, and integrations. We win when customers get stable, repeatable outcomes quickly—and expand usage across teams.

Bangalore

2-5+ years

Full-time

Technical Solutions Engineer

TestZeus helps teams adopt AI agent-driven testing to validate real user workflows reliably in production-like environments. Customers typically define intent-based scenarios (often BDD/Gherkin), and TestZeus agents execute and adapt across real apps, browsers, and integrations. We win when customers get stable, repeatable outcomes quickly—and expand usage across teams.

Bangalore

2-5+ years

Full-time

Technical Solutions Engineer

TestZeus helps teams adopt AI agent-driven testing to validate real user workflows reliably in production-like environments. Customers typically define intent-based scenarios (often BDD/Gherkin), and TestZeus agents execute and adapt across real apps, browsers, and integrations. We win when customers get stable, repeatable outcomes quickly—and expand usage across teams.

Role Summary

As a Technical Solutions Engineer, you’ll work directly with customers to help them successfully implement and use TestZeus. You’ll troubleshoot product issues, guide customers through onboarding, and help them write effective agent-ready scenarios. You’ll use technical depth to diagnose problems and recommend best practices—without being expected to operate as the customer’s QA team or maintain their full test suite.

This role is ideal for someone who likes problem-solving, customer interaction, and building repeatable solutions.

Key Responsibilities

1) Customer issue resolution (primary)

  • Own incoming customer questions and technical issues: failed runs, unexpected agent behavior, configuration problems, CI/CD integration issues, access/permissions friction.

  • Investigate using run artifacts (logs, traces, screenshots/video) to isolate root cause.

  • Provide crisp, actionable guidance:

    • what happened

    • likely cause

    • how to fix it

    • how to prevent it next time

  • Escalate platform bugs with clear reproduction steps and strong supporting evidence.

2) Onboarding and enablement (primary)

  • Guide new customers through setup and their first successful runs:

    • environment configuration

    • workspace/project setup

    • CI integration basics

    • recommended usage patterns

  • Run short enablement sessions (live or async) and create repeatable onboarding checklists.

3) Scenario authoring help (supportive, not delivery)

  • Help customers write scenarios that agents can execute reliably:

    • reduce ambiguity

    • improve step structure

    • add practical checkpoints/assertions

    • recommend reusable patterns and templates

  • Help customers debug failing/flaky scenarios by suggesting improvements—without owning ongoing test maintenance for them.

4) Build leverage for scale

  • Create and maintain troubleshooting guides, FAQs, templates, and “known issues” documentation.

  • Identify recurring pain points and recommend product improvements (better errors, diagnostics, guardrails).

5) Feedback loop with Product & Engineering

  • Share trends and customer insights that improve reliability and usability.

  • Partner with engineering during incidents or regressions to ensure fast customer impact resolution.

What Success Looks Like

  • Customers get unblocked quickly and can run stable tests reliably.

  • Faster time-to-first-successful-run for new customers.

  • Fewer repeated issues through documentation, templates, and product feedback.

  • High-quality escalations that are easy for engineering to reproduce and fix.

Requirements

  • 2–5+ years in a customer-facing technical role (Technical Solutions / Implementation / Technical Account / Product Specialist in SaaS environments).

  • Strong debugging fundamentals:

    • reading logs and run outputs

    • basic browser devtools literacy

    • understanding common auth flows (cookies, redirects, SSO basics)

    • ability to reproduce issues and isolate variables

  • Comfort with technical tooling and configuration:

    • APIs basics, JSON, CLI comfort

    • familiarity with Python or JavaScript is a plus (not mandatory if troubleshooting skills are strong)

  • Clear written and verbal communication, with a bias for structured problem-solving.

Nice-to-Haves

  • Familiarity with BDD/Gherkin and scenario design.

  • Exposure to Playwright/Selenium/Cypress.

  • Experience supporting CI/CD pipelines (GitHub Actions, GitLab, Jenkins).

  • Experience with enterprise web apps (Salesforce is a plus).

What This Role Is Not

  • Not a full-time QA automation role.

  • Not “writing and maintaining the customer’s complete test suite.”

  • Not limited to forwarding tickets—you’ll own problems through to outcomes.

Application Process

To apply, please share the following details with us (same format as other roles on the TestZeus careers page):

  1. Your CV

  2. Your Current and Expected CTC

  3. Relevant experience in customer-facing technical roles (and any exposure to testing/automation/agentic systems)

  4. Links to Public Work (e.g., GitHub, Medium, personal website)

📬 Submit all the above to: hiring@testzeus.com

// Start testing //

balance cost, quality and deadlines with TestZeus' Agents.

balance cost, quality and deadlines with TestZeus' Agents.

2025© testZeus All Rights Reserved

2025© testZeus All Rights Reserved

2025© testZeus All Rights Reserved