Focus on three areas: core BA skills (requirement gathering, writing user stories and BRDs, SQL basics, Agile ceremonies), domain knowledge for the industry you're applying to, and structured storytelling using the STAR method for project questions. Most interviews in India follow a pattern — introduction, scenario-based questions, and a technical or domain round — so prepare 3–4 detailed project stories and practise them out loud. A consistent business analyst interview preparation plan over 3–4 weeks, including mock interviews with someone from the industry, usually beats last-minute reading.

The most frequently asked ones include: What does a business analyst do? Explain the SDLC and your role in it. What is the difference between a BRD and an FRD? How do you gather requirements? How do you write a user story? Agile vs Waterfall? Basic SQL queries? And how did you handle a difficult stakeholder? For banking roles, expect domain questions on core banking and payments (UPI, NEFT, RTGS, SWIFT) and compliance topics like KYC. Instead of memorising answers, prepare a framework for each type of question so you can adapt it to your own projects.

Typically there are 3–4 rounds: an aptitude or screening round, a technical round (SQL, tools like JIRA, Visio, Excel), a scenario or case round, and a domain round, followed by HR. Topics usually cover requirements elicitation, documentation, prioritisation, user stories, UAT, and Agile ways of working. Freshers get more concept-based questions, while experienced candidates get deep-dives into real projects they have delivered.

Freshers are mostly asked fundamentals: the role of a business analyst, SDLC stages, Agile vs Waterfall, the difference between a use case and a user story, basic SQL, and why you want to become a BA. Scenario questions like "How would you handle a changing requirement?" are also common. Highlight transferable skills, internships, academic projects, and certifications such as ECBA to compensate for limited work experience.

At this level, interviewers test end-to-end project ownership — how you gathered requirements, managed difficult stakeholders, handled scope changes, wrote BRDs and user stories, and supported UAT. Expect deep dives into your domain, such as payments, lending, or core banking, and follow-up questions on outcomes and metrics. Prepare two or three projects in STAR format with quantified results, because almost every question will be traced back to something you actually did.

Structure every answer: take a second to understand what is being asked, state your assumptions, then respond using a framework — STAR for behavioural questions and a step-by-step approach for scenario questions. Use real examples from your projects with numbers wherever possible, and connect your answers to the interviewer's domain instead of giving textbook definitions. Practising aloud, ideally in mock interviews, helps you sound natural rather than rehearsed.

You will find plenty of free PDFs on job portals and training websites, but generic question banks rarely match a specific role — a fresher BA interview, an experienced BA interview, and a banking or payments domain interview all test different things. A better approach is to build your own answer bank from the job description, and supplement it with curated playbooks created by working BA mentors that cover domain-specific interview questions. Combine that with a few mock interviews and you'll be far better prepared than with a random PDF alone.

Start with a clear structure: contact details and LinkedIn, a short summary tailored to BA roles, key skills (requirement gathering, SQL, JIRA, Agile, domain expertise), work experience written as achievement bullets (action + task + result, with numbers), tools, certifications, and education. Mirror the keywords from each job description so your resume passes ATS screening, and keep it to one page if you have under three years of experience, two pages maximum otherwise.

It should be clean, ATS-friendly, and easy to scan in under 30 seconds: reverse-chronological order, no heavy graphics or tables, clear section headings, and bullets that start with action verbs and end with measurable outcomes. A simple business analyst resume template with sections for summary, skills, experience, tools, certifications, and education is a good starting point — just customise the content for every application rather than sending the same version everywhere.

Lead with education and certifications (ECBA, SQL, Excel, or data analysis courses), then create a strong projects section where you frame academic or internship work in BA terms — requirements you gathered, process flows you documented, data you analysed. Add transferable skills from any prior work, such as stakeholder communication or documentation. Keep it to one page, and quantify whatever you can, even in projects, to make it credible.

Core banking is the centralised backend system that connects all of a bank's branches and channels — branches, ATMs, net banking, mobile banking — to a single platform, so a customer can access accounts, deposits, loans, and payments in real time from anywhere. Popular core banking solutions used by Indian and global banks include Finacle (Infosys), Flexcube (Oracle), and Temenos T24. For aspiring business analysts, core banking basics are one of the most common topics in banking domain interviews.

All branches, ATMs, and digital channels of a bank connect to a central server or data centre. When a customer makes a transaction at any branch, the branch user's entry goes to the central system, which updates the account in real time so the balance reflects instantly everywhere. The system is organised into modules such as customer information (CIF), deposits, loans, payments, and the general ledger, with end-of-day batch jobs for interest accrual and reconciliation. Modern core banking software also exposes APIs so that UPI apps, fintechs, and third-party services can integrate with the bank.

Build a clear picture of the payments ecosystem: card flows (authorization, clearing, settlement), Indian rails like UPI, IMPS, NEFT, and RTGS, SWIFT for cross-border transfers, and concepts such as chargebacks, reconciliation, PCI-DSS, and fraud monitoring. Practise explaining end-to-end payment flows and failure scenarios out loud, because that is what domain rounds usually test. Using a structured resource such as a payment domain BA playbook, along with mock interviews with someone who has worked in banking, helps you cover the right depth in less time.