iRacing.com Reviews

Leadership operates in organized chaos. Priorities shift frequently and can feel like they're driven by whoever upstairs got frustrated with a specific part of the product that week rather than a clear strategic roadmap. Business goals tend to stay vague - "grow the business" rather than specific measurable outcomes - which makes it genuinely hard as an IC to know if the work you're doing is moving the needle. Over-promising is baked into the culture. Projects get announced publicly as if they're around the corner, then take years to ship - or get shelved entirely when something shinier comes along. The community has memes about features "Coming Soon™" and so does the internal team. It stems from consistent underestimation of scope and tech debt, and a PM culture that sets tight deadlines to "create urgency" then quietly slips 6-18 months. If you're self-directed, patient, and okay with ambiguity this can still be a rewarding place to build - but if you need clear direction and predictable roadmaps, look elsewhere. Onboarding is sink or swim. There's minimal documentation and not much structured ramp-up. If you're not comfortable asking a lot of questions and piecing things together yourself you'll struggle.

Some teams could benefit from stronger support structures and clearer communication practices. In certain areas, issues raised by team members don’t always receive the level of follow‑through or coordination needed, which can be challenging in a remote‑first environment. When communication gaps appear, it can affect trust and make collaboration feel more fragmented than it should be. This may vary across different groups and projects, and the experience is not necessarily uniform throughout the studio.