Wise

You work on things at scale. Many of the challenges that smaller companies are afraid of wasting their time on, or over-optimizing for, are crucial here.

You're trusted to do your work independently and are given support when you ask for it.

Engineers (and all team members!) are completely involved and relied upon during project planning – so you always have a say in what your team will work on.

• Flexible remote working policy (e.g., expecting a delivery at home today, traveling, etc.)
• Travel opportunities to work with teammates or cross-teammates from other offices.

There is a chance some of your work will be on legacy code (Java 8, Groovy, Grails, Angular 1.x), but this is quickly changing. As of late 2019, many services have upgraded to newer Java (11+) and/or the latest frameworks (React, Spring).

Fragmented frontend code. TW has taken a "microservices for frontend" approach, which is more difficult to work with versus the ease of developing a true SPA.

Team structure happens organically. This makes sense to those involved but looks quite strange to anyone trying to understand where to go for specific help. Sometimes it is very obvious, and other times it is not.

Too much information. There are hundreds, if not thousands, of nontrivial initiatives going on at once. Keeping abreast is challenging, but somewhat expected of you to a degree.

Training should not stop at onboarding or be completely left up to the individual teams.

A formal plan for keeping engineers at above a particular level of competency would work wonders, especially as internal tooling, libraries, and best practices are created.