Pros
Rebilly is a truly distributed, asynchronous and diverse company. You can decide when (any timezone) and where (any place with internet) to work. There are few (and optional) meetings cause async communication and proceses work efficiently. Of course, there are challenges and adjustments because the company is always trying to be faithful to its teal principles and continuous improvement principles. Currently we were using Shape Up and RFCs to prioritise and divide work. There is a lot of freedom and opportunities to participate in the product definition and execution as the whole team can act as product managers. As a developer you shape up and choose the projects to work in each cycle, and it is very likely that you can work in the area that motivates you more.
Cons
Being autonomous and working asynchronously is not for everyone. There are quiet a few projects. Like in almost every successful company, some of them are quiet big and contain some technical debt. So you must like and be ready to balance new shiny features with parallel change and refactoring of old code. The good news is that there won't be a manager or boss stoping you from doing that but encouraging you to do it. If you convince the team that it is time to replace an old library or to refactor into a new pattern, that will be included in the cycle betting. If you prefer not to decide and just execute the plans of the team, that's also fine. The company is not forcing you to do what you don't like. It respects your mood, skills and personality.