Manual Tester Salary in India (2026)

TL;DR

For 2026 planning, current published references place fresher manual QA around INR 3 to 5 LPA and manual testers with roughly 3 to 5 years around INR 4 to 8 LPA. These are directional market observations, not guaranteed bands, and the fixed-pay component matters more than a headline CTC.

Key Takeaways

• Current 2026 sources place fresher manual QA near INR 3 to 5 LPA and mid-level manual testing near INR 4 to 8 LPA, but employer tiers vary widely.
• Always separate fixed pay, variable pay, employer contributions, benefits, bonuses, and equity before comparing Indian CTC offers.
• Product companies, GCCs, services firms, consultancies, and startups reward different combinations of execution, domain, communication, and technical depth.
• API testing, SQL, browser diagnostics, accessibility, mobile risk, and domain expertise can improve a manual tester's scope without erasing exploratory work.
• City labels alone do not determine pay, company type, office policy, shift, commute, and responsibility are stronger comparison variables.
• A matched job dataset and defensible project evidence create more negotiating leverage than an arbitrary percentage hike over current CTC.

Manual Tester salary India research for 2026 points to a broad market rather than one dependable average. Current published guides place fresher manual QA around INR 3 to 5 lakh per annum, commonly written as LPA, and one hiring-platform analysis places mid-level manual testers around INR 4 to 8 LPA. A current job-aggregation estimate sits near INR 6.39 lakh annually, but it reflects a different collection method.

The practical answer depends on fixed pay, experience, company type, city, shifts, domain, role scope, and the evidence you can demonstrate. This guide shows how to interpret the numbers, avoid CTC traps, and build a salary target that survives recruiter and hiring-manager questions.

TL;DR

Do not turn the upper end of any table into an entitlement. Match the job's employer tier, responsibilities, location, shift, domain, and interview bar.

1. Manual Tester salary India benchmarks in 2026

The SourceKode 2026 software testing career guide lists INR 3 to 5 LPA for a fresher Manual QA or Test Engineer. The source describes the figures as indicative. It is useful for entry-level orientation, but it is not an official wage survey and should not be applied to experienced candidates.

The Instahyre QA and SDET salary analysis lists roughly INR 4 to 8 LPA for a mid-level Manual Tester with 3 to 5 years. Instahyre is a hiring platform, and its table compares manual, automation, and SDET compensation. This provides role-specific context, although an individual employer may sit outside the range.

A Jooble QA manual testing salary page reported about INR 6,38,794 per year in July 2026. Job aggregators derive estimates from listings and their available records. Their title mix, geography, duplicate handling, and update process can differ from hiring-platform analysis.

Do not average these three numbers. The fresher range answers an entry question, the Instahyre band answers a mid-level role question, and Jooble provides an aggregated central signal. Keep the source, date, population, and pay definition beside every figure. Then compare the job in front of you.

2. Manual Tester salary India by experience and ownership

Experience matters, but calendar years are not a complete level system. Two candidates with four years can have different market scope. One may execute predefined cases on a single web application. Another may design risk coverage, query databases, validate APIs, lead UAT coordination, analyze production incidents, and influence release decisions. The second candidate has evidence for a wider comparison market.

The Instahyre INR 4 to 8 LPA reference specifically describes 3 to 5 years in a mid-level manual category. It does not say every five-year tester should receive INR 8 LPA, nor that nobody can exceed it. Company tier, interview performance, current hiring demand, location, fixed-pay mix, and specialist scope affect placement.

Audit your last 12 months. List decisions you made independently, serious defects found, ambiguity resolved, risks prevented, and improvements adopted by others. That evidence is a better salary argument than total executed test cases.

3. CTC, fixed pay, variable pay, and monthly in-hand

Cost to Company, or CTC, is not the same as fixed salary and not the same as bank credit. CTC may include fixed gross pay, performance variable, employer provident-fund contribution, gratuity accrual, insurance, joining bonus, retention bonus, allowances, and equity. Companies structure these components differently, so two INR 8 lakh CTC offers can deliver different guaranteed cash.

Build five rows for every offer:

1. Annual fixed gross paid through payroll.
2. Employee deductions that affect monthly in-hand, estimated from current rules and personal declarations.
3. Conditional cash, including performance variable and retention payments.
4. Employer-paid benefits or statutory contributions.
5. Equity or other uncertain long-term value.

If a recruiter says INR 7.5 LPA CTC, ask for the full compensation sheet. Do not assume the entire amount is divided by 12. Check the variable percentage, payout frequency, target achievement, first-year proration, joining-bonus clawback, and gratuity representation. Seek qualified tax or payroll advice for a material decision because individual deductions and rules change.

