Embee
Embee is an Information technology company that specializes in workspace & data centre Transformation.
- Open roles
- 105
- New role every
- ~0.8 days
- Posting trend
- 0.9× vs prior 90d
Company signals
Score: 78Job facts
- Location
- Mumbai, India
- Type
- Full-time
- Department
- Services Delivery
- Posted
- Oct 14, 2026
Last verified live 1 week ago · checked directly on the company's Darwinbox
More roles at Embee
- Assistant Manager - NSD Operations · Kolkata - EMBI-Infinity Benchmark, Kolkata, West Bengal , India
- Integration Specialist · Noida - NQIND, Noida, Uttar Pradesh , India
- Junior Pentest · Ha Noi - NQVNM, Ha Noi, Ha Noi , Vietnam
- Microsoft Modern Workplace Engineer · Makati - NQPHL, Makati, National Capital Region, Philippines
- Cloud Trainee Engineer · Noida - NQIND, Noida, Uttar Pradesh , India
- Account Manager · San Borja - NQPER, San Borja, Lima , Peru
Senior Quality Engineer
at Embee
We are looking for a passionate and detail-oriented Software Engineer in Quality Assurance (Automation) to join our engineering team. In this role, you will be at the forefront of building and scaling our test automation ecosystem — owning quality end-to-end, from test design to continuous delivery pipelines. You'll work closely with developers, product managers, and DevOps to ensure our products are robust, reliable, and release-ready at all times.
What You'll Do
• Design, build & maintain scalable automation frameworks using Selenium WebDriver, Cucumber, and TestNG.
• Own test strategy for assigned squads — defining scope, coverage, and risk from requirements through production.
• Write BDD feature files (Gherkin) to enable collaboration between QA, Dev, and Product stakeholders.
• Implement TDD practices — writing tests before or alongside code to drive quality in development cycles.
• Integrate automated suites into CI/CD pipelines (Jenkins, GitHub Actions, or similar) for continuous feedback.
• Perform API testing and validate end-to-end user journeys across web and services.
• Identify, document & triage defects with clear reproduction steps, severity classification, and root-cause analysis.
• Mentor junior QA engineers and champion quality best practices across the engineering org.
• Continuously evaluate test health, flakiness, and coverage gaps — iterating to keep automation suite trustworthy.
What We're Looking For
Must-Have Skills
• 3+ years of hands-on experience in QA automation in a product engineering environment.
• Strong proficiency with Selenium WebDriver — page object model, explicit waits, cross-browser testing.
• Solid experience with Cucumber (BDD) — writing and maintaining feature files, step definitions, and hooks.
• Hands-on with TestNG — test configuration, data providers, listeners, parallel execution, and reporting.
• Working knowledge of TDD principles and integrating tests into agile development workflows.
• Proficiency in at least one programming language — Java or Python preferred.
• Experience with CI/CD integration and running tests in automated pipelines.
• Strong analytical thinking with an eye for edge cases, boundary conditions, and failure modes.
• Excellent communication skills — ability to clearly articulate test findings to technical and non-technical audiences.
Nice to Have
• Domain knowledge in Payments — understanding of payment flows, gateways, settlement, reconciliation, or fraud systems.
• Experience testing APIs with tools like Postman, RestAssured, or similar.
• Familiarity with performance / load testing tools (JMeter, Gatling, k6).
• Exposure to cloud testing environments (Sauce Labs, BrowserStack, AWS Device Farm).
• Knowledge of security testing basics relevant to financial or transactional systems.
• Experience with mobile automation (Appium or similar).
The Mindset We Value
Beyond technical skills, we hire for how you think and operate:
• Ownership mindset — you treat quality as your personal responsibility, not a sign-off gate. You proactively identify risks, flag issues early, and see bugs as a systemic problem to solve.
• Shift-left thinking — you involve yourself in requirements and design discussions, not just execution phase.
• Bias for automation — if something is tested manually more than twice, you ask how to automate it.
• Collaborative — you work with developers as partners, not adversaries, and build shared ownership of quality.
• Continuous improvement — you regularly revisit your frameworks and practices, improving coverage, speed, and reliability.