IT Employment optimize

10 things you should know about hiring a business or systems analyst

Hiring the right business or systems analyst can be a tricky undertaking because the necessary skills and experience are often hard to define. Justin James offers some basic ways to help identify the best candidate for the job.

Business and systems analysts (BAs and SAs) fill an interesting role in IT organizations: They straddle the gap between the users and the IT department, taking an active role in the development of IT solutions without performing much of the hands-on work of the users or the IT team. BAs and SAs often catch a lot of heat from the IT department for "not knowing what we do," and users often point the finger at them when the IT department's solution is well executed but does not meet their needs.

Navigating this interaction between IT and users can be a huge challenge for BAs and SAs. But hiring someone to fill that job can be equally challenging. While technical know-how and experience are a big help, it can be difficult to determine what will be useful for the job and what won't. The same can be said for understanding the business end of things. Here are 10 tips and interview ideas to help you pick the best BA or SA candidate for the job.

Note: This article is also available as a PDF download.

1: Experience in an analyst role

There's nothing wrong with bringing in someone who is considered entry level for a particular job role. After all, that's how we all learn. But keep in mind that the "A" in "BA" and "SA" stands for analyst. No, that does not mean you are expected to lie on a couch and tell them your feelings. It means that they need to be able to examine the facts and information given to them, ask the right questions, perform research, and distill this mixture into a combination of documents, charts, workflows, technical specifications, and presentations. Even if your prospective BA or SA has never held this role before, he or she should be experienced in some sort of role that requires similar skills.

2: Experience in the right IT discipline

This may sound obvious, but there is a world of difference between a programmer and a system administrator and a desktop technician -- and the dozens of other IT job roles. Plenty of developers can't fix a PC and lots of system administrators know nothing about programming. Within the IT department, everyone knows the roles and what they do, but it's easy for those outside the IT department to lump them all together as "IT." Technical experience is helpful in a BA or SA candidate, but it's even more important that it be the right kind. Talk to the IT people who will be working with the BA or SA. Learn exactly what kind of work they will be doing and then look for candidates with that kind of background. A non-related IT history is helpful too, but it's not worth paying a premium for.

3: Internal candidates...

Every organization has some quirks in its process. These quirks are often handed down from one employee to another, never written down, and are lurking in the grass ready to surprise newcomers. Those who are already working for you know your organization, and this will give them a huge advantage in ramping up quickly and understanding the unique needs of your organization.

4: ...Versus outside perspective

Unfortunately, internal candidates are sometimes so experienced in the current process, they can't see the problems with it or areas for change. This is doubly true if they have had any kind of role in shaping the process as it currently stands. Just as we all think our own kids are the cutest kids on the planet, people who have a hand in the current process tend to think it makes perfect sense. Someone who is not familiar with the current way of doing things is much better able to see where improvements can be made.

5: The ability to document effectively

One of the biggest problems I see with some BAs and SAs is that you can talk to them and see that they know what is needed -- but they just can't get it out of their head and onto paper. I have seen too many process documents that were written by someone who couldn't write things in a fashion that could be followed. One of my favorite examples was a flowchart showing a process. Entire sections were completely orphaned (no way to get to them) and none of the "exit conditions" was reachable. Needless to say, this document wasn't worth the drive space it took up. During the interview, bring paper or a whiteboard and have candidates do some samples on the spot, such as creating a flowchart for a process. If they can't handle simple examples in the interview, it is likely that they will struggle on the job too.

6: Problem-solving skills

In the IT realm, it is common to see interviews where candidates are given a variety of brainteasers, math questions, and other tests of analytic capability. The BA and SA roles require similar abilities, albeit in a different area of knowledge. Some of the classic IT examples can be easily adapted (or even used as-is) to take out the technical knowledge and still test the analytic skills. For example, the classic river-crossing question is a great way of assessing someone's ability to solve problems.

7: Industry knowledge

All too often, the candidate whom people want to hire is simply impossible to find. The only person who fit the bill is the one who recently vacated the position. It's tempting to think that the ideal candidate has in depth knowledge of your industry and understands it completely. This is a trap. The fact is, that mindset greatly shrinks your candidate pool. By the time you find and hire the "right" person, you could have taught someone else how to do the job! That being said, there are some fields where industry knowledge is crucial, such as those that are highly regulated. But before you insist that your candidates have a ton of time in your industry, ask yourself whether that's truly needed or whether someone from a related or unrelated field would be fine as well.

