Business analyst and management interviews test how you understand business problems, gather requirements, analyse data and drive decisions with stakeholders. These questions suit business analyst, MBA, project management, operations and product roles.
Fundamentals, definitions and simple scenarios. Good for freshers and warm-ups.
A business analyst bridges the business and the delivery team. They understand business problems, gather and document requirements (as BRDs, user stories and process flows), analyse processes and data to find improvements, help the team build the right solution, support testing and user acceptance, and measure whether the change achieved its goal.
SWOT is a framework for assessing a business or project. Strengths and Weaknesses are internal, such as a strong brand or high costs. Opportunities and Threats are external, such as a growing market or a new competitor or regulation. Its value comes from using the findings: building on strengths to seize opportunities, and fixing weaknesses that threats could exploit.
SMART goals are Specific, Measurable, Achievable, Relevant and Time-bound. "Improve sales" is vague; "Increase online sales in Maharashtra by 15% by 31 March through a new referral programme" is SMART, because everyone knows exactly what success looks like and when it will be checked.
Waterfall moves through phases in sequence (requirements, design, build, test, release) with scope fixed upfront, which suits projects with stable, well-understood requirements, such as regulatory work. Agile delivers in short iterations or sprints, gathers feedback frequently and adapts the plan, which suits projects where requirements are uncertain or likely to change. Many organisations use a hybrid.
Applied problems, trade-offs and questions about your own projects.
I identify the stakeholders, then use a mix of techniques: one-to-one interviews, workshops, observing how people currently work, reviewing existing documents and systems, surveys, and prototypes for early feedback. I write requirements as user stories or use cases with clear acceptance criteria, confirm them with stakeholders, and prioritise them, for example using MoSCoW (Must, Should, Could, Won't).
A user story describes a requirement from the user's point of view: "As a [type of user], I want [goal] so that [benefit]." A good story follows INVEST: Independent, Negotiable, Valuable, Estimable, Small and Testable. It comes with acceptance criteria, often written as Given / When / Then, which define exactly when the story is done.
The critical path is the longest chain of dependent tasks in a project, and it sets the shortest possible project duration. Tasks on the critical path have zero slack, so any delay to them delays the whole project, while other tasks have some float. Project managers focus monitoring and resources on critical-path tasks, and shorten the path by adding resources or running tasks in parallel.
A Key Performance Indicator is a measurable value that shows how well an objective is being achieved. Good KPIs are linked to goals, clearly defined and tracked over time. Examples are revenue growth, gross margin, customer acquisition cost, churn rate, Net Promoter Score, on-time delivery rate, inventory turnover and employee attrition.
System design, deep internals, leadership and tough follow-ups.
I prevent it with a clearly agreed scope baseline and a change control process. When a new request comes in, I log it, assess its impact on timeline, cost, resources and quality, and take it to the decision-makers with the trade-offs: add time or budget, or drop something else. Approved changes are added to the plan formally. The aim is not to refuse every change, but to make sure every change is a conscious decision.
I tie prioritisation to the business strategy and use a framework to keep it objective, such as RICE (Reach × Impact × Confidence ÷ Effort), MoSCoW, or a simple value-versus-effort matrix. I use data like usage analytics and customer feedback, consider dependencies and risks, and explain the reasoning to stakeholders so they understand what is not being done and why.
I would break revenue into price and volume, then split it by product, customer segment, region and channel to find where the drop is concentrated. I would separate new customers from existing ones (fewer new sales or more churn?). Then I would check internal causes, such as a price change, stock shortages, outages or a sales team change, and external ones, such as competitors, seasonality or the economy. With the root cause found, I would recommend specific actions.
I try to understand what drives them: their goals, concerns and pressures. I map stakeholders by influence and interest, and involve the difficult one early rather than surprising them. I keep communication regular and transparent, use data rather than opinions in disagreements, and look for shared goals. If we still cannot agree on something critical, I escalate respectfully with the options and their impact clearly laid out.