Pros: Over my career at Revolut, the company has consistently provided opportunities for both technical and managerial growth. I’ve had the chance to collaborate with many high-performing individuals ("A players") on a variety of challenging and impactful projects, which makes the company a good place to get experience and grow.

Cons: Revolut’s focus on retaining only top performers creates a highly competitive work environment. It's sometimes hard to match high expectations, which makes Revolut a stressful place to work. A strong "can-do" attitude is essential for both career progression and recognition within the company. Recognition tends to remain within a few organizational layers above the individual contributor and rarely reaches the broader senior leadership. Although some initiatives have been introduced to improve this, they haven't fully addressed the gap. Compensation practices can be inconsistent across regions. Employees in smaller countries often face delays in salary benchmark reviews due to limited data, resulting in significant differences in pay across locations.

Pros: You get to touch and configure all layers of infrastructure. High standards on deliverables. Live product with high load specific challenges. Good compensation.

Cons: If we are talking about the Retail app (where I work), don't go there if you are looking for a chill <8h per day work. You really need to show results and, the majority of the time, you actually need to work. Overtimes can happen, and management won't stop you from doing so, but I've never seen someone being forced to overtime. So, the level of stress here is higher than in places where I've worked before.

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.