Advertisements

Business Analyst Interview: Requirements, BPMN, Cases [EN]

Advertisements
business analyst interview questions | BA interview prep | BPMN | user stories | requirements | STAR method | scorecard
1
1/5
(96) Ratings
206 students
Created by PapaHR ★ 160K students: Courses in Human Resources, HR, SHRM, AI Talent Analytics, HRMS, HRIS, CIPD, Claude, HRCI, PHR, Rewards
Advertisements

What you'll learn

  • Tell a symptom from a problem out loud, which is what the interview tests
  • Answer with the problem-goal-constraint-metric frame instead of a tool list
  • Write user stories with acceptance criteria in the given-when-then form
  • Draw the minimum BPMN an interviewer expects, and read it back
  • Read the scorecard you are being marked against before you walk in
  • Answer with STAR and CARE so the interviewer can actually score you
  • Recognise when a question is testing a competency rather than knowledge
  • Explain how you handled conflicting requirements from two stakeholders
  • Negotiate salary, and ask the questions that tell you whether to accept
  • Learn alongside Mike’s 1.6 million students from 185 countries
This course includes:
17 total hours on-demand video
0 articles
0 downloadable resources
33 lessons
Full lifetime access
Access on mobile and TV
Certificate of completion
Advertisements

Course content

Requirements

  • An interest in business analyst roles. Prior experience helps but is not required
  • No certification needed. The analysis material is taught from the beginning
  • Two or three real work situations you can describe in detail
  • English at intermediate level or above, since all lessons are in English
  • Willingness to prepare examples rather than memorise definitions

Description

This course contains the use of artificial intelligence.

You listed the notations you know and the tools you have used. They were testing how you think, because notation takes a week to learn and thinking does not.

Two predictable ways this goes wrong

The first is answering with a toolkit. Asked about a difficult project, you describe the artefacts you produced rather than the decision you were actually facing, and the interviewer writes nothing down. The second is invisible: your answers are being scored against a table of behavioural indicators on a five-point anchored scale, drawn up before you were invited, and you have never seen one. So a perfectly true answer scores a two because it described a situation and never named a constraint or a measure. You reach the final round, you are told they went with someone else, and nobody explains which box stayed empty.

What this course covers

Thirty-three lessons in two halves. The craft first, because that is what gets probed: the analyst as a translator of business value, problem-driven against solution-driven thinking, telling a symptom from a problem, stating a business problem so it can be tested, the problem-goal-constraint-metric frame, stakeholder mapping and influence, elicitation techniques, asking the business the right question, handling requirements that contradict each other, prioritising by value against effort, the three types of requirement, user stories with their anti-patterns, acceptance criteria in the given-when-then form, use cases and requirement documents, as-is and to-be, the minimum necessary BPMN, finding bottlenecks, the system context diagram, functional decomposition, data objects and business rules, non-functional requirements, traceability, working inside Agile and sequential delivery, change requests and impact analysis, managing scope, and defending requirements to business and engineering at the same time. Then process description in its own right, from methodology and tooling through implementation and running a description project. Then the assessment machinery: what a scorecard is, why most hiring decisions are made within ten minutes, the halo effect, the intake meeting that produced your requirements, behavioural indicators and the anchored scale, competency libraries, profiling from top performers, behavioural, situational, panel and stress formats, STAR and CARE, how an interviewer detects an invented example, how soft skills get assessed, tests and cases, and how candidates are finally compared. Then the funnel: how vacancies arise, how a CV is read, the telephone screen, staying steady through a long search, asking for more money, and being found on the professional network.

Three blocks recorded for the hiring side

The scorecard, competency interview and screening blocks were recorded for the people doing the assessing rather than for candidates. That is the point. Those are the exact documents and procedures you are being marked against, and reading them from the other side of the table is the fastest way to understand your own scores — including why an honest answer can be marked down for a reason nobody will ever tell you.

Who is teaching this

I am Mike Pritula. I built the people system at Preply as it became a unicorn, and I have worked at Wargaming, iDeals and Alfa-Bank. More than 1.6 million students have enrolled in my courses across 185 countries, and over 150,000 specialists have gone through my programmes. I hold PHRi and SHRM-CP certifications and represent HRCI in more than ten countries.

What is included

  • Lifetime access to all 33 lessons

  • Active instructor support in the Q&A section

  • A Udemy Certificate of Completion

  • Working material: the problem-goal-constraint-metric frame, elicitation techniques, user story and acceptance criteria patterns, the minimum BPMN set, the system context diagram, the scorecard structure and anchored scale, competency libraries, STAR and CARE, the assessment matrix and the salary conversation

  • The interviewer’s toolkit in full, rather than a list of questions to memorise

Where to start

Take the last project you would describe in an interview and write down the constraint you were working against. If you reach for the tools instead, that is what this course fixes. Enrol now and start today.

Who this course is for:

  • Candidates with a business analyst interview booked
  • Support, testing and operations people moving into analysis
  • Analysts who reach the final round and do not receive the offer
  • Developers and project managers switching to a requirements role
  • Business analysts who have not interviewed in several years
  • People who know BPMN and freeze on behavioural questions
  • Anyone told “we went with someone else” without an explanation
Advertisements
PAPAHR_AUG_217406
Advertisements
Advertisements
Free Online Courses with Certificates
Logo
Register New Account