Senior SDET – Automation Framework Architect (Playwright, Selenium, API, CI/CD)

Senior SDET – Automation Framework Architect (Playwright, Selenium, API, CI/CD) THE ROLE Own test strategy, quality architecture, and the automated regression infrastructure for Securly Flex — the flex period scheduling and attendance platform that 1,000+ schools use every school day to place students into intervention, enrichment, and support sessions. Flex decides where students are supposed to be. A defect in Autoassign placement, capacity limits, separation rules, roster sync, or attendance recording does not just break a feature — it can put a student in the wrong room, leave a must-attend intervention empty, place students together who are required to be kept apart, or send inaccurate attendance into a district's student information system. The test infrastructure you build is the last line of defense before production. This is an engineering leadership role, not a QA role. You will define what "production-ready" means for Flex, build the automation platform that enforces it through CI/CD quality gates, and write production-quality code for that platform yourself. You will also serve as the team's expert on rules-engine correctness and edge-case testing — your understanding of how Flex's rules interact (priorities, capacity limits, restricted sessions, sign-up cutoffs, and check-in controls) directly shapes both the test suite and the implementation team's design decisions. Location: Pune, India (Hybrid – 2 days onsite) Experience: 6–10+ years Reports to: Director of Quality Engineering WHAT YOU'LL DO Own the quality bar. Define what "passing" means for Flex: establish written quality criteria covering scheduling correctness, data integrity, access control, and performance that gate production releases. Test the rules engine. Design and implement automated test suites covering Autoassign placement logic — student choice, teacher priority, must-attend assignments, rostered and restricted sessions, at-risk designations, seat and room capacity, separation (contact control) rules, conflict detection, and the guarantee that manual registrations are never overwritten — plus the edge cases around them: conflicting rules, boundary conditions, concurrent registrations at capacity limits and sign-up cutoffs, API calls that skip UI validation, and permission boundaries. Gate every release. Build CI/CD quality gates that prevent regressions from reaching production; own the pipeline configuration and ensure the quality bar is enforced, not advisory. Set performance baselines. Measure and establish written performance baselines for peak-load moments: sign-up windows opening and closing, Autoassign runs before each flex period, and attendance taking across thousands of concurrent users; define the thresholds that constitute a performance regression. Cover web, mobile, and integrations.