Role Summary

Own the quality of capital markets back-office software through rigorous manual testing across functional, regression, integration, and user acceptance testing phases. Work closely with Business Analysts, Developers, and Product Owners to understand requirements, design comprehensive test scenarios, and ensure that regulatory compliance features, trade lifecycle workflows, and exchange connectivity modules are defect-free before every release. Bring domain knowledge of broking back-office operations to design tests that go beyond surface-level validation and catch real business-impact defects.

Key Responsibilities

A. Test Planning & Design

• Test Planning: Analyse BRDs, FSDs, and user stories to prepare comprehensive Test Plans covering scope, approach, entry/exit criteria, risks, and timelines for each release cycle.
• Test Case Design: Design detailed test cases and test scenarios for functional, regression, integration, boundary, and negative testing — with clear steps, test data, expected results, and traceability to requirements.
• Requirement Traceability: Maintain a Requirements Traceability Matrix (RTM) linking every test case to its corresponding BRD/FSD requirement — ensuring full coverage and audit readiness.
• Domain-Driven Test Design: Leverage capital markets domain knowledge to design test scenarios that mirror real broking operations — end-of-day batch runs, margin computation cycles, settlement obligation mismatches, exchange file ingestion failures, and regulatory report generation.

B. Test Execution

• Functional Testing: Execute manual test cases across all modules — trade booking, order management, margin management, clearing & settlement, depository operations, regulatory reporting, and brokerage computation.
• Regression Testing: Run full and targeted regression test suites after every build/patch to ensure existing functionality is not broken by new changes — particularly critical after regulatory change releases.
• Integration Testing: Validate end-to-end data flows across modules and across external integrations — exchange file ingestion (NSE/BSE/MCX), depository (NSDL/CDSL) transactions, bank feed reconciliation, and third-party API connectivity.
• Exchange File Testing: Test ingestion, parsing, and processing of exchange files — SPAN files, bhavcopy, obligation files, pay-in/pay-out data, TBT feeds — validating computed outputs against expected values.
• UAT Support: Co-ordinate and support client User Acceptance Testing — prepare UAT test packs, guide client operations teams through test execution, log observations, and track sign-off.
• EOD Batch Testing: Test end-of-day and end-of-week batch processes — EOD position computation, margin file generation, settlement batch, obligation upload, and report generation — verifying output files against expected exchange/regulator formats.

C. Defect Management

• Defect Logging: Log defects with complete reproducible steps, screenshots, log excerpts, and severity/priority classification in Jira, Azure DevOps, or equivalent tools — enabling developers to reproduce and fix without back-and-forth.
• Defect Triage: Participate in daily defect triage calls with developers and product owners — validating severity, agreeing priority, and tracking resolution within the sprint.
• Defect Retesting & Closure: Retest fixed defects in the correct build environment, confirm resolution, and formally close — ensuring no regression before marking a build as release-ready.
• Root Cause Tracking: Identify recurring defect patterns across releases and report to the product team — enabling upstream process improvements in requirements or development practices.

D. Regulatory & Compliance Testing

• Regulatory Change Testing: Test all product changes driven by SEBI circulars, NSE/BSE exchange notices, and IRDAI/RBI guidelines — validating compliance with effective dates, reporting formats, and computation rule changes.
• SEBI Report Validation: Verify regulatory reports (SEBI margin reporting, exchange MIS, client-wise position reports, UCC linkage) against regulator-prescribed formats and data accuracy requirements.
• Peak Margin Testing: Test peak margin snapshot computation, intra-day margin reporting, and upload file generation — validating against SEBI peak margin framework requirements.
• Audit Trail Validation: Ensure all regulated workflows maintain complete, tamper-proof audit trails — verifying timestamps, user actions, and system-generated entries as required by SEBI and exchange compliance frameworks.

E. Quality Assurance Process

• Test Environment Management: Coordinate with DevOps/infrastructure teams to maintain stable test environments — managing test data, environment refreshes, and configuration consistency across QA, UAT, and staging.
• Release Sign-Off: Prepare and publish Test Summary Reports at the end of each release cycle — summarising test execution metrics, defect status, open risks, and formal go/no-go recommendation.
• Agile Ceremonies: Participate in sprint planning, backlog grooming, daily stand-ups, and sprint reviews — providing QA input on effort estimates, acceptance criteria clarity, and release readiness.
• Knowledge Base: Maintain and continuously improve the test case repository — keeping test cases current with product changes and regulatory updates across every release.

Capital Markets Domain Knowledge — Preferred

Candidates with hands-on knowledge of the following areas will be able to design significantly more effective test scenarios:

Skills & Qualifications

Preferred Background — Employers & Platforms

Candidates with prior testing experience at the following capital markets technology firms are strongly preferred:

Educational Qualifications

• B.E. / B.Tech / BCA / B.Sc (Computer Science or Information Technology)
• MBA (Finance) or B.Com candidates with strong technology aptitude and capital markets operations background are equally considered
• ISTQB Foundation Level certification — preferred; Advanced Level is an added advantage
• NISM Series VII or VIII certification — an advantage for candidates from capital markets background

Behavioural Competencies

• Detail-obsessed — naturally notices inconsistencies, edge cases, and boundary conditions that others overlook
• Domain-curious — goes beyond the test script to understand why a feature works the way it does in a broking back-office context
• Deadline-aware — manages test execution under release pressure without compromising coverage or quality
• Collaborative — works constructively with developers on defect reproduction and resolution, not adversarially
• Proactive — raises test environment issues, data gaps, and specification ambiguities early rather than discovering them mid-execution
• Ownership mindset — treats the quality of the product as a personal responsibility, not just a process to follow