Pros
- Small engineering team, so you can work closely with other developers and see the impact of your work quickly. - Exposure to a wide range of responsibilities (backend, front-end, infrastructure/DevOps), which can be good for building a broad skill set. - Fast-moving environment where decisions are made quickly and priorities change often, which some people may find exciting. - Strong focus on mentoring interns, especially from well-known schools.
Cons
- Noticeable turnover across multiple roles (management, design, QA, and infrastructure/DevOps). During my time there, many colleagues in different functions were either let go or left. - Roles and responsibilities changed frequently. I was hired for one area of the stack but was repeatedly moved into very different areas without clear discussion, support, or adjustment of expectations. - Expectations around performance and output were not always clearly communicated. Feedback often arrived only when leadership had already decided someone was underperforming, and decisions to let people go were made quickly with limited opportunity to course-correct. - Decision-making felt concentrated within a small, tight-knit leadership circle with long-standing personal relationships. This could make it difficult for other voices to influence direction or challenge decisions. - The culture did not strongly encourage speaking up or pushing back; many people chose to stay quiet to avoid drawing attention during periods of change or reorganization. - In my experience, compensation did not feel aligned with the breadth of responsibilities and the pace of change expected from engineers. - Heavy focus on recruiting and mentoring interns from well-known schools, which at times felt disconnected from the team’s actual capacity and longer-term product and engineering needs.