QA Automation Engineer

QA Test Automation Engineer

Location: Pune HO, India (In Campus) • Experience: 3–5 years • Team: Validation

The Role

We’re looking for a QA engineer who thinks in frameworks, not test cases. You’ll own and grow the automated testing that gives us confidence to ship changes across a distributed, hardware-in-the-loop system — from API and integration layers up through operator-facing UIs — and wire that testing into CI so regressions get caught before they reach a warehouse floor.

What you’ll do

• •Design, build, and maintain automated test suites (API, integration, UI, and end-to-end) for our control and fulfilment systems.
• •Own test automation frameworks — choosing the right tools, keeping them fast and non-flaky, and making them easy for engineers to extend.
• •Integrate automated tests into CI/CD pipelines (GitLab CI) so quality gates run on every merge, with clear signal on failures.
• •Build test coverage for services that talk over message queues (RabbitMQ) and persist to PostgreSQL, including data-integrity and state-transition checks.
• •Design and run performance, load, and reliability tests against critical paths, and help define pass/fail thresholds.
• •Partner with developers to shift testing left — reviewing testability of new features, defining acceptance criteria, and contributing to test strategy early in the cycle.
• •Triage, reproduce, and root-cause defects; write clear, reproducible reports and track them to closure.
• •Contribute to release readiness — go/no-go assessments, regression sign-off, and release validation across projects.

What you’ll need

• •3–5 years in software QA / test automation, with a strong track record building automated suites (not just running manual cases).
• •Solid programming ability in Python and/or JavaScript/TypeScript for writing maintainable test code.
• •Hands-on experience with test automation frameworks — e.g. Playwright, Cypress, or Selenium for UI, and pytest / REST-assured / Postman-Newman for API testing.
• •Practical experience integrating tests into CI/CD pipelines and reasoning about flaky-test mitigation, parallelisation, and test data management.
• •Comfort with API testing (REST), reading logs, and querying databases (SQL) to validate behaviour end-to-end.
• •Strong debugging instincts and the ability to isolate whether a failure is in the test, the code, the data, or the environment.
• •Clear written communication for defect reports, test plans, and release notes.

Good to have

• •Experience testing distributed systems, event-driven architectures, or message-queue-based services (RabbitMQ, Kafka).
• •Exposure to performance/load testing tools (k6, Locust, JMeter).
• •Familiarity with containerised environments (Docker/Podman) and setting up reproducible test environments.
• •Experience with hardware-in-the-loop, IoT, robotics, or other systems where software meets the physical world.
• •Familiarity with observability tooling (Prometheus, Grafana) to validate system behaviour under test.
• •Prior work in warehousing, logistics, or industrial automation domains.