Pros
I enjoyed being able to give a technical presentation on a topic of my choice for the interview. Expedition emphasizes communication skills as well as technical knowledge which I find refreshing. The executive team also gives regular, detailed briefings on the financial prospects and overall status of the company which I appreciate. Management does a good job of scheduling technical briefings to give a project or team the opportunity to share their progress and challenges with the rest of the company. The work here is challenging and there are a variety of projects to work on. There are lots of opportunities to work with modern technologies and tools such as TensorFlow, AWS, Python 3, and Docker. Engineers are trusted to be creative, explore different solutions, and take ownership of new efforts. I also like that there is a focus on the technical work and the project management activities to support that work without a lot of extra process or meetings. As a small but growing company, there is a lot of room for personal growth since most projects have small teams where each person has multiple roles. My co-workers here are fun, friendly, and smart. I see myself being at Expedition for a long time! I also appreciate that Expedition encourages continual learning, whether it's through education, conferences, journal club presentations, or employees being motivated to give a lunch time presentation on something that interests them. The benefits are great and I feel that management puts a lot of effort into making sure employees are happy. There's also fun events sponsored by the company every quarter and an interesting assortment of bagels every Friday!
Cons
The company is growing quickly and the old structure of the company is changing. I don't think this by itself is a bad thing, but it will certainly come with some learning and pain as the company grows. Since the teams are small right now, you usually end up working with 1-3 people for a given project which might not be ideal for everyone. There are larger projects on the horizon, so I think this will be changing. A lot of projects are also just starting to move out of the research/prototyping phase, so there's not a lot of the traditional infrastructure/tools/processes that you might see for larger, more established software projects. This does create opportunities for defining and implementing these things, but that may not be for everyone.