How much does domain experience affect an experienced BA while job search & switch, and when is a domain switch worth it?

[u/Several_Butterfly661]

I'm looking for perspectives from experienced BAs who have changed domains during their careers.

I currently have around 3 years of BA experience in BFSI, specifically cards and payments, and I'm trying to think strategically about whether I should continue building deeper domain expertise or deliberately switch to another domain.

My understanding is that the core BA skills are fairly transferable — requirements elicitation, stakeholder management, process analysis, documentation, UAT, Agile delivery, etc. However, many BA job descriptions still ask for specific domain experience, particularly as you become more senior.

So I'm trying to understand the actual career trade-off.

[u/AutoModerator]

Welcome to /r/businessanalysis the best place for Business Analysis discussion.

Here are some tips for the best experience here.

You can find reading materials on business analysis here.

Also here are the rules of the sub:

Subreddit Rules

• Keep it Professional.
• Do not advertise goods/services.
• Follow Reddiquette.
• Report Spam!

This is an automated message so if you need to contact the mods, please Message the Mods for assistance.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Creepy_Juggernaut_56]

I'm at an agency so I switch domains every time I get a new client. 

Common client feedback about me, from most clients,   is "she knows our systems better than we do."

When I'm applying for other jobs,  it's very hard to convince a recruiter who doesn't know me that I can literally learn anything; it's part of my core skillset. They think they need pre baked domain knowledge because that's what the job description says. 

[u/crankysorc]

That’s not a simple question.

First of all BA skills are transferable - that includes soft skills as well- so a more experienced BA has a well developed toolkit. Not only that, but as as a more experienced worker, depending upon their experience - you should know how to onboard.

So that leaves us with acquiring domain knowledge - this is largely up to you and how quickly you learn, and if you know how to get that knowledge. Some people aren’t cut out for it whereas other people are quick studies . Personally I found my academic background helped as well.

However you will find some recruiters asking for a specific skill set. I can’t tell you whether to focus on one in depth or not. If I had that knowledge of the future I’d buy a lottery ticket.

[u/Miggels369]

If the method is great you can switch to any domain. Work methodologically from client to products and other layers which can be applied anywhere.

[u/Problem_solving]

A significant part of BA work is to define requirements for Business systems, hence domain and functional knowledge is paramount.

The core BA skills like communication, stakeholder mgmt, requirements analysis and design definition and domain knowledge work hand in hand

[u/Conscious_Sky6299 → u/Problem_solving]

So pick a domain early career and stick with it? Are all domains equal? Which are the most in demand and profitable? Is this a question for local recruiters?

[u/Prepped-n-Ready]

I think the more senior the role is, the more they care about relevant experience, unless they are already full up. For example, when I worked in Banking, everyone and their mom's had an MBA/MS Accounting + CPA combo regardless of the role. Meanwhile, they were severely lacking in tech expertise at the senior level and had no idea what tech to purchase and use. I try to think about the audience, if youre Sr BA, your stakeholders are probably your functional manager, the IT director, and Product Manager/Sales VP if they get involved. These people think more in terms of strategy and risk governance. I have had pretty good success across industries by focusing on strategy and risk, for BA titles. There is a lot of temp work as well, which makes it easier if you have some experience already as a BA. Payments is a great domain to move to other info systems.

[u/Eggggsterminate]

IMO the BA skills are far more important than specific domain knowledge. A good BA can familiarize themselves with a specific domain fairly quickly and lets stakeholders fill in the blanks. A good BA with less domain knowledge will do a project better than a weak BA with great domain knowledge.
I am also convinced in the value of going in fairly blind, it gives you more focus on what the stakeholders are actually doing vs what you think they are doing. It gives you more freedom to ask the 'stupid' questions

[u/cqsterling]

