Quality Engineer

Job Title

QA Engineer – OSS

Location

Pune

About the Role

We are looking for a QA Engineer with strong experience in API testing and automation to work on our OSS (Operational Support Systems) stack. The ideal candidate is hands‑on with Karate for test automation, comfortable performing both automated and manual testing, and familiar with telecom/billing domains such as CDRs, whitelisting, A2P messaging, online charging systems, and billing.

Key Responsibilities

Design, develop, and maintain automated API test suites using Karate.

Perform functional, regression, integration, and exploratory testing for REST/HTTP APIs across OSS components, using both automation and manual testing as appropriate.

Analyze and validate telecom/billing data flows, including:

CDR generation, mediation, and rating

Whitelisting/blacklisting rules

A2P messaging flows and routing

Online Charging System (OCS) interactions and balance updates

Billing, invoicing, and usage aggregation

Create, maintain, and execute manual test cases where automation is not yet in place or not feasible.

Use Postman (and similar tools) for exploratory, ad‑hoc, and manual API testing.

Collaborate closely with developers, product owners, and operations teams to clarify requirements and define acceptance criteria.

Investigate defects, analyze logs/data (including CDRs), and provide clear, reproducible bug reports.

Contribute to test strategy, coverage, and quality gates in CI/CD pipelines.

Maintain test data and test environments relevant to OSS components.

Must‑Have Skills & Experience

3–6 years (adjust as needed) of experience in QA/software testing, with a strong focus on API testing.

Solid hands‑on experience with Karate for API test automation (feature files, CI integration, data‑driven tests, etc.).

Proven experience in manual testing of APIs and backend flows.

Strong understanding of REST APIs, HTTP, JSON, and common authentication mechanisms (tokens, OAuth, etc.).

Practical experience with the following telecom/OSS/billing concepts:

CDR (Call/Charging Detail Records) – structure, lifecycle, validation

Whitelist/blacklist – rules configuration and enforcement

A2P (Application‑to‑Person) messaging – routing, charging, delivery flows

Online Charging System (OCS) – real‑time balance checks, charging, and rating

Billing – usage aggregation, rating, and invoice generation

Strong experience using Postman (collections, environments, scripting) or similar tools for manual and exploratory API testing.

Good understanding of SDLC, QA methodologies, and different test types (functional, regression, integration).

Ability to read and analyze logs, API responses, and data records (e.g., CDRs, CSVs, DB tables).

Familiarity with version control (Git) and CI/CD tools (e.g., Jenkins, GitLab CI, GitHub Actions, Bamboo, etc.).

Good communication skills; able to work closely with cross‑functional teams.

Nice‑to‑Have

Experience in telecom operators, MVNO/MVNE, messaging, or charging/billing platforms.

Knowledge of scripting or programming (Java/JavaScript or similar) to extend/maintain automation frameworks.

Experience with performance testing of APIs (e.g., Gatling, JMeter, k6, or Karate performance runs).

Familiarity with microservices, message queues (Kafka/RabbitMQ), and event‑driven systems.

Experience testing integrations between OSS/BSS systems (CRM, billing, provisioning, mediation).

Exposure to SQL/NoSQL databases for test data setup and verification.