Key Skills
Health Policy
Analyzing health systems through an economic lens to evaluate policy effectiveness, resource allocation, and market dynamics. Applying health economics principles to assess cost-effectiveness, understand incentive structures, and develop evidence-based recommendations that balance fiscal sustainability with improved health outcomes.
Data Analysis
Transforming complex datasets into actionable insights using statistical methods, data visualization, and advanced analytics. Proficient in exploratory data analysis, predictive modeling, and building automated reporting solutions that support data-driven decision-making across healthcare and policy domains.
IT Strategy
Architecting enterprise-wide data strategies and frameworks aligned with industry best practices, including loosely coupled architectures, domain-driven design principles, and event-driven integration patterns to ensure scalability, maintainability, and organizational agility.
Cloud Computing
Developing cloud-native data architectures which scale effectively to deliver services at a lower cost while leveraging modern infrastructure patterns, automated provisioning, and optimized resource allocation to maximize efficiency and minimize operational overhead.
Team Management
Leading and developing cross-functional teams of engineers and analysts in Agile environments. Building high-performing engineering teams using Scrum and Kanban methodologies while fostering collaboration and continuous improvement.
Languages & Tools
My aspiration to work in healthcare began early in college, when I decided that I was going to become a doctor (specifically, I wanted to be a neurologist). This led to the predictable pre-med requirements, along with the unorthodox effort to get my Emergency Medicine Tech (EMT) certification, and a regular volunteer shift in a Level 1 emergency department. I was so eager to begin practicing that I didn't want to wait until medical school to get my hands dirty.
While I enjoyed every minute of hands-on work that I was privileged to get - including assisting a radiology team with a portable scan during a hip surgery – I was constantly shocked by the systems that clinicians dealt with. By my junior year of college, I had no less than five physicians tell me "you don't want to be a doctor." Their reasons were always the same: it's the system, stupid.
My focus shifted to the healthcare system as a whole, and after undergrad I found myself at the Evans School of Public Policy and Governance, where I specialized in the area of health policy. At the first official gathering of my cohort, the Evan's school staff said, "you're all here because you saw something in the world that you didn't like, and you want to change it." No truer words have ever been said. My academic training focused on policy analysis, management, accounting, extensive writing, and a heavy dose of economics (which the Evan's school is known for in the field of public policy).
These skills have served me well, but I had a professor who said, "you can be really good at one thing, but you'll never be the best. If you combine two things you're good at, you might be the best." As I began my career after school, I realized that a childhood of building my own computers (typically out of spare parts) left me far better equipped to tackle technology problems than the average policy analyst.
My first job as a project manager quickly morphed into a data analyst, which turned into a project to develop a data warehouse (which required a bigger team). This eventually led me to bigger data, which required different technology (and even bigger teams).
Today, I am a tech leader in the healthcare space, guiding IT efforts around architecture, data engineering, and the way that we can use data to make better decisions to improve the healthcare system.