I am fan of experimenting with different front end tooling, but when I was looking for a job a few years ago, I was explicitly told by one employer that I would have gotten the job if I had a couple of more years experience with react. And the interview wasn't even focused on react, it was mostly js and front end fundamentals.

I think I know why. We are using Blazor at my job, and everyone who worked on it before I was on the project was new to it. Recently they had us rework the front-end visually, so one of the senior developers took it upon herself to take full advantage and restructure the logic, it looks more like what I expect a React application to look like, and what I had hoped Blazor applications would look like structure wise. The best analogy I can come up with is think early 2000s PHP vs the most beautifully done OOP project you've ever seen or worked on, where everything is reasonably reusable.

If you can't look at a front-end component and grab the code, and pop it in literally anywhere else on your website, then you are doing React wrong, component driven development is insanely the best part of React that I dont know if people talk more about (I have not done React in a while).