The focus of this video is on one of the most pressing talent challenges organizations face today: how to identify, interview, and onboard truly professional business analysts - and how to tell them apart from candidates who simply look the part.

The session is structured in two parts. Part one establishes the context: what a business analyst actually is, what distinguishes a professional analyst from what can be called an "order taker," and why that distinction matters so much. Part two is the secret sauce itself - four key traits to look for, two essential interviewing techniques, and four red flags to watch for during the interview process.

Part One: Setting the Context

What Is a Business Analyst?

Using the International Institute of Business Analysis (IIBA) as the reference framework, the business analyst role encompasses a wide range of titles: business systems analyst, requirements engineer, process analyst, product owner, enterprise analyst, business architect, BI analyst, data scientist, and others. What ties all of these together is a focus on analyzing the business from a business perspective - not purely a technical one.

Per IIBA, business analysis is the practice of enabling change in an organizational context, refining needs, and recommending solutions that deliver value. The role of a great business analyst is to go in, understand the business, understand what drives value, assess the current state, envision what a future state could look like, and make well-grounded recommendations for business and systems requirements.

The value of that work, again per IIBA, includes the realization of benefits, avoidance of costs, identification of new opportunities, and an understanding of the capabilities the organization needs to move forward. The underlying imperative is clear: organizations cannot be static. Whether the initiative is reengineering, digital transformation, or an agility push, getting the requirements right is essential - and getting them right requires professional business analysts.

Professional Analyst vs. Order Taker

The single most important distinction to understand going into any BA interview is the difference between a professional analyst and an order taker. A useful way to think about it is the contrast between a fine dining server and a fast food counter worker.

The fast food counter worker engages the customer in a purely transactional way. The questions are basic: What do you want? What size? Can I supersize it? The role is essentially to act as a set of hands for the customer placing an order. That's fine - it's the right model for that context. But it is a superficial, transactional level of engagement.

The server at a fine dining restaurant operates at an entirely different level. They understand the menu deeply, they know what pairs well with what, they read the table, they ask thoughtful questions, and they create an engaging, personalized experience for their guests. That's a professional. It takes knowledge, judgment, and skill to do it well - not thirty minutes of training.

The order taker in business analysis does the equivalent of the fast food transaction. They sit with subject matter experts, ask what they want and what they need, compile a bullet list of wishes and gripes, and hand it off. They never get to the core of what the business actually needs or how it creates value.

The professional analyst digs in. They're curious. They probe. They facilitate. They model. They validate. And as a result, they surface requirements that actually move the business forward.

Why It Matters

The consequences of hiring an order taker into a business analyst role are significant and often underestimated:

Project deliverable risk. What the business stakeholders said they wanted, what they actually needed, and what ends up in production are frequently not the same thing. Superficial requirements gathering is the most common root cause of that disconnect.

Reputational damage. Over time, SMEs and stakeholders learn to dread engaging with order takers. The dynamic becomes: "Here comes an analyst — duck for cover." They know the interaction will produce a bullet list of vague requirements that nobody fully understands and that will result in a deliverable that misses the mark. When that reputation sets in, getting meaningful engagement from the business becomes even harder.

Lost engagement. A common complaint is that "the business people don't have time to engage." That's not the full story. Business people don't make time to engage with order takers — because they get nothing of value from the interaction. Put a professional analyst in the room, and that changes. When the analyst is asking the right questions, understanding the business, and helping stakeholders surface and articulate ideas that create real value, people engage.

At the core, the goal is not just to get requirements — it's to get the right requirements right.

Part Two: The Secret Sauce

Four Key Traits to Look For

1. Curiosity

If the candidate isn't genuinely curious about the world, the business, and the domain they'd be analyzing, they're going to struggle to surface deep requirements. The professional analyst is the person who isn't satisfied with stock answers. They dig in. They ask, "Tell me more about that. How did you get there? What's that related to? How does this add value?"

Questions to ask in the interview to surface this trait:

• "What did you learn about the business space in your current or previous role that you didn't know going in?" An order taker will struggle to answer this — because they never really learned the business. They just transacted with it. A professional analyst will have a list of things they discovered, found interesting, and wanted to understand more deeply.
• "Did you do any industry or domain research outside of your sessions with subject matter experts?" A professional analyst will have gone beyond what the SMEs told them. They'll have looked at industry publications, professional associations, competitive context. An order taker won't have thought to do that.

What to look for is enthusiasm and excitement in the candidate about learning new things — new business concepts, new ways problems get solved, new areas of a domain. That quality is usually unmistakable. You know it when you see it, and you know it when you don't.

2. Customer Engagement Skills

The ability to genuinely engage stakeholders — not just transactionally query them — is the second critical trait. A professional analyst is outward-facing. They don't just ask a set of scripted questions and record the answers; they conduct a conversation, they probe, they build on what's being said, they facilitate.

Ask the candidate: "How did you work with SMEs and stakeholders in your current or past role to elicit requirements? Walk me through what that looked like."

What you're listening for is whether the engagement was transactional (Q&A with a note-taker) or whether it was facilitated and dynamic — working in groups, on whiteboards, in workshop settings, surfacing things collaboratively. Most high-quality business analysis happens in facilitated workshops, not in one-on-one Q&A sessions.

A best practice tip: watch how the candidate engages you during the interview itself. If you ask a question and they simply answer it, and then you ask another question and they answer that, that's more of an order-taker pattern. If they take your question, build on it, explore it, and maybe turn it back with a clarifying question of their own — that's a more engaging, professional pattern. The interview itself is a live demonstration of how they'll work with your stakeholders.

3. Analytical Depth and Deliverables

