Pros
REA Group is a good place to work if you want exposure to large-scale product engineering and modern technology practices. The products are widely used, and the work can feel meaningful because it impacts a large customer base in the Australian property market. One of the biggest positives was the quality of many engineers and tech leads. I worked with some extremely knowledgeable, pragmatic, and supportive tech leads who were among the best people I have worked with. Their technical judgement, ownership, and willingness to support others made a big difference. There were also strong engineering practices in many areas, including code quality, observability, reliability, and long-term maintainability. Engineers often had opportunities to own meaningful work across backend systems, APIs, search, data pipelines, customer-facing features, and platform improvements. The people culture was generally positive. Many colleagues were helpful, approachable, and genuinely invested in doing good work. The flexible working environment was also a major benefit.
Cons
Leadership quality was inconsistent across teams. While some managers and leaders were excellent, others lacked the technical judgement, communication skills, people leadership, or clarity needed to help teams operate at their best. In some areas, decision-making felt disconnected from the realities of day-to-day engineering work. This sometimes led to unclear direction, slow execution, unnecessary process, and avoidable friction for engineers trying to deliver good outcomes. There also seemed to be a lacklustre level of support for strong technical engineers. Investment in engineering excellence, both monetarily and culturally, did not always feel aligned with the calibre of talent the company expected to attract and retain. Over time, this could risk weakening what was once considered a great engineering environment. Product and design quality could also be inconsistent. Some product designers and product stakeholders added real value, but in other cases the work felt more process-heavy than outcome-focused. At times, design decisions appeared disconnected from customer needs, technical constraints, or measurable business impact, which made collaboration harder than it needed to be. Like many larger product companies, priorities could shift frequently, and multiple layers of alignment could slow down delivery. Cross-team dependencies were sometimes harder than they needed to be, and teams occasionally had to balance delivery pressure with technical debt and platform constraints. Career progression could also feel dependent on visibility, timing, and organisational needs rather than only on individual performance and impact. Overall, REA had some excellent people, especially at the tech lead level, and I learned a lot during my time there. The biggest challenge was the inconsistency in management, product, design, and engineering leadership quality across different teams, along with reduced support and investment in retaining strong technical engineers.