BOF: SDET – yet another rattle title or separate engineering line
summary
The talk examines the SDET role as originating at Microsoft but often marketed as a premium title, illustrating concrete work such as testing storage firmware and automotive instrumentation, building CI pipelines with Jenkins, automating with Selenium and unit tests, and creating in‑house frameworks and accelerators. It argues SDET is primarily a mindset of ownership and product focus rather than just higher pay, and reports that over a year and three months the author received only a few client requests for SDETs, suggesting the title sometimes succeeds and sometimes is mere rebranding.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 5:21Testing roles experience
- 11:24New titles creation
- 17:12SDET vs testers
- 24:15SDET client positioning
- 29:57Building SDET community
- 35:20SDET mindset and skills
- 40:00SDET qualities
- 44:54SDET job reality
- 49:15Conclusion
related talks
49mSDET: The Next Level in Test Automation
13mHow to Become an SDET from Automation QA | Role of an SDET
16mThe Era of Intelligent Testing Transforming Testers into Skilled SDETs
43mFrom Clickers to Coders: The SDET Evolution Story
52mMaking SDETs from ppl with 0 programming experience
43mEndless Metamorphoses of Consciousness or The Saga of a Transformer Man
38mThe New Skill Stack for SDETs in the Agentic Era
43mSoftware Developer in Test: Who Is That?