When comparing, use annual fixed pay first. Then add realistic scenarios for variable pay. Keep ESOPs separate until you understand instrument, units, vesting, exercise price, dilution, liquidity, departure rules, and tax. A high CTC with speculative ESOP value may be weaker than a lower CTC with stronger fixed pay.

4. Bengaluru, Hyderabad, Pune, NCR, Chennai, and remote pay

Bengaluru has a dense mix of product companies, startups, global capability centers, or GCCs, and services firms. Hyderabad has major GCC, cloud, financial, pharmaceutical, and enterprise employers. Pune spans services, product engineering, automotive, banking, and industrial technology. Delhi NCR includes fintech, telecom, commerce, travel, consulting, and enterprise companies. Chennai is strong in SaaS, automotive, finance, healthcare, and global delivery. Mumbai adds finance, media, commerce, and high housing costs.

That does not create a fixed city premium. A Bengaluru services role, Hyderabad GCC role, and Pune product role can sit in different compensation markets even when the title is Manual Tester. Company tier, customer budget, role grade, shift, and scope can outweigh the city label. Create separate samples for comparable employers.

Office policy changes personal value. Record rent, deposit, commute time, transport, office days, meal costs, shift transport, and relocation. Confirm whether remote means anywhere in India, a specific state, or periodic attendance at a base office. Ask whether the policy applies to your actual team rather than relying on a generic careers page.

A lower-cost city role with strong mentorship, service testing, and product ownership may improve long-term earnings more than a slightly higher repetitive execution role. Salary and career capital should be scored separately.

5. Services firms, product companies, GCCs, and startups

Indian QA compensation varies by employer economics. Large IT services firms consider client rate, account budget, billability, grade, location, and internal parity. Some roles provide exposure to global systems and structured learning. Others narrow the tester to case execution. Ask about the actual account, bench policy, project allocation, shift, travel, and what happens when the assignment ends.

Product companies often pay for direct product ownership, fast feedback, domain understanding, and collaboration with developers. Their interview may examine ambiguity, system behavior, API investigation, SQL, and product sense. GCCs can reward regulated-domain experience, global communication, platform knowledge, and long-term ownership. A support-oriented GCC and an engineering-led GCC should not be placed in the same bucket automatically.

Startups can give a manual tester broad access to requirements, analytics, customers, releases, and incident learning. They may also offer less stable process, uncertain equity, and high workload. Ask how quality responsibility is shared, whether developers test, how releases are approved, and who handles production incidents.

Do not choose a category from reputation alone. Ask who designs coverage, who owns automation, which environments exist, what the first 90 days will deliver, and how performance is evaluated. Those answers reveal whether the job develops your future comparison market.

6. Skills that move manual testers into stronger roles

The most useful career upgrade is not changing your title to Automation Tester on the resume. It is expanding the evidence you can gather. A strong manual tester observes systems across interfaces, tests business rules and failure paths, and communicates uncertainty. Technical skills make that work faster and less dependent on someone else.

High-value combinations include:

• HTTP, REST, JSON, authentication, headers, cookies, browser network tools, and API clients.
• SQL SELECT queries, joins, grouping, null handling, and safe verification against approved non-production data.
• Mobile permissions, interruptions, network transitions, device storage, notifications, and upgrade behavior.
• Accessibility checks for keyboard operation, semantics, contrast, zoom, forms, and screen-reader-supported journeys.
• Domain depth in payments, lending, insurance, healthcare, commerce, logistics, telecom, or enterprise workflows.
• Basic Java, Python, JavaScript, or TypeScript to read utilities, generate data, and understand automated failures.
• CI awareness, logs, feature flags, environments, and observability so defects include diagnostic context.

Learn API depth through the API testing guide and practice data reasoning with SQL interview questions for testers. Do not abandon exploratory testing. Use technology to reach states, isolate conditions, and verify outcomes while keeping human judgment focused on risk.

Certifications can help when target employers or clients request them. They do not replace a project, defect story, or deep explanation.

7. Create a runnable CTC comparison tool

This Python 3 program uses only the standard library. It does not calculate Indian income tax or statutory deductions, which depend on current rules and personal facts. Instead, it makes the offer components explicit. Save it as compare_ctc.py and run python3 compare_ctc.py. Replace the illustrative numbers with the written compensation sheets.

from dataclasses import dataclass

@dataclass(frozen=True)
class Package:
    name: str
    fixed_rupees: int
    target_variable_rupees: int
    employer_benefits_rupees: int
    equity_notional_rupees: int = 0

    @property
    def stated_ctc(self) -> int:
        return (
            self.fixed_rupees
            + self.target_variable_rupees
            + self.employer_benefits_rupees
            + self.equity_notional_rupees
        )

packages = [
    Package('Offer A', 600000, 60000, 40000, 0),
    Package('Offer B', 560000, 20000, 40000, 120000),
]

