Quality Assurance Tester

Company - Arcitech

Location - Turbhe, Navi Mumbai (On site)

Experience - 1 to 4 years

Budget - 3lpa to 4.2lpa

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. Quality is central to our reputation — a

client-reported bug is not just a technical issue, it reflects on our credibility as an engineering

company. We are looking for manual testers who take genuine ownership of quality, not box-

tickers.

About the Role

As a Manual QA Tester you are the last line of defense for quality before anything reaches a

client or a live user. You will work on our highest-stakes products — systems that handle

payments, children's education data, recorded customer conversations, and healthcare

information — where a missed defect has real consequences. This is a craft role: we care about

how well you test (your coverage, your edge-case thinking, the clarity of your bug reports) far

more than how many cases you can rush through.

This is a manual testing role. Automation is not required, though an interest in growing toward it

over time is welcome.

What You Will Test

You will test complex, data-sensitive products and client projects, including:

• An education platform with student and teacher flows, course purchases, multi-currency

payments, tax/GST calculations, ratings, and strict separation of one user's data from

another's — including data belonging to younger users, where correctness and privacy

matter most.

• A customer-conversation analytics platform involving recorded calls, dashboards, and

sentiment/quality data, where accuracy and access control are critical.

• A healthcare interpreting platform where data handling and reliability carry real-world

impact.

• Complex client projects with intricate business logic and integrations that demand

careful, methodical testing.

Because of this, your day-to-day testing goes well beyond happy-path clicking — it includes

payment and transaction edge cases (failed payments, refunds, currency conversion, minimum-

amount limits), role and permission boundaries, data-accuracy checks across dashboards and

reports, validation and error handling, and regression across releases.

Key Responsibilities

• Test case design and execution. Prepare clear test case scenarios before sign-off

testing begins, covering positive flows, negative scenarios, edge cases, role/permission

checks, validation, regression impact, and cross-browser/device variations where relevant.

• Find issues before users do. Test assigned features, fixes, and regression areas

thoroughly. Catching a bug internally is a win; a bug that reaches a client or user is a miss.

• High-quality defect reporting. Log every issue with clear reproduction steps, expected

vs. actual behavior, environment details, and evidence (screenshots, recordings, console

logs) — so a developer can reproduce it without you explaining it verbally.

• Accurate classification and retesting. Classify bugs by severity (Critical / High / Medium

/ Low), retest fixes, and update records with outcomes.

• Release sign-off discipline. Never mark something fully tested without documented,

executed test cases. Block release when material bugs are open or testing is incomplete.

• Tooling discipline. Maintain accurate, current records in our project and issue-tracking

systems (we use Zoho Projects and Zoho Desk) and log working hours via our time-

tracking tool.

• Continuous improvement. Surface recurring defect patterns, suggest process and

tooling improvements, and contribute to the wider QA practice.

Quality Independence — An Important Part of This Role

READ THIS BEFORE APPLYING

Our testers operate independently from delivery pressure. You do not approve work because a

team wants to hit a date. Quality decisions are made on the merits of what is actually working.

If you are ever pressured to sign off on something that is not ready, you are expected to block the

release and escalate — not give in. Quality and sign-off matters report to the Senior QA Engineer

who leads testing, not to the delivery team. We are looking for someone with the integrity and

backbone to hold that line.

Required Qualifications

• 2+ years of manual testing on web or software applications, with at least 1 year owning

testing for a product or module end to end (not only executing someone else's test

scripts).

• Strong test design. Demonstrable ability to write thorough test cases covering positive,

negative, edge, and regression scenarios — not just the happy path.

• Defect reporting track record. Clear, reproducible bug reports with proper evidence.

• Integrity and independence. Willingness to log every issue honestly, block a release that

is not ready, and escalate when pressured.

• Tooling familiarity. Comfortable with a defect/issue tracking system (Zoho, Jira, or

similar) and standard QA workflows.

• Testing fundamentals. Solid grasp of the QA lifecycle, test case management,

severity/priority classification, and regression testing.

• Attention to detail and communication. Methodical and thorough, able to describe

issues clearly in writing and coordinate with developers and project managers.

Preferred (Not Required)

• Experience testing applications involving payments, multi-currency, or sensitive/regulated

user data.

• Exposure to API testing (e.g., Postman) at a basic level.

• ISTQB Foundation or similar QA certification.

• Interest in growing toward test automation over time.

Your First 90 Days

• First 30 days: Understand our QA standards and SOP, set up in our tools, complete

assigned test cases with documented scenarios, and log your first genuine bug findings.

• By 60 days: Your test case library for assigned products is complete and current, your

bug reports are consistently reproducible and well-evidenced, and your daily/weekly

testing rhythm runs without reminders.

• By 90 days: Zero material defects escaping to clients on releases you approved, same-

day acknowledgment on client-reported issues, and active contribution to cross-team

defect-pattern discussions.

Interview Process

Our hiring process has multiple stages:

1. An initial conversation with our HR team.

2. An AI-led video screening interview about your background and testing experience.

3. A practical testing exercise: given a sample feature or application, you will design test

cases (including negative and edge scenarios) and write up any defects you find. This is

the core of our assessment.

4. A final discussion with the Senior QA Engineer who leads the testing team.

We assess how you think about testing, not just whether you know the terminology. Be ready to

walk through how you would test a real feature — say, a course-purchase payment flow — end

to end.

Why Join Arcitech

• Test real, production software across high-stakes products and complex client projects.

• A QA function where independence and quality are genuinely respected, not overruled by

deadlines.

• Clear standards, structured processes, and a senior QA lead to learn from and grow your

craft.

• Collaborative, growth-focused environment with Provident Fund and employee benefits.