“Carl was the Head of Engineering at Lucerna and managed me for my entire time there, from intern to senior engineer. He played a big part in getting my career where it is today. He's technically excellent and stays current in a way most engineering leaders stop doing once they move up. He was deep in the architecture, in the code, and in the hard technical calls, not just running the org from above. He had us experimenting with AI tools well before everyone else figured out they mattered. But the technical stuff isn't even what stands out most about him. Carl genuinely cares about his engineers, about the culture of the team, and about all the intangibles that quietly decide whether a group of people does great work or just gets by. As a mentor he pushed me, gave me opportunities above my experience level, and then backed me while I figured them out. That kind of investment in someone is hard to come by. Any engineer would be lucky to work for Carl.”
About
Engineering leader with 6 years building a healthcare data platform from zero to…
Experience
-
HaloCare Health Tech
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Volunteer Experience
-
-
Teacher
TEALSK12
- 1 year 11 months
Education
Taught Computer Science to a high school class in El Paso, Texas as part of Microsoft's TEALS program.
Honors & Awards
-
Outstanding Leadership Achievement Award
Cerner Engineering
Official recognition by the engineering division of Cerner for excellent leadership of his agile software team. His team delivered numerous major product enhancements to clients quickly, both new features and critical bug fixes.
-
Bravo for Open Source Compliance Activities
Motorola Software Pedigree Review Board
Demonstrated exceptional initiative and strong, positive contributions to the compliance management activities of the Software Pedigree teams, the group involved in ensuring Motorola products act responsibly and legally with respond to open source and proprietary software licensing.
Recommendations received
3 people have recommended Carl
Join now to viewOther similar profiles
Explore more posts
-
Preeti Krishnan
On the heels of Thanksgiving, here's week 2 of learnings around building product for clinical teams. WEEK 2: TASKS ARE UNIVERSALLY REVILED, WORKFLOWS DON'T HAVE TO BE One of the biggest misconceptions in healthcare software is that workflows are the problem. Most products start by solving a narrow workflow: prior auth, documentation, referral management. The pitch is always the same: "We'll nail this one thing, then expand into adjacent workflows." This sounds great in theory. It works in lots of other areas of SaaS! But clinicians aren’t software engineers. What we've learned is that clinical teams feel pain most acutely in the TASKS that span workflows. Across specialties, org sizes, and roles, the same handful of tasks trigger frustration every single day: • Searching through an EHR for information that should be easy to find • Copying-and-pasting patient data between systems • Re-entering the same insurance details in 3–5 different places • Uploading, downloading, renaming, or reconciling the same documents • Jumping between tabs, faxes, portals, and PDFs to complete one "simple" action These tasks show up everywhere: prior auth, insurance verification, scheduling, handoffs, charting, follow-ups, portal management. When I talk to clinical teams, I rarely hear: "I wish my prior auth tool were better." I hear (a lot): "I spend half my day doing the same five things across fifteen different systems. It's tedious and frustrating." At Leela, Frank Kim and I have learned that there is enormous pain (and thus enormous opportunity) in solving these real, day-to-day challenges. From our perspective, the best way to do so is by: • Observing how clinicians actually work across systems (understanding the realities and nuances of their work) • Identifying the atomic tasks that create friction (abstracting away this responsibility from the clinicians themselves) • Providing relief by automating or removing those tasks entirely (executing on the things that frustrate teams the most) When annoying tasks disappear, workflows become smooth and tolerable. This is not because the workflows themselves are redesigned (doing so causes a lot of internal friction and change management), but rather, because the most painful parts inside of each workflow are gone. Up next: The Best Product Specs Live Inside Your Users’ Heads
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content