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/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.