Nubank

Amazing people at hand in Slack. You can reach the folks that wrote Clojure, Datomic, and the ones that created Nubank from the start to ask questions and learn from them.

Really hard to get promoted, its probably easier to quit, return a year later and apply to the next level and get hired.

Sometimes the priority is to show off your work than doing it, so a document that explains how to do something better (even if it's wrong) might be better for your career than make the thing better without much documentation.

For promotions, you're overly dependent on how your manager sells you, there's no way you can overcome a bad manager aside from changing teams.

The issue is that most tech managers are mid. Usually the ones that were engineers and did the work (and they were good engineers) and became managers because they didn't like their managers are the good ones.

Most tech managers (not all, but almost all) spend all their time in meetings pushing people to do things and document them so that they can align them with the OKRs and explain the status of things.

It's not adding value to the team itself, a good way is to somehow measure how would the team feel if the manager took a three month vacation, most engineers would not really notice aside from having more time due to less meetings. Would be nicer to define the goals based on the OKRs, not the other way around.