I'll take a slightly contrarian point of view: it probably depends on whether they're talking about a technology or a specific system/process.
If they want you to become a SME on JQuery, or on .NET Generics, or on Git, or on SQL table performance? Then what they're really saying is, "We like having someone around that knows this particular technology inside and out, and we can have people use them as a resource when they're working with that technology." For instance, we'd love to get a Git subject matter expert... because right now, our group sucks with it (we barely manage to scrape by.)
But if they want you to become the SME on 'How the logger system works' or 'The code behind the Flooby system' or 'How to clear errors from the batch process'? Then... yeah, there's a decent chance they're silo'izing to at least some extent. Because if they want someone to the level of a "subject matter expert" on a specific process like that, it probably means they intend for that person to do most of the troubleshooting/maintenance on it.
And... as sad as it is, I'd actually imagine the second being the more likely scenario (but this is just a personal guess on my part, and could be wildly off base.) I mean, there are good companies that recognize the benefit of SME on technologies... but there are bad companies that silo'ize their projects. And it's more likely the latter would make a point of asking about SME in the interview than the former.
Anyway, like other answers said: ask 'em. Interviews are also meant for you to interview them, to figure out if you want to work there. If you have a concern, figure out a way of asking questions that will either confirm or alleviate that fear.