01
Severity vs priority — with an example.
Show answer
Severity = impact on the system. Priority = urgency to fix.
Logo misspelt on the homepage → low severity, high priority.
Crash in a rarely used report → high severity, low priority.
Airtel Software Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Airtel hiring for Software Testing roles
Bharti Airtel is an Indian telecom company providing mobile, broadband, DTH, enterprise connectivity and digital services such as Airtel Thanks and Airtel Payments Bank. Its digital and analytics teams work on network data, customer analytics and app development. It hires for software engineers, testers, network engineers and data professionals.
For Software Testing roles, this Airtel practice set focuses most on Database Testing (6), Agile, SQL and API Testing (5), Testing Types (4), Automation Basics for Manual Testers (4). It has 12 easy, 27 medium, 1 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Telecom
- Headquarters
- New Delhi, India
- Main India offices
- Gurugram, Bengaluru, Mumbai, Pune
Airtel 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 AirtelStart 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 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.
03
A hotfix build arrives and you have only 15 minutes before deployment. How do you sanity check it?
Show answer
Read the hotfix ticket to know exactly what changed. First verify the fix with the original reproduction steps and data. Then check the directly connected flows, for example if the fix is in coupon calculation, test applying, removing and paying with a coupon. Finish with a quick smoke of login and the main business flow. Report the result immediately, mentioning what was and was not covered.
04
How do you convert existing manual test cases into automated scripts?
Show answer
Pick a small set of stable, high-value regression cases first. Review each one: make steps precise, remove judgement-based checks and define clear expected results. Prepare test data that the script can create and clean up. Build reusable page objects and helpers for common steps like login. Automate, run several times to confirm stability, then link each script to its manual case ID and mark the manual case as automated.
05
How is back-end database testing different from front-end UI testing?
Show answer
UI testing checks what the user sees and does: screens, buttons, messages and flows. Database testing checks what happens underneath: whether the right rows are inserted, updated or deleted, whether constraints hold and whether data stays consistent across tables. A screen can show a success message while the database saved a wrong amount or nothing at all. So testers combine both, using SQL to confirm that every important UI action leaves the database in the expected state.
06
What is test monitoring and control?
Show answer
Test monitoring compares actual testing progress with the plan, using metrics like test cases executed, pass rate, open defects and effort spent. Test control is the action taken when monitoring shows a gap, such as re-prioritising tests, adding testers, changing the schedule or tightening entry criteria. For example, if half the time has passed but only a quarter of cases are executed, the lead must act and inform stakeholders.
07
What happens in the requirement analysis phase of STLC?
Show answer
In requirement analysis, the testing team studies the requirements to understand what needs to be tested. They identify testable requirements, clarify doubts with the business analyst or client, decide test types needed, note automation candidates and look at environment needs. The outputs are a list of questions, a requirement traceability matrix draft and an automation feasibility note. Problems found here are the cheapest to fix.
08
Why is orientation and screen size testing important?
Show answer
Mobile users have many screen sizes, resolutions, notches and foldable screens, and they rotate their phones. Rotation can recreate the screen and lose entered data if not handled. Test portrait and landscape on key screens, small and large phones and tablets, and check text does not cut off, buttons stay reachable and the keyboard does not hide input fields. Check entered form data survives rotation.
09
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.
10
How do you test location-based features in a mobile app?
Show answer
Test with location permission allowed, denied and approximate only. Use mock location tools to simulate different cities and moving routes. Verify the app shows nearby results correctly, updates location while moving and handles GPS turned off. Check accuracy indoors and with weak GPS, battery impact of continuous tracking and that background location is used only if needed and explained to the user.
11
What are suspension and resumption criteria in a test plan?
Show answer
Suspension criteria define when testing should be paused because continuing would waste effort, for example when a blocker bug stops the main flow, the build fails smoke testing or the environment is down. Resumption criteria define what must happen to restart, such as a new build that passes smoke testing or the environment restored. Writing these down avoids arguments and shows clearly why testing time was lost.
12
Write a basic Selenium test in Python that opens a page and checks its title.
Show answer
from selenium import webdriver
def test_home_title():
driver = webdriver.Chrome() # Selenium Manager finds the driver
try:
driver.get('https://qa.example.com')
assert 'Home' in driver.title
finally:
driver.quit()
13
A security scan says your login page can be loaded inside a frame on other sites. What is the risk and how do you confirm it?
Show answer
Clickjacking tricks a user into clicking something on your site while it is hidden inside a frame on an attacker's page, for example a hidden Transfer button under a fake Play button. A tester checks whether sensitive pages can be loaded in an iframe on another site, and inspects response headers for Content-Security-Policy frame-ancestors or X-Frame-Options set to DENY or SAMEORIGIN. If the page loads in the frame, log it.
14
A developer changed a shared header component used on every page. What testing do you plan?
Show answer
Retest the change itself, then run a focused regression on every page type that uses the header: home, listing, detail, checkout and account. Check navigation links, search, login and logout state, cart count and the mobile menu. Do cross-browser and responsive checks because layout changes affect all sizes. A quick visual comparison against the previous build helps spot alignment issues across many pages.
15
What is data masking and why is it used in test databases?
Show answer
Data masking replaces real sensitive values with realistic but fake ones, for example changing real phone numbers to valid-looking dummy numbers and real names to generated names. It lets teams test with production-like data volume and patterns without exposing customer information. It also supports compliance with India's Digital Personal Data Protection Act. Testers should check that masked data still passes validation rules and keeps relationships between tables intact.
16
What is the difference between path parameters, query parameters and the request body?
Show answer
Path parameters identify a specific resource and are part of the URL, as in /users/42. Query parameters filter, sort or paginate and come after a question mark, as in /users?city=Pune&page=2. The request body carries data for creating or updating, usually JSON, in POST, PUT or PATCH. Testers check invalid values in each: a wrong ID in the path, unknown query parameters and missing body fields.
17
What is localisation and internationalisation testing?
Show answer
Internationalisation tests that the product can support many languages and formats; localisation tests that a specific locale is correct for text, currency, date and layout.
18
SQL: how do you test a foreign key defined with ON DELETE CASCADE?
Show answer
-- Create a parent and child, delete the parent, child rows must disappear
INSERT INTO customers (id, name) VALUES (501, 'Cascade Test');
INSERT INTO orders (id, customer_id, total) VALUES (7001, 501, 250);
DELETE FROM customers WHERE id = 501;
SELECT COUNT(*) FROM orders WHERE customer_id = 501;
-- Expected: 0
-- Also test inserting an order for a non-existent customer: it must fail
19
What are test data and how do you prepare them?
Show answer
The inputs used in tests. Prepare using valid, invalid and boundary values from production-like but masked data, spreadsheets or generators.
20
Write a Postman test script that checks the status is 201 and the response contains an id.
Show answer
pm.test('Status is 201', function () {
pm.response.to.have.status(201);
});
pm.test('Response has id', function () {
const body = pm.response.json();
pm.expect(body).to.have.property('id');
pm.expect(body.id).to.be.a('number');
});
21
What are components, labels and fix versions in Jira?
Show answer
Components are fixed sub-parts of a project, such as Payments or Login, often with a default owner. Labels are free-text tags, such as regression or ui, that anyone can add for grouping. Fix version is the release in which the issue is planned to be fixed, while affects version is where the bug was found. Testers use these fields to filter bugs and to build release-wise reports.
22
How do you explain a technical bug to a non-technical stakeholder?
Show answer
Focus on impact, not internals. Say who is affected, what they cannot do, how often it happens and what it may cost, for example: 'About one in twenty users paying by UPI see a failure message even though money is debited, which will raise refund complaints.' Then give the options and a recommendation. Avoid jargon like null pointer or race condition unless asked. A short screen recording often helps.
23
How do you test battery and memory usage of a mobile app?
Show answer
Run typical user sessions on a real device and measure battery drain, CPU and memory with platform profiling tools or the device's battery statistics. Compare with the previous version. Look for background work continuing after the app is closed, GPS left on, frequent network polling and memory that keeps growing, which signals a leak. Test on low-RAM devices too, where the OS kills heavy apps quickly.
24
How do specification-based techniques differ from experience-based techniques?
Show answer
Specification-based (black box) techniques derive tests systematically from requirements: equivalence partitioning, boundary values, decision tables, state transitions and use cases. They give measurable coverage. Experience-based techniques rely on the tester's knowledge and intuition: error guessing, exploratory testing and checklist-based testing. They are good at finding defects the specification never mentioned. Strong testers use specification techniques for coverage and experience techniques to fill the gaps.
25
What is defect clustering?
Show answer
The observation that a small number of modules contain most defects, so testing should focus on those areas.
26
What is recovery testing?
Show answer
Recovery testing checks how well the system recovers from crashes, hardware failures, network loss or other failures. For example, kill the server during a file upload, or disconnect the network during payment, and verify the system restores a consistent state, does not lose or duplicate data and resumes or shows a clear message. It also measures recovery time against agreed targets, which matters for banking and healthcare systems.
27
What is visual regression testing in automation?
Show answer
Visual regression testing takes screenshots of pages or components and compares them with approved baseline images to detect unexpected layout, font, colour or spacing changes that functional assertions miss. When a difference crosses a threshold, a person reviews it and either accepts the new baseline or logs a bug. Dynamic content like dates and ads must be masked, and the same browser and screen size must be used to avoid noise.
28
SQL: find customers who placed more than three orders in the last 30 days.
Show answer
SELECT c.id, c.name, COUNT(o.id) AS order_count
FROM customers c
JOIN orders o ON o.customer_id = c.id
WHERE o.order_date >= CURRENT_DATE - INTERVAL '30' DAY
GROUP BY c.id, c.name
HAVING COUNT(o.id) > 3
ORDER BY order_count DESC;
29
Describe how you contributed in a sprint retrospective to improve quality.
Show answer
Model answer: Situation: our sprints kept ending with stories stuck in testing. Task: suggest a fix in the retrospective. Action: I showed that most stories reached QA in the last two days and proposed smaller stories, early test case sharing and developers deploying to QA daily. Result: the team tried it next sprint, and the number of stories carried over dropped from five to one.
30
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.
31
How do you break a requirement into testable conditions?
Show answer
Read the requirement and identify inputs, outputs, business rules, user roles and states. Turn each rule into a condition with an expected result, then add negative and boundary conditions. For example, 'users can withdraw up to 10,000 per day' becomes: withdraw below the limit, exactly at the limit, above the limit, multiple withdrawals adding up to the limit, and the limit resetting the next day. Each condition then becomes one or more test cases.
32
How do you test a web page using only the keyboard?
Show answer
Put the mouse away. Press Tab and Shift+Tab to move through every link, button and field, and check that the order is logical and the focus outline is always visible. Use Enter and Space to activate buttons and links, arrow keys for menus, radio groups and sliders, and Escape to close dialogs. Check that nothing traps focus, hidden items do not receive focus and a skip to main content link works.
33
Your test repository has many duplicate and outdated test cases. How do you clean it up?
Show answer
Export the cases and group them by module and requirement. Mark duplicates, merge them into one well-written case, and retire cases for removed features. Check which cases have not been executed or failed in months and confirm whether they are still valid. Link the remaining cases to requirements so gaps are visible. Do it module by module with peer review, and set a rule that every story update also updates its test cases.
34
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.
35
What is normalization and why should a tester understand it?
Show answer
Normalization organises tables to reduce duplicate data, for example storing the customer address once in a customers table instead of repeating it in every order. Testers should understand it because it explains where data lives and which joins are needed to verify a screen. It also shows risk: in a denormalized report table, the same value is copied in many places, so updates must be tested to confirm every copy changes.
36
What is WCAG and what are its conformance levels?
Show answer
WCAG, the Web Content Accessibility Guidelines from the W3C, is the main standard for making web content usable by people with disabilities. The current version is WCAG 2.2. It has three conformance levels: A is the minimum, AA is the usual legal and contract target, and AAA is the highest and rarely required for a whole site. Each level adds success criteria, such as colour contrast at AA.
37
SQL: find orders that have an order date in the future.
Show answer
-- Orders cannot be placed in the future
SELECT id, order_date, status
FROM orders
WHERE order_date > CURRENT_TIMESTAMP;
-- Expected result: no rows. If rows appear, check time zone handling and input validation.
38
What are the main testing differences between Android and iOS?
Show answer
Android has many manufacturers, screen sizes and OS versions with custom skins, so device fragmentation and background-kill behaviour need more coverage. iOS has fewer devices but strict permission, privacy and store review rules. Navigation differs: Android has a system back button or gesture, iOS relies on in-app navigation and swipe back. Notification, permission and file-access behaviours also differ, so test cases need platform-specific steps.
39
Why are stable locators like data-testid or roles preferred over position-based XPath?
Show answer
A position-based XPath such as /html/body/div[3]/div[2]/button breaks whenever a developer adds a wrapper div or reorders the layout, even though the feature still works. That creates false failures and maintenance work. Locators based on a dedicated data-testid attribute or the accessible role and name, like a button named Submit, stay valid through design changes and describe intent clearly. Testers should ask developers to add test IDs.
40
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;
Tips to crack the Airtel Software Testing interview
- Learn telecom basics like ARPU, churn, 4G and 5G networks, and broadband rollout for case discussions.
- Prepare analytics cases on reducing customer churn or improving network quality using data.
- Read about Airtel's digital products like Airtel Thanks and Xstream, and its enterprise business Airtel Business.
- 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; Airtel interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Airtel 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 Airtel Software Testing interview?
This practice set leans on Database Testing (6), Agile, SQL and API Testing (5), Testing Types (4), Automation Basics for Manual Testers (4). Revise those first, then practise explaining one or two of your own projects end to end, because most Airtel interviewers ask you to walk through real work.
Are these the exact questions asked at Airtel?
No. These are curated practice questions that match the skills and difficulty usually tested in telecom interviews like Airtel's. They are not a leaked or verified list of past questions.
Where does Airtel hire Software Testing professionals in India?
Airtel has large teams in Gurugram, Bengaluru, Mumbai, Pune. Openings and locations change often, so check the Airtel 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 questionsTelecom
Jio Platforms
Software Testing interview questions
Navi Mumbai, Bengaluru, Hyderabad
View questionsIT services
TCS
Software Testing interview questions
Mumbai, Chennai, Pune +2
View questionsTelecom
Vodafone Idea
Software Testing interview questions
Mumbai, Pune
View questionsIT services
Infosys
Software Testing interview questions
Bengaluru, Mysuru, Pune +2
View questionsTelecom
Nokia
Software Testing interview questions
Bengaluru, Chennai, Noida +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