The third trait is whether the candidate has actually done sophisticated analytical work — and whether they can show it. A strong indicator of a professional analyst is whether they create visual, model-based artifacts: process maps, activity diagrams, data models, use case diagrams, and similar structured work products.

An order taker typically produces bullet lists of shell statements: "The system shall do X. We need to change Y. We want Z." That type of deliverable is the output of transactional elicitation — it captures what people said, not what the business actually needs.

Ask the candidate: "Describe the types of artifacts and documents you create as a result of your work with SMEs and stakeholders."

If the answer is bullet lists, that's a clear signal. If the answer involves models, diagrams, and structured visual representations of business processes and data, that's a strong indicator of professional-level analysis.

Also probe for formal training and knowledge versus pure on-the-job experience. Someone who has been winging it without a framework, methodology, or body of knowledge to draw on tends toward order-taking. Someone who has invested in their craft — and continues to develop it — is trending toward professional. Importantly, being a professional analyst is not the same as being a senior analyst. It's possible to be a professional at any career stage — early, mid-level, or senior. What matters is the orientation: curious, outward-facing, engaged, and actively developing skills.

4. Business Acumen

The fourth trait is business acumen — a foundational understanding of how businesses work. This doesn't require an MBA. But it does require enough grounding in basic business concepts to provide context for analysis.

Without business acumen, the analyst can take input from subject matter experts but lacks the framework to understand what they're hearing, whether it adds value, or how it connects to other parts of the business. That context is not optional — it's what separates someone who can interpret requirements from someone who just records them.

Test for this directly in the interview. Ask the candidate to explain the difference between cost accounting and financial accounting. Ask them to describe the difference between an income statement and a balance sheet. Price versus cost. Fixed versus variable cost. Marketing versus sales. These are basic business concepts. If the candidate can't speak to them, they're going to struggle to engage stakeholders at the level the business needs.

The right mental model for a professional business analyst is that of an advocate for the business people — someone who looks at what those stakeholders do, what they need, and how their work can be made more effective and more efficient. That advocate role is simply not possible without business acumen.

Two Essential Interviewing Techniques

1. Let the Candidate Conduct the Interview

When a candidate is on-site (or in a live video session), identify a business scenario, process, or concept from your organization - one for which you have genuine subject matter expertise - and let the candidate run with it. Have them play the role of the business analyst. You play the SME. Let them ask the questions they would ask to understand and elicit requirements in that environment.

A skilled professional analyst doesn't need domain knowledge going in. The analytical framework - the ability to ask the right questions, understand context, probe for root causes and value drivers - is transferable across any domain. Watching how the candidate handles this exercise is far more revealing than any resume or interview question.

2. Require Deliverables in Real Time

Alongside the live elicitation exercise, have the candidate create some actual work products - even in a compressed, five-to-ten-minute window. It doesn't need to be polished. The point is to see what they naturally produce when they're doing analysis: Do they sketch a process flow? Start structuring a model? Or do they produce a bullet list?

This is one of the most powerful interview techniques available: it is very difficult to fake analytical skills when required to conduct a requirements session and produce deliverables in real time. You quickly find out what someone's actual capabilities are.

Four Red Flags

These are not automatic disqualifiers - think of them as orange flags that signal the need to probe deeper. Each one can represent a candidate who lacks the underlying business analysis skills, or one who simply hasn't been asked the right questions yet. Either way, they warrant a closer look.

1. Heavy reliance on Agile buzzwords. Agile is a valuable body of knowledge - no question. But if a candidate spends more time talking about burn charts, backlog grooming, and sprint ceremonies than about how they engage stakeholders, what artifacts they produce, and how they validate requirements, that's a concern. Agile terminology is not a substitute for business analysis substance.

2. Confusing project management with business analysis. Project management is also a legitimate and important discipline - managing timelines, dependencies, resource plans, and deliverables. But it is a different set of skills from business analysis. If a candidate's strongest talking points are about how well they can manage a project in Microsoft Project and track dependencies, that's a flag. The question is whether they can analyze, not just administer.

3. Support role experience vs. actual analysis experience. Listen carefully for whether the candidate has actually done analysis, or whether they've supported someone else doing it - scribing sessions, scheduling meetings, creating notes. Analysis support experience is valuable, but it's not the same as leading the elicitation, building the models, and driving the requirements. Be clear about which one you're looking at.

4. Technical solution focus vs. business analysis focus. When a candidate's natural frame of reference is the solution - the technology, the architecture, what was built - rather than the business problem and the requirements that shaped it, that's worth exploring. Technical people are smart and their perspective has value. But if the conversation keeps drifting toward the solution rather than the analysis, that's a signal to probe for whether the underlying business analysis skills are really there.

Putting It in Perspective

Recruiting professional business analysts involves a lot of moving parts: getting the right job descriptions written, sourcing candidates, screening and filtering, interviewing, credentialing, presenting offers, onboarding, skills development, and retention. Each of those stages matters.

The focus here is on the interviewing stage - giving interviewers a real edge when it counts. The four traits (curiosity, customer engagement, analytical depth, and business acumen), the two techniques (live elicitation and real-time deliverables), and the four red flags together form a framework that cuts through resume polish and surface-level interview performance to reveal whether a candidate is a genuine professional analyst or an order taker.

The consequences of getting it wrong are real: wasted project time, misaligned deliverables, frustrated stakeholders, and a business analysis function that never quite earns the trust it needs. The benefits of getting it right - validated, accurate requirements that drive breakthrough improvements - are equally real.

Learn More

Inteq Group offers management consulting services and a full suite of training programs in business systems analysis, business process management, business process reengineering, digital transformation, agentic AI, and organizational change management. Inteq also provides staffing services to help organizations source, vet, and onboard professional business analyst talent.

To explore Inteq's training courses or consulting and staffing services, visit inteqgroup.com.