What is an SDET? Part 2
---- Skill Matrix of SDET
(Instead of naming it as part 2 of What is an SDET?, it would be nearer the mark to say it is a Skill Matrix of SDET.)
Well, after my last post What is an SDET, here in part 2 I share some inside baseball with you. I found a bulleted list of items I send to recruiters to explain to them what I am looking for in an SDET candidate. This list is reflective of my current role as a SDE-T at Microsoft, hence the .NET centric view of things. ….and yes, we are hiring SDETs!
Before the original writer, I want to insert an import point: as a Chinese Code Monkey, you must be proficient in English, especially reading and writing skills.
What is an SDE-T?
- Programming experience is a must
- Key here is that the candidate is a Developer. Strong QA candidates without development experience are generally not acceptable for this role.
- Test Automation
- Writing code to test code: UI and API level testing
- Creating, modifying, or designing test frameworks
- Good: Selenium, JUnit, NUnit, TestNG, etc.
- Using "canned" products like QuickTest Pro, TestDirector, SilkTest is generally *not* sufficient
- SDLC and Software Processes
- Agile/Scrum a plus
- QA interest / enthusiasm / experience
- Created Test Cases, Test Plans
- Debug / troubleshoot issues that they found (deep dive)
- Bug reporting / triage / prioritization
- Was responsible for guiding quality on production release
- Functional, load, stress, user interaction testing
- Customer focus
- Customer facing experience a plus
- "Soft" Skills
- Communication
- Driving consensus
- Leadership
- Creativity
- Technologies
- Must have experience programming a high-level OO language (C#, Java, C++, or C#)
- C#/.NET experience highly preferred
- RDBMS, SQL, stored procedures. SQL Server preferred.
- Web technologies: HTML, JavaScript, web services, XML, CSS
- Must have experience programming a high-level OO language (C#, Java, C++, or C#)
How to sell the SDE-T role to a developer
- Breadth of experience over narrow focus
- End to end product expertise. From development to user interaction
- Subject Matter Expert on product. Has input on product direction.
- Career "big fish in a small pond"… a strong contributor can really make a name for him or herself. Easier than in Dev because do not get "pigeon holed" and because the QA field is more exclusive.
原文转自Seth Eliot. 有删改
Yes, we are hiring SDETs, if you are willing, feel free to ping me. :-)
Lionden 2015年5月16日
E-mail：[email protected]
转载请注明原文地址和博客园Lionden：http://www.cnblogs.com/lionden/
