Founding SDET

Benefits

Parental leave

Not verified

Non-birth-parent leave

Not verified

Family-building benefits

• Fertility benefits: Not verified
• Adoption assistance: Not verified
• Surrogacy assistance: Not verified

Mental health support

Not verified

Relocation assistance

Not verified

Childcare support

Not verified

Learning budget

Not verified

Verification

Not verified

Salary

Not verified

Was this benefit information wrong? Tell us.

Market context

U.S. role benchmark (BLS OEWS)

$116,543 U.S. median for this role

Projected growth (BLS Employment Projections)

+9.8% - Much faster than average

Matched to SOC 15-1252 - Software Engineering aggregate by role bucket.

Source: U.S. Bureau of Labor Statistics, OEWS, May 2024 and Employment Projections, 2024-2034.

Role

Role function

Engineering From the posting source checked Jun 20, 2026

Seniority

Mid From the posting source checked Jun 20, 2026

Work mode

Onsite From the posting source checked Jun 20, 2026

In-office days

5 days From the posting source checked Jun 20, 2026

Schedule

Shift type

Not verified

Weekend work

Not verified

Application

Cover letter

Not verified

Assessment

Not verified

Deadline

Not stated

Where they hire

State eligibility is not yet verified.

About this role

Founding SDET Bengaluru | OnSite Clueso is building a new class of AI-native creation tools used by teams to turn raw screen recordings into polished product videos and step-by-step documentation. Over 100,000 videos have been created on Clueso. We're SOC 2 Type II and ISO 27001 certified, and we ship fast. We're hiring a Founding SDET, our first dedicated quality hire to make shipping fast and shipping confidently the same thing. This is automation-first and code-heavy. You'll write the safety net yourself: E2E test suites, API and integration coverage, CI gates, flake hunting. You'll also own the QA function strategically deciding what stays in-house, what we hand to an agency, and what we hire for next as the team grows. WHAT YOU'LL OWN The release safety net - Build out E2E coverage for the workflows that matter most: recording, editing, AI generation, translations, exports. - Stand up CI test gates that catch real regressions before they ship. - Hunt and kill flake. A flaky test is worse than no test. You set the bar. - Wire in API and integration suites alongside the UI ones; pick the right level for each check. Pre-release acceptance - Drive structured release passes across the realistic product surface recorder, editor, avatars, lipsync, exports across browsers and the device matrix our customers use. - Build the regression checklist that turns into automation over time. Manual where automation isn't worth it yet. The bug loop - Own the path from "user reported X" → minimal repro

Read the full description at jobs.ashbyhq.com. FewerJobs shows a preview and links to the original posting.