Pros
The mission is real and it resonates. Cortex sits at the intersection of engineering operations and developer experience at a moment when the industry is finally catching up to why that matters. If you've spent time in orgs where engineering velocity degraded silently; sprawl, no ownership clarity, no production readiness standards, no visibility into DORA; you understand immediately why this product exists and why it wins when it's positioned correctly. That context makes the work feel meaningful, not manufactured.
The culture is genuinely collaborative. Cross-functional alignment here isn't a talking point. Product, engineering, and CX are actively in the same channels, sharing feedback, tagging each other, running bug bashes together, and course-correcting in real time. When a new entity relationship UX shipped, the internal excitement was authentic. That's not theater; that's operational maturity. The "no ego" value shows up in practice. I've seen leadership take direct feedback, adjust course, and do it without making the person who flagged it feel exposed.
The product is shipping. Cortex Academy, the integration platform, 30+ native Workflow blocks, MCP support, incident.io core types, Entra ID SCIM; meaningful releases are landing consistently. As someone customer-facing, that gives you real ammunition in QBRs and renewals. You're not defending a roadmap: you're delivering against one.
The people are smart and genuinely care about outcomes. The CX team in particular punches above its weight, and the collaboration across CS, CE, and product is the best I've seen at a company this size.
Cons
Startup ambiguity is a feature and a bug. If you need clearly defined lanes and predictable process, this stage will test you. If you thrive in "write the rules" environments, it's energizing; but be honest with yourself about which person you are before you sign.