Principal Software Engineer - QA (Automation) - Growth For Impact

Principal Software Engineer – QA (Automation)

×

Principal Software Engineer – QA (Automation)

Esyasoft – Bangalore, Karnataka, India

ROLE
– Test coverage and quality across mobile, web and backend products
– Test automation — building, extending and maintaining the automated suites
– Release-gate discipline and defect triage
– Quality advocacy and test ability across the wider engineering team
– Design and own test plans and coverage across the products — functional, regression, integration, UI and end-to-end
– Take a risk-based approach, focusing test effort where the user and commercial impact is greatest
– Define clear, repeatable test cases and keep them current as the products evolve
– Develop the automation framework and integrate tests into the CI/CD pipeline so quality checks run continuously
– Reduce manual regression effort by automating the right things at the right level
– Carry out exploratory and manual testing where it adds value beyond automation
– Own release-gate discipline — clear, evidence-based go / no-go on quality
– Lead defect triage, raising, tracking and verifying fixes to closure
– Cover non-functional quality — performance, load, accessibility and reliability — where relevant to the release
– Partner with DevOps and engineering on environment stability, test data and monitoring of quality in production
– Partner with mobile, web and backend engineers and with Product to build quality in from the start, not bolt it on at the end
– Advocate good testing and test ability practice across the engineering team, and coach engineers on it
– Communicate quality status and risk clearly to engineering and product stakeholders
– Improve test tooling, processes and documentation so quality scales with the products
– Evaluate and adopt new testing tools and approaches responsibly — proving value before adopting

REQUIREMENTS
– A demonstrable senior-level QA / test engineering track record across web and mobile products
– Experience integrating automated tests into CI/CD pipelines
– Strong defect analysis, root-cause investigation and clear bug reporting
– Comfortable combining structured, risk-based testing with exploratory testing
– Strong communication — able to explain quality risk to engineers and non-technical stakeholders
– Performance / load testing and accessibility testing experience
– Experience testing mapping / geolocation or payment integrations
– Familiarity with mobile device farms and cross-device / cross-browser testing
– Knowledge of EV charging, smart metering, mobility or energy products
– Quality-Obsessed — treats the end-user’s experience as the bar, and won’t wave through what isn’t ready
– Systematic — methodical and thorough — covers the edges others miss
– Automation-Minded — automates the repeatable so human effort goes where it counts
– Clear Communicator — reports quality and risk plainly, and pushes back without drama