What are the typical responsibilities of an SDET?

@fredericmaiborn recently asked on Slack:

What are your opinions of the work a SDET should be able to do? In my experience following things are demanded mandatory:

  • Coaching Devs on UNIT/Integration
  • Pipeline Stuff
  • Be able to setup E2E on a green field
  • Backend Implementation /Frontend Implementation ( one of them), like a normal Dev
  • Observability ( logging/ monitoring)
  • Drive forward test tickets

Is there anything you would add to or take from the list that Frederic has created?


I would add that an SDET should advocate for testability. This starts at the design of a product where testability can be designed into the product. Improvements in testability can reduce testing time and improve speed to market.