Pros
How many companies actually invest in their stack instead of just piling onto it? Most of my career was spent in codebases that nobody wanted to own. Systems held together by institutional knowledge and optimism. Debugging things nobody had looked at in years because touching them felt risky. You normalize it after a while you forget what it's like to work in something clean. Coming to Trafilea was a reset. The architecture is thought through. Tooling decisions get made intentionally, not reactively. When something is introduced, there's usually a real reason behind it, and someone you can ask. That sounds like table stakes. It isn't. I've talked to enough engineers at enough companies to know that "we have a modern stack" can mean a lot of things, and what it means here is meaningfully better than average. If you've spent time fighting infrastructure you didn't build and can't change, this will feel like a different job category. The other thing worth saying: there's space to experiment. If you want to test a new approach and can make a reasonable case for it, you'll get room to try.
Cons
High expectations around technical reasoning may feel demanding for engineers used to reactive cultures