Senior Quality Assurance Tester

Company Arcitech
Location - Navi Mumbai (On-site)
Experience 6 years+
IMMEDIATE JOINERS PREFERRED

About Arcitech
Arcitech is an enterprise AI automation and software development company building production
software for clients and for our own AI-native products — several of which handle payments,
children’s education data, recorded customer conversations, and healthcare information. Quality
is central to our reputation and, on these products, to our legal and compliance standing. We
are building out a serious QA function and need a senior leader to anchor it.
About the Role
This is a senior, hands-on leadership role. You will lead our manual testing team and own the
testing craft across our highest-stakes products. Today we have capable testers but no one
owning test strategy, coverage standards, and QA process maturity at a senior level — that is
the gap you will fill. You will set how we test, raise the bar on the team’s test design and defect
quality, govern release readiness, and bring the structure (test plans, coverage tracking,
traceability) that our most complex products demand.
You remain hands-on — you still test the hardest, highest-risk areas yourself — while also
leading: setting standards, mentoring testers, and owning quality outcomes across the portfolio.
What You Will Own

• Test strategy across products. Define how each product is tested — Pro School
(education, payments, children’s data), the customer-conversation analytics platform
(recorded calls, dashboards), the healthcare interpreting platform, and complex client
projects — prioritizing by risk and data sensitivity.

• Process maturity that does not exist today. Build and maintain test plans, coverage
matrices, and requirements traceability so testing is systematic and auditable rather than
memory-based — the structure our products currently lack.

Arcitech | Senior QA Engineer (Testing Team Lead) | Page 2

• Leading and mentoring the testing team. Raise the team’s standard of test design,
edge-case thinking, and defect reporting through review, coaching, and clear standards.
Identify weak testing and fix it.

• Release-readiness governance. Own the sign-off discipline across products: nothing
ships as “tested” without documented, executed coverage. Uphold QA independence from
delivery pressure across the whole team.

• Root-cause analysis on escaped defects. Lead RCAs when a material bug reaches a
client, identify how it escaped (missing coverage, bad handoff, rushed sign-off, regression
not tested), and drive corrective action so it does not recur.

• Quality reporting to leadership. Report quality status, risks, and trends across products
to the CEO, with a clear, honest picture at all times.

Key Responsibilities

• Define and own the QA process and test strategy for Tier 1 products and complex client
projects.

• Build and maintain test plans, coverage matrices, and traceability across products.

• Establish testing standards for the hard areas: payment and multi-currency flows,
role/permission boundaries and data isolation, sensitive- and regulated-data handling, and
integration-heavy business logic.

• Lead, mentor, and review the manual testing team; improve each tester’s test design and
defect-reporting quality.

• Own release-readiness decisions and sign-off discipline; protect and model QA
independence from delivery pressure.

• Lead escaped-defect RCAs and implement corrective actions across the team.

• Coordinate testing across multiple products and complex client projects simultaneously.

• Maintain accurate records in Zoho Projects and Zoho Desk; ensure the team does the
same.

• Identify automation opportunities and build the case and roadmap for introducing
automation over time.

• Report quality metrics and risks to leadership on a regular cadence.
Leadership & Quality Independence
CENTRAL TO THIS ROLE
You set the standard for quality independence and model it for the team. QA decisions are made
on the merits of what is actually working, never on schedule or incentive pressure. When a
release is not ready, you block it and you back your testers when they block it.
You hold the line so your testers can hold theirs. You own final QA sign-off and override
authority; in…