Juspay Business Analytics 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 Business Analytics 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 Business Analytics roles, this Juspay practice set focuses most on Excel for Business Analysts (7), Requirements and Agile (6), SQL for Business Analysis (5), Case Studies and Guesstimates (4). It has 3 easy, 28 medium, 9 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 Business Analytics 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
01
A manager says the dashboard total does not match the finance team's Excel sheet. What do you do?
First agree on the definition: date range, gross or net, tax, returns, currency and which date (order or invoice) is used. Then reconcile at a small grain, such as one month and one region, comparing row counts and sums between the source query and the sheet. Common causes are filters on the page, missing relationships, duplicate rows after a join or a late refresh. Document the agreed definition in the report tooltip.
02
What is the difference between Definition of Ready and Definition of Done?
Definition of Ready is a checklist a story must meet before the team pulls it into a sprint: clear description, acceptance criteria, dependencies identified, designs attached and estimated. Definition of Done is the checklist for calling work complete: coded, reviewed, tested, acceptance criteria passed, documented and deployable. The BA mostly drives readiness, while the whole team owns done. Both reduce rework and arguments at sprint end.
03
What is a business case document and what does it contain?
A business case justifies why an organisation should invest in a project. It usually contains the problem or opportunity, objectives and success measures, options considered including do nothing, costs and benefits of each option with a financial evaluation such as NPV and payback, risks and assumptions, impact on people and processes, a recommended option and an implementation timeline. A BA often builds it with finance, and it becomes the baseline for checking benefits after delivery.
04
Vendor A has a lower licence price, but Vendor B has lower running costs. How do you compare them?
Compare total cost of ownership over the same period, usually 3 to 5 years. Include licence or subscription fees, implementation, data migration, integration, training, internal staff time, infrastructure, support and upgrade costs, and exit costs. Discount the yearly totals to present value if the timing differs. Then weigh the result against non-cost factors such as fit to requirements, scalability and vendor stability. Often the cheaper licence ends up costlier once customisation and support are added.
05
Tell me about a time you led or mentored a team of analysts.
Situation: I led three junior analysts on a pricing review with a six-week deadline. Task: deliver quality work while developing them. Action: I split the work by workstream, set up short daily check-ins and a shared query library, reviewed their logic rather than rewriting it, and let each present their section to the client. Result: we delivered a week early, two juniors later handled client calls alone, and the review practice became standard in our team.
06
A bank's mobile app logins increased, but digital transactions fell. What could explain this?
Users are coming but not completing transactions, so look at the gap. Possible causes: a release that broke a payment flow, new security steps like extra OTPs adding friction, logins driven by balance checks or offers, or transactions shifting to another channel. Compare the funnel from login to transaction by app version and device, check failure and error rates, and review support complaints before recommending fixes.
07
Tell me about a time poor or outdated documentation caused a problem. How did you fix it?
Situation: a new developer built a GST calculation from an old FRD version, and the error was caught only in UAT. Task: fix the defect and prevent repeats. Action: I moved all requirement documents into one shared space with version history, added a change log and status labels such as draft or approved, and linked each user story to the latest approved section. Result: in the next two releases we had no defects caused by outdated specifications.
08
A lender is launching a new personal loan product. What KPIs would you set up?
Cover the full funnel and risk. Acquisition: applications, approval rate, cost per disbursed loan and time to disbursal. Value: disbursed amount, average ticket size and net interest margin. Risk: delinquency rates at 30 and 90 days past due by cohort, and early default rate. Customer: drop-off by application step, complaint rate and repeat borrowing. Track risk by monthly disbursal cohort, because defaults show up months later.
09
Split the epic 'Customers can track their order online' into user stories.
Possible stories: As a customer, I want to see my order status (placed, packed, shipped, delivered) so that I know its progress. As a customer, I want an SMS or email when the status changes so that I do not have to check. As a customer, I want the expected delivery date so that I can plan. As a customer, I want a courier tracking link once shipped. As support staff, I want to see the same timeline so that I can answer queries.
10
Managers want to click a region on a summary report page and jump to a detail page for only that region. How do you build it in Power BI?
Use drill-through. Create a detail page, add the Region field to the page's drill-through filter well, and design visuals for orders, products and trends. Power BI adds a back button automatically. On the summary page, users right-click a region and choose Drill through. Keep all filters on so date selections carry over. For guided navigation, you can also add buttons with bookmarks, but drill-through is the cleanest way to pass the selected region.
11
Write a SQL query for the top 3 products by revenue in each category.
WITH ranked AS (
SELECT category, product_id, SUM(amount) AS revenue,
DENSE_RANK() OVER (PARTITION BY category
ORDER BY SUM(amount) DESC) AS rk
FROM sales
GROUP BY category, product_id
)
SELECT category, product_id, revenue
FROM ranked
WHERE rk <= 3
ORDER BY category, rk;
12
Write SQL checks to validate a customer data migration between the legacy and new systems during UAT.
-- 1. Row counts should match
SELECT
(SELECT COUNT(*) FROM legacy.customers) AS legacy_rows,
(SELECT COUNT(*) FROM target.customers) AS target_rows;
-- 2. Records missing in the target
SELECT l.customer_id
FROM legacy.customers l
LEFT JOIN target.customers t ON t.customer_id = l.customer_id
WHERE t.customer_id IS NULL;
-- 3. Financial totals should reconcile
SELECT SUM(outstanding_balance) FROM legacy.customers;
SELECT SUM(outstanding_balance) FROM target.customers;
Start from the questions to answer: how many users discover it, use it and later buy saved items. Define events such as save_clicked, saved_item_viewed, saved_item_removed and saved_item_purchased, with properties like product ID, price, source screen and platform. Follow the existing naming convention, assign owners, review with developers, and test events in a staging build. Build the dashboard before launch so data is checked on day one.
15
What is the difference between absolute, relative and mixed cell references in Excel?
A relative reference like A1 shifts when the formula is copied. An absolute reference like $A$1 stays fixed, useful for a tax rate or target cell. A mixed reference fixes only the column ($A1) or only the row (A$1), which is handy in multiplication grids or when copying a formula across months and products. Press F4 to cycle through the four options while editing a formula.
16
A product line shows a loss after allocated overheads. Leadership wants to shut it down. How do you advise?
Separate contribution from allocation. If the product's revenue exceeds its variable and directly attributable fixed costs, it contributes to covering shared overheads, which will not disappear if it is closed and will be reallocated to other products. Check whether the overhead allocation key, such as revenue share, is fair. Also consider strategic links, like customers who buy it alongside profitable products. Recommend shutting it only if contribution is negative or the freed capacity has a better use.
17
Write a SQL query to get each customer's first order date and first order amount.
WITH ordered AS (
SELECT customer_id, order_date, amount,
ROW_NUMBER() OVER (PARTITION BY customer_id
ORDER BY order_date, order_id) AS rn
FROM orders
)
SELECT customer_id, order_date AS first_order_date,
amount AS first_order_amount
FROM ordered
WHERE rn = 1;
18
Write a SQL query for Day-7 retention by weekly sign-up cohort.
WITH cohort AS (
SELECT user_id, signup_date,
DATE_TRUNC('week', signup_date) AS cohort_week
FROM users
),
ret AS (
SELECT DISTINCT c.user_id
FROM cohort c
JOIN events e ON e.user_id = c.user_id
AND e.event_date = c.signup_date + INTERVAL '7 day'
)
SELECT c.cohort_week, COUNT(*) AS users,
ROUND(100.0 * COUNT(r.user_id) / COUNT(*), 1) AS d7_retention_pct
FROM cohort c
LEFT JOIN ret r ON r.user_id = c.user_id
GROUP BY c.cohort_week
ORDER BY c.cohort_week;
19
How would you forecast next quarter's sales in Excel?
-- late = delivered after the promised date
SELECT
city,
COUNT(*) AS total_orders,
SUM(CASE WHEN delivered_at > promised_at THEN 1 ELSE 0 END) AS late_orders,
ROUND(100.0 * SUM(CASE WHEN delivered_at > promised_at THEN 1 ELSE 0 END)
/ COUNT(*), 2) AS late_pct
FROM orders
WHERE status = 'DELIVERED'
GROUP BY city
ORDER BY late_pct DESC;
Value chain analysis breaks a business into the activities that create value: primary activities such as inbound logistics, operations, outbound logistics, marketing and sales, and service, plus support activities like procurement, technology, HR and infrastructure. For each activity you look at cost and differentiation. In cases it helps locate where costs are rising or where a competitive advantage can be built, for example in last-mile delivery.
22
In UAT cycle 2, a feature that passed in cycle 1 is now broken after a defect fix. What does this tell you and what should change?
It is a regression: the fix for one defect broke existing functionality, which usually means changes were not impact-analysed and there is no regression suite. Log it as a new high-priority defect linked to the fix. Agree with the team that every UAT build comes with release notes listing the changes, and that QA runs an automated or core manual regression pack before handing the build to business testers. Also add the broken flow to the UAT regression checklist.
23
Tell me about a time you said no to a stakeholder.
Situation: a regional manager wanted a custom report changed daily, which would have taken half my week. Task: support him without blocking other priorities. Action: I asked which decisions the report fed and found he needed only four numbers. I said no to the custom version, explained the impact on other work, and added those four metrics with a filter to the existing dashboard. Result: he got his numbers the same day and the team kept its capacity.
It means making sure stakeholders know realistically what will be delivered, when, and with what limits, before they form their own assumptions. A BA confirms scope in writing, states assumptions and dependencies, shares estimates with ranges, and flags risks early. When something changes, they update stakeholders immediately with options. Most stakeholder conflict comes from surprises, not from bad news itself.
26
The CEO wants one KPI to judge the customer support team. What would you propose?
A single KPI can be gamed, so I would propose one headline with guardrails. The headline could be first-contact resolution rate, because it reflects solving problems, not just closing tickets. Guardrails would be customer satisfaction score after the ticket and median first response time. I would also watch ticket volume per thousand orders, which shows whether product issues are falling. Review targets quarterly with the support head.
Both stack the results of two queries with the same number and type of columns. UNION removes duplicate rows, which needs a sort or hash step and is slower. UNION ALL keeps every row and is faster. Use UNION ALL when combining data such as online and store sales where duplicates are genuine or impossible, and UNION only when you specifically need a distinct list, such as unique customer IDs from two sources.
30
How do you estimate the annual revenue of a coffee shop chain?
Drive it from vehicles. Assume about 2 crore new two-wheelers are sold a year, each with an average of 1.5 helmets bought (rider plus pillion), giving 3 crore. The existing fleet is around 25 crore vehicles; assume 60 percent are active and each active vehicle replaces one helmet every 3 years: 15 crore / 3 = 5 crore. Total is about 8 crore helmets a year. Sanity check: enforcement varies by state, so give a range of 6 to 9 crore.
32
What is the difference between a sprint review and a sprint retrospective?
A sprint review is held at the end of the sprint with stakeholders to demonstrate completed work, gather feedback and adjust the backlog; it is about the product. A sprint retrospective is an internal team meeting afterwards to discuss what went well, what did not and what to improve in the way of working; it is about the process. The BA often helps demo stories in the review.
33
How would you decide whether to launch a new product?
Assess market size and demand, customer need, competition, unit economics, capabilities, risks and strategic fit, then test with a pilot before scale-up.
Not automatically. Find out why: the variant may push cheaper products, bigger discounts or smaller orders, so more people buy but each spends less. Check average order value, margin and long-term metrics like repeat purchase. Decide based on the metric tied to the business goal, usually revenue or contribution per user, which should have been the primary metric or a guardrail. Consider iterating to keep the conversion gain without lowering order value.
A model classifying features as basic, performance or delight attributes based on how they affect customer satisfaction, helping decide what to build first.
37
After many sprints, project documentation is out of date and new team members are confused. What do you do?
Identify which documents are actually used: usually a product overview, process maps, business rules, data dictionary and integration details. Update those first rather than everything. Make documentation part of the Definition of Done, so a story is not complete until related docs are updated. Keep living documents in a shared wiki with owners and last-reviewed dates, and archive outdated files clearly. Test the result by having a new joiner use it during onboarding.
38
What are dynamic array functions in Excel and how do they help analysts?
Dynamic array functions return several values that spill into neighbouring cells. UNIQUE lists distinct values, SORT and SORTBY order data, FILTER returns rows meeting conditions, SEQUENCE builds number series, and XLOOKUP can return whole rows. For example =SORT(UNIQUE(FILTER(Sales[Region], Sales[Year]=2026))) builds a live region list. They replace many helper columns and Ctrl+Shift+Enter array formulas, and the # operator references a full spill range.
39
Write an Excel formula for month-to-date sales up to today.
// Dates in Sales[Date], amounts in Sales[Amount]
=SUMIFS(Sales[Amount],
Sales[Date], ">=" & EOMONTH(TODAY(), -1) + 1,
Sales[Date], "<=" & TODAY())
// EOMONTH(TODAY(),-1)+1 gives the first day of the current month
40
Write non-functional requirements for an online payment page.
NFR-01 Performance: the payment page loads within 2 seconds for 95 percent of requests at 500 concurrent users. NFR-02 Availability: 99.9 percent monthly uptime outside planned maintenance. NFR-03 Security: card data is never stored by the application, and all traffic uses TLS 1.2 or higher. NFR-04 Compliance: the flow meets PCI DSS and RBI payment guidelines. NFR-05 Usability: works on mobile screens from 360 pixels wide. NFR-06 Audit: every transaction attempt is logged with a timestamp.
Tips to crack the Juspay Business Analytics 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 Business Analytics 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 Business Analytics interview?
This practice set leans on Excel for Business Analysts (7), Requirements and Agile (6), SQL for Business Analysis (5), Case Studies and Guesstimates (4). 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 Business Analytics 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.
Business Analytics questions for similar companies