Happiest Minds Technologies Business Analytics Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Happiest Minds Technologies hiring for Business Analytics roles
Happiest Minds Technologies is a Bengaluru-based IT services company focused on digital transformation work such as product engineering, cloud, data analytics, cybersecurity and automation. It was founded by Ashok Soota and serves clients in edtech, retail, manufacturing and banking. In India it hires freshers and experienced professionals for development, testing, data and infrastructure roles, with an emphasis on digital skills.
For Business Analytics roles, this Happiest Minds Technologies practice set focuses most on Requirements and Agile (7), Excel for Business Analysts (6), SQL for Business Analysis (5), Case Studies and Guesstimates (4). It has 16 easy, 24 medium questions, so you can start easy and work up to the harder ones.
Company type
IT services
Headquarters
Bengaluru, India
Main India offices
Bengaluru, Noida
Happiest Minds Technologies Business Analytics interview process
Online assessment (aptitude + technical MCQs)
Coding test
Technical interview
Managerial or HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for Happiest Minds TechnologiesStart 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
What is the profit equation and how do you use it in cases?
Row-level security restricts which rows a user can see in the same report. In Desktop you create roles under Manage Roles with a DAX filter, such as 'Region'[Manager Email] = USERPRINCIPALNAME() for dynamic RLS. You test with View as Role, publish, and then map users or groups to roles in the Service. Dynamic RLS with a mapping table scales better than creating one static role per region.
A short requirement written as 'As a user, I want X so that Y', backed by acceptance criteria. Good stories follow INVEST: independent, negotiable, valuable, estimable, small and testable.
05
What is the difference between a report and a dashboard in Power BI Service?
A report is a multi-page, interactive view built in Power BI Desktop from one semantic model, with slicers, drill-through and cross-filtering. A dashboard is a single-page canvas in the Service made of tiles pinned from one or more reports, and is meant for monitoring key numbers at a glance. Dashboards support data alerts on card and KPI tiles, but have limited interactivity; clicking a tile opens the underlying report for detailed exploration.
Cycle time (lead time) is the total elapsed time from the start to the end of a case. Touch time is the time someone actually works on it. Process cycle efficiency is touch time divided by cycle time. Example: a refund takes 5 working days (40 working hours) end to end, but the agents spend only 2 hours in total working on it. Efficiency is 2 / 40 = 5 percent, so 95 percent of the time is waiting, and queues are the main target.
08
What does GROUP BY do and how is HAVING different from WHERE?
Log the change, assess impact on scope, cost and timeline, get approval through change control or backlog grooming, and update documents and stakeholders.
10
What is backlog refinement and what is the BA's role in it?
Backlog refinement, also called grooming, is a regular session where the team reviews upcoming backlog items to clarify, split, estimate and order them, so the next sprints have ready work. The BA prepares the stories in advance with business context, acceptance criteria, rules and examples, answers questions from developers and testers, and captures follow-ups. It is usually a short weekly session, not a sprint ceremony.
11
What is conditional formatting and how would you use it in a business report?
Conditional formatting changes a cell's look based on rules or formulas. In reports you can highlight targets missed in red, use data bars for sales size, colour scales for a region heatmap, icon sets for trend direction, or a formula rule like =$E2<$F2 to colour an entire row. Use it sparingly and with a legend so the eye goes only to the exceptions that need action.
AARRR breaks the customer lifecycle into five stages: Acquisition, how users find you; Activation, their first good experience; Retention, whether they come back; Referral, whether they recommend you; and Revenue, whether they pay. Each stage gets one or two metrics, such as sign-ups by channel, activation rate, Day-30 retention, invite rate and conversion to paid. It helps find which stage is the weakest bottleneck.
13
What is an index in a database and when can it hurt performance?
An index is a sorted lookup structure on one or more columns that lets the database find rows without scanning the whole table, much like a book index. It speeds up WHERE filters, joins and ORDER BY on those columns. It hurts when there are too many indexes, because every insert and update must maintain them, and it may not help on low-selectivity columns or when functions are applied to the indexed column.
14
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.
15
What is the difference between SQL and Excel for analysis?
Data storytelling combines data, visuals and narrative so the audience understands what happened, why, and what to do. A good story has context, a clear insight, supporting evidence in one or two simple charts and a recommendation. Accurate numbers alone rarely change decisions; people act when they see the implication. Remove chart clutter, highlight the key point with colour and use titles that state the conclusion.
The total profit expected from a customer over the relationship, roughly average margin x purchase frequency x lifespan, compared with acquisition cost.
18
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.
19
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.
20
Explain exclusive, parallel and inclusive gateways in BPMN.
An exclusive gateway (diamond with X) sends the flow down exactly one path based on a condition, for example approved or rejected. A parallel gateway (diamond with +) splits into all paths at once and, when joining, waits for every path to finish. An inclusive gateway (diamond with O) activates one or more paths whose conditions are true and joins only those that were activated. Choosing the wrong one causes deadlocks or duplicated work in automated processes.
21
What is the difference between release notes and a user manual?
Release notes describe what changed in a specific release: new features, enhancements, fixed defects, known issues and any actions users must take. They are short and version-specific. A user manual or user guide explains how to use the whole system to complete tasks, with step-by-step instructions and screenshots, and is updated as the product evolves. BAs often review both, because users rely on them in the first weeks after go-live.
A defect is logged as New with steps, expected and actual results, and evidence. It is reviewed in triage and moves to Open or Assigned, or to Rejected, Duplicate or Deferred. The developer fixes it and marks it Fixed or Ready for retest. The tester retests: if it passes it moves to Closed, and if not it is Reopened. Tracking status and age helps the UAT lead report readiness and spot defects stuck too long.
An epic is a large body of work that delivers a major business goal and spans several sprints, such as 'Online loan application'. It is broken into features or capabilities, such as 'Document upload'. Each feature is split into user stories small enough to finish in one sprint, such as 'As an applicant, I want to upload my PAN card photo so that I do not need to visit a branch'.
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.
27
Describe how you would model an employee leave approval process in BPMN.
Use one pool for the company with lanes for Employee, Manager and HR system. Start event: leave request submitted. Task: system checks leave balance. Exclusive gateway: balance sufficient? If no, end event that notifies the employee. If yes, user task: manager reviews. Add an interrupting timer boundary event of 3 days that escalates to the skip-level manager. Gateway: approved or rejected. Approved path updates the leave balance and calendar, then both paths notify the employee and end.
28
What is the difference between churn rate and retention rate?
Churn rate is the percentage of customers who leave in a period: customers lost divided by customers at the start. Retention rate is the percentage who stay, roughly 100 minus churn for the same cohort. If you start a month with 1,000 subscribers and 50 cancel, churn is 5 percent and retention 95 percent. Count new customers separately, otherwise growth hides churn. Revenue churn can differ from customer churn.
29
How do you calculate monthly revenue growth in SQL?
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.
31
An order has a value of 600 rupees, product cost 360, delivery 60, payment fee 12 and a discount of 50. What is the contribution margin?
Net revenue after discount is 600 minus 50, which is 550 rupees. Variable costs are 360 plus 60 plus 12, totalling 432. Contribution margin is 550 minus 432, so 118 rupees per order, or about 21 percent of net revenue. This is what each order contributes towards fixed costs such as salaries and rent. If the discount were raised to 150, the order would contribute only 18 rupees.
32
What is an issue tree and how does a hypothesis-driven approach work?
An issue tree breaks the main question into smaller, MECE sub-questions until each can be answered with data, such as 'why are profits down?' into revenue and cost branches. A hypothesis-driven approach starts with a likely answer, for example 'profit fell because delivery costs rose', and uses the tree to decide which data proves or disproves it first. It focuses effort and keeps the case structured and fast.
Operating expenses here exclude depreciation. Gross profit is 50 - 30 = 20 crore. EBITDA is gross profit minus operating expenses: 20 - 12 = 8 crore. EBITDA margin is 8 / 50 = 16 percent. EBIT is EBITDA minus depreciation, 8 - 2 = 6 crore, which is a 12 percent operating margin. In an interview, state your assumption about whether operating expenses include depreciation, because that changes the answer.
UAT sign-off is the formal acceptance by the business that the solution meets agreed requirements and is fit to go live, often with a list of known open defects and agreed workarounds. It should be given by the accountable business owner or product owner, not by the IT team or the BA. The BA prepares the evidence: test execution summary, defect status and traceability to requirements. Sign-off is recorded in writing, usually by email or in the test management tool.
36
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.
37
What is product analytics and how is it different from business reporting?
Product analytics studies how users behave inside a digital product, using event data such as sign-ups, clicks, feature use and purchases, to improve activation, engagement and retention. Business reporting usually summarises outcomes like revenue, cost and orders by period. Product analytics answers questions like where users drop off, which features retained users adopt, and whether a change worked, often through funnels, cohorts and experiments.
38
What do interviewers evaluate in a business case interview?
They assess how you think, not just the final answer. Key areas are clarifying the problem before solving, building a clear and MECE structure, handling numbers accurately with sanity checks, using business sense to prioritise, adapting to new information, and ending with a crisp recommendation with risks and next steps. Thinking aloud and communicating clearly matter as much as getting the right number.
39
Daily active users dropped 10 percent week over week. How do you investigate?
Rule out data issues first: tracking changes, app release bugs, pipeline delays or bot filters. Check whether the drop is seasonal by comparing with the same week last year or a festival calendar. Then segment by platform, app version, country or city, acquisition channel and new versus returning users to locate it. Look at the funnel for the core action. Connect findings to releases, outages or marketing changes, then recommend fixes.
40
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.
Tips to crack the Happiest Minds Technologies Business Analytics interview
Prepare one programming language deeply along with SQL, and be ready to write and explain small programs during the technical round.
Highlight any hands-on work in cloud, analytics, security or automation, since the company positions itself around digital-only services.
Read about the company's people-first culture and values so your answers on teamwork and learning sound genuine.
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; Happiest Minds Technologies interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Happiest Minds Technologies Business Analytics interview?
Candidates usually go through 4 stages: Online assessment (aptitude + technical MCQs); Coding test; Technical interview; Managerial or 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 Happiest Minds Technologies Business Analytics interview?
This practice set leans on Requirements and Agile (7), Excel for Business Analysts (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 Happiest Minds Technologies interviewers ask you to walk through real work.
Are these the exact questions asked at Happiest Minds Technologies?
No. These are curated practice questions that match the skills and difficulty usually tested in it services interviews like Happiest Minds Technologies's. They are not a leaked or verified list of past questions.
Where does Happiest Minds Technologies hire Business Analytics professionals in India?
Happiest Minds Technologies has large teams in Bengaluru, Noida. Openings and locations change often, so check the Happiest Minds Technologies careers page and filter by city and experience.
Business Analytics questions for similar companies