> Markdown version of [/jobs/ext/4444617-senior-technical-lead-ai-product-engineering-cmh-health](https://www.wearedevelopers.com/jobs/ext/4444617-senior-technical-lead-ai-product-engineering-cmh-health). 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). --- # Senior Technical Lead - AI Product Engineering (CMH Health) - **Company:** Milliman, Inc. - **Location:** Chicago, IL, United States (Remote available) - **Experience:** Expert - **Salary:** $131,600.0 - $249,780.0 - **Contract:** Permanent contract - **Skills:** AI Evaluation, Application Programming Interfaces (APIs), Artificial Intelligence, Automation of Tests, Microsoft Azure, Health Informatics, Cloud Computing, Code Review, Continuous Integration, Data Integrity, Software Debugging, Software Product Management, Software Engineering, SQL Databases, Systems Integration, Infrastructure Automation Frameworks, Information Technology, Data Pipelines, Databricks - **Published:** October 31, 2026 - **Apply:** https://diversityjobs.com/career/18802171/Senior-Technical-Lead-Ai-Product-Engineering-Cmh-Health-Illinois-Chicago ## About the Role * Bachelor's degree in Computer science, Engineering, or a related field. * At least six years of relevant experience in software engineering, data-intensive systems, platform engineering, or closely related work. * At least two years in a technical lead, staff engineer, or similar role, including technical direction, delivery ownership, and developing others. * Strong production-software engineering skills, with the ability to inspect, debug, and improve implementations-not just describe proposed solutions. * Experience designing and operating cloud-based systems on Azure or a comparable platform, including deployment, identity and access, observability, and operational reliability. * Strong understanding of SQL, data modeling, APIs, and cross-system integration. * Demonstrated judgment about testing, data integrity, security boundaries, failure modes, and the evidence needed before releasing a change. * Practical experience using AI-assisted development tools, with a disciplined approach to validating their output. * Evidence of leading substantial technical work through delivery while managing dependencies, scope, and stakeholder expectations. * Clear written and verbal communication, constructive technical pushback, and a record of helping other engineers become more capable. * Curiosity about the business behind the software and a willingness to learn complex healthcare and actuarial workflows., * Azure services, infrastructure as code, CI/CD, or Databricks. * Healthcare analytics, claims data, actuarial systems, or another regulated, data-intensive domain. * Production AI-enabled workflows with evaluation datasets, traceability, and appropriate human review. * Modernizing established applications and data pipelines without disrupting users. * Reducing recurring support effort, release friction, or cloud operating costs through measurable improvements., It is preferred that candidates work on-site at our Chicago, IL, Milwaukee, WI, or Hartford, CT office. Remote candidates will be considered. ## Description Milliman's CMH Health practice is hiring a Senior Technical Lead to own the technical direction of our AI-enabled healthcare products. You will turn complex actuarial and business workflows into reliable software, and help other engineers do the same. You will be accountable for the technical outcome of your assigned products and workstreams. That includes the work of the engineers who build them with you. You will set the architecture, decide how work is broken down and verified, review designs and code, and answer for whether what ships is correct, reliable, and on time. You lead through technical authority: you make the calls in your area, and you develop the engineers around you so they can own more of it. This is a hands-on engineering role. You will read code, investigate production issues, and build critical components yourself., * Lead pragmatic architecture and integration. Design service boundaries, APIs, data models, and integrations that balance reliability, security, performance, cost, and maintainability. Explain the tradeoffs and choose the simplest approach that meets the need. * Turn business needs into executable technical plans. Work with product owners and domain experts to clarify requirements, identify dependencies, and sequence small, testable increments. Own technical delivery commitments and raise scope, budget, or timing risks early. * Build verification into delivery. Strengthen automated tests, data-quality controls, regression checks, and AI evaluation practices. Ensure evidence demonstrates that the complete workflow works-not just that individual components run. * Improve production readiness and operability. Establish practical deployment, monitoring, rollback, and support practices. Investigate recurring failures and reduce manual intervention through targeted engineering improvements. * Make AI-assisted engineering effective and accountable. Guide the use of coding agents and other AI tools, including context management, generated-code review, evaluation, and appropriate human oversight. Measure improvements in complete delivery outcomes rather than code volume. * Create reusable engineering capabilities. Improve shared patterns and tooling where they solve demonstrated needs. Help teams adopt them without introducing unnecessary abstraction or approval bottlenecks. * Develop independent engineers. Delegate meaningful ownership, review designs and implementations, provide timely feedback, and coach others through difficult technical decisions. * Connect engineering decisions to user outcomes. Stay close to consultants and users, support rollout and adoption, and explain technical risks clearly. Partner with the appropriate domain and control authorities to meet our quality and risk management requirements., During your first six months, you will establish priorities and baselines with the team, then demonstrate progress through: * Your area has one clear technical owner. Partners know who to go to, and they get a straight answer. * A meaningful system or workflow improvement delivered into use, with clear acceptance evidence and operational ownership. * Stronger, reusable verification and release practices adopted within your assigned scope. * Fewer recurring technical blockers or avoidable manual interventions. * Engineers making better decisions and owning larger outcomes with less dependence on senior escalation. * Product and domain partners who understand the technical tradeoffs and trust the team's commitments. The Team * Builder to owner. Everyone on the team uses AI to build fast, and senior leaders own client outcomes and commercial results. * Forward-deployed. Our engineers and product owners work inside real client and consulting workflows, not in a software silo. * Think big, prioritize, execute, earn trust. We value bold ideas sequenced for compounding impact, delivered reliably, and backed by sound trade-offs. * Quality is non-negotiable. Milliman's name is on everything we ship. How This Role May Evolve AI is changing how software is built. We expect it to change what a technical lead spends time on, but we do not know exactly how far or how fast that will go. Today, this role is hands-on. As AI takes on more of the implementation work, we expect the most valuable part of the role may shift toward product leadership: deciding what our products should do and why, working closely with our actuaries and clients to understand their work, and owning the outcome. That is also how many leaders at Milliman grow: by taking on more responsibility for client problems and the solutions to them. We are describing a direction, not a commitment. We cannot promise a particular title, timeline, or path. The role will be shaped by how the technology develops, what our clients need, and your strengths and interests. If you find that kind of change interesting rather than unsettling, we would like to talk.