If you want a more nimble tech stack, small companies are where it's at -- the ones who don't have much to lose, who are often working on greenfield projects and have both the personnel and the lack of legacy baggage to be able to explore more modern stacks. But even then, you're probably just catching them at the start of a cycle, and if they survive 5-10 years, they'll probably be using an old (by then) tech stack.
I will say this: You can have a lot more sway about the stack once you're hired, especially if you're a full employee. I've convinced several companies to modernize their stacks only after working with them for a year or two, doing good work on their old (terrible) stacks, and then showing a demo of how much easier a new stack could be for the people involved. On the other hand, if I go in swinging during an interview and say "your stack sucks, I want to rewrite it right away" they'll never hire me. Makes sense, because I don't know their pain points and workflows yet; I'm not in a position to make that sort of judgment call from the outside.
Just my 2¢.