I bring production AI, security, resilience, enterprise change, and product-building experience to a specific purpose: helping attorneys use AI without surrendering confidentiality, professional judgment, or control of the firm.
In my work with Amazon Web Services, I operate where scale, resilience, recovery, and operational judgment are not abstractions. Each lesson maps directly to the decisions firms now face with AI.
Ran high-performance computing clusters used in the development of Meta’s AI models.
For a law firmI understand what sits beneath an AI product—so I can press vendors on architecture, data movement, access, and the controls behind their promises.
Helped prepare systems for the concentrated New Year’s Eve traffic surge when millions of people send at once.
For a law firmI plan for failure, pressure, and incident response before a new workflow becomes something attorneys and clients depend on.
Designed backup strategy around the question every critical system must answer: what happens when something fails?
For a law firmI treat continuity, recoverability, and control of client information as design requirements—not cleanup after a vendor or system fails.
Built chatbot capability for a customer environment where reliability, clarity, and operational integration matter.
For a law firmI know a chatbot needs boundaries, escalation paths, testing, monitoring, and a clearly accountable human—not merely a polished interface.
Selected engagements from Ken’s work with AWS. Company names identify project experience only and do not imply affiliation or endorsement.
I work with AWS Professional Services on the architecture and operationalization of large-scale AI infrastructure and publish technical guidance for production conversational AI systems.
For your firm:I can trace where client information goes, challenge security and privacy claims, and separate a compelling demonstration from a system the firm can responsibly support.
My career includes leading automation and cloud initiatives at organizations including Salesforce, KAR, Angie’s List, and Interactive Intelligence.
For your firm:I can turn partner priorities into ownership, policy, workflow, training, and measurable adoption across attorneys, paralegals, staff, and outside IT.
I founded ParaLocker after going through a legal case of my own. I was fortunate to work with an excellent attorney who patiently taught me the law behind the dispute. The experience showed me both the intellectual rigor of legal work and the burden of keeping evidence, chronology, and context connected.
For your firm:I do not begin with technology. I begin with the people doing consequential work, the sources they must trust, the information they must protect, and the human judgment the system must support.
I founded DevOps Library and have spent years writing courses, articles, and tools that make difficult technical ideas usable by working professionals.
For your firm:I can give partners, attorneys, paralegals, and staff a common language without flattening the real risks or hiding behind jargon.
Visit DevOps LibraryMBA, EntrepreneurshipIndiana University Kelley School of Business
B.S., InformaticsIndiana University
Security and infrastructureSecurity+, Network+, Microsoft, Puppet, Splunk, CloudBees, and SaltStack credentials
Public technical writingAI architecture, retrieval systems, infrastructure, automation, and software design
I was fortunate to work with a fantastic lawyer who was patient enough to help me understand the law governing my own case. Watching him turn facts, language, procedure, and judgment into a strategy gave me a lasting respect for the work—and showed me the practical burden attorneys and paralegals carry behind every matter. That experience led me to create ParaLocker.
As a technologist, law feels familiar: it is a system of rules expressed through language, where definitions, exceptions, evidence, and edge cases can change the outcome. But it also demands patience and human judgment that software cannot replace.
That combination is why I care about legal work. It is also why I want firms to use AI carefully: to strengthen the people doing the reasoning, not weaken the standards their clients rely on.