Pros
Having followed the educational technology industry for many years, I can confidently say that Minerva is one of the few companies that deeply care about improving student learning - on the one hand boldly believing that they can do far better than even elite universities currently do, on the other hand being humble enough to realise that we have much to learn and that success comes from strong first principles, and then an ongoing process of continuous improvement. I have been very impressed by how closely engineers and product managers work with curriculum developers and students to create more engaging experiences. The engineering team is very diverse, highly remote-friendly, and consists of people who are both technically very strong, but also all motivated by the mission of Minerva. We work very closely with faculty, students and partners, and are able to have a lot of input into feature design, technical approaches and execution. Product team is only about 25 people, so nobody is "just a number", everyone have their unique skills and approaches to contribute, and my manager has been very supportive in thinking about how to grow and develop, not just as an engineer. Communication in the whole organization (almost 180 people at this time) is very fluid and open, and we often get to interact with faculty teams, but also student experience, strategic partnerships etc.
Cons
There is a fair amount of technical debt, and a lot of the stack is based on old technology (Backbone, Django DRF), although that is slowly changing. We are very proactive about testing, but engineers often have to jump in and help with escalated issues - while it's good to see firsthand the pain points of customers, I hope we can get to a point where we will feel more confident in the code. Part of the reason, apart from the old code, is that we're currently expanding from our main partner (Minerva Schools) to a number of new partners, each requiring a fair amount of customization etc as we work on "crossing the chasm".