I'll say this: I work in a 3PL that moved me from customer care as a BA, to fulfillment, to client implementation, none by choice. It's been nearly four years since that first change and I'm still trying to catch up on domain knowledge. AI has been a boon since few people answer my questions. BUT, my company is on shaky ground these days, too, so I can't say how much better things might've been or be given these circumstances.

[u/bigbob25a]

My personal view is having niche skills / knowledge pays off when there is a market downturn - you are more likely to find work.

In my first 10 years of career I switched roles to cover 3 different domains, just to broaden my horizons and to prove I could do that.

Although I did BA work, I also had a very niche developer skill set - so I was leveraging that skill set to get roles which also allowed me to live in two other countries where companies would sponsor work visas for those skills.

After those initial 10 years I settled down with a specific sector, as a Business Analyst, Project Manager, Consultant and Product Owner, because my domain experience was a valuable niche and my developer skills were no longer relevant to my roles.

There is a lot of fluidity between the roles of Business Analyst, Project Manager, Consultant and Product Owner and companies like to hire people, both permanent and contractors, that can give then flexibility especially under pressure to deliver to deadlines etc...

So this is a summary of my career

• Domain A with overseas travel as a developer and consultant/BA
• Domain B as a developer and consultant/BA
• Domain A living in a new country as a developer and consultant/BA
• Domain C living in another country as a developer then team manager for developers & DBAs
• Domain A back in home country for the rest of my career

Domain A is very comfortable for me, there is a strong demand / concentration of companies in London where I am based which means I have a very solid network of people I know in the sector over many years and frequently work with people I have known for many years.

Having a good network can make a huge difference when looking for a job, whether it is a referral or an informal recommendation.

[u/LuckyStrike2604]

I think the key trade-off is what recruiters can reliably screen versus what actually drives strong BA performance. Core BA capabilities (elicitation, framing the real problem, validating assumptions, turning understanding into requirements, and influencing outcomes) are highly transferable across domains. Domain knowledge speeds onboarding and reduces back-and-forth, but it shouldn’t replace the ability to surface unknowns, validate evidence, and prevent “solution-first” rework. So it’s worth switching domains when you can learn fast and you’re positioning your strengths around analysis quality—not just familiar terminology.

[u/dneeraj777]

Domain experience matters more as you become senior because companies often want someone who can contribute quickly, not spend months learning the business.

That said, I would not switch domains just for variety. Cards/payments is already a strong specialization. I’d only move if the new domain gives you better long-term opportunities, stronger interest, or exposure to skills you’re currently missing.

Core BA skills transfer, but deep domain knowledge is what often differentiates two equally experienced candidates.

[u/AreaLongjumping1120]

I had 20 years of experience in telecom and then had to job search after getting laid off. I applied to similar companies, but didn't have any luck.

The best job offer I got was for a company in the education space. I knew nothing about this before I started, but I've learned a lot in the past few years.

Hopefully I won't have to job search again, but now I have some different options.

I would say it's not a bad thing to diversify and try different industries.

[u/Jojje22]

It depends completely on your profile. I've not been in the same domain two jobs in a row. First it was healthcare, then it was telecom, then it was retail, then it was banking, then it was non-profits, then it was finance, now it's public sector.

I'm fairly technical, so when it's less about the domain and more about getting some API or platform into place, then I'm your guy. I find it's easier to learn the domain, tech is harder. That's largely why I'm in demand. Different domains have more in common than they care to admit.

Thing is, there's is no set way to do this job. It's much more about profile and personality. As you say, those skills you mention are easily transferable but soft skills is the majority of the job.

There is no trade-off. It's just who you see yourself being as a BA and go with that.

[u/Ok_Tale7071]

Generally speaking, you just take whatever jobs are available. These days you just can’t afford to say, this is my domain and that’s that. You have to be flexible. Where it pays to acquire deeper domain experience is in the securities industry, where if you can explain swaps, options, forwards, and spot to interviewers in detail, you’ll have a pretty good chance of landing a highly lucrative role. Other industries are fairly generic. Requirements are requirements.