for package in packages:
    guaranteed_share = package.fixed_rupees / package.stated_ctc
    print(
        f'{package.name}: stated CTC INR {package.stated_ctc:,}, '
        f'fixed INR {package.fixed_rupees:,}, '
        f'fixed share {guaranteed_share:.1%}'
    )

The output reveals why a larger CTC may contain less fixed pay. It does not declare a winner. You still need payout rules, benefits, equity terms, working conditions, learning, and risk. Do not put private offer letters or personal identifiers in a public repository.

For a testing portfolio, add a sanitized exploratory charter, defect examples against a practice application, API evidence, and a small SQL dataset. Keep it runnable and original. Never reuse employer code, credentials, customer records, internal documents, or protected screenshots.

8. Resume evidence for a manual testing career

A resume should show what you tested, how you reasoned, and what changed because of your work. 'Executed 500 test cases' says little about risk or quality. A better bullet might say: 'Mapped refund states across UI, payment callback, and order data, identifying a duplicate-refund path before the festive release and adding targeted regression coverage.' Use that sentence only if it is true and explainable.

Organize skills around evidence. If you list Postman, describe the authorization, negative, schema, or state checks you performed. If you list SQL, explain a data inconsistency you diagnosed. If you list Jira, show the clarity of defect reporting rather than the tool name. Hiring managers can distinguish real use from a keyword collection.

Freshers need not invent commercial experience. Test a public practice app, write a small test strategy, log thoughtful defects, query a local database, and document a short accessibility review. Explain the limits of the exercise. A portfolio is credible when it shows judgment and admits what was not tested.

Use the manual testing interview questions for three years experience to rehearse evidence. Keep employment dates, title, notice period, and education accurate. Inflated experience may pass a keyword screen but fails follow-up questions and verification.

9. Job search strategy and salary calibration

Create a spreadsheet of 25 to 40 roles collected within the last month. Capture company type, city, work model, title, requested experience, domain, manual scope, API, SQL, mobile, accessibility, automation expectation, shift, disclosed fixed pay, CTC, source, and date. Remove jobs that are actually automation engineering, support, business analysis, or test leadership unless those are your targets.

Classify requirements as must have, useful, or employer-specific. Score your evidence rather than your confidence. For example, give 0 when you cannot demonstrate API testing, 1 when you completed a guided project, and 2 when you independently used it to diagnose product risk. This creates a learning plan based on repeated market demand.

Recruiter conversations supply missing band information. Ask whether the number is fixed, total CTC, or maximum including variable. Confirm shift, office days, location, notice-period preference, interview rounds, and joining timeline. Record the response immediately. Several consistent data points are more useful than one attractive promise.

Refresh the sample throughout an active search. Job markets and project demand change. Do not base a July 2026 decision on screenshots collected years earlier or social posts without a comparable role.

10. Negotiate without being limited by current CTC

Many Indian recruiters ask current CTC, expected CTC, notice period, and competing offers early. Answer truthfully while redirecting the discussion to the new role's scope. A concise response is: 'My current structure is INR A fixed and INR B total CTC. For this role's API, SQL, and release ownership, my research supports INR X fixed and INR Y total. Could you share the approved band and variable structure?'

Prepare three private numbers: an evidence-based target, an acceptable guaranteed package, and a walk-away point. Do not disclose the walk-away point. Treat fixed pay as the main comparison, then evaluate variable, joining bonus, leave, remote terms, insurance, commute, shift, brand, manager, and learning.

If fixed pay cannot move, explore a sign-on bonus, guaranteed first-year variable, additional leave, remote terms, training support, title accuracy, or an earlier written review with measurable criteria. Read clawback language. A joining bonus repayable after an early exit is not free cash.

Never fabricate another offer, edit documents, inflate salary, or claim a notice period you cannot meet. Credibility affects the present offer and future employment. The QA salary negotiation guide provides a more detailed conversation framework.

11. Prepare for a higher-paying manual QA interview

Higher-value manual interviews go beyond definitions of severity, priority, smoke, and regression. Expect scenarios about incomplete requirements, production-like data, payment failures, intermittent defects, release decisions, browser differences, API investigation, SQL, mobile conditions, accessibility, and stakeholder conflict. The interviewer wants to see how you structure uncertainty.

For each scenario, state the user and business goal, model states and dependencies, rank risks, choose coverage, gather evidence, and communicate residual risk. Do not start by listing every testing type. A checklist without prioritization does not show judgment.

Prepare six real stories: a severe defect, a missed defect, a rejected defect, a compressed release, an unclear requirement, and a process improvement. Explain your exact contribution, not what the team collectively did. Use measured outcomes only. If you cannot disclose business data, generalize the domain while preserving the technical decision.

