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

> India · Staff · Backend · open. Source: https://alderhq.app/jobs/greenhouse%3Asecurly13%3A8331968 (read 2026-11-12).

## Facts (observed)

- Company: [Securly](https://alderhq.app/companies/securly)
- Location text: Pune City, Maharashtra, India; Pune, India
- Where it can be done from (inferred): India (evidence: "Location lists "pune"")
- Posted: 2026-10-28 (14 days ago)
- First seen by alder: 2026-11-07 · last verified: 2026-11-07
- Reposted: 0 times · edited: 0 times
- Apply on the employer's site: https://www.securly.com/job-description?gh_jid=8331968
- Skills listed (inferred): Testing

## Pay and sponsorship

- Posted pay: not posted
- Market band for similar posted roles (India, n 3): p25 ₹63L, median ₹81.4L, p75 ₹83.2L

## Description (the employer's text)

### 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. Own end-to-end coverage across web, mobile, and integrations: student, teacher, and admin workflows; the student mobile app; email, in-product, and push notifications; roster imports and attendance exports to the SIS; and the shared rostering and single sign-on Flex runs on with Securly Pass.
- Build the framework. Architect and build the Flex automation framework: reusable libraries, test data utilities for roster and attendance files, parallel execution, and reporting that the whole team extends — and contribute fixes to product code where it improves testability.
- Mentor and scale. Mentor engineers on test architecture as a first-class discipline, and bring AI-assisted tooling into how the team generates scenarios, triages failures, and scales coverage.
- Shape architecture. Partner with your technical lead and the Distinguished Engineer on architecture and testability decisions, and influence testing standards across teams beyond your own squad.
- Own incidents. Join the on-call rotation and own the full incident lifecycle for quality regressions: detection, diagnosis, resolution, and retrospective.
### SKILLS & REQUIREMENTS

### Must-Have

- Test framework architecture — designing automation frameworks from scratch (page object or screenplay patterns, BDD where it fits, parallel execution, reporting) that other engineers extend. You build the platform, not just the scripts.

---
Data: alder (https://alderhq.app). Cite https://alderhq.app/jobs/greenhouse%3Asecurly13%3A8331968 and the date you read it. Observed facts come from the employer's own listing; location reach, level, family and skills are inferences.