Protiviti Business Analytics Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Protiviti hiring for Business Analytics roles
Protiviti is a global consulting firm that is a subsidiary of Robert Half. It specialises in internal audit, risk and compliance, technology consulting, cybersecurity, data analytics and business process improvement. In India it operates through a member firm and hires analysts and consultants for risk advisory, IT audit, security, finance transformation and technology implementation roles for clients across many sectors.
For Business Analytics roles, this Protiviti practice set focuses most on Stakeholder Communication (5), Product Analytics (5), Case Studies and Guesstimates (5), Excel for Business Analysts (5). It has 6 easy, 26 medium, 8 hard questions, so you can start easy and work up to the harder ones.
Company type
Consulting
Headquarters
Menlo Park, California, USA
Main India offices
Gurugram, Mumbai, Bengaluru, Hyderabad
Protiviti Business Analytics interview process
Resume screening or online assessment
Technical interview
Managerial round
HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for ProtivitiStart 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
You need to explain the results of a sales forecast model to a non-technical sales team. How do you do it?
Skip the formulas and talk about what drives the forecast, such as seasonality, past trend and pipeline, in plain words. Show one chart of actuals versus forecast with a range rather than a single number, and explain that the range reflects uncertainty. Translate it into their terms: what it means for their targets and stock. Invite questions and share an example of where it would be wrong.
02
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.
03
Your process diagram has grown to 80 shapes on one page and stakeholders say they cannot read it. What do you do?
Restructure it into levels. Create a high-level map with 7 to 10 main steps, then collapse detailed parts into sub-processes with their own diagrams. Move complex decision logic into a decision table rather than chains of gateways. Show the happy path first and handle exceptions in separate views. Use consistent naming in verb-noun form and remove duplicated steps. Finally, test readability by asking a stakeholder to explain the diagram back to you.
04
A product manager wants to stop an A/B test after three days because the variant is winning. What do you advise?
Advise against it. Checking results repeatedly and stopping at the first significant result inflates false positives, often far beyond the planned 5 percent. Three days also misses weekly patterns and novelty effects. Run the test for the pre-calculated sample size and duration. If speed is critical, the team can use a sequential testing method designed for early looks, but that must be planned before the test starts.
Check the refresh history error first: expired credentials, gateway offline, source schema change or timeout. Fix the quick cause and trigger a manual refresh. If it cannot be fixed in time, inform the stakeholders early, state the last refreshed date clearly on the report and share the key numbers from a direct query if needed. Afterwards add refresh failure alerts and a data-as-of label so it never surprises anyone.
07
A new TO-BE process went live three months ago. How do you prove that the improvement actually worked?
Compare against the baseline you measured before the change, using the same definitions: cycle time, first-time-right rate, cost per case, backlog and customer complaints. Pull data from system timestamps rather than surveys. Check that the gain is not explained by lower volumes or seasonality, ideally by comparing similar periods. Also check for side effects, such as faster processing but more rework downstream. Present the before-and-after with the business owner, and note where adoption is still incomplete.
08
How would you measure the success of a new feature?
Define a goal metric, a baseline and guardrail metrics, run an experiment or before-after comparison and review adoption, retention and revenue impact.
09
Stakeholders give conflicting requirements. What do you do?
Clarify the goal behind each request, map them to business objectives, prioritise with MoSCoW, run a joint session, then document the decision and get sign-off.
10
How would you analyse the declining sales of a retail store?
Use an extract with only the needed columns and rows, aggregated to the visible grain where possible. Replace quick filters showing all values with fewer filters, use context filters wisely and avoid 'only relevant values' on large fields. Move complex calculations into the data source, reduce marks per view and the number of sheets per dashboard. Use the Performance Recorder to find the slowest queries and fix those first.
13
Write a SQL query that shows revenue per region with one column per quarter.
SELECT region,
SUM(CASE WHEN EXTRACT(QUARTER FROM order_date) = 1 THEN amount ELSE 0 END) AS q1,
SUM(CASE WHEN EXTRACT(QUARTER FROM order_date) = 2 THEN amount ELSE 0 END) AS q2,
SUM(CASE WHEN EXTRACT(QUARTER FROM order_date) = 3 THEN amount ELSE 0 END) AS q3,
SUM(CASE WHEN EXTRACT(QUARTER FROM order_date) = 4 THEN amount ELSE 0 END) AS q4
FROM orders
WHERE EXTRACT(YEAR FROM order_date) = 2026
GROUP BY region;
14
How would you improve a company's low app conversion rate?
A RAID log tracks Risks, Assumptions, Issues and Dependencies for a project. Each entry has an ID, description, owner, impact, status, mitigation or action, and due date. A risk is something that may happen, an issue is something that has already happened, an assumption is believed true but unverified, and a dependency is something the project needs from others. A BA uses it to record requirement assumptions and dependencies, and reviews it weekly so nothing is silently forgotten.
16
Gross margin fell from 38 percent to 34 percent in one quarter. How do you investigate?
Break the change into drivers. Price: were discounts or promotions deeper? Mix: did sales shift towards lower-margin products, channels or regions? Cost: did raw material, freight or supplier prices rise, or did currency movements raise import costs? Also check one-offs like inventory write-offs and accounting reclassifications. Build a margin bridge showing how many percentage points each driver contributed, then take the biggest driver to the business owner with a specific action.
ROI (return on investment) is the gain from a specific investment divided by its cost and is used to judge projects or campaigns. ROE (return on equity) is net profit divided by shareholders' equity and shows the return to owners; high debt can inflate it. ROCE (return on capital employed) is EBIT divided by equity plus long-term debt and shows how efficiently all long-term capital is used. ROCE is better for comparing companies with different debt levels.
18
How do you calculate the percentage contribution of each category?
Top-down starts from a large known number, such as population or total industry size, and narrows it with percentages to the target segment. Bottom-up starts from a unit, such as one store's daily sales or one customer's purchase frequency, and multiplies up by the number of units. Top-down is fast; bottom-up is more grounded in operations. Doing both and comparing results is a strong sanity check.
20
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.
21
Write an Excel formula for the weighted average selling price across orders.
// B2:B200 = price per unit, C2:C200 = units sold
=SUMPRODUCT(B2:B200, C2:C200) / SUM(C2:C200)
// a simple AVERAGE(B2:B200) would wrongly give a small order
// the same weight as a large one
22
How do sample size and minimum detectable effect affect an A/B test design?
The minimum detectable effect is the smallest lift worth detecting, such as a 2 percent relative increase in conversion. Smaller effects, lower baseline rates and higher required power need much larger samples, roughly four times the users to detect half the effect. Calculate sample size before starting using the baseline rate, MDE, significance level and power, usually 80 percent, then fix the test duration and avoid stopping early.
23
Leadership wants to automate an invoice approval process with RPA. What do you check in the process model before agreeing?
Check that the process is stable, rule-based and high volume, with structured digital inputs. Look at the variant rate: if half the cases are exceptions handled by judgement, a bot will fail often. Verify that the underlying systems and screens will not change soon. Fix the process first, because automating a broken flow only makes errors faster. Finally estimate hours saved against bot build and maintenance cost, and define how exceptions get routed to people.
24
Your measure shows the same value on every row of a matrix. Why might that happen?
The filter from the row field is not reaching the fact table. Usually there is no relationship between that dimension and the fact, the relationship is inactive, or it filters in the wrong direction. It can also happen when the measure uses ALL or REMOVEFILTERS on that column, or when the row field comes from the fact table of a different grain. Check the model view and test the measure with a simple SUM.
MECE means Mutually Exclusive and Collectively Exhaustive. When you break a problem into parts, the parts should not overlap and together should cover every possibility. For example, profit splits into revenue and cost, and revenue into price times volume. A breakdown of customers into 'young' and 'students' is not MECE because they overlap. MECE structures prevent double counting and missed causes, which is what interviewers check.
26
What is the difference between Power BI Desktop, Power BI Service and Power BI Mobile?
Power BI Desktop is the free Windows app where you connect to data, model it, write DAX and design reports. Power BI Service is the cloud portal where you publish reports, schedule refresh, build dashboards, set permissions and share with users. Power BI Mobile is the phone app for viewing reports on the go. A typical flow is build in Desktop, publish to a Service workspace, and consume on web or mobile.
XLOOKUP can look left or right, uses exact match by default, returns a custom value if nothing is found and doesn't break when columns move. VLOOKUP only looks right and needs a column number.
28
Tell me about a time a SQL query you wrote gave wrong results. How did you catch it?
Situation: my weekly sales report showed a 12 percent jump that no one could explain. Task: verify the number before it reached leadership. Action: I compared row counts before and after each join and found a new promotions table had multiple rows per order, duplicating revenue. I aggregated promotions per order first and added a test comparing totals with the source. Result: the corrected report went out the same day, and I now check grain on every new join.
29
Describe a time your analysis found a cost-saving opportunity.
Situation: monthly cloud and software subscription costs had grown 35 percent in a year without anyone tracking why. Task: my manager asked me to review them. Action: I combined invoices with user login data in Excel and found 140 licences unused for over 90 days and two tools doing the same job. Result: we cancelled unused licences and consolidated tools, saving about 18 lakh rupees a year, and I set up a quarterly licence review report.
Log the change, assess impact on scope, cost and timeline, get approval through change control or backlog grooming, and update documents and stakeholders.
31
Tell me about a time you mapped a process and discovered a major inefficiency.
Situation: vendor onboarding at my company took around 18 days and procurement blamed finance. Task: I was asked to map the AS-IS process. Action: I interviewed five roles, traced 25 recent vendor records through system timestamps and built a swimlane map. It showed that bank details were collected twice and verified by two teams separately. Result: we merged the steps into one checklist at intake, cut onboarding to 9 days and reduced rework emails by about half.
32
How do you manage conflicting requirements from two senior stakeholders?
Clarify the underlying goals, present data and trade-offs, facilitate a joint session, escalate to the sponsor if needed and document the agreed decision.
33
Developers say a requirement is not technically feasible, but the business insists on it. How do you mediate?
Get to the underlying business goal behind the requirement, because the goal is often achievable in another way. Ask developers to explain the constraint and the cost of alternatives. Bring both sides together with options: a simpler version, a phased delivery, a manual workaround or a different design. Show effort, risk and value for each, and let the product owner or sponsor decide. Document the decision.
34
Guesstimate: how many pizzas are sold in Mumbai on a weekend?
About 20 million people, roughly 10% order pizza on a weekend, about 1 pizza per 2 people in an order. This gives roughly 1 million pizzas, adjusted for outlets and delivery capacity.
35
A feature was launched to all users at once without an A/B test. How would you measure its impact?
Use quasi-experimental methods. Compare before and after with enough history to account for trend and seasonality. If it rolled out at different times in regions or platforms, use difference-in-differences between early and late groups. Compare users who adopted with similar non-adopters using matching, while being careful about self-selection. For future launches, recommend keeping a small holdout group so impact can be measured cleanly.
36
Users in a shared Excel tracker keep typing region names with different spellings. How do you stop this?
Use Data Validation with a List rule. Keep the allowed regions in a separate sheet as an Excel Table, name it, and set the validation source to that range so the dropdown grows when you add a region. Turn on an error alert so free text is rejected. Then clean existing entries once with Find and Replace or a mapping lookup. For stronger control, protect the sheet and unlock only the input cells, so the list cannot be edited by mistake.
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
You receive two customer lists from sales and billing and must reconcile them. How do you do it?
Standardise both first: trim spaces, fix case, convert IDs to the same type and remove duplicates. Use a unique key like customer ID, or a combined key of phone and email if IDs differ. Then use XLOOKUP or COUNTIFS to mark each record as matched, only in sales or only in billing, or a Power Query merge with anti joins. Summarise mismatches by type and share the exception list with both owners.
39
You must gather requirements to replace a 15-year-old legacy system with no documentation. How do you approach it?
Combine several sources. Interview and observe users doing real tasks, and review screens, reports and outputs to infer business rules. Analyse the database and logs to see which data and functions are actually used. Work with long-serving staff and IT support for hidden rules and workarounds. Build AS-IS process maps, decide what to keep, drop or improve, and validate the findings with users. Plan data migration requirements early.
40
Guesstimate: how many weddings take place in India in a year?
Assume a population of about 144 crore and an average life expectancy of about 70 years, so roughly 2 crore people reach a typical marriage age each year. If about 95 percent of them marry at some point, that is around 1.9 crore people, or about 95 lakh weddings, since each wedding involves two people. A reasonable estimate is around 1 crore weddings per year, concentrated in the winter wedding season.
Tips to crack the Protiviti Business Analytics interview
Learn the basics of internal audit, risk management and controls, along with frameworks such as COSO for advisory interviews.
For technology consulting roles, revise cybersecurity basics, SQL and data visualisation, and mention any relevant certifications you are pursuing.
Practise explaining technical ideas in simple business language, since consultants often present findings to non-technical client stakeholders.
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; Protiviti interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Protiviti Business Analytics interview?
Candidates usually go through 4 stages: Resume screening or online assessment; 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 Protiviti Business Analytics interview?
This practice set leans on Stakeholder Communication (5), Product Analytics (5), Case Studies and Guesstimates (5), Excel for Business Analysts (5). Revise those first, then practise explaining one or two of your own projects end to end, because most Protiviti interviewers ask you to walk through real work.
Are these the exact questions asked at Protiviti?
No. These are curated practice questions that match the skills and difficulty usually tested in consulting interviews like Protiviti's. They are not a leaked or verified list of past questions.
Where does Protiviti hire Business Analytics professionals in India?
Protiviti has large teams in Gurugram, Mumbai, Bengaluru, Hyderabad. Openings and locations change often, so check the Protiviti careers page and filter by city and experience.
Business Analytics questions for similar companies