> Markdown version of [/jobs/ext/4324075-ai-engineer](https://www.wearedevelopers.com/jobs/ext/4324075-ai-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # AI Engineer - **Company:** Certified Collateral Corporation - **Location:** Chicago, IL, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** LangGraph Framework, A/B Testing, Artificial Intelligence, Amazon Web Services, Microsoft Azure, Command-Line Interface, Continuous Integration, Cursor, Software Design Documents, Graph Database, Python (Programming Language), PostgreSQL, MongoDB, Neo4j, Search Technologies, Software Engineering, Data Streaming, Strategies of Testing, TypeScript, Microsoft Agent Framework, GitHub Copilot, ReactJS, Large Language Models, Claude Code, Agentic-AI, LangSmith, PydanticAI Framework, Model Context Protocol, Microservices, Agent2Agent Protocol - **Published:** October 31, 2026 - **Apply:** https://www.themuse.com/jobs/cccintelligentsolutions/senior-ai-engineer-0c7662 ## About the Role * 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 output, from daily use of Claude Code, Cursor, GitHub Copilot, or similar on production work, plus changes you turned back, and why. * Pipelines you designed that blend LLMs, semantic search, and classical NLP, including a retrieval design you can defend and a case where a classical technique beat an LLM on cost, latency, or reliability. * Durable, event-driven systems you designed with deterministic orchestration around non-deterministic model steps: compensating actions, idempotency, backpressure, and event-sourced replay. * Data modeling and development across relational, document, and graph databases such as PostgreSQL, MongoDB, and Neo4j, including when each type fits and the partition-key, consistency, and tenant-isolation calls you made. * Systems architected and operated on Azure or AWS, with CI/CD and infrastructure as code, and hands-on time with a durable workflow engine such as Temporal or the Durable Task Scheduler. * Technical design documents you have authored for systems that span more than one team, used to get feedback and buy-in before building, and that those teams then built to. * Clear writing and discussion for technical and non-technical audiences: drawing out a customer's real problem and explaining the trade-offs back to them. Even Better if You Have: * React and TypeScript experience, so you can deliver a full-stack feature end to end, especially chat, streaming, and citation-heavy AI experiences. * Experience with agent frameworks, LangGraph, PydanticAI, and the Microsoft Agent Framework among them, and with the ways agents reach their tools: the Model Context Protocol (MCP), the Agent2Agent (A2A) protocol, command-line tools, and microservices. * Experience with LLM observability and evaluation tooling such as LangSmith, Arize, or Braintrust, and with OpenTelemetry-based tracing. * Experience designing A/B tests for AI features. * Exposure to the insurance, claims, or automotive repair domains. ## Description * 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.