Senior SDET – Automation Framework Architect (Playwright, Selenium, API, CI/CD)
Senior SDET who owns the quality bar and automation framework for Securly Flex, a K-12 flex-period scheduling and attendance platform. Day to day: architect Playwright/Selenium/API test suites, enforce CI/CD release gates, set performance baselines, and mentor engineers, hybrid from Pune (2 days onsite).
- Compensation
- Not disclosed
- Location
- Pune City, Maharashtra, India
- Work setup
- Hybrid
- Seniority
- Senior
- Employment
- Contract
- Experience
- 10+ years
- Category
- Qa
- Posted
Skills
Must have
- Test framework architecture — designing automation frameworks from scratch (page object/screenplay, BDD, parallel execution, reporting)
- SDET-level test automation with Playwright, Cypress, or Selenium plus API-level automation (REST, contract testing)
- CI/CD quality gates — integrating test suites into pipelines and enforcing regression gates
- Rules-engine and data-integrity testing — deterministic fixtures, CSV/XML import/export validation, concurrent edits
- Strong programming in JavaScript/TypeScript, Java, or Python (TypeScript strongly preferred)
- Technical communication — written quality criteria, test strategy, and performance baseline documents
- Bachelor's degree in Computer Science or related technical field
- 6 to 10+ years of hands-on SDET / test automation experience
Nice to have
- Performance & concurrency testing with k6, JMeter, Gatling, or Locust
- AI-assisted test engineering — scenario generation, failure triage, framework adoption
- Security & access-control testing — RBAC, multi-tenant data isolation, student data privacy
- Mobile test automation — Appium, Maestro, Detox, or similar for iOS and Android
- Integration testing — SIS import/export, rostering sync, single sign-on, notification delivery
- K-12 EdTech domain knowledge — bell schedules, flex periods, MTSS, SIS data
Full description
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.