Risk Engineer - Risk Engineer Coalition Employee Review

Good and no issues as long as you are happy

Good nothing much but can be improved

Strong product and mission. The product is good, the space is interesting, and it generally feels like the company is trying to do something real for customers. Company-wide culture is mostly positive. Outside of CS, many people seem to have a better experience with leadership and culture; most cross-functional partners I worked with were thoughtful and values-aligned. Good coworkers in CS. Day-to-day peers in Customer Success care about brokers and about doing quality work, even when the structure around them is messy. Flexible and remote-friendly. If you’re comfortable managing your own time, the setup works.

CS is often in rebuild mode. The org structure and priorities change a lot, and communication doesn’t always keep up, so it can feel chaotic. Leadership consistency is mixed. Some leaders are great; others are less consistent with expectations and follow-through. Persistent underperformance or poor behavior can drag on for a long time with little visible action, and when something finally happens, it’s rarely explained. High performers can end up carrying extra load. Heavy focus on solves and volume. There is constant pressure to hit ticket and solve targets, which can be exhausting when combined with all the change. It’s easy to feel like a number. Limited follow-through on improvements. People surface ideas and problems, but efforts to fix how things run often stall or get constrained by disorganized or shifting leadership priorities. Metrics and processes aren’t used the same way everywhere. Tools, dashboards, and QA exist, but not all teams use them consistently, which can make expectations and accountability feel uneven. These are patterns in part of CS leadership and structure, not every manager or team lead—there are definitely bright spots.