Pros
CiBO has a strong cultural commitment to multidisciplinary solutions (truly fusing the approaches from many diverse disciplines: math/stats/Bayesian/functional programming/software engineering/plant science...), team work, learning and development, and transparency. At the end of the day, that culture trumps process and structure and moves us forward together.
We have a very unique business model for a software company that let's us be tightly integrated with our customers to truly understand their needs and ensure that our software is solving their issues.
CiBO has a very high % of very senior developers (10-15yr+ and 25yr+) that changes the culture and work experience to be more "chill" and focused on the best solutions instead of political posturing.
We work using cutting edge technologies (MCMC, mechanistic crop modeling, Scala, HTML5 Canvas) backed by well-principled approaches (Bayesian, Functional Programming, Computer Science theory, real agronomic and plant science theory) applied to a problem that really matters - improving sustainable global agriculture.
We have the freedom, permission and resources to do our work right, without financial or political constraints. I am always the rate limiting factor to delivering for the business, not anything imposed by the organization.
Cons
The team is constantly doubling in size, so there is a moderate background level of ambiguity/uncertainty in structure/roles/responsibilities/planning that takes time and effort to wade through.
Communication and team work is exceptionally higher here than anywhere I've ever worked, but still not enough to avoid some level of inadvertently hurt feelings, lack of perfect synchronization, some duplication of effort, etc.
We are operating on the cutting edge of business model innovation, scientific innovation and software excellence, so it takes real work and moderate frustration to get everyone on the same page and account for the uncertainties and diverse needs and requirements/opportunities of everyone involved.