CCC Intelligent Solutions Inc. (CCC) is a leading cloud platform for the multi-trillion-dollar insurance economy, creating intelligent experiences for insurers, repairers, automakers, part suppliers, and more. At CCC, we’re making life just work by empowering more than 35,000 businesses with industry-leading technology to get drivers back on the road and to health quickly and seamlessly. We’re pushing boundaries with innovative AI solutions that simplify and enhance the claims and repair journey. Through purposeful innovation and the strength of its connections, CCC technologies empower the people and industry relied upon to keep lives moving forward when it matters most. Learn more about CCC at www.cccis.com.

The Role

CCC Intelligent Solutions Inc. (CCC) is a leading cloud platform for the multi-trillion-dollar insurance economy, creating intelligent experiences for insurers, repairers, automakers, part suppliers, and more. At CCC, we’re making life just work by empowering more than 35,000 businesses with industry-leading technology to get drivers back on the road and to health quickly and seamlessly. We’re pushing boundaries with innovative AI solutions that simplify and enhance the claims and repair journey. Through purposeful innovation and the strength of its connections, CCC technologies empower the people and industry relied upon to keep lives moving forward when it matters most. Learn more about CCC at www.cccis.com.

The Role:
You will own LLM-powered systems and agentic workflows for our customers. These systems automate the routine parts of a claim and guide customers on the rest, so they have to earn that trust with a measured accuracy you can defend as models change and usage grows. Agents run as steps inside deterministic workflows, and privacy and security are design baselines, not review gates. Agentic coding tools are how you move fast. What you add is what they are worst at: system architecture, code quality, security, and the debugging nobody else gets to the bottom of. You own a product area end to end and define the eval bar it ships against.

Key Responsibilities:

• Own the delivery of LLM-powered systems in Python and TypeScript, from an ambiguous customer problem, scoped with product managers and data scientists, through production operation.

• Set the evals and guardrails strategy for your area: what gates a release, what production signals the team watches, and how a change is simulated against historical claims before it ships.

• Raise the bar for how the team works with agentic coding tools: sharpen the specifications, instruction files, hooks, and permission policies they run under, and hold generated code to the same review standard before it merges.

• Design the NLP pipelines that turn unstructured claim data into structured data customers can act on, choosing where semantic search, classical NLP, or an LLM fits.

• Build and operate durable, event-driven, multi-tenant systems in which agents run as steps inside deterministic workflows, designing their failure modes, replay semantics, and cost profile before they show up under load.

• Own tracing and audit for your area: every model call and agent step recorded, so any recommendation can be reconstructed and cited back to its sources by on-call and auditors alike.

• Set the privacy and security baseline every system in your area starts from: tenant isolation, least-privilege access for agents and their tools, redaction, retention, and what data may reach a model provider.

• Author the design documents for complex systems to get feedback and buy-in, review other engineers’ designs and code with the same care, and mentor the engineers in your area.

• Take part in a shared on-call rotation for the systems you own.

Requirements:

• 6+ years of professional software engineering experience, including an LLM-powered system you architected, shipped to external customers, and carried through at least one model or prompt migration.

• Python and TypeScript at the level of setting a team’s conventions: the async model, typing strictness, and test strategy for a shared codebase, plus a performance problem you profiled and fixed.

• An evals and guardrails strategy you set for a product area others built in: where human approval was required, and how production corrections re-entered the evals.

• A clear account of how you constrain an agentic coding tool’s context and verify its o…