01
What is use case testing?
Show answer
Designing tests from user flows described in use cases to verify complete real-world interactions.
Juspay Software Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Juspay hiring for Software Testing roles
Juspay is a Bengaluru-based payments technology company that builds payment orchestration, checkout and UPI infrastructure for merchants and banks. Its products help businesses manage multiple payment gateways and improve transaction success rates. It is known for using functional programming languages such as Haskell and PureScript, and hires software engineers and product engineers.
For Software Testing roles, this Juspay practice set focuses most on Test Case Design (7), Accessibility & Usability Testing (6), Agile, SQL and API Testing (5), STLC and Test Planning (5). It has 4 easy, 29 medium, 7 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Fintech
- Headquarters
- Bengaluru, India
- Main India offices
- Bengaluru
Juspay Software Testing interview process
- Online coding assessment or hackathon-style challenge
- Technical round 1 (problem solving)
- Technical round 2 (design or functional programming)
- Hiring manager and culture round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for JuspayStart 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
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;
03
What are the typical JIRA workflows for bugs?
Show answer
Statuses like To Do, In Progress, In Review, Ready for QA, Done and Reopened, with transitions that depend on the team's configuration.
04
As a QA lead, how do you measure the quality of test case design?
Show answer
Look at requirement coverage through the traceability matrix, the share of defects found by scripted tests versus exploratory testing or production, and defect leakage per module. Review samples for clear objectives, correct expected results and use of techniques like boundaries and negative cases. Track how many cases were updated or retired after changes. If many production bugs map to areas with passing tests, the design, not the execution, needs improvement.
05
How do you test an email notification feature?
Show answer
Trigger the email from each event, such as signup or order placed, and verify it arrives at the right address within the expected time. Check subject, sender name, personalised fields, amounts and links. Click every link and confirm it opens the right page. Check the layout on desktop and mobile mail apps, the unsubscribe option where required, and that no email is sent for failed or cancelled actions. Use a test mailbox tool in QA.
06
Write test cases for a file upload feature.
Show answer
Allowed and disallowed formats, size limits, empty file, duplicate names, special-character names, cancel upload, slow network and multiple files.
07
What do testers look for during a requirement review?
Show answer
Check that each requirement is clear, complete, consistent and testable. Look for vague words like fast or user-friendly, missing error handling, undefined limits, conflicting rules and missing roles or states. For each requirement ask how you would test it and what the expected result is. Record questions in a review log and get answers from the business analyst before writing test cases, so ambiguity does not turn into defects later.
08
Which accessibility laws and standards matter for products used in India and abroad?
Show answer
In India, the Rights of Persons with Disabilities Act 2016 requires accessible information and communication technology, and government sites follow the GIGW guidelines, which align with WCAG. Abroad, the US uses the ADA and Section 508, Europe uses EN 301 549, and the European Accessibility Act applies to many digital products and services from June 2025. Most of these point to WCAG AA as the practical testing target.
09
Design EP and BVA tests for a password that must be 8 to 16 characters and contain at least one digit.
Show answer
Length partitions: below 8 (invalid), 8 to 16 (valid), above 16 (invalid). Boundaries: 7, 8, 9, 15, 16 and 17 characters. Digit partitions: contains a digit (valid), no digit (invalid). Sample tests: 'abc1234' with 7 characters is rejected, 'abcdefg1' with 8 is accepted, a 16-character value with a digit is accepted, 17 characters is rejected, and 'abcdefgh' with no digit is rejected. Also test empty input and spaces.
10
What is mobile app testing and what extra checks does it need?
Show answer
Test on real devices and OS versions, interrupts such as calls, battery, network changes, gestures, permissions and app store guidelines.
11
What is a test environment?
Show answer
The hardware, software, data and configuration where testing happens, set up to mirror production as closely as practical.
12
An automated test passes on your laptop but fails in the CI pipeline. How do you troubleshoot?
Show answer
Check the CI logs, screenshots, video or trace to see exactly where it failed. Then compare the environments: headless versus headed browser, screen size, browser version, time zone, environment URLs and secrets, test data and network speed. Run the test locally in headless mode with the CI settings. Common causes are timing, missing data in the CI environment and tests depending on run order. Fix the cause, not with a sleep.
13
What goes into a test plan?
Show answer
Scope (in and out), objectives, approach, environments, schedule, roles, entry/exit criteria, risks and mitigation, deliverables and tools.
14
How do you test a country dropdown that controls a dependent state dropdown?
Show answer
Check the state list is empty or disabled until a country is selected. Select a country and verify the correct states load. Change the country and confirm the old state selection is cleared and the new list loads. Test countries with no states, a long list with scrolling and search, and default values on page load. Submit the form and verify the saved values, then reload and check both dropdowns keep the saved selection.
15
What is the difference between a test suite and a test run?
Show answer
A suite is a collection of related test cases; a run is one execution of a set of tests against a build.
16
SQL: find orders that have no matching customer record.
Show answer
-- orphan orders indicate a broken foreign key or bad data load
SELECT o.order_id, o.customer_id
FROM orders o
LEFT JOIN customers c ON c.customer_id = o.customer_id
WHERE c.customer_id IS NULL;
17
A CAPTCHA on the signup page blocks screen reader users. What do you recommend?
Show answer
Log it as a high-severity accessibility bug because it fully blocks a group of users from signing up. An image-only CAPTCHA fails WCAG unless an alternative is offered. Recommend options such as invisible or risk-based bot checks, an email or OTP verification step, an audio alternative plus another modality, and rate limiting on the server. Retest the full signup with NVDA and TalkBack after the change.
18
The developer says "it's not a bug". What do you do?
Show answer
Re-check the requirement, reproduce with clear steps and evidence (screenshots, logs), discuss with the BA/PO and record the final decision.
19
What automated accessibility tools exist and what are their limits?
Show answer
Common tools are axe DevTools, Lighthouse in Chrome, WAVE and accessibility linters in CI. They quickly catch missing alt text, low contrast, missing labels and invalid ARIA. Their limit is that they find only roughly a third of WCAG issues. They cannot judge whether alt text is meaningful, focus order is logical, error messages make sense or a custom widget works with a screen reader, so manual testing is still required.
20
What does Won't Fix mean and who decides it?
Show answer
Won't Fix means the bug is acknowledged as real, but the team decides not to fix it, usually because the impact is very low, the feature is being retired or the cost of fixing is higher than the benefit. The decision is made by the product owner, often in triage with dev and QA leads. The tester should make sure the reason is recorded and, if user-facing, documented as a known issue.
21
How do you decide the priority of test cases?
Show answer
By business criticality, usage frequency, defect history, risk and dependencies, running high-priority cases first.
22
What is compliance testing?
Show answer
Compliance testing checks that software meets external laws, standards or internal policies, not just functional requirements. Examples include payment security standards for card data, data protection rules for personal data, accessibility guidelines and RBI rules for banking apps. Testers verify items such as consent capture, data retention, audit logs and masking. Findings are usually documented as evidence for auditors, so traceability and clear records matter as much as the tests.
23
How do you test session management in a web application?
Show answer
Check that a new session ID is created after login, and that the session expires after the defined idle time. Verify logout invalidates the session on the server, so pressing back or reusing the old cookie does not work. Check that cookies use Secure, HttpOnly and SameSite flags. Test concurrent logins if they are limited, and that changing the password ends other sessions. Session IDs must not appear in URLs.
24
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.
25
A client needs WCAG 2.2 AA compliance before launch in two weeks. How do you plan the testing?
Show answer
Agree on scope: key user journeys and page templates, not every page. Day one, run automated scans on all templates to fix easy issues fast. Then do manual checks of each journey with keyboard, NVDA, VoiceOver on mobile, zoom and contrast. Log issues with WCAG references and severity, and get blockers fixed first. Retest fixes and deliver a conformance summary with known issues. Be honest if full compliance is not realistic.
26
A security reviewer asks you to confirm that passwords and personal data are stored safely. What do you check in the database?
Show answer
Query the users table after signup and confirm the password is not stored in plain text or reversible encoding, but as a salted hash from a slow algorithm such as bcrypt or Argon2. Two users with the same password should have different hashes. Check that card numbers are not stored at all or are tokenised, that personal data like Aadhaar numbers is masked or encrypted, and that logs and audit tables do not copy the raw values.
27
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.
28
What is think time in performance testing?
Show answer
Think time is the pause a real user takes between actions, such as reading a product page before adding it to the cart. Performance scripts add think time, often with random variation, so virtual users behave realistically. Without think time, a few virtual users generate a load equal to many real users, which gives misleading results. Think time values are usually taken from analytics or production logs.
29
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
30
During a load test, some booking requests fail with a 'deadlock detected' error. What is happening and how do you report it?
Show answer
A deadlock happens when two transactions each hold a lock the other needs, so neither can continue. The database detects it and kills one transaction with an error. During testing it usually appears under concurrent load, for example two users booking the last seats at once, as random failures or 'deadlock detected' entries in logs. Testers report the exact actions and timing, and developers fix it with consistent lock order or shorter transactions.
31
Write a simple Playwright test in TypeScript that logs in and checks the dashboard heading.
Show answer
import { test, expect } from '@playwright/test';
test('valid user can log in', async ({ page }) => {
await page.goto('https://qa.example.com/login');
await page.getByLabel('Email').fill('qa.user@test.com');
await page.getByLabel('Password').fill('Secret@123');
await page.getByRole('button', { name: 'Login' }).click();
await expect(page.getByRole('heading', { name: 'Dashboard' })).toBeVisible();
});
32
What sensitive data checks do you do in API responses and logs?
Show answer
Check that responses return only needed fields, with no passwords, password hashes, full card numbers, full ID numbers or internal keys. Verify personal data is masked where required, for example only the last four digits of a phone number. Look at application and browser console logs for tokens or personal data. Check error responses do not expose stack traces, SQL or server versions. Raise any leak as a high-severity bug.
33
What is SDLC and STLC?
Show answer
SDLC is the full software development life cycle; STLC is the testing life cycle: requirement analysis, test planning, test design, environment setup, execution and closure.
34
What is Appium at a high level?
Show answer
Appium is an open-source tool for automating native, hybrid and mobile web apps on Android and iOS using the WebDriver protocol. Tests can be written in Java, Python, JavaScript and other languages, and it uses platform drivers such as UiAutomator2 for Android and XCUITest for iOS. It can run on emulators, simulators, real devices and cloud device farms. Stable accessibility IDs make the best locators for it.
35
How do you test a REST API that is not ready yet?
Show answer
Use mocks or stubs from the API contract such as Swagger, write test cases early and validate again when the real service is available.
36
How do you test zoom, text resizing and reflow?
Show answer
Set browser zoom to 200 percent and check that all text is readable and no content or buttons are cut off. Then zoom to 400 percent, or use a 1280 pixel wide window, which gives a 320 CSS pixel viewport; content should reflow into one column without horizontal scrolling, except for things like data tables and maps. Also increase text spacing and the operating system font size to check that labels do not overlap.
37
A screen reader announces 'button, button, button' on a toolbar. What is the bug and how do you report it?
Show answer
The toolbar uses icon-only buttons without accessible names, so users hear the role but not the purpose. Report it with the page, the screen reader and browser versions, the exact announcement and the expected one, such as 'Bold, toggle button, not pressed'. Reference WCAG 4.1.2 Name, Role, Value. The fix is an aria-label or visually hidden text on each button, plus a tooltip that also helps sighted users.
38
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.
39
What is the difference between statement coverage and branch coverage?
Show answer
Statement coverage measures the percentage of code statements executed by tests. Branch coverage measures whether every decision outcome, true and false, has been executed. Branch coverage is stronger: for 'if (amount > 1000) applyDiscount()', one test with 1500 gives 100 percent statement coverage, but you need a second test with 500 to cover the false branch. 100 percent branch coverage implies 100 percent statement coverage, not the other way round.
40
What is UAT?
Show answer
User Acceptance Testing — end users or the client verify that the system meets business needs in a production-like environment before go-live.
Tips to crack the Juspay Software Testing interview
- Practise DSA problems seriously, since Juspay hiring challenges are known to be competitive and focused on problem-solving ability.
- Learn functional programming basics like immutability, pure functions and recursion, and try a little Haskell or PureScript.
- Understand UPI and card payment flows, including authorisation and settlement, to discuss the domain with confidence.
- 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; Juspay interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Juspay Software Testing interview?
Candidates usually go through 4 stages: Online coding assessment or hackathon-style challenge; Technical round 1 (problem solving); Technical round 2 (design or functional programming); Hiring manager and culture 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 Juspay Software Testing interview?
This practice set leans on Test Case Design (7), Accessibility & Usability Testing (6), Agile, SQL and API Testing (5), STLC and Test Planning (5). Revise those first, then practise explaining one or two of your own projects end to end, because most Juspay interviewers ask you to walk through real work.
Are these the exact questions asked at Juspay?
No. These are curated practice questions that match the skills and difficulty usually tested in fintech interviews like Juspay's. They are not a leaked or verified list of past questions.
Where does Juspay hire Software Testing professionals in India?
Juspay has large teams in Bengaluru. Openings and locations change often, so check the Juspay careers page and filter by city and experience.
Software Testing questions for similar companies
Fintech
DE Shaw
Software Testing interview questions
Hyderabad, Bengaluru, Gurugram
View questionsFintech
Mastercard
Software Testing interview questions
Pune, Vadodara, Gurugram +1
View questionsFintech
PayPal
Software Testing interview questions
Chennai, Bengaluru, Hyderabad
View questionsFintech
Pine Labs
Software Testing interview questions
Noida, Bengaluru
View questionsFintech
Razorpay
Software Testing interview questions
Bengaluru, Mumbai
View questionsFintech
Stripe
Software Testing interview questions
Bengaluru
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