Pros: Things move fast, and you're constantly working on new things and making impactful decisions. You own what you do and have a broad range of permissions and scope to manage your work. Colleagues across the whole company are friendly and easy to work with. I've noticed many belligerent or overly aggressive people move along to opportunities at a different company. Code quality is very high, and you get the sense that you're working with very capable and experienced engineers on state-of-the-art systems.

Cons: There is a lot of tech debt and reluctance to improve the codebase. My team doesn't have the headcount to manage what's requested of us, and the state of the product is affected. I can only speak for my team in this regard, however, as mentioned, I feel that the wider state of the software is excellent.

Pros: Cool office space. Many people I've met were very nice, knowledgeable, and humble. No one tells you how to do things, as long as you get things done (this also proved to be one of their issues).

Cons: - Arrogant management. - Probation period goals are poorly defined and most of the times not measurable. - Lack of support or direction during your probation period. You'll have to constantly chase your line manager to give you feedback, and luckily they won't be too busy. - No one will tell you whether you passed the probation period or not, even though they are supposed to give you written confirmation. - Blame culture. Instead of focusing on solutions, fixing problems, or educating people, some senior engineers/managers prefer to just make fun of other people's lack of skills or point fingers. - People are treated as disposable and will be let go during their probation period for no reason. With luck, they will tell you, "You're not a good fit for the company." - They tell you that no one forces you to work long hours, but the tasks they give you during your probation force you to work many extra hours and during the weekend. - Job specs advertised are completely different from the actual work you'll do (given the speed at which the company is growing, you'll end up doing really crappy work that other people who've been longer in the company don't want to do).

Pros: - Good compensation and benefits. - Full lifecycle exposure: Engineers are involved in everything from requirements to implementation, fostering well-rounded skills. - Efficient hiring and onboarding: The process was streamlined and smooth. - Remote flexibility: Fully remote setup offers good work-life balance. - No on-call responsibilities: The systems are designed in a way that engineers don’t need to handle on-call duties, which is excellent for work-life balance. - Supportive management: While I’ve seen reviews about overworking, I believe it depends on the team and individual. For instance, we had an ambitious quarterly KPI for the team, but when communicated early about challenges, the manager and tech lead were understanding, and nobody asked anyone to do any overtime.

Cons: - Unclear reporting structure: The dual reporting to a line and functional manager can be confusing, especially when some engineers report to product managers, which is unconventional. - Knowledge sharing through peers: Most knowledge sharing is done through peers; there’s little focus on having internal tech talks or blog posts to share learnings. - Documentation gaps: Internal tools and frameworks lack proper documentation, which is critical in a remote company. - Communication issues: Communication practices could improve, such as avoiding unnecessary mentions or DMs for topics that could be public. - Workforce and culture: The culture is mostly focused on delivering results, which can sometimes feel bland. Additionally, the workforce could be more diverse.