Lead Software Architect - Testing

JOB DESCRIPTION

Must Have :

• Should have 15+ years of experience,
• This is Lead Architect role, should have experience in test automation and simulation. If required, leader should contribute to execution.
• Strong knowledge on web automation, desktop automation, mobile automation and embedded automation
• Should have strong programming knowledge (C# / Java / Python)
• Should be a technical mentor to the team
• Good Understanding of OOPS concepts
• Work experience in developing simulators is a great added advantage
• Able to drive the initiatives across V&V and within BA
• Should have experience in understanding build deployment and DevOps.
• Should have experience / expertise in end-to-end test for large scale platform on prem / cloud application (module test, component test, integration test, API test, End to End, Performance / NFR / Ilities Test).
• Should have experience in developing test automation frameworks (Ex : Python, Java, C#).
• Should have experience in handling local and global stakeholders.
• Should have experience in planning, resource assignment, execution, and reporting.
• Should have experience in running test for agile programs (PI, Sprint, Scrum Teams, Velocity, Sprint Say / Do etc).
• Should have experience in handling mix of senior and junior resources.
• Should have experience in collaborating with global teams
• Should have skills in mentoring, talent management, coaching, motivating resources to retain key talent and develop succession plan for leadership role.
• Should have experience using simulators to run uilities / performance test.
• Should have experience in assessing technical and resource related risks in program and coming with mitigation plan by working with different functions / stakeholders.
• JIRA, X-RAY, Confluence etc tool understanding is added benefit.
• Person having experience in handling overall H / W and S / W integration test is preferred (Embedded and Software Automation).
• Person with experience of end-to-end product development (Discovery->

Release) is preferred.