Software Development Engineer In Test (SDET) Interview Experience - Bengaluru, India
Process
HMS round. Then 2 technical rounds, then one HR round in the end.
I got rejected in HMS, so I don't have feedback on other rounds.
HMS was different compared to what was mentioned in the reference document shared by Glean.
Questions
Why is MCP needed in playwright?
TypeScript code to get adjacent table values.
How does playwright work in the backend?
How does playwright internally handle wait?
Why did you prefer playwright over selenium?
How would you debug if 1000 test files fail at the same time?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Glean Software Development Engineer In Test (SDET) role in Bengaluru, Karnataka.
Success Rate
Glean's interview process for their Software Development Engineer In Test (SDET) roles in Bengaluru, Karnataka is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for Glean's Software Development Engineer In Test (SDET) interview process in Bengaluru, Karnataka.
Glean Work Experiences
- 5.0Amazing work culture with opportunities to learn and work with cutting-edge technologySWE New Grad • Current EmployeeBengaluru, Karnataka, IndiaApril 22, 2023Pros: People, product, benefits, salary, learning opportunitiesCons: I don't have any to mention here.
- 5.0Good Culture, Long HoursSoftware Engineer • Current EmployeeBengaluru, Karnataka, IndiaOctober 22, 2025Pros: Good work culture and balance.Cons: Long working hours and pressure
- 5.0Great People, Great ProductSoftware Engineer • Current EmployeeBengaluru, Karnataka, IndiaAugust 2, 2023Pros: Good People, Good ProductCons: None that I can think of
