Senior Test Lead

Job Summary

• Key Responsibilities • Build, expand, and maintain a robust automated test suite covering UI flows, • backend services, APIs, and data pipeline correctness. Automation is the team's top priority and the primary measure of success this year.
• Integrate automated tests into Recon's CI/CD pipelines so regressions are caught pre-merge and pre-release.
• Perform end-to-end testing of the Recon application, covering data ingestion, processing, transformation, and delivery across frontend and backend systems.
• Develop comprehensive test plans and test cases up front and in writing, shared with engineers for review before testing begins, for web application interfaces, backend data processing, and API integration.
• Collaborate with engineers to prioritize and resolve identified issues.
• Document test results, defects, and recommendations for process and technology improvements.
• Attend Recon stand-ups daily (QA Lead required; QA engineers only required to attend when the Lead is unavailable) and provide both verbal and written comprehensive status updates.
• Continuously improve QA processes, tools, and methodologies to enhance team efficiency and effectiveness. Scope of Testing The QA team is expected to deliver four distinct types of testing: 1. Manual Testing Validate developer fixes and new features as they are completed, hands-on, case-by-case testing against documented test cases that have been reviewed by Engineering ahead of time. 2. Automated Testing Once a feature ships to production, QA is expected to automate the corresponding test cases and add them to the automated test suite. If a test case cannot be automated, it must be explicitly documented and tracked as a recurring manual regression item so nothing is silently dropped. 3. Performance Testing Build and maintain a framework to track Recon's system performance over time. This is not exercised frequently but becomes critical during events like database upgrades, infrastructure changes, or major releases. Recon currently lacks this capability and closing this gap is an expected outcome of this engagement. 4. Load Testing Build and maintain a framework to evaluate Recon's load-bearing capacity. Like performance testing, this is run infrequently but is essential when needed. This is also a current gap that the QA team is expected to close. Proven experience in QA, testing web applications, data pipelines, and large scale cloud-based services.
• Expertise in test planning, creating test cases, and executing manual and automated tests.
• Demonstrated track record of building automated test frameworks from scratch or significantly expanding existing ones.
• Familiarity with the Recon / Extract Scheduler technology stack: Ruby on Rails, Ember.js, React.js, TypeScript, Django, Backend / data: Python, AWS Aurora Postgres, Cassandra, Trino, Apache Iceberg, AWS SQS, Docker • QA tooling expertise required:
• Test automation frameworks such as Selenium, JMeter, or equivalent • Jenkins for CI/CD integration • Python for scripting and test development • A test case management tool such as JAMA • Strong analytical and problem-solving skills with attention to system-wide complexities.
• Experience with Agile, CI/CD pipelines, and version control (Git).
• Excellent communication skills and the ability to collaborate in a cross functional team.
• Willingness and proactiveness in learning and understanding complex engineering workflows, as well as the fundamentals of Recon — including how data flows through the system end-to-end — contributes directly to success in this role.
• Proactive mindset for proposing innovative

Key Responsibilities

• Key Responsibilities
• Build, expand, and maintain a robust automated test suite covering UI flows,
• backend services, APIs, and data pipeline correctness. Automation is the
  team's top priority and the primary measure of success this year.
• Integrate automated tests into Recon's CI/CD pipelines so regressions are
  caught pre-merge and pre-release.
• Perform end-to-end testing of the Recon application, covering data
  ingestion, processing, transformation, and delivery across frontend and
  backend systems.
• Develop comprehensive test plans and test cases up front and in writing,
  shared with engineers for review before testing begins, for web application
  interfaces, backend data processing, and API integration.
• Collaborate with engineers to prioritize and resolve identified issues.
• Document test results, defects, and recommendations for process and
  technology improvements.
• Attend Recon stand-ups daily (QA Lead required; QA engineers only required
  to attend when the Lead is unavailable) and provide both verbal and written
  comprehensive status updates.
• Continuously improve QA processes, tools, and methodologies to enhance
  team efficiency and effectiveness.

Scope of Testing
The QA team is expected to deliver four distinct types of testing:

1. Manual Testing
   Validate developer fixes and new features as they are completed, hands-on,
   case-by-case testing against documented test cases that have been reviewed
   by Engineering ahead of time.

2. Automated Testing
   Once a feature ships to production, QA is expected to automate the
   corresponding
   test cases and add them to the automated test suite. If a test case cannot be
   automated, it must be explicitly documented and tracked as a recurring manual
   regression item so nothing is silently dropped.

3. Performance Testing
   Build and maintain a framework to track Recon's system performance over
   time.
   This is not exercised frequently but becomes critical during events like
   database
   upgrades, infrastructure changes, or major releases. Recon currently lacks this
   capability and closing this gap is an expected outcome of this engagement.

4. Load Testing
   Build and maintain a framework to evaluate Recon's load-bearing capacity. Like
   performance testing, this is run infrequently but is essential when needed. This
   is also a current gap that the QA team is expected to close.

Skill Requirements

Proven experience in QA, testing web applications, data pipelines, and large
scale cloud-based services.

• Expertise in test planning, creating test cases, and executing manual and
  automated tests.
• Demonstrated track record of building automated test frameworks from
  scratch or significantly expanding existing ones.
• Familiarity with the Recon / Extract Scheduler technology stack: Ruby on
  Rails, Ember.js, React.js, TypeScript, Django, Backend / data: Python, AWS
• Aurora Postgres, Cassandra, Trino, Apache Iceberg, AWS SQS, Docker
• QA tooling expertise required:
• Test automation frameworks such as Selenium, JMeter, or equivalent
• Jenkins for CI/CD integration
• Python for scripting and test development
• A test case management tool such as JAMA
• Strong analytical and problem-solving skills with attention to system-wide
  complexities.
• Experience with Agile, CI/CD pipelines, and version control (Git).
• Excellent communication skills and the ability to collaborate in a cross
  functional team.
• Willingness and proactiveness in learning and understanding complex
  engineering workflows, as well as the fundamentals of Recon — including
  how data flows through the system end-to-end — contributes directly to
  success in this role.
• Proactive mindset for proposing innovative solutions and driving
  improvements.

Other Requirements

• Based in the US.
• Timezone overlap with Apple (Recon team): Must overlap with Pacific Time at
  minimum until 2:00 PM PT, Monday through Friday.
• Timezone overlap with HCL India QA team: Must maintain 3–4 hours of daily
  overlap with the India-based QA engineers, especially during the first 12
  months while onboarding, training, and ramping the broader team.
• Primary point of contact for the Recon team on all QA matters.
• Required to attend Recon standup daily and deliver comprehensive verbal
  and written updates covering progress, blockers, risks, and automation
  milestones.
• Strong people-management experience: capable of training, coaching, and
  holding the India QA engineers accountable to delivery.
• Hands-on technical depth — the Lead is expected to contribute directly to
  the automation framework, not solely manage.