01
What is a sprint planning meeting and what does QA contribute?
Show answer
The team selects stories for the sprint. QA helps estimate testing effort, clarifies acceptance criteria and flags dependencies and risks.
Jio Platforms Software Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Jio Platforms hiring for Software Testing roles
Jio Platforms is the digital services arm of Reliance Industries, operating Reliance Jio telecom along with digital services such as MyJio, JioFiber, JioCloud and JioTV. Its technology teams build telecom software, 5G systems, apps and data platforms. It hires for software engineers, testers, network engineers, data engineers and data scientists.
For Software Testing roles, this Jio Platforms practice set focuses most on Agile, SQL and API Testing (8), Bug Life Cycle and Jira (6), Test Case Design (5), Accessibility & Usability Testing (4). It has 6 easy, 30 medium, 4 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Telecom
- Headquarters
- Navi Mumbai, India
- Main India offices
- Navi Mumbai, Bengaluru, Hyderabad
Jio Platforms Software Testing interview process
- Online assessment (aptitude + technical)
- Technical interview
- Managerial round
- HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for Jio PlatformsStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
3 questions free Unlock the rest in seconds
02
What is a REST API?
Show answer
An API style using HTTP methods on resources identified by URLs, usually exchanging JSON and staying stateless.
03
What is the difference between ad hoc testing and monkey testing?
Show answer
Ad hoc testing is informal testing without test cases, done by a tester who understands the application and tries likely weak areas based on experience. Monkey testing gives random inputs and actions, often without knowing the application, to see if it crashes. Ad hoc testing is targeted and good at finding logical bugs, while monkey testing is good at finding stability issues and is often automated.
04
Write test cases for a one-to-one chat feature.
Show answer
Send and receive text messages and check order and timestamps. Test sent, delivered and read status. Send emojis, long messages, links and attachments within and over the size limit. Check messages sent while offline are queued and delivered on reconnect. Verify blocking a user stops messages. Test notifications when the app is in background. Check chat history after reinstall or on a second device, and that deleted messages disappear for both users if supported.
05
What is JMeter and what does a basic test plan in it contain?
Show answer
Apache JMeter is an open-source load testing tool, mainly for HTTP APIs and web pages. A basic test plan has a Thread Group that sets the number of virtual users, ramp-up time and loop count; samplers such as HTTP Requests; config elements like headers and CSV data; timers for think time; assertions on responses; and listeners or reports showing response times, throughput and errors. Run real load in non-GUI mode.
06
Release is tomorrow and you can't test everything. What now?
Show answer
Risk-based testing: cover critical user flows, recent changes and high-defect areas first. Clearly communicate the untested risks and get stakeholder sign-off.
07
How do you test form accessibility, including labels and error messages?
Show answer
Check that every field has a visible label tied to it, so clicking the label focuses the field and a screen reader announces it. Required fields must be indicated in text, not only by colour or an asterisk without explanation. Submit with errors and check that messages are specific, appear next to the field, are announced by the screen reader and focus moves to the first error. Also check autocomplete for name, email and address.
08
The app crashes only on one older Android version. What are your steps?
Show answer
Reproduce it on that exact OS version, using a real device or an emulator image, and note the device model and app build. Capture the crash log and stack trace. Check if the code uses an API or library not supported on that version, or a permission or storage behaviour that changed. Log the bug with logs and the minimum supported version from the requirement, so the team can decide to fix it or raise the minimum version.
09
A user fills a long form, switches to another app and comes back. What should you test?
Show answer
Check that the form data is still there when the user returns after a few seconds and after a longer time. Test when the OS kills the app in background due to low memory, which you can force with developer options, and confirm the app restores state or at least warns the user. Also check session timeout behaviour and that sensitive screens are hidden in the recent apps view if required.
10
What is the difference between a defect and a production incident?
Show answer
A defect is a flaw in the software that makes it behave differently from the requirement, whether found in testing or production. A production incident is an event that disrupts or degrades service for users, such as an outage or a failed payment flow. An incident may be caused by a defect, but also by infrastructure, configuration or third-party failures. Incidents are handled by an incident process first, then linked to defects for the fix.
11
What is accessibility testing?
Show answer
Checking that people with disabilities can use the product, using screen readers, keyboard navigation, colour contrast and WCAG guidelines.
12
What is the difference between GET and POST?
Show answer
GET retrieves data and has parameters in the URL; POST sends data in the body to create or process something.
13
How do you write test cases when only wireframes are available and the UI is not ready?
Show answer
Use the wireframes and the user story as the test basis. Write test scenarios and high-level cases for the flows, field validations, navigation and error states shown in the design. Note open questions, such as missing empty states or error messages, and clarify them with the designer. Keep exact UI text and steps light so they are easy to update. Once the build arrives, refine the cases and add any missing details.
14
What are latent defects and masked defects?
Show answer
A latent defect exists in the software but has not caused a failure yet because the needed conditions have not occurred, such as a leap-year bug that appears only on 29 February. A masked defect is hidden by another defect, for example a broken discount calculation you cannot reach because the cart page crashes first. After the first bug is fixed, the masked one appears, which is one reason regression and retesting matter.
15
What are test deliverables?
Show answer
Test deliverables are the documents and artefacts produced during testing and shared with stakeholders. Before testing: test plan, test strategy and estimates. During testing: test scenarios, test cases, test data, traceability matrix, execution logs and bug reports. After testing: test summary report, closure report, metrics and lessons learned. The test plan should list which deliverables are expected so nothing is missed at sign-off.
16
When should you reopen a bug and when should you log a new one?
Show answer
Reopen the bug when the same issue, with the same steps and expected result, still fails after the fix. Log a new bug when the fix works but a different problem appears, even in the same screen, or when the original bug has already been closed in a past release. Link the new bug to the old one. Mixing different problems in one reopened ticket confuses tracking and metrics.
17
What is shift-left testing and why is it cheaper?
Show answer
Shift-left means starting testing activities earlier in the life cycle: reviewing requirements, joining design discussions and writing tests before code is complete. A defect found in requirements may cost a short conversation to fix, while the same defect found in production may need a hotfix, data correction and customer support. Testers shift left by asking questions in grooming, defining acceptance criteria and reviewing designs.
18
Write test cases for a shopping cart.
Show answer
Add, remove, update quantity, price and tax calculation, coupon codes, stock limits, cart persistence after login and checkout navigation.
19
How do you test touch target size and gestures for accessibility in a mobile app?
Show answer
Check that buttons and icons are large enough to tap without hitting neighbours: Android guidance is 48 by 48 dp and iOS is 44 by 44 points. Test with large font settings and one-handed use. Any action using complex gestures, such as swipe to delete or pinch, must have a simple tap alternative. Then turn on TalkBack and VoiceOver and confirm each control can be focused, named and activated.
20
How do you test an API using Postman?
Show answer
Create a request with method, URL, headers and body, send it, check status and body, add test scripts and save it in a collection.
21
Write a JQL query for open high or highest priority bugs in the current sprint of project PAY.
Show answer
project = PAY
AND issuetype = Bug
AND statusCategory != Done
AND priority in (Highest, High)
AND sprint in openSprints()
ORDER BY priority DESC, created ASC
22
SQL: verify that row counts and totals match between a source table and a target table after a data load.
Show answer
-- Compare counts and sums side by side; both columns must match
SELECT
(SELECT COUNT(*) FROM staging_orders) AS src_count,
(SELECT COUNT(*) FROM dw_orders) AS tgt_count,
(SELECT SUM(amount) FROM staging_orders) AS src_amount,
(SELECT SUM(amount) FROM dw_orders) AS tgt_amount;
23
What is defect density?
Show answer
The number of defects per size of software, for example defects per thousand lines of code or per module, used to compare quality.
24
What is the difference between a story, epic, task and bug in JIRA?
Show answer
An epic is a large body of work; stories are user-facing slices of it; tasks are technical work items; bugs are defects.
25
Your automated accessibility scan shows zero errors. Is the page accessible?
Show answer
Not necessarily. Automated tools catch only a part of WCAG issues, such as missing labels and contrast. A clean scan still needs manual checks: keyboard-only navigation, focus order, a screen reader pass, meaningful alt text and link names, error handling, zoom and reflow and dynamic content. Report the result as 'no automated violations found' and add the manual checklist outcome before claiming conformance.
26
What is CI/CD and how does testing fit?
Show answer
Code is built and tested automatically on each change; tests are quality gates that stop faulty builds from moving forward.
27
Write test cases for an ATM withdrawal.
Show answer
Valid card and PIN, wrong PIN, three failed attempts, amount above balance, amount above daily limit, invalid denomination, machine out of cash, network failure and receipt printing.
28
How would you test a pen?
Show answer
First ask what type of pen and who the users are. Functional: it writes smoothly, ink flows without leaking, the cap or click mechanism works and the ink colour matches the label. Non-functional: comfort of grip, writing length before ink runs out, performance at different temperatures and on different paper. Negative: dropping it, pressing hard, leaving it uncapped. Safety: the cap is non-toxic and has an air hole. This shows structured thinking, not just a list.
29
Explain three usability heuristics with examples from a web app.
Show answer
Visibility of system status: after clicking Pay, show a progress indicator so users do not click again. Error prevention: disable the Submit button until required fields are valid, or ask for confirmation before deleting an account. Recognition rather than recall: show recently searched items and saved addresses instead of making users remember them. Other heuristics include consistency, user control with undo, and clear help for recovering from errors.
30
What is cross-site scripting (XSS)?
Show answer
XSS is a vulnerability where an attacker's script is injected into a page and runs in other users' browsers, which can steal session data or change the page. It occurs when user input is shown without proper encoding. Testers enter a harmless script tag or an image tag with an onerror alert in comments, profile names and search boxes, then check if it executes when the page is displayed. Output encoding prevents it.
31
How do you test a mobile app's offline mode and data sync?
Show answer
Turn off the network and perform supported actions, such as creating, editing and deleting records, and check they are saved locally with a pending status. Reconnect and verify everything syncs once, in order, with no duplicates. Test conflicts, where the same record is changed on two devices, and confirm the agreed rule applies. Test sync after app restart, on a slow network and when the server rejects a change.
32
SQL: how do you test that a primary key rejects duplicate values?
Show answer
-- Insert a row, then try the same key again; the second insert must fail
INSERT INTO users (id, email) VALUES (9001, 'a@test.com');
INSERT INTO users (id, email) VALUES (9001, 'b@test.com');
-- Expected: duplicate key or unique constraint error
SELECT COUNT(*) FROM users WHERE id = 9001;
-- Expected: 1
DELETE FROM users WHERE id = 9001;
33
How do you test database integrity using SQL?
Show answer
Verify inserted, updated and deleted rows match UI actions, check constraints, duplicates, NULLs and totals with COUNT and SUM queries.
34
What is network condition testing for mobile apps?
Show answer
It checks app behaviour on different networks: Wi-Fi, 4G, 5G, slow 2G or 3G, high latency, packet loss and no network. Also test switching between Wi-Fi and mobile data in the middle of an action, and airplane mode. The app should show loaders and clear offline messages, retry safely without duplicate actions and not freeze. Network throttling tools in developer options or proxy tools help simulate these conditions.
35
What is a blocker bug?
Show answer
A defect that stops testing or release of a feature because no workaround exists, so it is highest priority.
36
Why do performance reports use percentiles like p90 and p95 instead of averages?
Show answer
An average hides slow requests. If 90 requests take 1 second and 10 take 10 seconds, the average is 1.9 seconds, which looks fine, but one user in ten waits 10 seconds. The p95 value means 95 percent of requests were faster than it, so it shows what most users actually experience, including the slow tail. Service level targets are usually written as percentiles, such as p95 under 2 seconds.
37
What is integration testing and what are its approaches?
Show answer
Integration testing checks that modules or services work correctly together, focusing on interfaces and data flow. Approaches: big bang, where all modules are combined at once and testing is simple to plan but defects are hard to locate; top-down, where high-level modules are tested first using stubs for lower ones; bottom-up, using drivers for higher ones; and sandwich, which mixes both. Incremental approaches make it easier to find which interface failed.
38
Write SQL to verify an order was saved correctly.
Show answer
SELECT status, amount FROM orders WHERE order_id = 'ORD123';
-- compare with the UI, then check the matching rows in order_items
39
What is the difference between DELETE and TRUNCATE?
Show answer
DELETE removes selected rows and can be rolled back; TRUNCATE quickly removes all rows and resets the table.
40
What are implicit waits, explicit waits and auto-waiting?
Show answer
An implicit wait, in Selenium, sets a global time the driver keeps retrying to find any element before failing. An explicit wait waits for a specific condition, such as an element being clickable or a spinner disappearing, and is more precise. Auto-waiting, built into Playwright and Cypress, automatically waits for elements to be visible, enabled and stable before acting. Mixing implicit and explicit waits in Selenium can cause unpredictable delays.
Tips to crack the Jio Platforms Software Testing interview
- Learn telecom and 5G basics, as Jio develops parts of its 5G stack and network software in-house.
- Use MyJio and Jio apps and prepare suggestions or test ideas for their features.
- Read about Reliance's digital strategy and Jio's role in expanding mobile internet access in India.
- Keep a one-minute story ready for every project on your CV: problem, your part, tools, result.
- Practise the hard questions on this page aloud; Jio Platforms interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Jio Platforms Software Testing interview?
Candidates usually go through 4 stages: Online assessment (aptitude + technical); Technical interview; Managerial round; HR round. The exact rounds change with the role, team, location and your experience, so confirm the process with the recruiter.
Which topics should I prepare for the Jio Platforms Software Testing interview?
This practice set leans on Agile, SQL and API Testing (8), Bug Life Cycle and Jira (6), Test Case Design (5), Accessibility & Usability Testing (4). Revise those first, then practise explaining one or two of your own projects end to end, because most Jio Platforms interviewers ask you to walk through real work.
Are these the exact questions asked at Jio Platforms?
No. These are curated practice questions that match the skills and difficulty usually tested in telecom interviews like Jio Platforms's. They are not a leaked or verified list of past questions.
Where does Jio Platforms hire Software Testing professionals in India?
Jio Platforms has large teams in Navi Mumbai, Bengaluru, Hyderabad. Openings and locations change often, so check the Jio Platforms careers page and filter by city and experience.
Software Testing questions for similar companies
Telecom
Ericsson
Software Testing interview questions
Gurugram, Bengaluru, Chennai +2
View questionsIT services
Infosys
Software Testing interview questions
Bengaluru, Mysuru, Pune +2
View questionsIT services
TCS
Software Testing interview questions
Mumbai, Chennai, Pune +2
View questionsTelecom
Vodafone Idea
Software Testing interview questions
Mumbai, Pune
View questionsTelecom
Nokia
Software Testing interview questions
Bengaluru, Chennai, Noida +1
View questionsTelecom
Airtel
Software Testing interview questions
Gurugram, Bengaluru, Mumbai +1
View questionsMore ways to practise
Company-wise Software Testing questionsPackage-wise Software Testing questionsExperience-wise Software Testing questionsRole-wise Software Testing questionsCity-wise Software Testing questionsMost asked Software Testing questionsScenario-based questionsPractical / hands-on questionsHR & behavioural questionsSoftware Testing mock interviewOnline assessment questionsTechnical round questionsManagerial round questionsSoftware Testing topic sheets