Kartik Patel
I came up through public safety systems - 911 dispatch, criminal justice records, and the mobile terminals officers use in patrol cars - before moving into public safety SaaS and, most recently, insurance claims platforms. Today I lead cloud modernization and AI-enabled engineering work across .NET, AWS, EKS, and internal developer tooling.
in regulated, mission-critical software
led across four squads in current role
a customer base served by public-safety product lines I helped modernize and support
across two programs: GovCloud planning and deep dives with AWS ProServ; current EKS migration
production support for 911 and law enforcement systems
Engineering Work I Have Led
A compact view of the work behind the resume.
Multi-year program to rewrite CAD, RMS, and MCT applications used by 911 centers and police agencies. Customers depended on the existing products in production, so the challenge was shipping the rewrite without disrupting agencies in the field.
I led teams on the early planning and deep-dive phase of a public safety suite moving to AWS GovCloud, partnering with AWS ProServ. I moved to a different company before that migration completed. Today I am leading an on-prem-to-EKS migration of a .NET platform at my current employer.
Led a cross-functional group across Dev, QA, and IT to containerize the application stack. The hard part was getting three groups with different incentives and on-call models to agree on what deployable meant.
Years of 24/7 on-call for public safety applications where downtime affects officer safety. The lasting takeaway: many reliability problems are operating-model problems - ownership, triage flow, and feedback loops back into engineering.
Now
I am building an internal AI developer platform for my engineering org. It pulls from Confluence, Azure DevOps, GitHub, and internal databases so engineers can ask grounded questions about our codebase and runbooks. The real test is whether engineers use it twice.
Currently leading an EKS migration of a .NET platform from on-prem to AWS. Earlier in my career I led teams on the early phase of moving a public safety suite to AWS GovCloud and the Docker containerization of that same suite.
I came up through production support for 911 and criminal justice systems. Most of what I do as a manager now - ownership boundaries, on-call rotations, triage processes, escalation paths - traces back to that environment.
Projects
The rewrite of a public safety suite from FoxPro to .NET while agencies depended on the existing products in production.
Hiring signal: Modernization experience in systems where customer cutover, dual operations, and domain knowledge mattered as much as code.
A sequencing playbook for legacy .NET modernization into AWS and Kubernetes, drawn from early GovCloud planning and a current EKS migration.
Hiring signal: Modernization judgment that balances platform ambition with delivery continuity and operational risk.
Running an internal AI developer platform that connects Confluence, Azure DevOps, GitHub, and internal databases.
Hiring signal: AI adoption treated as workflow redesign, not a tool rollout.
A side project exploring document workflows beyond chat-with-PDF: classification, extraction, citations, mismatch detection, and spreadsheet Q&A.
Hiring signal: Hands-on AI product thinking across documents, data, citations, and workflow design.
Writing
Years of on-call for 911 and law enforcement systems shaped how I think about runbooks, automation, dashboards, synthetic transactions, and the hero anti-pattern.
Read noteWhat document AI looks like when it stops being chat-with-PDF and starts being workflow.
Read noteA modernization playbook drawn from early GovCloud planning with AWS ProServ and a current on-prem-to-EKS migration.
Read noteA working note from a current internal AI developer platform rollout: what not to measure, what to measure, and where trust breaks.
Read noteNotes from the work