Pros: - Fair, location-agnostic pay – Salaries are not reduced based on where you live, which is rare and commendable. - Fantastic company culture – Supportive, transparent, and people-first. - Remote work done right – Async-first philosophy, excellent tooling, and a genuine trust in employees to manage their time and work.

Cons: - Role mismatch in practice – Many engineering positions, even those advertised as front-end, involve a significant amount of WordPress/PHP backend work. This can be frustrating if your expertise lies elsewhere. - Varied experience depending on team – The decentralized, team-autonomous culture is great for flexibility, but it also means your work experience can differ widely depending on your team lead and product team. - Constant skill misalignment challenges – If you’re not a PHP/WordPress backend specialist, it can be difficult to reach the comfort level that comes with working primarily in your core expertise. In my case, I was hired as a front-end engineer but rarely did front-end tasks, which meant I was frequently tackling unfamiliar backend/DevOps challenges. This often made backend specialists appear more productive, even if the actual effort required was higher on my side.

Pros: The company culture is very friendly, but with strong issues to provide visibility about performance.

Cons: The processes not related to writing code are still in development, with no well-defined approach.

Pros: A real remote job with async communication.

Cons: I used to love this job, but in the past few months, everything has been falling apart. There’s constant confusion. Leadership changes direction every few days, and no one takes responsibility; it always ends up on the ICs. Collaboration with design and product teams is also completely broken.