Job Description –
Positions: SDET LEAD
Duration: 6 + Month contract (POSSIBLE EXTENSIONS)
Location: Deerfield Beach, FL (Hybrid 3/2)
Interview: virtual
Need LinkedIn and managerial reference.
Use the notes below. The job specs are generic
This is a true SDET role. Need a senior person to be a liaison between development and testing
This is not just a regular QA automation person
SDET LEAD (NOT MANAGING PEOPLE, BUT NEED LEADERSHIP SKILLS) (TOSCA BIG PLUS. MUST HAVE EITHER JAVA OR PYTHON AND NEED SQL, API TESTING, AUTOMATION. LIAISION BETWEEN DEVELOPMENT/ARCHITECTURE AND TESTING TEAMS. THIS RESOURCE WILL BE THE GO TO FOR SEVERAL TESTING TEAMS AND ACT AS THE LIASION WITH THE DEVELOPMENT TEAMS)
- SDET lead for multiple teams with excellent communication skills.
- Day to day bridge between the teams, building the software and testing the software.
- We have testers that learned the application but need someone that can help that team learn the underlining technologies
- Create patters that the qa teams can repeat on similar interfaces
- Someone that can speak to the dev team, architecture nuances
- Conduit to the team team.
- That way not every lead from every test team not asking the same questions to the dev team
- Cross functional teams focus on different business processes. Horizontally
- Help test teams understand the vertical slice where and how data flows across teams.
- Tech side:
- For Automation using tosca(how to maximize Tosca, sit and baby sit Tosca also, unplanned issues)
- Own and fix those things.
- Fluent in dev speak and data side so they understand architecture and create test patterns.
- Then help the test team where they get stuck especially with Tosca. (if they don’t have Tosca they need to be familiar with it and have other similar tool) Focus on solutions and not rephrasing problems.
- Data testing coming up.
- Need either Python or Java (not coding every day, but a good coding or test automation background). Need to be able to build patterns. Need to read and follow Java/Python code and SQL
- Understand data so they can communicate with the development engineers and architects once not multiple times)
- Some API testing. Enhancing existing API’s. make sure they understand the API they’re testing. (not just testing the front end. Need to review the test cases)
From:
Santosh,
Vyzeinc
ssharma@vyzeinc.com
Reply to: ssharma@vyzeinc.com