Pros
I've been working at Fluidly as a Senior Software Engineer and Tech Lead for 9 months. The CEO/CTO have created an energetic, productive culture in engineering where people are responsible for delivering business goals instead of just code/features We have a very lean approach to software development and are always looking to reduce waste, the amount of which always annoyed me at other companies We don't have any staging environments - each merged PR goes straight to production. This has actually increased stability by putting the onus of responsibility directly onto individual developers to practice TDD, pair programming, good architectural practices and have high coding standards (14 engineers typically release 40 times a day) The team is nice, smart and friendly - not only do most of us eat lunch together every day, but we are often social outside of work, be it going to the pub, karaoke, or playing board games. I enjoy working with everyone on the team We try to maintain a blame-free culture at all times, so that when mistakes are made we own them and deal with them as a team
Cons
In many ways Fluidly is still early stage, but growing fast and this means change is the only constant. It can sometimes be difficult to adjust to the chaos of constantly shifting priorities We've had to scale out the architecture very quickly, so things are messy and many details are in various people's heads. We'll need good people to work hard at making sure this doesn't slow us down as we grow Everyone is expected to deliver and there is no absence of pressure to do so (not so negative for me, but some may not like such high expectations) Because this is a new product in a new space (intelligent cashflow) the product team are in uncharted waters and are still figuring out their approach, which means engineering has to work closely with them to define everything. No spoon feeding of requirements here!