Practice simple SQL and HTTP reasoning. You may be asked how to verify an order state, detect duplicates, test pagination, or inspect a failed request. A manual tester is not expected to invent an API, but should understand evidence beyond pixels. Ask the interviewer what quality ownership looks like, how releases use testing, and what distinguishes strong performers at the level.

12. A 90-day plan to increase market value

Days 1 to 30 are for calibration. Select one target, such as mid-level manual QA in a Bengaluru product company or a Hyderabad banking GCC. Build the role dataset, identify the three most repeated gaps, and rewrite the resume with truthful evidence. Practice test design and one SQL problem most days.

Days 31 to 60 are for a compact project. Choose a practice commerce or booking application. Create a risk map, exploratory charters, high-value cases, clear defects, API requests where available, local SQL verification, and an accessibility pass. Add a README that explains scope, environment, assumptions, and untested risks. The objective is reasoning, not volume.

Days 61 to 90 are for market execution. Apply to roles that genuinely match, rehearse scenario answers, and track results by interview stage. If multiple rejections cite API depth, improve that evidence. If the issue is communication, record and critique answers. If salary expectations are consistently outside approved bands, validate whether the role set or the target is mismatched.

Do not promise yourself a fixed salary increase after 90 days. The plan improves evidence, comparison quality, and interview readiness. Hiring volume, timing, current compensation, and employer constraints remain outside your control.

Interview Questions and Answers

Q: What Manual Tester salary India package do you expect?

State fixed and total separately: 'Based on the responsibilities and comparable 2026 roles, I am targeting INR X fixed and approximately INR Y total CTC, depending on variable and benefits.' Ask for the approved band and replace the placeholders with honest evidence.

Q: Why do you expect a large hike over your current CTC?

Explain that the target reflects the new role's scope, current matched market, and evidence, not a reward for resigning. Connect your request to independent risk ownership, API and data investigation, domain depth, or release responsibility. Avoid criticizing the current employer.

Q: How would you test a UPI payment that remains pending?

Model initiation, provider handoff, callback, polling, timeout, retry, duplicate notification, order state, ledger state, user messaging, and reconciliation. Verify idempotency and recovery at service and data layers where access is approved. Keep correlation identifiers so the path is diagnosable.

Q: How do you test with only one day before release?

Identify the change surface and highest-consequence user journeys, then protect those first. Use focused exploration at integration boundaries and a small known regression set. Report what was tested, what was not, and the residual risk before the release decision.

Q: How do you handle a production defect that escaped your testing?

Help contain and understand the issue without becoming defensive. Reconstruct the missing condition, determine whether the gap was requirement, coverage, data, environment, observability, or decision-related, and add the lowest-cost prevention. Share the learning without turning the review into blame.

Q: What should remain manual even if the team automates?

Exploratory investigation, rapidly changing behavior, subjective usability, and novel risk discovery often benefit from human judgment. Repeated deterministic checks with clear oracles are stronger automation candidates. The boundary should follow value and maintenance cost, not ideology.

Q: How do you write a high-quality bug report?

Lead with the violated behavior and user impact. Include environment, data, build, minimal steps, actual and expected results, reproducibility, and focused evidence such as requests or logs. Avoid assigning root cause unless the evidence proves it.

Common Mistakes

• Comparing CTC from one offer with fixed pay from another.
• Treating fresher, mid-level, automation, SDET, and lead figures as one salary market.
• Assuming an experience boundary automatically guarantees the top of a band.
• Counting target variable, gratuity, insurance, or ESOPs as monthly in-hand pay.
• Applying a generic Bengaluru premium without matching company type and role.
• Listing Postman, SQL, and Jira without a concrete investigation story.
• Inventing experience, offers, current CTC, notice period, or project outcomes.
• Ignoring shift, office frequency, commute, bench policy, and bonus clawbacks.
• Asking only for a percentage hike instead of a role-based fixed-pay range.
• Accepting a verbal compensation summary without the detailed written structure.

Conclusion

Manual Tester salary India benchmarks in 2026 support a practical planning zone, with published fresher references around INR 3 to 5 LPA and a mid-level manual testing reference around INR 4 to 8 LPA. The Jooble estimate near INR 6.39 lakh adds another signal, but each source answers a different question and uses a different method.

Build your own matched-role dataset, compare annual fixed pay before CTC, and show evidence of risk analysis, API and data investigation, domain knowledge, and communication. A truthful, structured case for scope will outperform a copied average or arbitrary hike demand.

Interview Questions and Answers

Frequently Asked Questions

Related Guides

• Automation Tester Salary in India (2026)
• Manual Tester Salary in Canada (2026)
• Manual Tester Salary in Germany (2026)
• Manual Tester Salary in UK (2026)
• Manual Tester Salary in USA (2026)
• Performance Tester Salary in India (2026)