Pros
The engineering culture is built on async and remote-first principles, as well as a high regard for code quality, which I greatly appreciate. The team does a good job navigating the waters between ideal engineering pragmatic business needs. The company has a good culture of CI testing, and the codebase is fairly clean and manageable -- built on AWS with python and react.
There is an authentic concern for the needs and goals of the individuals who works here, as well as a strong drive to do right by our customers. The concern for people and an inclination for long term thinking comes from the top, and it is refreshing.
And although practical concerns do sometimes require immediate responses, the overall flexibility of the working hours and the tightness of the team despite the remoteness cannot be understated.
Cons
The team is small, and as exciting it is to punch above our weight class it means that a lot of time and energy needs to go into work that is needed but not necessarily our primary skillset or our product's main focus, such as spending time tackling regulatory compliance as an engineer, or ensuring that elastic search is properly monitored as a frontend engineer. On the plus side, there's a ton of opportunity for a motivated learner to tackle new challenges, and good support from the rest of the team for when people do go beyond their comfort zone.
Another challenge is that working with large and often bureaucratic clients can be an exercise in patience and perseverance. A lot can hinge on bigger deals, so there can be periods of pressure associated with closing those deals.