8: Basic skills

I have been quite surprised by the lack of basic skills in many BAs and SAs I have worked with. By this I mean things like the ability to put together and conduct a presentation, use calendar systems to set up meetings properly, and understand Web conferencing software. These basic tools are the bread-and-butter of the BA and SA role. An "analyst" who can't use a spreadsheet to perform data analysis is about as useful as a carpenter who doesn't know how to use a hammer. Don't be ashamed to give prospective BA or SA candidates a simple computer literacy test to ensure that they can handle the job.

9: Self-directed and self-motivated attitude

These kinds of jobs typically require workers to guide themselves. It is up to them to get the right people in the room at the right time, to call others and get information, and so on. Someone who needs to be micromanaged to do these tasks -- or who does not know when to ask questions -- is not going to thrive. You will want to ask questions that evaluate how well they work on their own. Asking them to describe their typical workday will give you more useful information than asking them, "Are you able to manage yourself?"

10: Communication and people skills

Above all, the BA and SA role is about working with others to craft a solution to a problem. Someone who can't work well with others is not going to be effective. Ask your candidates to describe how they go about handling friction with others. Ask them to describe a conflict in the past. You're not looking at how they claimed they solved it as much as you're trying to get a handle on their ability to let the past be the past and to let business be business. The last thing you want is an analyst who holds grudges or turns differences of opinion on work-related issues into all-out war.

About

Justin James is the Lead Architect for Conigent.

9 comments
MikeAngelStar
MikeAngelStar

Most of the BA positions I see also require these skills. But there was no mention of them here. Are they not important?

leslie
leslie

While I agree that some of this is pretty basic, there seems to be one key piece missing. The ability to articulate the business value of projects/programs/enhancements that the IT organization works on. A truly strong analyst should be able to derive this metric oriented information and convey to all stakeholders the "why" of a work-effort.

leslie
leslie

While I agree that some of this is pretty basic, there seems to be one key piece missing. The ability to articulate the business value of projects/programs/enhancements that the IT organization works on. A truly strong analyst should be able to derive this metric oriented information and convey to all stakeholders the "why" of a work-effort.

kitico
kitico

Really? Maybe you have to post something on a deadline, but how can anybody in a hiring role get anything from this post? This post lacks perspective and depth. You should have talked to other senior people in wildly different environments than your current position to get a sense of how others view these roles and what makes a good hire. Once, years ago, I was talking with the head of the Internal Audit department at a major brokerage house where I was employed. He said that the best auditors he ever hired had no background in accounting or finance or audit. Amazing, isn't it. Similarly, I met a fellow some years ago who had no experience in programming and was beginning to tinker with HTML. He progressed quickly and became a systems architect and now has his own business. Don't rate experience or formal education too highly. Everybody start out with nothing.

bfrick76
bfrick76

Some organizations (like the one I am in) have a Business Systems Analyst role or BSA. I think all ten points raised in the post apply equally to this type of role. But even in this type of role I have found that the amount of B and S knowledge required (no pun intended) varies greatly depending on which group/function/project at hand. Great article! Great article!

ITTrainer2000
ITTrainer2000

Agree totally with these 10 while on the other hand, the hiring manager or party (IT group) need to know what they need and what they are looking for specifically to make a meaningful addition to their team. If they interview and give all their wants, the candidate can most likely talk to them and that's great. At the end of the day, when that BA or SA is hired, they need to be ready for what they have asked for. If they are behind their own curve and not ready for the experience that they asked for, they have simply wasted their time and budget as well as the newly hired BA or SA's time and career opportunity!

Englebert
Englebert

Whereas a SA is more IT centric with the responsibility of building/maintaining/supporting the SYSTEM, the BA does the same for the business. So, it's not entirely fair to lump them together. The BA s/b asked more Business type questions, the SA more tech type questions

Justin James
Justin James

You're right, they could definitely have been included here. Maybe I should have gone for a bonus 11th item. :) J.Ja

Justin James
Justin James

The article was actually written in response to a question from a reader who asked about both, but you are right that there should be some leaning in the appropriate direction based on the role. Thanks for bringing it up. J.Ja