Technical Lead / Automation Architect in Indianapolis, IN

1. Technical assessment and test architecture: Assess the technical characteristics of assigned applications, changes, interfaces, environments, and release components. Define how functional, system, integration, regression, and automated tests should be structured to provide appropriate coverage. Identify dependencies across applications, services, databases, middleware, batch processes, and external interfaces, and translate these into a coherent technical test design.

2. Automation strategy and framework governance: Establish automation design principles and recommend which test cases are suitable for automation based on repeatability, stability, business value, execution frequency, and maintenance cost. Define reusable framework components, coding conventions, object or service interaction patterns, data management, exception handling, logging, and reporting standards. Ensure that automation assets are maintainable and are not created solely to maximize script counts.

3. Tooling, environments, and execution integration: Provide technical direction for use of approved test-management, automation, defect-tracking, source-control, and execution tools. Coordinate with CLIENT technical contacts on environment readiness, connectivity, access, test configuration, and execution constraints. Where authorized, guide integration of automated tests with build or deployment pipelines and ensure that execution results can be traced to the relevant application version or release.

4. API, middleware, and cross-system testing oversight: Define technical coverage for APIs, service endpoints, message flows, middleware, data transformations, batch interfaces, and cross-platform transactions. Ensure that positive, negative, boundary, exception, authentication, error-handling, and recovery scenarios are considered as appropriate to the approved scope. Coordinate technical validation with the Salesforce / MuleSoft / MDM QA Engineer and relevant application owners.

5. Technical design and code reviews: Review test designs, automation scripts, reusable components, test data approaches, execution logs, and technical evidence for completeness and maintainability. Identify fragile scripts, insufficient assertions, poor test isolation, unreliable data dependencies, and gaps in error handling. Provide specific review comments and confirm that material issues are corrected before assets are treated as ready for repeated use.

6. Root-cause analysis and complex defect support: Provide technical leadership when defects span multiple applications, integration layers, environments, or data stores. Help distinguish application defects from environment, configuration, test-data, automation, or requirement issues. Coordinate technical investigation, reproduce complex failures, interpret logs and execution evidence, and support verification of corrective changes.

7. Technical quality metrics and risk visibility: Monitor relevant technical indicators such as automation stability, regression coverage, execution success, script maintenance, repeat failures, integration defects, and environment-related interruptions. Identify limitations in coverage or reliability and communicate their effect on test confidence. Ensure that metrics are interpreted in context and are not presented as proof of quality without supporting evidence.

8. Knowledge transfer and continuous engineering improvement: Provide technical guidance and knowledge transfer to QA and automation personnel. Maintain or oversee technical standards, framework documentation, reusable test assets, and design decisions. Recommend practical improvements to automation, test data, integration coverage, and execution efficiency, subject to CLIENT direction and approved tools.