15 Nov
|
Ciklum
|
Hyderabad
You are an engineer who specialises in proving things work. The distinction between dev and QA” work is not one we maintain: you read the application code, you write production-grade Python, and you build agents. The difference is what you point them at.
- Core DNA
- AI-Native Workflow. You use AI to accelerate everything you do as a default, not an experiment. You have
opinions about which tools earn their place.
- Agentic Implementation. You build, debug and deploy autonomous agents — LLM-driven test generation,
Playwright browser-use agents, self-healing locator strategies — against complex ERP screens and workflows.
- Legacy-to-Up-to-date Bridge. Some of what you’ll test is a modern web rewrite. Some is a desktop application
older than your career. Both are puzzles.
- Evidence Over Confidence. A generated test that has never been executed is not a test. You know your own
false-positive and flake rates rather than claiming there aren’t any.
- What You Own The ticket-to-test pipeline. An agent that reads a requirement or defect, understands the affected area, and produces a real test — grounded in the actual application, not in what the model imagines the application looks like. Hallucinated locators are the failure mode that kills these systems; preventing them is your problem.
Execution and stabilization. Generation is the easy half. Your pipeline isn’t done when a test file exists or a ticket gets created — it’s done when the test has run against a real build, passed repeatedly, and earned its place in the suite. Flake is the enemy, because a suite nobody trusts is worse than no suite.
Coverage that means something. You can tell the difference between a suite that covers the code and a suite that covers the risk. You use mutation testing and real defect history rather than counting tests, and you argue for the edge cases that actually bite: fiscal calendars, multi-currency, partial shipments,
period-end adjustments.
- Where You Might Lean In
- Test Generation & Grounding — the retrieval and context problem. How does an agent know what the screen
really contains, what the business rule really is, and what changed in this release?
- Adversarial & Red-Team — you build agents whose job is to break things. Programmatic prompt optimization
(DSPy), fuzzing business logic, hunting the input nobody thought of.
- Test Infrastructure & Agent-Ops — the factory the test agents run in: parallel execution, environment and
data management, tracing, and the observability to know why a run went sideways.
- Legacy Surface Automation — desktop and thick-client applications where modern tooling doesn’t reach and
the automation has to be built rather than installed.
What You’ll Actually Do
- Build test-generation agents that take a ticket and produce an executable test grounded in the live application.
- Close the loop. Make generation, execution, stabilization and reporting one pipeline rather than four
disconnected steps with a human carrying work between them.
- Automate the untestable. Wrap legacy business logic — the modules everyone has avoided because there’s no
spec — in characterization tests that capture what the system actually does today.
- Kill flake. Find the root cause rather than adding a retry. Retries are how suites die.
- Red-team the financial logic. Build the agents that go looking for the case where the ledger doesn’t balance.
- Fix your own agents in production. Read the traces, find why it went sideways, make it not happen again.
The Stack
- Python, pytest, Playwright, SQL (Postgres/SQL Server), TypeScript, OpenAI/Anthropic, LangChain/LangGraph, DSPy,
- pgvector/Qdrant, Docker, CI/CD pipelines, OpenTelemetry, eval and tracing platforms (LangSmith / Langfuse /
- Braintrust or equivalent), desktop automation frameworks where the application demands it. And any other tool that
- helps us achieve greatness.
📌 Senior AI Automation QA (Hyderabad)
🏢 Ciklum
📍 Hyderabad