Cookies & analytics consent
We serve candidates globally, so we only activate Google Tag Manager and other analytics after you opt in. This keeps us aligned with GDPR/UK DPA, ePrivacy, LGPD, and similar rules. Essential features still run without analytics cookies.
Read how we use data in our Privacy Policy and Terms of Service.
🤖 15+ AI Agents working for you. Find jobs, score and update resumes, cover letter, interview questions, missing keywords, and lots more.

InfraCloud Technologies • Pune, Maharashtra, India
Role & seniority: QA Engineer (Backend Testing), 5+ years experience
Location & work type: Pune, India; full-time, on-site
Stack/tools: Java-based microservices; REST APIs; API testing; backend automation (e.g., REST-assured or Java automation frameworks); end-to-end backend workflows; familiarity with transitioning from Tibco/Mulesoft to microservices
Test Java-based backend microservices and REST APIs; validate request/response payloads, data transformations, and error handling
Design, execute, and automate API and backend test cases; ensure functional, regression, integration, and acceptance testing
Validate end-to-end claims processing workflows across multiple services; perform data validation; document defects with logs and evidence; collaborate with developers and stakeholders
Backend/API testing of REST services; hands-on experience with Java-based testing/automation
Automation of API/backend tests; experience with Java automation frameworks (e.g., REST-assured)
Microservices/distributed systems testing; functional, integration testing; data validation; debugging
Understanding of Java applications and how services interact
Insurance/claims domain experience
CI/CD pipelines and automated test execution in build processes
Service virtualization or mocking frameworks; experience with event-driven or asynchronous processing
Experience - 5 + years (Location - Pune)
Role Overview We are building a backend claims processing platform in the insurance domain. The current system is built using workflow tools like Tibco and Mulesoft, and we are transitioning to a Java-based microservices architecture to replicate and enhance this logic. This role is focused purely on backend testing. There is no UI testing involved. The QA Engineer will be responsible for testing Java-based microservices, APIs, and end-to-end backend workflows, along with building automation for the same. Key Responsibilities Test Java-based backend microservices that replicate business logic previously handled by workflow tools. Design and execute API test cases for RESTful services. Validate request/response payloads, business rules, data transformations, and error handling. Perform functional, regression, integration, and acceptance testing at the backend level. Validate end-to-end claims processing workflows across multiple microservices. Automate API and backend test cases to ensure scalable and repeatable test coverage. Perform data validation across services and ensure correctness of business logic. Collaborate with backend developers and product stakeholders to understand complex rules and edge cases. Identify, reproduce, and document defects clearly with supporting logs and test evidence. Contribute to improving test processes and ensuring quality in a microservices-based architecture. Mandatory Skills
Backend/API Testing: Strong hands-on experience testing REST APIs and backend systems.
Automation Skills: Experience automating API test cases (e.g., REST-assured, Java-based automation frameworks, or similar tools).
Microservices Testing: Experience testing distributed systems or microservices-based architectures.
Functional & Integration Testing: Ability to validate complex backend workflows and business rules.
Data Validation: Comfortable validating JSON payloads, service responses, and backend data flows.
Understanding of Java Applications: Basic understanding of Java-based services and how microservices interact. Strong analytical and debugging skills. Good to Have Experience in the insurance or claims domain. Exposure to CI/CD pipelines and automated test execution in build processes. Experience with service virtualization or mocking frameworks. Understanding of event-driven systems or asynchronous processing.